ThinkWiki - User contributions [en]

Talk:Problem with unauthorized MiniPCI network card

2006-07-26T14:57:27Z

Supermihi:

== Affected Models ==
I am unsure about which models this applies to. I have seen reports of this problem affecting a T41p, T43, X40, R31, X31, and T30; but I do not know how far back this problem goes or if there are exceptions. If anyone has better information, please clarify/specify the "Affected Models" section. --[[User:Kevinoid|Kevinoid]] 05:44, 14 Dec 2005 (CET)

== Solution on T43? ==
There were several edits to the previous page to the effect that "this didn't work for my T43". Although I do not weight this as highly credible (please just ask for help on the ML rather than adding random comments to pages), I did feel that it deserved a mention that the solution may not work on the T43. If anyone can confirm or deny this statement, please do so (and possibly ask on the ML for solutions if it does not work for you). --[[User:Kevinoid|Kevinoid]] 05:44, 14 Dec 2005 (CET)

== Confirmation - patch not working on T43 ==
I can confirm, that a "nvram/cmos" patch is not working on my T43, exact type 1871-A62. I tried several cards (some working without patch in another thinkpads (t40, t42, x40), but no success.--[[User:Jap|Jap]] 09:50, 13 June 2006 (CEST)

== Hotplugging PCI device ==
I'd like to send out a '''BIG FAT WARNING''' that 'hotplugging' the mini-PCI card can easily lead to frying the system board, mini-PCI bus, or both. Yes, it happened to me... :-( Interrupting the boot process at the lilo boot menu, and then inserting the ipw2915abg card worked as a charm to circumvent the BIOS white list. However, somewhere it must have gone wrong because now the laptop hangs immediately when the IBM/Intel boot logos appear. --[[User:LJSBrokken|LJSBrokken]] 13:01, 20 July 2006 (GMT+1)

== Z60 series ==
I tried this on a Lenovo Z60t. Bought an Intel Wireless card since the linux drivers for the madwifi are crap. I applied the C-Patch from here. Then after booting with the intel device installed I get some weird broadcom PXE boot messages displayed ontop of the key symbol for startup security. Even if I don't put my finger on the sensor, it continues with GRUB. At this point I can't use the keyboard, the key symbol is still displayed in the upper left corner. After a few secons grub starts with its default entry (Gentoo Linux). It all works, but no Wireless Adapter shows up in lspci.

So, I don't have that 1802 error, but still can't use my wifi card. Any ideas?

ThinkPad 11a/b/g Wireless LAN Mini Express Adapter

2006-07-14T21:10:53Z

Supermihi: added a photo of the actual device

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad 11a/b/g Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5006EX
* Integrated Mac Processor and Radio Chip: Atheros 5424
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: ??
</div>
|style="vertical-align:top" |
[[image:Atheros_mini_express_wifi(thumbnail).jpg|Atheros mini-PCIe WiFi Adapter]]
|}

=== IBM Partnumbers ===
IBM Option PN (US): 40Y7026

=== Linux WiFi driver ===
Try the [[Madwifi]] driver.

OR

get the driver from http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52527 and use ndiswrapper

=== ThinkPads this card may be found in ===
* {{T60}}, {{T60p}}
* {{Z60t}}

=== Related Links ===
* [http://www.madwifi.org MadWifi project page]
* [http://madwifi.org/ticket/263 MadWifi ticket #263]

[[Category:Components]]

File:Atheros mini express wifi(thumbnail).jpg

2006-07-14T21:08:09Z

Supermihi: Small version of Image:Atheros_mini_express_wifi.jpg

Small version of [[Image:Atheros_mini_express_wifi.jpg]]

File:Atheros mini express wifi.jpg

2006-07-14T21:04:30Z

Supermihi: This is the Atheros mini pci express wifi adapter that comes with some of the new Thinkpad models (e.g. Z60m/t).

This is the Atheros mini pci express wifi adapter that comes with some of the new Thinkpad models (e.g. Z60m/t).

How to make ACPI work

2006-07-13T11:11:06Z

Supermihi: /* ThinkPads on which it is recommended to use ACPI */

==general==
===Kernel configuration===
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).
To do this open your kernel config and enable ACPI Power Management:
:{{kernelconf|CONFIG_PM|<*>|Power Management support|Power management options|||}}
:{{kernelconf|CONFIG_ACPI_SLEEP|<*>|ACPI|Power management options|||}}

You'd most likely want to enable the following ACPI options:
:{{kernelconf|CONFIG_ACPI_SLEEP|<*>|Sleep States|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_AC|<*>|AC Adapter|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_BATTERY|<*>|Battery|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_FAN|<*>|Fan|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_PROCESSOR|<*>|Processor|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_THERMAL|<*>|Thermal Zone|ACPI|Power management options||}}

If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:
CONFIG_PM=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y

Then recompile your kernel.

{{HINT| ACPI SLEEP States option did only show up for me after patching [[Software Suspend 2]] into the kernel .}}

===Kernel boot parameters===
Many ThinkPads have been hit by a recent (kernel 2.6.16) change to ACPI4Linux that changed the default means of accessing the ACPI Embedded Controller as a way to shake out underlying bugs in the EC access code. If your ThinkPad fails to resume properly (a blinking Sleep light on resume that doesn't go away, or a hang when trying to suspend/standby a second time), adding {{bootparm|ec_intr|0}} to your kernel command line may help.

===IBM specific ACPI driver===
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.

You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.

If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.

{{HINT|Generally it is a good idea to read the README included with the driver.}}

===ACPI daemon===
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].

==Screen blanking (Standby)==
Make sure you have
Option "DPMS"
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.

Running {{cmduser|xset +dpms}} and then {{cmduser|xset dpms force off}} will turn off the backlight on a laptop screen.<br />

Note that this may not work in combination with {{cmduser|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.

==Suspend to RAM (Sleep)==
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.

For Troubleshooting, look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].

==Suspend to disk (Hibernate)==
There are two drivers for this available:
* [[swsusp]], which is in the kernel and
* [[Software Suspend 2]] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself.

Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].

Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.

See the according drivers page for instructions.

==ThinkPads on which it is recommended to use ACPI==
*ThinkPad {{770X}}, {{770Z}}
*ThinkPad {{A20m}}, {{A20p}}, {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
*ThinkPad {{G40}}, {{G41}}
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R40e}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}
*ThinkPad {{Z60t}}, {{Z60m}}
*ThinkPad {{TransNote}}

How to make ACPI work

2006-07-13T11:10:51Z

Supermihi: /* ThinkPads on which it is recommended to use ACPI */

How to protect the harddisk through APS

2006-07-12T19:00:08Z

Supermihi: /* Gentoo */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page tells you how to make the [[Active Protection System]] work under Linux to protect your harddrive from damage in case of a notebook drop or other kind of impact while it is running.

Specific instructions for {{Fedora}} can be found [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]].

== How APS works in Linux ==
APS in Linux consists of four components on the software side:
* The [[HDAPS]] driver (included in recent kernels). It exports a sysfs interface providing the acceleration values.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdaps_protect</tt>] disk protection kernel patch, which exports a sysfs interface that enables an ide or sata disk to be protected by a userspace process.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdapsd</tt>] disk protection userspace daemon. It monitors the acceleration values through the HDAPS interface and automatically initiates disk protection through the hdaps_protect interface - given that the movement exceeds a user specified threshold.
* Optional: the [http://www.oakcourt.dyndns.org/projects/khdapsmon/ <tt>khdapsmon</tt> KDE System Tray applet] or the [http://www.dresco.co.uk/hdaps/ <tt>gnome-hdaps-applet</tt>]. These applets provide a visual indication of the disk protection status and also a graphical interface for adjusting configuration options for <tt>hdapsd</tt>.
|}

==Installation==
As mentioned above, the hdaps kernel driver found in recent kernels is only responsible for reading the accelerometer data and exporting it through the sysfs interface.

In order to use this information to protect the disk, some additional steps are required.

* Download and build the latest hdaps_protect disk protection kernel patches.
* Enable the drivers in the kernel (requires kernel rebuild).
* Download, build and configure the hdapsd userspace daemon.
* Download and build one of the applets to get a real-time representation of the disk protection status.

===Getting the files===
{| border="1" cellspacing="0" cellpadding="2"
! Latest Sources
|
*<tt>hdaps_protect</tt>, <tt>hdapsd</tt> and the <tt>gnome-hdaps-applet</tt>: http://www.dresco.co.uk/hdaps
*<tt>khdapsmon</tt>: http://www.oakcourt.dyndns.org/projects/khdapsmon/
|-
! {{Debian}}
|
*<tt>hdapsd</tt>, <tt>hdaps_protect</tt>, <tt>khdapsmon</tt>, <tt>gnome-hdaps-applet</tt>:
:{{cmdroot|deb http://www.oakcourt.dyndns.org/debian/ ./}}
:{{cmdroot|deb-src http://www.oakcourt.dyndns.org/debian/ ./}}
|-
! {{Fedora}}
| see instructions [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]]
*kernel RPM packages including <tt>hdaps_protect</tt>: http://www.dresco.co.uk/hdaps/
*kernel RPM packages including <tt>hdaps_protect</tt> and [[Software Suspend 2]]: http://mhensler.de/swsusp/download/yum/development/fc5/ (build 2084_2 and up)
|-
! {{Gentoo}}
|
*<tt>hdapsd</tt> ebuild: http://bugs.gentoo.org/show_bug.cgi?id=119845
*<tt>khdapsmon</tt> ebuild: http://bugs.gentoo.org/show_bug.cgi?id=124175
|}

=== Adding kernel support ===
A kernel patch is required for disk head parking and queue freezing.

==== Manually patching and compiling a kernel ====
As root, do:
:{{cmdroot|cd /usr/src/linux}}
:{{cmdroot|patch -p1 < ~/hdaps_protect.20060409.patch}}
:{{cmdroot|make clean}}
:{{cmdroot|make}}
:{{cmdroot|make modules_install}}

=== Installing hdapsd ===
==== Manual compilation from source ====
* Download the <tt>hdapsd</tt> sources (see above)
* Compile using {{cmdroot|gcc -o hdapsd hdapsd-*.c}}
* Run {{cmdroot|./hdapsd -d sda -s 12 -a}} (replace <tt>sda</tt> with your hard disk device; run {{cmdroot|./hdapsd}} without arguments for help)

==== Gentoo ====
{{Gentoo}} users can try the ebuild attached to [http://bugs.gentoo.org/show_bug.cgi?id=119845 gentoo bug 119845].
{{NOTE|1=hdapsd was added to the official portage tree on the 26th June 2006.}}
*Add hdapsd support in your kernel: device drivers -> hardware monitoring -> ... (you need it as a module if you want to use tp_smapi and hdaps, see [[Tp_smapi]])
*Download the ebuild, use same ebuild date as the kernel-patch.
*Make known the portage an extern ebuild path and add the following line to {{path|/etc/make.conf}}:
PORTDIR_OVERLAY="/usr/local/portage/" (or any other location)
*Create directory {{path|/usr/local/portage}} and {{path|/usr/local/portage/app-laptop/}}
*Copy the downloaded ebuild to {{path|/usr/local/portage/app-laptop}} ({{path|/usr/local/portage/app-laptop/hdapsd}} should now exists)
*Make portage known the new ebuild and creat digist with:
:{{cmdroot|ebuild /usr/local/portage/app-laptop/hdapsd/hdapsd-20060326.ebuild digest}}
*Optional: Copy source file to portage distfiles (if no internet connection is available):
:{{cmdroot|cp hdapsd-20060326.c /usr/portage/distfiles}}
*Accept the x86 keyword for this package: {{cmdroot|echo "app-laptop/hdapsd ~x86" >> /etc/portage/package.keywords}}
*Install hdapsd with: {{cmdroot|emerge hdapsd}}.
*Edit {{path|/etc/conf.d/hdapsd}} (change your harddrive if neccessary: mine is sda, and change the value from 5, 5 is to sensitive, 12 is a good value in my opinion).
*start deamon with: {{cmdroot|/etc/init.d/hdapsd start}}
*Optional: add to default runlevel: {{cmdroot|rc-update add hdapsd default, rc-update add hdapsd battery}}
Write an eMail to abartel[Ã¤d]htwm.de, if you want to get my hdapsd-20060326.ebuild and please upload it.

=== Building an applet ===
====hdaps-gl====
*Make sure you have installed hdaps [and loaded] and ?opengl?
*Download <tt>hdaps-gl-0.0.5</tt> from the web.
*Extract files to {{path|/opt/hdaps-gl}}.
*{{cmdroot|make}}
*Start the applet: {{cmdroot|./hdaps-gl}}

====khdapsmon====
This application uses GNU autotools, so building it is the same as any other autotooled program:
*extract the source somewhere and change to that directory,
*run {{cmdroot|./configure && make && make install}}.
See [[#Getting the files|above]] for Debian packages and a Gentoo ebuild.

====gnome-hdaps-applet====
=====Debian/Ubuntu=====
Packages available at site listed above (with source packages that can do the building for you)

==Troubleshooting==
See the [[Problem with APS harddisk parking]] page for troubleshooting APS issues.
{{NOTE|1=If you use [[tp_smapi]], remember to include the option <tt>HDAPS=1</tt> when [[Tp_smapi#Installation|installing tp_smapi]]. Also, you might need to build the hdaps driver as module.}}

==Further Information==
*Additonal information and support is available through the [[Mailinglists#HDAPS Developers Mailinglist|hdaps-devel]] mailinglist and its archive.

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]]

How to configure acpid

2006-07-12T16:43:09Z

Supermihi: /* Troubleshooting */

__TOC__
==Introduction==
Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}}.

==Sources of Information==
*{{cmduser|man acpid}} holds detailed information on how to configure acpid.
*The [[ibm-acpi]] package includes example scripts in the {{path|config}} folder inside the tarball. They are a good starting point to adjust them to your needs.
*You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository.
*And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].

==Example: go to sleep on lid close==
To make the ThinkPad go to sleep when you close the lid, you need to add
an event handler for the lid event and an action script that takes care
of going to sleep and resuming.

===Event Script===
The event script needs to be created within {{path|/etc/acpi/events}} and can have any name you like.
In this case we call it lid because it will trigger the lid event. Do {{cmdroot|vi /etc/acpi/events/lid}} and make it look like this:
event=button/lid
action=/etc/acpi/actions/sleep.sh %e

The "event" line is a regular expression specifying the events we're
interested in. You can determine what the event strings are from looking at
{{path|/var/log/acpid}} after trying to suspend, close the lid, etc. .
You can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].

The "action" line is the command to be executed when these events are
dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.

For the script you can use the <tt>hibernate</tt> script of [http://www.suspend2.net/ Software Suspend 2] (it is independent of the [[Software Suspend 2|suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.

{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}

===Action Script===
Our example {{path|/etc/acpi/actions/sleep.sh}} script looks as follows:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6
/usr/sbin/radeontool light off

# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd

# turn on the backlight and switch back to X
radeontool light on
chvt $FGCONSOLE

====Explanations====
*The lid generates an event for both opening and closing thus requiring that we check its state and only act if it's closed.
*There have been problems encountered with the USB devices not working properly after a resume from suspend. To circumvent those we remove the USB driver prior to suspend and reload it afterwards.
*Note that the {{cmdroot|echo -n "mem" > /sys/power/state}} line does not return until we are revived. So there is only one event generated and there is no need to check the state of anything.
*The console switching code in this script is a special solution for [[Problem with LCD backlight remaining on during ACPI sleep|a problem where the backlight doesn't switch off]] on the {{T30}} and some other models. Before going to sleep, these models switch to console mode which causes the backlight to come back on. So we preemptively switch to console mode and turn off the backlight using [[radeontool]] before going to sleep.

==Troubleshooting==
*If something doesn't work, your first action should be a {{cmdroot|tail /var/log/acpid}}. It will tell you a lot about what is going on. If it has "Permission denied" errors, check the permissions of your {{path|/etc/acpi/actions}} scripts (especially make sure that the executable bit is set). Also check the permissions for other involved files like i.e. device nodes.
*For further problems look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].

[[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:Z60t]] [[Category:Z60m]] [[Category:TransNote]]