ThinkWiki - User contributions [en]

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-09-20T19:48:32Z

Shamuki: /* TouchPad */ added syndaemon vs palm detect

== Model ==
Lenovo Thinkpad {{T410s}} 2912-W1C, BIOS 6UET36WW (1.14), ECP 6UHT28WW (1.09)

== General ==
This installation instruction describes these parts that do not or do not completely work after my {{OpenSUSE}} 11.3 DVD installation using KDE 4 as window manager.

== Graphics ==
Samsung SyncMaster 225bw (1680x1050) is unuseable when connected via DVI, probably due to an EDID-related bug (see the corresponding [https://bugzilla.novell.com/show_bug.cgi?id=613165 bug report]). Other displays are probably not affected, but feedback is lacking.

As a workaround, create a standard mode, add it to the display and set the display to use it:
xrandr --newmode "1680x1050+h+v" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync +vsync;
xrandr --addmode HDMI2 "1680x1050+h+v";
sleep 0.5; # arbitrary crashes might occur without this statement, probably some race condition
xrandr --output HDMI2 --mode "1680x1050+h+v";
Thanks to openSUSE's Stefan Dirsch for [https://bugzilla.novell.com/show_bug.cgi?id=613165#c15 pointing that out] in the bug report mentioned above.

== Network ==

=== Wireless LAN ===
The [[Intel Centrino Ultimate-N 6300]] adapter works out of the box.
Note that your T410s might come with another adapter installed, so your mileage may vary.

=== Wireless WAN ===
The optional Wireless WAN (WWAN) adapter [[Qualcomm Gobi 2000]] does not work out of the box. First, the current (2.6.34) qcserial kernel driver module does not support the 2000 version of the Qualcomm Gobi. Second, the application that uploads the firmware to the WWAN device is broken since kernel 2.6.32 [https://bugzilla.kernel.org/show_bug.cgi?id=15134]. Thus, you need kernel 2.6.35 or to backport the related patches manually [https://bugzilla.novell.com/show_bug.cgi?id=611270].

== UltraNav ==

=== TouchPad ===
The TouchPad is configured by the KDE system settings, e.g., the mouse clicks triggered by tapping. However, for enabling two-finger scrolling, some XInput properties must be set:
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Scrolling" 1 0
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Pressure" 30

Another way to adjust the synaptics parameters is via a file under xorg.conf.d, like
/etc/X11/xorg.conf.d/20-synaptics.conf

I found the following settings to be comfortable:

Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "HorizScrollDelta" "99" # enable horizontal scrolling
Option "VertTwoFingerScroll" "True" # enable vertical two-finger scrolling
Option "VertScrollDelta" "99"
Option "TapButton1" "1" # 1-finger tap = left mouse click
Option "TapButton2" "3" # 2-finger tap = right mouse click
EndSection

The synaptics manpage describes all possible options.
man synaptic

==== Palm detection vs. syndaemon ====
For many people, spurious mouse clicks during typing, caused by your palm touching the pad, are a major source of serious headache. There are two ways out: Enabling palm detection in the driver and syndaemon, a program which shuts off the touchpad while you're typing.

I found syndaemon to be more useful, because it can be difficult to adjust the palm detection parameters such that it reliably suppresses palm events without also suppressing some voluntary mouse events.

To enable palm detection, add the following lines to your xorg.conf (or the respective file under xorg.conf.d):

Option "PalmDetect" "True" # enable palm detection
Option "PalmMinZ" "50"
Option "PalmMinWidth" "7"

To enable syndaemon, add a line like the following to the autostart mechanism of your favorite desktop environment:
syndaemon -d -i 1.0 -K
This makes syndaemon start as a daemon (-d), disable the touchpad during 1.0 seconds after the last key stroke (-i 1.0), ignoring modifier keys and modifier key combos (-K). Other people find the -t option useful, which disables only tapping and scrolling, but not mouse movements. The syndaemon man page gives you all options.
man syndaemon

=== TrackPoint ===
The [[TrackPoint]] can be used to perform scrolling, similar to Windows, by holding down the middle button and moving the TrackPoint. Horizontal scrolling is now enabled by default. The Opera browser moves forward and backward in its history instead, see [[How to configure the TrackPoint#Configure Opera for using trackpoint horizontal scrolling|here]] to fix it or disable horizontal scrolling completely by:
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 -1 -1 4 5

== Integrated Fingerprint Reader ==
The [[Integrated Fingerprint Reader]] is a UPEK TouchStrip (USB ID 147e:2016). The release of libfprint that ships with openSUSE 11.3 does NOT support that device. A device with the same ID is listed as being supported on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki]. Rumor has it that the development version of libfprint (v. 0.1.0_pre2) supports the reader, but a naive build from source of this lib failed to read fingerprints from the sensor.

More information is in the [http://bugzilla.novell.com/show_bug.cgi?id=528596 corresponding bug in openSUSE's bugzilla], and on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki].

Category:T410s

2010-09-06T17:17:49Z

Shamuki: /* Getting rid of the blue cast */ changed header

__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 T410s ===
This page gives an overview of all ThinkPad T410s related topics.

==== Machine Type ====
* 2901, 2904, 2912, 2924

==== Standard Features ====
*One of the following [[Intel Core i5]] processors:
** Intel® Core™ i5-520M (2.4GHz, 3MB L2)
* [[Intel HD Graphics]]
* One of the following displays
** 14.1" TFT display with 1440x900 (WXGA+) resolution with LED backlight
** 14.1" TFT display with 1440x900 (WXGA+) resolution with LED backlight and Multitouch
* 2, 3 or 4GB [[PC3-8500]] memory standard upgradable to 8GB
* One of the follow HDD
** 80GB SSD 1.8" HDD
** 128GB SSD 1.8" HDD
** 120GB 5400rpm 1.8" SATA HDD
** 250GB 5400rpm 1.8" SATA HDD
* [[Ultrabay|Serial Ultrabay Slim]] with one of the following:
** [[Serial Ultrabay Slim DVD Burner II]]
* 2.0MP [[Integrated camera]] on select models
* [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2.1)|Bluetooth]] on select models
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* Intel HD Audio with a [[CX20585]] codec
* [[ExpressCard slot|ExpressCard/34 slot]]
* [[MiniPCI Express slot]] 1 with the following:
** [[Intel Centrino Advanced-N 6200]]
** [[Intel Centrino Advanced-N + WiMAX 6250]]
** [[Intel Centrino Ultimate-N 6300]]
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty)
** [[Qualcomm Gobi 2000]] WWAN with GPS
* [[Integrated Fingerprint Reader]] on select models
* [[UltraNav]] (TrackPoint / Touchpad combo)
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Intel Active Management Technology (AMT)]]
</div>
|style="vertical-align:top" |
[[Image:ThinkPadT410s.jpg|ThinkPad T410s|300px]]
|}

=== Linux Installation ===

Installation instructions for the {{ThinkPad|T410s|Installation instructions for the}}

[[Category:T Series]]

=== Automatic Display Switching on Resume ===

* See [[Automatic Display Switching on Resume]]

=== Color profile for the display ===

Some people find the display to have an ugly blue cast. To get rid of it, you can download this [http://biomachinelearning.net/T410sTwoDown.icc ICC profile] which, once loaded, should give you much more neutral colors. The profile was created with [http://argyllcms.org/ ArgyllCMS], a formidable free open source color management system. Once you installed Argyll, use this line to load the profile:
dispwin path/to/profile.icc

The profile was created with display bightness two ticks below maximum. Note that although the profile is likely to improve your color rendering, it may be not optimal for your display. For better results, get a colorimeter and create your own profile.

Your distribution might even offer packages of Argyll (e.g., openSUSE does in its [http://download.opensuse.org/repositories/multimedia:/photo/openSUSE_11.3/ multimedia:photo repository.]).

If you want to give me some feedback about the profile, you can do so on my [[User_talk:Shamuki |Talk page]].

[[Category:T Series]]

Category:T410s

2010-08-27T08:41:09Z

Shamuki:

__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 T410s ===
This page gives an overview of all ThinkPad T410s related topics.

==== Machine Type ====
* 2901, 2904, 2912, 2924

==== Standard Features ====
*One of the following [[Intel Core i5]] processors:
** Intel® Core™ i5-520M (2.4GHz, 3MB L2)
* [[Intel HD Graphics]]
* One of the following displays
** 14.1" TFT display with 1440x900 (WXGA+) resolution with LED backlight
** 14.1" TFT display with 1440x900 (WXGA+) resolution with LED backlight and Multitouch
* 2, 3 or 4GB [[PC3-8500]] memory standard upgradable to 8GB
* One of the follow HDD
** 80GB SSD 1.8" HDD
** 128GB SSD 1.8" HDD
** 120GB 5400rpm 1.8" SATA HDD
** 250GB 5400rpm 1.8" SATA HDD
* [[Ultrabay|Serial Ultrabay Slim]] with one of the following:
** [[Serial Ultrabay Slim DVD Burner II]]
* 2.0MP [[Integrated camera]] on select models
* [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2.1)|Bluetooth]] on select models
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* Intel HD Audio with a [[CX20585]] codec
* [[ExpressCard slot|ExpressCard/34 slot]]
* [[MiniPCI Express slot]] 1 with the following:
** [[Intel Centrino Advanced-N 6200]]
** [[Intel Centrino Advanced-N + WiMAX 6250]]
** [[Intel Centrino Ultimate-N 6300]]
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty)
** [[Qualcomm Gobi 2000]] WWAN with GPS
* [[Integrated Fingerprint Reader]] on select models
* [[UltraNav]] (TrackPoint / Touchpad combo)
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Intel Active Management Technology (AMT)]]
</div>
|style="vertical-align:top" |
[[Image:ThinkPadT410s.jpg|ThinkPad T410s|300px]]
|}

=== Linux Installation ===

Installation instructions for the {{ThinkPad|T410s|Installation instructions for the}}

[[Category:T Series]]

=== Automatic Display Switching on Resume ===

* See [[Automatic Display Switching on Resume]]

=== Getting rid of the blue cast ===

Some people find the display to have an ugly blue cast. To get rid of it, you can download this [http://biomachinelearning.net/T410sTwoDown.icc ICC profile] which, once loaded, should give you much more neutral colors. The profile was created with [http://argyllcms.org/ ArgyllCMS], a formidable free open source color management system. Once you installed Argyll, use this line to load the profile:
dispwin path/to/profile.icc

The profile was created with display bightness two ticks below maximum. Note that although the profile is likely to improve your color rendering, it may be not optimal for your display. For better results, get a colorimeter and create your own profile.

Your distribution might even offer packages of Argyll (e.g., openSUSE does in its [http://download.opensuse.org/repositories/multimedia:/photo/openSUSE_11.3/ multimedia:photo repository.]).

If you want to give me some feedback about the profile, you can do so on my [[User_talk:Shamuki |Talk page]].

[[Category:T Series]]

User talk:Shamuki

2010-08-27T08:09:58Z

Shamuki:

Welcome to my talk page!

I'm listening... :)

User talk:Shamuki

2010-08-27T08:09:30Z

Shamuki: â†Created page with 'Welcome to my talk page!'

Welcome to my talk page!

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-08-26T19:09:35Z

Shamuki: /* TouchPad */ updated synclient xorg hack

== Model ==
Lenovo Thinkpad {{T410s}} 2912-W1C, BIOS 6UET36WW (1.14), ECP 6UHT28WW (1.09)

== General ==
This installation instruction describes these parts that do not or do not completely work after my {{OpenSUSE}} 11.3 DVD installation using KDE 4 as window manager.

== Graphics ==
Samsung SyncMaster 225bw (1680x1050) is unuseable when connected via DVI, probably due to an EDID-related bug (see the corresponding [https://bugzilla.novell.com/show_bug.cgi?id=613165 bug report]). Other displays are probably not affected, but feedback is lacking.

As a workaround, create a standard mode, add it to the display and set the display to use it:
xrandr --newmode "1680x1050+h+v" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync +vsync;
xrandr --addmode HDMI2 "1680x1050+h+v";
sleep 0.5; # arbitrary crashes might occur without this statement, probably some race condition
xrandr --output HDMI2 --mode "1680x1050+h+v";
Thanks to openSUSE's Stefan Dirsch for [https://bugzilla.novell.com/show_bug.cgi?id=613165#c15 pointing that out] in the bug report mentioned above.

== Network ==

=== Wireless LAN ===
The [[Intel Centrino Ultimate-N 6300]] adapter works out of the box.
Note that your T410s might come with another adapter installed, so your mileage may vary.

=== Wireless WAN ===
The optional Wireless WAN (WWAN) adapter [[Qualcomm Gobi 2000]] does not work out of the box. First, the current (2.6.34) qcserial kernel driver module does not support the 2000 version of the Qualcomm Gobi. Second, the application that uploads the firmware to the WWAN device is broken since kernel 2.6.32 [https://bugzilla.kernel.org/show_bug.cgi?id=15134]. Thus, you need kernel 2.6.35 or to backport the related patches manually [https://bugzilla.novell.com/show_bug.cgi?id=611270].

== UltraNav ==

=== TouchPad ===
The TouchPad is configured by the KDE system settings, e.g., the mouse clicks triggered by tapping. However, for enabling two-finger scrolling, some XInput properties must be set:
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Scrolling" 1 0
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Pressure" 30

Another way to adjust the synaptics parameters is via a file under xorg.conf.d, like
/etc/X11/xorg.conf.d/20-synaptics.conf

I found the following settings to be comfortable:

Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "HorizScrollDelta" "99" # enable horizontal scrolling
Option "VertTwoFingerScroll" "True" # enable vertical two-finger scrolling
Option "VertScrollDelta" "99"
Option "PalmDetect" "True" # enable palm detection
Option "PalmMinZ" "50"
Option "PalmMinWidth" "7"
Option "TapButton1" "1" # 1-finger tap = left mouse click
Option "TapButton2" "3" # 2-finger tap = right mouse click
EndSection

The synaptics manpage describes all possible options.
man synaptic

=== TrackPoint ===
The [[TrackPoint]] can be used to perform scrolling, similar to Windows, by holding down the middle button and moving the TrackPoint. Horizontal scrolling is now enabled by default. The Opera browser moves forward and backward in its history instead, see [[How to configure the TrackPoint#Configure Opera for using trackpoint horizontal scrolling|here]] to fix it or disable horizontal scrolling completely by:
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 -1 -1 4 5

== Integrated Fingerprint Reader ==
The [[Integrated Fingerprint Reader]] is a UPEK TouchStrip (USB ID 147e:2016). The release of libfprint that ships with openSUSE 11.3 does NOT support that device. A device with the same ID is listed as being supported on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki]. Rumor has it that the development version of libfprint (v. 0.1.0_pre2) supports the reader, but a naive build from source of this lib failed to read fingerprints from the sensor.

More information is in the [http://bugzilla.novell.com/show_bug.cgi?id=528596 corresponding bug in openSUSE's bugzilla], and on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki].

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-08-26T19:06:21Z

Shamuki: /* TouchPad */

== Model ==
Lenovo Thinkpad {{T410s}} 2912-W1C, BIOS 6UET36WW (1.14), ECP 6UHT28WW (1.09)

== General ==
This installation instruction describes these parts that do not or do not completely work after my {{OpenSUSE}} 11.3 DVD installation using KDE 4 as window manager.

== Graphics ==
Samsung SyncMaster 225bw (1680x1050) is unuseable when connected via DVI, probably due to an EDID-related bug (see the corresponding [https://bugzilla.novell.com/show_bug.cgi?id=613165 bug report]). Other displays are probably not affected, but feedback is lacking.

As a workaround, create a standard mode, add it to the display and set the display to use it:
xrandr --newmode "1680x1050+h+v" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync +vsync;
xrandr --addmode HDMI2 "1680x1050+h+v";
sleep 0.5; # arbitrary crashes might occur without this statement, probably some race condition
xrandr --output HDMI2 --mode "1680x1050+h+v";
Thanks to openSUSE's Stefan Dirsch for [https://bugzilla.novell.com/show_bug.cgi?id=613165#c15 pointing that out] in the bug report mentioned above.

== Network ==

=== Wireless LAN ===
The [[Intel Centrino Ultimate-N 6300]] adapter works out of the box.
Note that your T410s might come with another adapter installed, so your mileage may vary.

=== Wireless WAN ===
The optional Wireless WAN (WWAN) adapter [[Qualcomm Gobi 2000]] does not work out of the box. First, the current (2.6.34) qcserial kernel driver module does not support the 2000 version of the Qualcomm Gobi. Second, the application that uploads the firmware to the WWAN device is broken since kernel 2.6.32 [https://bugzilla.kernel.org/show_bug.cgi?id=15134]. Thus, you need kernel 2.6.35 or to backport the related patches manually [https://bugzilla.novell.com/show_bug.cgi?id=611270].

== UltraNav ==

=== TouchPad ===
The TouchPad is configured by the KDE system settings, e.g., the mouse clicks triggered by tapping. However, for enabling two-finger scrolling, some XInput properties must be set:
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Scrolling" 1 0
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Pressure" 30

Another way to adjust the synaptics parameters is via a file under xorg.conf.d, like
/etc/X11/xorg.conf.d/20-synaptics.conf

I found the following settings to be comfortable:

Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
#enable horizontal scrolling
Option "HorizScrollDelta" "99"

Option "VertScrollDelta" "99"
Option "VertTwoFingerScroll" "True"
Option "PalmDetect" "True"
Option "PalmMinZ" "50"
Option "PalmMinWidth" "7"
Option "TapButton1" "1"
Option "TapButton2" "3"

EndSection

The synaptics manpage describes all possible options.
man synaptic

=== TrackPoint ===
The [[TrackPoint]] can be used to perform scrolling, similar to Windows, by holding down the middle button and moving the TrackPoint. Horizontal scrolling is now enabled by default. The Opera browser moves forward and backward in its history instead, see [[How to configure the TrackPoint#Configure Opera for using trackpoint horizontal scrolling|here]] to fix it or disable horizontal scrolling completely by:
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 -1 -1 4 5

== Integrated Fingerprint Reader ==
The [[Integrated Fingerprint Reader]] is a UPEK TouchStrip (USB ID 147e:2016). The release of libfprint that ships with openSUSE 11.3 does NOT support that device. A device with the same ID is listed as being supported on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki]. Rumor has it that the development version of libfprint (v. 0.1.0_pre2) supports the reader, but a naive build from source of this lib failed to read fingerprints from the sensor.

More information is in the [http://bugzilla.novell.com/show_bug.cgi?id=528596 corresponding bug in openSUSE's bugzilla], and on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki].

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-08-25T08:31:40Z

Shamuki: /* TouchPad */ added sample synaptics.conf for /etx/X11/xorg.conf.d

== Model ==
Lenovo Thinkpad {{T410s}} 2912-W1C, BIOS 6UET36WW (1.14), ECP 6UHT28WW (1.09)

== General ==
This installation instruction describes these parts that do not or do not completely work after my {{OpenSUSE}} 11.3 DVD installation using KDE 4 as window manager.

== Graphics ==
Samsung SyncMaster 225bw (1680x1050) is unuseable when connected via DVI, probably due to an EDID-related bug (see the corresponding [https://bugzilla.novell.com/show_bug.cgi?id=613165 bug report]). Other displays are probably not affected, but feedback is lacking.

As a workaround, create a standard mode, add it to the display and set the display to use it:
xrandr --newmode "1680x1050+h+v" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync +vsync;
xrandr --addmode HDMI2 "1680x1050+h+v";
sleep 0.5; # arbitrary crashes might occur without this statement, probably some race condition
xrandr --output HDMI2 --mode "1680x1050+h+v";
Thanks to openSUSE's Stefan Dirsch for [https://bugzilla.novell.com/show_bug.cgi?id=613165#c15 pointing that out] in the bug report mentioned above.

== Network ==

=== Wireless LAN ===
The [[Intel Centrino Ultimate-N 6300]] adapter works out of the box.
Note that your T410s might come with another adapter installed, so your mileage may vary.

=== Wireless WAN ===
The optional Wireless WAN (WWAN) adapter [[Qualcomm Gobi 2000]] does not work out of the box. First, the current (2.6.34) qcserial kernel driver module does not support the 2000 version of the Qualcomm Gobi. Second, the application that uploads the firmware to the WWAN device is broken since kernel 2.6.32 [https://bugzilla.kernel.org/show_bug.cgi?id=15134]. Thus, you need kernel 2.6.35 or to backport the related patches manually [https://bugzilla.novell.com/show_bug.cgi?id=611270].

== UltraNav ==

=== TouchPad ===
The TouchPad is configured by the KDE system settings, e.g., the mouse clicks triggered by tapping. However, for enabling two-finger scrolling, some XInput properties must be set:
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Scrolling" 1 0
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Pressure" 30

Another way to adjust the synaptics parameters is via a file under xorg.conf.d, like
/etc/X11/xorg.conf.d/20-synaptics.conf

I found the following settings to be comfortable:

Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "HorizScrollDelta" "99"
Option "VertScrollDelta" "99"
Option "VertTwoFingerScroll" "True"
Option "PalmDetect" "True"
Option "PalmMinZ" "50"
Option "PalmMinWidth" "7"
EndSection

The synaptics manpage describes all possible options.
man synaptic

=== TrackPoint ===
The [[TrackPoint]] can be used to perform scrolling, similar to Windows, by holding down the middle button and moving the TrackPoint. Horizontal scrolling is now enabled by default. The Opera browser moves forward and backward in its history instead, see [[How to configure the TrackPoint#Configure Opera for using trackpoint horizontal scrolling|here]] to fix it or disable horizontal scrolling completely by:
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 -1 -1 4 5

== Integrated Fingerprint Reader ==
The [[Integrated Fingerprint Reader]] is a UPEK TouchStrip (USB ID 147e:2016). The release of libfprint that ships with openSUSE 11.3 does NOT support that device. A device with the same ID is listed as being supported on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki]. Rumor has it that the development version of libfprint (v. 0.1.0_pre2) supports the reader, but a naive build from source of this lib failed to read fingerprints from the sensor.

More information is in the [http://bugzilla.novell.com/show_bug.cgi?id=528596 corresponding bug in openSUSE's bugzilla], and on the [http://reactivated.net/fprint/wiki/Libfprint fprint wiki].

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-07-13T18:19:21Z

Shamuki: /* Graphics */ adde info on buggy Samsung 225bw

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-07-13T18:12:35Z

Shamuki: /* Integrated Fingerprint Reader */ added more info

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-06-14T09:34:43Z

Shamuki: /* Graphics */

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-06-14T09:33:31Z

Shamuki: /* Graphics */ updated graphics problem.

User talk:Gettalong15

2010-06-13T11:21:57Z

Shamuki: â†Created page with 'Hi Getalong15, I hope this page works as a way to contact you - I didn't find any email address. I read your article on automatic display switching for the t410s. Since...'

Hi Getalong15,

I hope this page works as a way to contact you - I didn't find any email address.

I read your article on automatic display switching for the t410s. Since you appear to have a docking station and use it with an external monitor, I wonder whether you have encountered a problem similar to mine - a flashing screen when a 1680x1050 monitor is connected via DVI on the docking station. 1280x1024 works just fine.

Can you confirm the problem with 1680x1050 screens, or should I have my docking station replaces?

Cheers,

Michael

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-06-10T08:42:13Z

Shamuki: /* Graphics */ added problem with 1680x1050 displays on DVI

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-06-08T22:16:17Z

Shamuki: /* TouchPad */ fixed typo in code (camelcase TouchPad), adjusted sensitivity to something more useful

Installing OpenSUSE 11.3 on a ThinkPad T410s

2010-06-07T12:43:52Z

Shamuki: /* Network */ added info on wifi.

== Model ==
Lenovo Thinkpad {{T410s}} 2912-W1C, BIOS 6UET33WW (1.11), Embedded Controller 6UHT27WW (1.08)

== General ==
This installation instruction describes these parts that do not or do not completely work after my {{OpenSUSE}} 11.3 Milestone 7 DVD installation using KDE 4 as window manager.

== Graphics ==
Enabling compositing crashes X due to a bug in the Intel 2010Q1 graphics package. Fixed packages are available [https://bugzilla.novell.com/show_bug.cgi?id=608149].

== Network ==
Because of bug [https://bugzilla.novell.com/show_bug.cgi?id=591703], the laptop pattern must be installed manually using YaST. Then, YaST must be used to switch to NetworkManager instead of traditional ifup.

=== Wireless LAN ===
The [[Intel Centrino Ultimate-N 6300]] adapter works out of the box, if the kernel-firmware package is installed. In OpenSUSE 11.3 Milestone 7 there's a [https://bugzilla.novell.com/show_bug.cgi?id=591703 bug] which prevents that package to be installed automatically. To install it manually, do (as root)
zypper in kernel-firmware
Note that your T410s might come with another adapter installed, so your mileage may vary.

=== Wireless WAN ===
The optional Wireless WAN (WWAN) adapter [[Qualcomm Gobi 2000]] does not work out of the box. First, the current (2.6.34) qcserial kernel driver module does not support the 2000 version of the Qualcomm Gobi. Second, the application that uploads the firmware to the WWAN device is broken since kernel 2.6.32 [https://bugzilla.kernel.org/show_bug.cgi?id=15134]. Thus, you need kernel 2.6.35 or to backport the related patches manually [https://bugzilla.novell.com/show_bug.cgi?id=611270].

== UltraNav ==

=== TouchPad ===
The TouchPad is configured by the KDE system settings, e.g., the mouse clicks triggered by tapping. However, for enabling two-finger scrolling, some XInput properties must be set:
{{cmduser|xinput set-prop "SynPS/2 Synaptics Touchpad" "Synaptics Two-Finger Scrolling" 1 0}}
{{cmduser|xinput set-prop "SynPS/2 Synaptics Touchpad" "Synaptics Two-Finger Pressure" 40}}

=== Trackpoint ===
The Trackpoint can be used to perform scrolling, similar to Windows, by holding down the middle button and moving the Trackpoint. If you do not like the horizontal scrolling enabled by default, since some browser might move forward and backward in their history, disable it by:
{{cmduser|xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 -1 -1 4 5}}

== Integrated Fingerprint Reader ==
The fingerprint sensor is a UPEK TouchStrip (USB vendor ID 0x147e). But the driver is only included in the development version of libfprint. Since the current release 0.0.6 is provided by the distribution, the reader does not work.

Intel Centrino Ultimate-N 6300

2010-06-07T12:43:48Z

Shamuki: added info on linux support

__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;">
== Intel Centrino Ultimate-N 6300 ==
This is a Mini-PCI Express WiFi Adapter, supported by the iwlagn driver

== Features ==
* Chipset: ?
* IEEE Standards: 802.11a, 802.11b, 802.11g ,802.11n
* 3x3 MIMO up to 450Mbps
* PCI ID: 8086:????
</div>
|style="vertical-align:top" |
[[image:IntelWiFi6200.jpg|Intel Centrino Advanced-N 6200]]<br/>
|}
=== Lenovo Partnumbers ===
* ?

=== Linux support ===
This card is supported out of the box on kernel 2.6.34; older kernels probably support it, too. On openSUSE 11.3, the linux-firmware package is required for the card to function.

=== Models featuring this Technology ===
* {{T410}}, {{T410s}}
* {{T510}}
* {{W510}}, {{W701}}, {{W701ds}}
* {{X201}}

=== External Links===
* http://www.intel.com/network/connectivity/products/wireless/adapters/6200-6300/index.htm
* http://intellinuxwireless.org/ - Intel website for Linux drivers

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

2007-09-18T13:38:30Z

Shamuki: /* AR5418 is still too new? */ added pointer to solution

__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/n Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5008 or Atheros AR5418
* Integrated Mac Processor and Radio Chip: Atheros, unknown model
* IEEE Standards: 802.11a, 802.11b, 802.11g, 802.11n (draft)
* PCI ID: 168c:0024
</div>
|style="vertical-align:top" |
 
|}

=== Different chipsets? ===
It has been reported that different chipsets may be used by Lenovo for this controller. This may, however, be only an issue of outdated PCI IDs. To clarify, please update your PCI IDs and report the name of the chipset. On a [[T60]] running OpenSuse 10.2, the following code does the job:

# update-pciids
# lspci|grep Atheros
03:00.0 Network controller: Atheros Communications, Inc. AR5418 802.11a/b/g/n Wireless PCI Express Adapter (rev 01)

If you get a different name for the chipset despite having the most current PCI IDs, please report it here! Note that, since pciids only translates numeric IDs to human-readable IDs, it is very unlikely (if not impossible) that the chip with PCI ID 0168:0024 gets annotated as different chipsets.

=== IBM Partnumbers ===
42T0825 [http://www-307.ibm.com/pc/support/site.wss/MIGR-64222.html]

=== Linux WiFi driver ===
There's now (04.04.07) added [http://madwifi.org/wiki/news/20070328/experimental-support-for-ar5008-802-11n experimental support] for the AR5008 chipset to a new branch in MadWifi. I have compiled this driver successfully, but it's still at an experimental stage, so no promises are given. [[How_to_checkout_and_install_madwifi_experimental_driver_for_ar5008 | Howto]]

There is an old ticket for this card at [http://madwifi.org/ticket/1001 madwifi, #1001].

There is an new ticket for this card at [http://madwifi.org/ticket/1243 madwifi-branch, #1243].

To install this driver, just checkout the branch madwifi-hal-0.9.30.13.

mkdir /tmp/madwifi
cd /tmp/madwifi
svn checkout http://svn.madwifi.org/branches/madwifi-hal-0.9.30.13/
cd madwifi-hal-0.9.30.13/
make
make install
*choose [r]
reboot

News fron the madwifi-branch:

* milestone changed from version 0.9.x - progressive release candidate phase to version 0.9.4.
FYI: the madwifi-hal-0.9.30.13 branch has been merged to trunk
(and the branch has been removed). If you don't want to wait until the next release (v0.9.4),
you could go with a snapshot or checkout from trunk - just make sure that your code is >= r2360.

Until the madwifi driver stabilizes you might want to get the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver] from Lenovo's support site and use a recent version of [http://sourceforge.net/project/showfiles.php?group_id=93482&package_id=99148 ndiswrapper (>= 1.29)]. I've compiled a [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter | Howto]] for this card.

=== AR5418 is still too new? ===
If anyone is able to get the AR5418 to work with madwifi, please add your procedure for getting it to work - in the meantime, [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter | ndiswrapper works]] with the windows driver.

'''Update 10.06.2007 from Stevie:'''

I have the AR5418 chipset and with the snapshot release r2431 this chipset works (with wpa-psk). Just try it...

[[User:Timmsc|Timmsc]]:

A number of folks have reported getting errors while using recent versions of madwifi with Feisty on the T60p with the AR5418. When the NMI is received, the wifi dies. If anyone knows the solution, please elaborate.

<pre>
Uhhuh. NMI received for unknown reason b0 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue
</pre>

<pre>
wifi0: rx FIFO overrun; resetting
wifi0: rx FIFO overrun; resetting
wifi0: rx FIFO overrun; resetting
</pre>

See the following threads and bug reports:
[http://ubuntuforums.org/showthread.php?p=3152517]
[http://ubuntuforums.org/showthread.php?t=500729]
[https://answers.launchpad.net/ubuntu/+question/5537]
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/116752]
[http://sourceforge.net/mailarchive/forum.php?thread_name=20070809145900.GD16023%40hank.org&forum_name=madwifi-users]

{{HINT|There's a [http://madwifi.org/ticket/1017 ticket on madwifi] with a potential solution for the rx FIFO overrun problem.}}

=== Hardware switch ===

Some ThinkPads have a hardware switch that must be in the '''on''' position for the radio to work, regardless of driver state:

[[Image:Wireless-switch.png|(ThinkPad R60 radio switch in the ON position)]]

In addition to hard-switching the wireless card, the switch also generates an [[Acpid|acpi event]] on transition from hi->lo and vice versa. It is however the same event in both directions.

=== ThinkPads this card may be found in ===
* {{R60}}, {{R60e}}
* {{T60}}, {{T60p}}
* {{X60}}, {{X60s}}, {{X60t}} Tablet
* {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}}

=== Related Links ===
* [http://www.madwifi.org MadWifi project page]
* [http://madwifi.org/ticket/1001 MadWifi ticket #1001]
* [http://ndiswrapper.sourceforge.net/ ndiswrapper at SourceForge]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver at Lenovo]

[[Category:Components]]

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

2007-09-18T13:35:01Z

Shamuki: /* AR5418 is still too new? */ added link to madwifi ticket

__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/n Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5008 or Atheros AR5418
* Integrated Mac Processor and Radio Chip: Atheros, unknown model
* IEEE Standards: 802.11a, 802.11b, 802.11g, 802.11n (draft)
* PCI ID: 168c:0024
</div>
|style="vertical-align:top" |
 
|}

=== Different chipsets? ===
It has been reported that different chipsets may be used by Lenovo for this controller. This may, however, be only an issue of outdated PCI IDs. To clarify, please update your PCI IDs and report the name of the chipset. On a [[T60]] running OpenSuse 10.2, the following code does the job:

# update-pciids
# lspci|grep Atheros
03:00.0 Network controller: Atheros Communications, Inc. AR5418 802.11a/b/g/n Wireless PCI Express Adapter (rev 01)

If you get a different name for the chipset despite having the most current PCI IDs, please report it here! Note that, since pciids only translates numeric IDs to human-readable IDs, it is very unlikely (if not impossible) that the chip with PCI ID 0168:0024 gets annotated as different chipsets.

=== IBM Partnumbers ===
42T0825 [http://www-307.ibm.com/pc/support/site.wss/MIGR-64222.html]

=== Linux WiFi driver ===
There's now (04.04.07) added [http://madwifi.org/wiki/news/20070328/experimental-support-for-ar5008-802-11n experimental support] for the AR5008 chipset to a new branch in MadWifi. I have compiled this driver successfully, but it's still at an experimental stage, so no promises are given. [[How_to_checkout_and_install_madwifi_experimental_driver_for_ar5008 | Howto]]

There is an old ticket for this card at [http://madwifi.org/ticket/1001 madwifi, #1001].

There is an new ticket for this card at [http://madwifi.org/ticket/1243 madwifi-branch, #1243].

To install this driver, just checkout the branch madwifi-hal-0.9.30.13.

mkdir /tmp/madwifi
cd /tmp/madwifi
svn checkout http://svn.madwifi.org/branches/madwifi-hal-0.9.30.13/
cd madwifi-hal-0.9.30.13/
make
make install
*choose [r]
reboot

News fron the madwifi-branch:

* milestone changed from version 0.9.x - progressive release candidate phase to version 0.9.4.
FYI: the madwifi-hal-0.9.30.13 branch has been merged to trunk
(and the branch has been removed). If you don't want to wait until the next release (v0.9.4),
you could go with a snapshot or checkout from trunk - just make sure that your code is >= r2360.

Until the madwifi driver stabilizes you might want to get the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver] from Lenovo's support site and use a recent version of [http://sourceforge.net/project/showfiles.php?group_id=93482&package_id=99148 ndiswrapper (>= 1.29)]. I've compiled a [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter | Howto]] for this card.

=== AR5418 is still too new? ===
If anyone is able to get the AR5418 to work with madwifi, please add your procedure for getting it to work - in the meantime, [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter | ndiswrapper works]] with the windows driver.

'''Update 10.06.2007 from Stevie:'''

I have the AR5418 chipset and with the snapshot release r2431 this chipset works (with wpa-psk). Just try it...

[[User:Timmsc|Timmsc]]:

A number of folks have reported getting errors while using recent versions of madwifi with Feisty on the T60p with the AR5418. When the NMI is received, the wifi dies. If anyone knows the solution, please elaborate.

<pre>
Uhhuh. NMI received for unknown reason b0 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue
</pre>

<pre>
wifi0: rx FIFO overrun; resetting
wifi0: rx FIFO overrun; resetting
wifi0: rx FIFO overrun; resetting
</pre>

See the following threads and bug reports:
[http://ubuntuforums.org/showthread.php?p=3152517]
[http://ubuntuforums.org/showthread.php?t=500729]
[https://answers.launchpad.net/ubuntu/+question/5537]
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/116752]
[http://sourceforge.net/mailarchive/forum.php?thread_name=20070809145900.GD16023%40hank.org&forum_name=madwifi-users]

There's also a [http://madwifi.org/ticket/1017 ticket on madwifi].

=== Hardware switch ===

Some ThinkPads have a hardware switch that must be in the '''on''' position for the radio to work, regardless of driver state:

[[Image:Wireless-switch.png|(ThinkPad R60 radio switch in the ON position)]]

In addition to hard-switching the wireless card, the switch also generates an [[Acpid|acpi event]] on transition from hi->lo and vice versa. It is however the same event in both directions.

=== ThinkPads this card may be found in ===
* {{R60}}, {{R60e}}
* {{T60}}, {{T60p}}
* {{X60}}, {{X60s}}, {{X60t}} Tablet
* {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}}

=== Related Links ===
* [http://www.madwifi.org MadWifi project page]
* [http://madwifi.org/ticket/1001 MadWifi ticket #1001]
* [http://ndiswrapper.sourceforge.net/ ndiswrapper at SourceForge]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver at Lenovo]

[[Category:Components]]

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

2007-06-17T13:18:16Z

Shamuki: /* Different chipsets */ request for clarification

__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/n Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5008 or Atheros AR5418
* Integrated Mac Processor and Radio Chip: Atheros, unknown model
* IEEE Standards: 802.11a, 802.11b, 802.11g, 802.11n (draft)
* PCI ID: 168c:0024
</div>
|style="vertical-align:top" |
 
|}

=== Different chipsets? ===
It has been reported that different chipsets may be used by Lenovo for this controller. This may, however, be only an issue of outdated PCI IDs. To clarify, please update your PCI IDs and report the name of the chipset. On a [[T60] running OpenSuse 10.2, the following code does the job:

# update-pciids
# lspci|grep Atheros
03:00.0 Network controller: Atheros Communications, Inc. AR5418 802.11a/b/g/n Wireless PCI Express Adapter (rev 01)

If you get a different name for the chipset despite having the most current PCI IDs, please report it here! Note that, since pciids only translates numeric IDs to human-readable IDs, it is very unlikely (if not impossible) that the chip with PCI ID 0168:0024 gets annotated as different chipsets.

=== IBM Partnumbers ===
42T0825 [http://www-307.ibm.com/pc/support/site.wss/MIGR-64222.html]

=== Linux WiFi driver ===
There's now (04.04.07) added [http://madwifi.org/wiki/news/20070328/experimental-support-for-ar5008-802-11n experimental support] for the AR5008 chipset to a new branch in MadWifi. I have compiled this driver successfully, but it's still at an experimental stage, so no promises are given. [[How_to_checkout_and_install_madwifi_experimental_driver_for_ar5008 | Howto]]

There is an old ticket for this card at [http://madwifi.org/ticket/1001 madwifi, #1001].

There is an new ticket for this card at [http://madwifi.org/ticket/1243 madwifi-branch, #1243].

To install this driver, just checkout the branch madwifi-hal-0.9.30.13.

mkdir /tmp/madwifi
cd /tmp/madwifi
svn checkout http://svn.madwifi.org/branches/madwifi-hal-0.9.30.13/
cd madwifi-hal-0.9.30.13/
make
make install
*choose [r]
reboot

News fron the madwifi-branch:

* milestone changed from version 0.9.x - progressive release candidate phase to version 0.9.4.
FYI: the madwifi-hal-0.9.30.13 branch has been merged to trunk
(and the branch has been removed). If you don't want to wait until the next release (v0.9.4),
you could go with a snapshot or checkout from trunk - just make sure that your code is >= r2360.

Until the madwifi driver stabilizes you might want to get the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver] from Lenovo's support site and use a recent version of [http://sourceforge.net/project/showfiles.php?group_id=93482&package_id=99148 ndiswrapper (>= 1.29)]. I've compiled a [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter | Howto]] for this card.

=== AR5418 is still to new? ===
If anyone is able to get the AR5418 to work with madwifi, please add your procedure for getting it to work - in the meantime, [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter | ndiswrapper works]] with the windows driver.

'''Update 10.06.2007 from Stevie:'''

I have the AR5418 chipset and with the snapshot release r2431 this chipset works (with wpa-psk). Just try it...

=== Hardware switch ===

Some ThinkPads have a hardware switch that must be in the '''on''' position for the radio to work, regardless of driver state:

[[Image:Wireless-switch.png|(ThinkPad R60 radio switch in the ON position)]]

In addition to hard-switching the wireless card, the switch also generates an [[Acpid|acpi event]] on transition from hi->lo and vice versa. It is however the same event in both directions.

=== ThinkPads this card may be found in ===
* {{R60}}, {{R60e}}
* {{T60}}, {{T60p}}
* {{X60}}, {{X60s}}, {{X60t}} Tablet
* {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}}

=== Related Links ===
* [http://www.madwifi.org MadWifi project page]
* [http://madwifi.org/ticket/1001 MadWifi ticket #1001]
* [http://ndiswrapper.sourceforge.net/ ndiswrapper at SourceForge]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver at Lenovo]

[[Category:Components]]

Wireless Network Adapters

2007-06-17T13:02:33Z

Shamuki: /* Atheros */ previous edit broke link to component page

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This document covers IBM integrated (MiniPCI), Cardbus and PC Card (PCMCIA) Wi-Fi devices.
|}

== Finding out which adapter you have ==
For MiniPCI or Cardbus adapters run the command:
:{{cmdroot|lspci -n <nowiki>|</nowiki> grep "Class 0200"}}
If that produces no output, run this command instead:
:{{cmdroot|lspci -n <nowiki>|</nowiki> grep "0200"}}

(Alternatively, grep for "0280" which identifies "Network" controllers, as opposed to "0200" which identifies "Ethernet" controllers.)

And compare the PCI IDS with the ones below.

{{NOTE| This will also return the PCI IDS of any Ethernet adapters, as Ethernet adapters and Wireless adapters share the same PCI Class ID.}}

== MiniPCI adapters ==
=== Atheros ===
*[[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]] <tt>(PCI-ID: 168c:0012)</tt>
*[[IBM 11b/g Wireless LAN Mini PCI Adapter]] <tt>(PCI-ID: 168c:0013)</tt>
*[[IBM 11a/b/g Wireless LAN Mini PCI Adapter]] <tt>(PCI-ID: 168c:1014)</tt>
*[[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]] <tt>(PCI-ID: 168c:1014)</tt>
*[[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]] <tt>(PCI-ID: 168c:1014)</tt>
*[[ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter]] (AR5BXB72) <tt>(PCI-ID: 168c:0024)</tt>
*[[SparkLAN WMIA-166AG Wireless LAN Mini PCI Adapter (AR5006XS)]] <tt>(PCI-ID: 168c:001b)</tt>

=== Cisco ===
*[[Cisco Aironet Wireless 802.11b]] <tt>(PCI-ID: 14b9:a504)</tt>
=== Intel ===
*[[Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter]] <tt>(PCI-ID: 8086:1043)</tt>
*[[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] <tt>(PCI-ID: 8086:4220)</tt>
*[[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]] <tt>(PCI-ID: 8086:4224)</tt>
*[[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]

=== Prism ===
*[[IBM High Rate Wireless LAN Mini-PCI Adapter with Modem]] <tt>(PCI-ID: 1260:3873)</tt>
*[[IBM High Rate Wireless LAN Mini-PCI Adapter with Modem II]] <tt>(PCI-ID: 1260:3873)</tt>
*[[IBM High Rate Wireless LAN Mini-PCI Adapter III]]

=== Error 1802 - "Unauthorized" MiniPCI network card ===
Attempts to install an unsupported card will result in the following message:

1802: Unauthorized network card is plugged in - Power off and remove the miniPCI network card.

For a resolution, see the [[Problem with unauthorized MiniPCI network card]] page.

== Cardbus adapters ==
Cardbus is a 32bits bus that runs at 33MHz, and is in many ways simular to the PCI bus. In fact under Linux Cardbus adapters are handled by the PCI subsystem.<br>
You can differentiate a PC Card adapter from a Cardbus adapter as the later has a gold coloured grounding strip
=== IBM 11 a/b/g Wireless Cardbus Adapter ===
Chipset: Atheros<br>
Driver: [[madwifi]]<br>
Supported wireless modes: 802.11a, 802.11b, 802.11g

Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51855 MIGR-51855]<br>
Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51959 MIGE-51855]<br>
Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51874 MIGR-51874]
Looking for a reverse PCI to cardbus (ie - want to fit a PCI card into a cardbus slot)

=== IBM 802.11a Wireless LAN Cardbus Adapter ===
Chipset: Atheros<br>
Driver: [[madwifi]]<br>
Supported wireless modes: 802.11a

Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42209 MIGR-42209]<br>
Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42233 MIGR-42233]<br>
Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42231 MIGR-42231]

== PC Card (PCMCIA) adapters ==
PC Card or PCMCIA (Personal Computer Memory Card International Association) as it used to be called, is an 8 or 16bits bus limited to 8MHz, in many ways simular to the old ISA bus and not suitable for highspeed devices.
=== Cisco Aironet 350 802.11b wireless PC card with 128bit ===
Chipset: Cisco<br>
Driver: airo_cs<br>
Supported wireless modes: 802.11b
=== IBM High Rate Wireless LAN PC Card ===
Chipset: Hermes I<br>
Drivers: [[orinoco|orinoco_cs]]<br>
Supported wireless modes: 802.11b

[[Category:Components]]

Talk:How to get special keys to work

2007-04-09T18:34:38Z

Shamuki: /* Toggle touchpad with Fn-F8 */

__TOC__

The xmodmap step doesn't seem to work when using the "kdb" driver of xorg. Here are the changes I needed to make to my setup to get the "back" and "forward" keys to work (in diff -u format);

--- xkb/symbols/inet.oud 2004-12-01 08:36:04.000000000 +0100
+++ xkb/symbols/inet 2005-03-08 19:59:32.587636120 +0100
@@ -1875,6 +1875,16 @@
key <I76> { [ XF86AudioLowerVolume ] };
};

+// IBM ThinkPad 41 Internet Keys
+
+partial alphanumeric_keys
+xkb_symbols "tp41" {
+ name[Group1]= "IBM ThinkPad 41 Internet Keys";
+
+ key <I69> { [ F22 ] };
+ key <I6A> { [ F21 ] };
+};
+
// Trust

partial alphanumeric_keys<br>

--- xkb/rules/xorg.lst.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.lst 2005-03-07 20:55:21.000000000 +0100
@@ -97,6 +97,7 @@
sven SVEN Ergonomic 2500
symplon Symplon PaceBook (tablet PC)
toshiba_s3000 Toshiba Satellite S3000
+ tp41 IBM ThinkPad 41 Internet Keys
trust Trust Wireless Keyboard Classic
trustda Trust Direct Access Keyboard
yahoo Yahoo! Internet Keyboard

--- xkb/rules/xorg.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg 2005-03-07 20:45:59.000000000 +0100
@@ -120,7 +120,7 @@
qtronix \
samsung4500 samsung4510 \
sk1300 sk2500 sk6200 sk7100 \
- sven symplon toshiba_s3000 trust trustda yahoo
+ sven symplon toshiba_s3000 tp41 trust trustda yahoo

! model = symbols
$inetkbds = +inet(%m)

--- xkb/rules/xorg.xml.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.xml 2005-03-07 20:52:35.000000000 +0100
@@ -975,6 +975,13 @@
</model>
<model>
<configItem>
+ <name>tp41</name>
+ <description>IBM Thinkpad 41 Internet Keys</description>
+ <description xml:lang="nl">IBM ThinkPad 41 internet toetsen</description>
+ </configItem>
+ </model>
+ <model>
+ <configItem>
<name>trust</name>
<description>Trust Wireless Keyboard Classic</description>
<description xml:lang="fr">clavier classique Trust Wireless</description>

Do not forget to add something like "+inet(tp41)" to /etc/X11/xorg.conf:
(...)
Option "XkbLayout" "us_intl+inet(tp41)"
(...)

----
I've filled a [https://bugs.freedesktop.org/show_bug.cgi?id=9779 bug] to freedesktop bugzilla, which has been applied. It adds inet(thinkpad) symbols with <I69>/<I6A> keys and adds thinkpad to $inetkbds list. So, Forward/Back keys will work out-of-box with thinkpad XkbModel. However, thinkpadintl model is not supported... --[[User:Raorn|Raorn]] 13:25, 27 January 2007 (CET)

== Not T41 specific ==

These keys are hardly T41 specific, they can also be found on the T30, T40, T42 and I'm sure several other ThinkPads in the X, R and G lineup.

Actually, the above patches could be completed with the information of the other special keys found on some Thinkpads (which is listed in [[How_to_get_special_keys_to_work#xmodmap_configuration]]) and submitted as a request for enhancement with [http://bugs.freedesktop.org xorg's bugzilla]. However, firefox doesn't yet recognize keysyms like XF86Back, XF86Forward, so then firefox still needs to be patched manually (unless an enhancement is requested for firefox too).

== Fake ACPI events? ==

Not all keys generate ACPI events. Maybe it is feasible to have the ibm-acpi module check the CMOS (instead of having tpb checking /dev/nvram) and generate fake ACPI events for those keys. Even if it is feasible, that is probably way to hacky for a kernel module ... Still, it would be nice to only have to use scripts triggered by ACPI events and not both scripts for ACPI events and scripts for tpb.

----
I think something like this is possible with ibm-acpi 0.10 already. It provides a proc file from which you can derive a table of CMOS states. You'd only have to figure the who is who of CMOS bits and write a daemon (or daemon like shell script) checking them regularly. This should be about what you suggest since tpb does the same thing with the bios ram. Of course generating ACPI events can not be done like that (or can it?), but you could trigger the ACPI action scripts directly then.

[[User:Wyrfel|Wyrfel]] 01:02, 14 Mar 2005 (CET)
----

It may be possible (I have a 770x, so don't have the special keys) to add the keys as real ACPI events, by altering the DSDT. I've done this to enable ACPI events for Fn-(every labelled F key),Home,End,PgUp,PgDn on mine, and they aren't labelled with anything physically (no thinklight and physical brightness control). The Embedded Controller reports all events, including keys, by calling one of the _Qxx functions (you'll find a whole pile in the sourcecode for the DSDT). If you then insert a fucntion in the same scope as the others like:-
Method (_Q12, 0, NotSerialized) { \_SB.HKEY.MHKQ (0x1003) } //Fn-F3
when executed, ibm-acpi will then report an acpi event numbered 0x0001003. You should find some functions, e.g. _Q1B For Fn-F12 identical to this.

I found some IBM DSDT's had functions that made MKHQ calls for EC functions _Q63, _Q64, _Q4E, _Q4F, but did nothing on mine---maybe these are a good starting point. Add a whole pile, and see if you get lucky! (At your own risk, of course... :/ But it should be pretty safe).

Yes, the above sounds pretty identical to tpb, except with /proc/ibm/ecdump instead of /dev/nvram. The above works very nicely, however there's luck involved in finding the right number, even if it exists!

[[User:lentinj|lentinj]]

----

Fn+F6 does not seem to generate an event on t41p even if the mask is set to 0xffff and experimental=1 is passed to ibm_acpi
[[User:tf|tf]]

----

==Bind Fn to super or hyper ==

Hello

Is it possible to bind Fn via Xmodmap to a key modifier such as hyper or super? Thanks
[[User:Oub|Oub]] 13:14, 6 February 2006 (CET):
----
I doubt it. The event for the {{key|Fn}} key is generated at release (as opposed to holding it where it serves it's usual special function). Hence you can't use it as a modifier. [[User:Wyrfel|Wyrfel]] 22:52, 6 February 2006 (CET)
----
==Bind Fn 12 say to F34 ==
Thanks Wyrfel for your reply, in order to display my question better, I use a new header: can I bind all the Fn Fx to hay F34 and the like?
[[User:Oub|Oub]] 21:33, 10 February 2006 (CET):
----
You can do this with all key '''combinations''' that support xmodmap (see the table). That means you can't do it with {{key|Fn}}}{{key|F12}}, because that combination doesn't generate a key event at all (it only generates an APM/ACPI event. Hence there is nothing vor xmodmap to remap.

But what is your wider focus goal? I'm sure that what you want to do can be realized, anyway: You can write an ACPI script and event file for {{key|Fn}}{{key|F12}} and have the script start some tool that sends a F34 key to the X server. I'm sure this is possible.

[[User:Wyrfel|Wyrfel]] 00:03, 11 February 2006 (CET)
----
==Can't bind Fn 12 ==

Hello

I am using a R51 and I have compiled ibm-acpi monolithic in the kernel (not as module, maybe this is a mistake?). Anyway, I am using
suspend2, which I compiled in the kernel as well. Now I have bound
''to hibernate '' first to Fn 4, with the following script
event=button[ /]sleep
action=/usr/local/sbin/mihibernate

This works fine. Now I want to do the same for Fn12, so following the key table I did:

event=button[/] ibm/hotkey HKEY 00000080 0000100c
action=/usr/local/sbin/mihibernate

But that does not work. What is the problem? I tried even
echo enable,0xffff >/proc/acpi/ibm/hotkey
without success. Can anybody help me?
[[User:Oub|Oub]] 16:27, 4 March 2006 (CET):
----
The proper event line is
event=ibm/hotkey HKEY 00000080 0000100c
.

Also, make sure that you are not using [thinkpad-acpi]. If <tt>event=button[ /]sleep</tt> works for {{key|Fn}}{{key|F4}}, that indicates that you do. It might block the ibm-acpi driver. Check your kernel config and disable any thinkpad acpi driver except ibm-acpi.

[[User:Wyrfel|Wyrfel]] 21:58, 4 March 2006 (CET)
----

:Hello
:
:It is odd, I am pretty sure, that I do not use [thinkpad-acpi], but [ibm-acpi], although event=button[ /]sleep works for FnF4, in any case I found out that
:
: event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
:
:Works! What do you think of adding a subsection to the [[How to get special keys to work]] page, with some examples, like the following:
:
:from ''/etc/acpi/events/battery'':
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
action=/usr/local/sbin/hibernate
:from ''/etc/acpi/events/lid''
event=button/lid
action=/usr/local/bin/mysleepram
:from ''/etc/acpi/events/sleepbtn''
event=(button/sleep|ibm/hotkey HKEY 00000080 00001004)
action=/usr/local/bin/mysleepram
:
:(Also ''event=button/sleep '' works for me)
:and then restart acpi:
:
/etc/init.d/acpid restart
:
:[[User:Oub|Oub]] 13:22, 5 March 2006 (CET):
----
What you do with
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
is to make a logical nonexclusive OR between
event=button/power
and
event=ibm/hotkey HKEY 00000080 0000100c
. If the first works, the whole thing works. So that's pretty logical.

Please, do a {{cmdroot|dmesg <nowiki>|</nowiki> grep thinkpad-acpi}} and do a {{cmdroot|dmesg <nowiki>|</nowiki> grep ibm-acpi}}. What is the output in either case?

I see no sense in putting examples to the page that only confuse people because they are not correct. ibm-acpi generates the events listed in the table and nothing else. If you get something like <tt>button/sleep</tt> it's not ibm-acpi generating it. You are running Debian, right? Let's hope they didn't patch the driver to generate different events.

Also, you can always do {{cmdroot|tail -f /var/log/acpid}} to have a life view of the generated events.

I am pretty sure that you are using thinkpad-acpi or - if not so - that something else must interfere.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)

----

:Hi
:
:Ok I admit everything is very odd. For the start, I seem to use
:ibm-acpi. As I said I am Debian, but I compiled my own kernel :(2.6.10)(but not as a module, maybe this was a bad idee??) and I used :the ibm-acpi driver which comes shipped with that kernel. I did not :download the driver from the official http://ibm-acpi.sourceforge.net/ :site. Here is the output of
:
:dmesg | grep acpi
Kernel command line: ro root=/dev/hda6 acpi_sleep=s3_bios
tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired
evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [df6ddaa8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1464768]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1467328]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146bba8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b628]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b3e8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b268]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146dde8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470d68]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470568]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c14719a8]
ibm_acpi: IBM ThinkPad ACPI Extras v0.8
ibm_acpi: http://ibm-acpi.sf.net/
acpi_bus-0081 [08] acpi_bus_get_device : Error getting context for object [c1467328]
ibm_acpi: dock device not present

:I don't understand the errors but anyway. Now the odd thing is that indeed the following works
:
event=button[ /]sleep
action=/usr/local/sbin/hibernate
:but
event=button[/]sleep
action=/usr/local/sbin/hibernate

:Does not work. But from what you said, using the ibm_acpi neither of '''these strings ''' should work? So I don't understand what is going on. [[User:Oub|Oub]] 20:28, 6 March 2006 (CET):

----

With any reasonably new kernel (2.6.16 in Thinkpad terms :-) ) and a good DSDT (say, like the one that comes inside the T43), you can get two classes of events: ACPI events (as in native ACPI events), and ibm-acpi hotkey events.

This has nothing to do with thinkpad-acpi.

Look under /proc/acpi/buttons. If you have sleep and maybe hibernate/suspend in there (I don't know how fn+f12 is called when properly supported through ACPI DSDT, the T43 doesn't support it like that), then your Thinkpad can, and will generate proper ACPI events without the help of ibm-acpi. This is valid for a complete ACPI config of kernel 2.6.16 with all modules loaded.

And it will generate regular ibm-acpi hotkey events if you enable the feature and use the correct mask, which may or may not confuse the thinkpad (I am not sure the correct DSDT handlers the BIOS expect to run are called in this case).

-- [[User:Hmh|hmh]] 2006-05-26 13:20 UTC

==Turn on/off Wifi on Fn5 ==
Hi

I hope this is the last question. I use a crude way to activate and deactivate my wificard: I remove and insert the relevant modules, with 2 simple scripts. Now the question is how can I bind Fn5 so, that it turns on and off the wificard? With my approach I need to fire up two scripts, and that I cannot bind to one button. Thanks
[[User:Oub|Oub]] 17:57, 5 March 2006 (CET):

Try a {{cmdroot|cat /proc/acpi/ibm/bluetooth}}. Maybe it returns the state. If not, the other way would be to check if the USB bluetooth controller device is listed in {{path|/proc/bus/usb}} somewhere. It shouldn't be there if bluetooth is switched off and should be there if it is on.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)
----

==Split page?==
This page is getting too long. Maybe we should split it. I'd suggest moving the "Example applications" to a seperate page.

[[User:Pebolle|Paul Bolle]] 22:46, 3 April 2006 (CEST)

==DIY Firefox 1.5 xpi==
Here's how I maneged a Firefox 1.5 compatible plugin (source: google). Note that the wiki eats some of the xml tags (so look at the source too)

$ ls -1R tp41.xpi
tp41.xpi/:
chrome
chrome.manifest
install.rdf

tp41.xpi/chrome:
content

tp41.xpi/chrome/content:
tp41keysOverlay.xul

$ cat tp41.xpi/chrome.manifest
content tp41keys chrome/content/
overlay chrome://browser/content/browser.xul chrome://tp41keys/content/tp41keysOverlay.xul

$ cat tp41.xpi/install.rdf
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">

<Description about="urn:mozilla:install-manifest">
<em:id>tp41keys@tp41keys.org</em:id>
<em:version>1.0</em:version>
<em:type>2</em:type>


<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>1.0+</em:minVersion>
<em:maxVersion>1.5.0.*</em:maxVersion>
</Description>
</em:targetApplication>


<em:name>IBM ThinkPad 41 Keys</em:name>
<em:description>Two Browser Navigation Keys</em:description>
<em:creator>Paul Bolle</em:creator>
<em:homepageURL>http://www.example.com/tp41keys.xpi</em:homepageURL>
</Description>
</RDF>

$ cat tp41.xpi/chrome/content/tp41keysOverlay.xul
<?xml version='1.0'?>
<!DOCTYPE overlay>

<overlay id='tp41keysOverlay'
xmlns='http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul'>

<keyset id='mainKeyset'>
<key id='tp41BackKey' keycode='VK_F21' command='Browser:Back' />
<key id='tp41ForwardKey' keycode='VK_F22' command='Browser:Forward' />
</keyset>

</overlay>

$ cat .mozilla/firefox/*.default/extensions/tp41keys\@tp41keys.org
~/tp41.xpi

==ibm-acpi hint==

I would like to add a hint under ibm-acpi to enable all hotkeys at boot, but I can not seem to get the HINT template to work:

<nowiki>{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}</nowiki>

It outputs:

{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}

Any ideas on how to get this to work? Also, does it even belong in the page?

--[[User:Paul Strefling|Paul Strefling]] 23:22, 10 August 2006 (CEST)

If you use ''ibm-apci'' as a module and have {{path|/proc}} filesystem enabled, you can tune it by
adding to {{path|/etc/modules.d/ibm_acpi}}:

post-install ibm-acpi /bin/echo enable,0x00d0 > /proc/acpi/ibm/hotkey
I added it after ''alias ibm-acpi ibm_acpi''. I'm not sure - if the order make sence. Params can be differ - it is an example.

Also works fine with {{cmdroot|modprobe}} (don't forget to run {{cmdroot|modules-update}} after editing {{path|/etc/modules.d/*}}).

(tested on Gentoo with vanilla kernel).

==Lock Screen with hotkey on models before T60==

In case it's of interest, it's possible to simulate the "lock screen" (Fn+F2) function of T60s on prior models. I wrote a little [http://forums.gentoo.org/viewtopic-p-3814885.html HOWTO] on the Gentoo forums explaining how to configure Fn+F3 to fire up xscreensaver instead of blanking the screen (though this could easily be changed to Fn+F2 instead). This was for my T42 but I presume it'd work on other models too. Perhaps it'd be worth mentioning in the Remarks column of the Fn+F2 row of the table at the top of the article? --[[User:Waveform|Waveform]] 03:42, 2 January 2007 (CET)

== Toggle touchpad with Fn-F8 ==

I often want to switch off the touchpad, since I tend to produce spurious taps while typing, sending my cursor to random places on the screen. To toggle touchpad operation, I use this little script:

#!/bin/sh
#
# toggle touchpad operation
# August 2, 2006
# (c) Michael Schmuker
#
if synclient -l | grep TouchpadOff | grep -q 0; then
synclient TouchpadOff=1;
kdialog --passivepopup "Touchpad is OFF" 2;
else
synclient TouchpadOff=0;
kdialog --passivepopup "Touchpad is ON" 2;
fi

This checks if the touchpad is on or off, and toggles its state accordingly. Note that it uses kdialog to display a notification on the desktop. This obviously works only with KDE, but there certainly is a similar mechanism for other desktop environments.

Now this script needs to be bound to the Fn-F8-key. On Suse 10.2, the ACPI-events produced by the thinkpad special keys are processed by powersaved. You need to edit the file {{path|/usr/lib/powersave/scripts/thinkpad_acpi_events}}.
There, thinkpad-ACPI events are bound to their actions. Where it comes to Fn-F8, just change it to the following (supposed you put the above script to {{path|/usr/local/bin/toggleTouchpad}} and make it executable):
4104) HOTKEY="Fn+F8" #toggle touchpad on/off
/usr/local/bin/toggleTouchpad
;;
Save the file, and the next time you press Fn-F8 you will toggle your touchpad.

Unfortunately, the notification via kdialog is not working when toggling with Fn-F8. If anyone finds out how to solve this: Let us know!

Talk:How to get special keys to work

2007-04-09T18:32:15Z

Shamuki: Toggle touchpad with Fn-F8

__TOC__

The xmodmap step doesn't seem to work when using the "kdb" driver of xorg. Here are the changes I needed to make to my setup to get the "back" and "forward" keys to work (in diff -u format);

--- xkb/symbols/inet.oud 2004-12-01 08:36:04.000000000 +0100
+++ xkb/symbols/inet 2005-03-08 19:59:32.587636120 +0100
@@ -1875,6 +1875,16 @@
key <I76> { [ XF86AudioLowerVolume ] };
};

+// IBM ThinkPad 41 Internet Keys
+
+partial alphanumeric_keys
+xkb_symbols "tp41" {
+ name[Group1]= "IBM ThinkPad 41 Internet Keys";
+
+ key <I69> { [ F22 ] };
+ key <I6A> { [ F21 ] };
+};
+
// Trust

partial alphanumeric_keys<br>

--- xkb/rules/xorg.lst.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.lst 2005-03-07 20:55:21.000000000 +0100
@@ -97,6 +97,7 @@
sven SVEN Ergonomic 2500
symplon Symplon PaceBook (tablet PC)
toshiba_s3000 Toshiba Satellite S3000
+ tp41 IBM ThinkPad 41 Internet Keys
trust Trust Wireless Keyboard Classic
trustda Trust Direct Access Keyboard
yahoo Yahoo! Internet Keyboard

--- xkb/rules/xorg.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg 2005-03-07 20:45:59.000000000 +0100
@@ -120,7 +120,7 @@
qtronix \
samsung4500 samsung4510 \
sk1300 sk2500 sk6200 sk7100 \
- sven symplon toshiba_s3000 trust trustda yahoo
+ sven symplon toshiba_s3000 tp41 trust trustda yahoo

! model = symbols
$inetkbds = +inet(%m)

--- xkb/rules/xorg.xml.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.xml 2005-03-07 20:52:35.000000000 +0100
@@ -975,6 +975,13 @@
</model>
<model>
<configItem>
+ <name>tp41</name>
+ <description>IBM Thinkpad 41 Internet Keys</description>
+ <description xml:lang="nl">IBM ThinkPad 41 internet toetsen</description>
+ </configItem>
+ </model>
+ <model>
+ <configItem>
<name>trust</name>
<description>Trust Wireless Keyboard Classic</description>
<description xml:lang="fr">clavier classique Trust Wireless</description>

Do not forget to add something like "+inet(tp41)" to /etc/X11/xorg.conf:
(...)
Option "XkbLayout" "us_intl+inet(tp41)"
(...)

----
I've filled a [https://bugs.freedesktop.org/show_bug.cgi?id=9779 bug] to freedesktop bugzilla, which has been applied. It adds inet(thinkpad) symbols with <I69>/<I6A> keys and adds thinkpad to $inetkbds list. So, Forward/Back keys will work out-of-box with thinkpad XkbModel. However, thinkpadintl model is not supported... --[[User:Raorn|Raorn]] 13:25, 27 January 2007 (CET)

== Not T41 specific ==

These keys are hardly T41 specific, they can also be found on the T30, T40, T42 and I'm sure several other ThinkPads in the X, R and G lineup.

Actually, the above patches could be completed with the information of the other special keys found on some Thinkpads (which is listed in [[How_to_get_special_keys_to_work#xmodmap_configuration]]) and submitted as a request for enhancement with [http://bugs.freedesktop.org xorg's bugzilla]. However, firefox doesn't yet recognize keysyms like XF86Back, XF86Forward, so then firefox still needs to be patched manually (unless an enhancement is requested for firefox too).

== Fake ACPI events? ==

Not all keys generate ACPI events. Maybe it is feasible to have the ibm-acpi module check the CMOS (instead of having tpb checking /dev/nvram) and generate fake ACPI events for those keys. Even if it is feasible, that is probably way to hacky for a kernel module ... Still, it would be nice to only have to use scripts triggered by ACPI events and not both scripts for ACPI events and scripts for tpb.

----
I think something like this is possible with ibm-acpi 0.10 already. It provides a proc file from which you can derive a table of CMOS states. You'd only have to figure the who is who of CMOS bits and write a daemon (or daemon like shell script) checking them regularly. This should be about what you suggest since tpb does the same thing with the bios ram. Of course generating ACPI events can not be done like that (or can it?), but you could trigger the ACPI action scripts directly then.

[[User:Wyrfel|Wyrfel]] 01:02, 14 Mar 2005 (CET)
----

It may be possible (I have a 770x, so don't have the special keys) to add the keys as real ACPI events, by altering the DSDT. I've done this to enable ACPI events for Fn-(every labelled F key),Home,End,PgUp,PgDn on mine, and they aren't labelled with anything physically (no thinklight and physical brightness control). The Embedded Controller reports all events, including keys, by calling one of the _Qxx functions (you'll find a whole pile in the sourcecode for the DSDT). If you then insert a fucntion in the same scope as the others like:-
Method (_Q12, 0, NotSerialized) { \_SB.HKEY.MHKQ (0x1003) } //Fn-F3
when executed, ibm-acpi will then report an acpi event numbered 0x0001003. You should find some functions, e.g. _Q1B For Fn-F12 identical to this.

I found some IBM DSDT's had functions that made MKHQ calls for EC functions _Q63, _Q64, _Q4E, _Q4F, but did nothing on mine---maybe these are a good starting point. Add a whole pile, and see if you get lucky! (At your own risk, of course... :/ But it should be pretty safe).

Yes, the above sounds pretty identical to tpb, except with /proc/ibm/ecdump instead of /dev/nvram. The above works very nicely, however there's luck involved in finding the right number, even if it exists!

[[User:lentinj|lentinj]]

----

Fn+F6 does not seem to generate an event on t41p even if the mask is set to 0xffff and experimental=1 is passed to ibm_acpi
[[User:tf|tf]]

----

==Bind Fn to super or hyper ==

Hello

Is it possible to bind Fn via Xmodmap to a key modifier such as hyper or super? Thanks
[[User:Oub|Oub]] 13:14, 6 February 2006 (CET):
----
I doubt it. The event for the {{key|Fn}} key is generated at release (as opposed to holding it where it serves it's usual special function). Hence you can't use it as a modifier. [[User:Wyrfel|Wyrfel]] 22:52, 6 February 2006 (CET)
----
==Bind Fn 12 say to F34 ==
Thanks Wyrfel for your reply, in order to display my question better, I use a new header: can I bind all the Fn Fx to hay F34 and the like?
[[User:Oub|Oub]] 21:33, 10 February 2006 (CET):
----
You can do this with all key '''combinations''' that support xmodmap (see the table). That means you can't do it with {{key|Fn}}}{{key|F12}}, because that combination doesn't generate a key event at all (it only generates an APM/ACPI event. Hence there is nothing vor xmodmap to remap.

But what is your wider focus goal? I'm sure that what you want to do can be realized, anyway: You can write an ACPI script and event file for {{key|Fn}}{{key|F12}} and have the script start some tool that sends a F34 key to the X server. I'm sure this is possible.

[[User:Wyrfel|Wyrfel]] 00:03, 11 February 2006 (CET)
----
==Can't bind Fn 12 ==

Hello

I am using a R51 and I have compiled ibm-acpi monolithic in the kernel (not as module, maybe this is a mistake?). Anyway, I am using
suspend2, which I compiled in the kernel as well. Now I have bound
''to hibernate '' first to Fn 4, with the following script
event=button[ /]sleep
action=/usr/local/sbin/mihibernate

This works fine. Now I want to do the same for Fn12, so following the key table I did:

event=button[/] ibm/hotkey HKEY 00000080 0000100c
action=/usr/local/sbin/mihibernate

But that does not work. What is the problem? I tried even
echo enable,0xffff >/proc/acpi/ibm/hotkey
without success. Can anybody help me?
[[User:Oub|Oub]] 16:27, 4 March 2006 (CET):
----
The proper event line is
event=ibm/hotkey HKEY 00000080 0000100c
.

Also, make sure that you are not using [thinkpad-acpi]. If <tt>event=button[ /]sleep</tt> works for {{key|Fn}}{{key|F4}}, that indicates that you do. It might block the ibm-acpi driver. Check your kernel config and disable any thinkpad acpi driver except ibm-acpi.

[[User:Wyrfel|Wyrfel]] 21:58, 4 March 2006 (CET)
----

:Hello
:
:It is odd, I am pretty sure, that I do not use [thinkpad-acpi], but [ibm-acpi], although event=button[ /]sleep works for FnF4, in any case I found out that
:
: event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
:
:Works! What do you think of adding a subsection to the [[How to get special keys to work]] page, with some examples, like the following:
:
:from ''/etc/acpi/events/battery'':
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
action=/usr/local/sbin/hibernate
:from ''/etc/acpi/events/lid''
event=button/lid
action=/usr/local/bin/mysleepram
:from ''/etc/acpi/events/sleepbtn''
event=(button/sleep|ibm/hotkey HKEY 00000080 00001004)
action=/usr/local/bin/mysleepram
:
:(Also ''event=button/sleep '' works for me)
:and then restart acpi:
:
/etc/init.d/acpid restart
:
:[[User:Oub|Oub]] 13:22, 5 March 2006 (CET):
----
What you do with
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
is to make a logical nonexclusive OR between
event=button/power
and
event=ibm/hotkey HKEY 00000080 0000100c
. If the first works, the whole thing works. So that's pretty logical.

Please, do a {{cmdroot|dmesg <nowiki>|</nowiki> grep thinkpad-acpi}} and do a {{cmdroot|dmesg <nowiki>|</nowiki> grep ibm-acpi}}. What is the output in either case?

I see no sense in putting examples to the page that only confuse people because they are not correct. ibm-acpi generates the events listed in the table and nothing else. If you get something like <tt>button/sleep</tt> it's not ibm-acpi generating it. You are running Debian, right? Let's hope they didn't patch the driver to generate different events.

Also, you can always do {{cmdroot|tail -f /var/log/acpid}} to have a life view of the generated events.

I am pretty sure that you are using thinkpad-acpi or - if not so - that something else must interfere.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)

----

:Hi
:
:Ok I admit everything is very odd. For the start, I seem to use
:ibm-acpi. As I said I am Debian, but I compiled my own kernel :(2.6.10)(but not as a module, maybe this was a bad idee??) and I used :the ibm-acpi driver which comes shipped with that kernel. I did not :download the driver from the official http://ibm-acpi.sourceforge.net/ :site. Here is the output of
:
:dmesg | grep acpi
Kernel command line: ro root=/dev/hda6 acpi_sleep=s3_bios
tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired
evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [df6ddaa8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1464768]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1467328]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146bba8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b628]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b3e8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b268]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146dde8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470d68]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470568]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c14719a8]
ibm_acpi: IBM ThinkPad ACPI Extras v0.8
ibm_acpi: http://ibm-acpi.sf.net/
acpi_bus-0081 [08] acpi_bus_get_device : Error getting context for object [c1467328]
ibm_acpi: dock device not present

:I don't understand the errors but anyway. Now the odd thing is that indeed the following works
:
event=button[ /]sleep
action=/usr/local/sbin/hibernate
:but
event=button[/]sleep
action=/usr/local/sbin/hibernate

:Does not work. But from what you said, using the ibm_acpi neither of '''these strings ''' should work? So I don't understand what is going on. [[User:Oub|Oub]] 20:28, 6 March 2006 (CET):

----

With any reasonably new kernel (2.6.16 in Thinkpad terms :-) ) and a good DSDT (say, like the one that comes inside the T43), you can get two classes of events: ACPI events (as in native ACPI events), and ibm-acpi hotkey events.

This has nothing to do with thinkpad-acpi.

Look under /proc/acpi/buttons. If you have sleep and maybe hibernate/suspend in there (I don't know how fn+f12 is called when properly supported through ACPI DSDT, the T43 doesn't support it like that), then your Thinkpad can, and will generate proper ACPI events without the help of ibm-acpi. This is valid for a complete ACPI config of kernel 2.6.16 with all modules loaded.

And it will generate regular ibm-acpi hotkey events if you enable the feature and use the correct mask, which may or may not confuse the thinkpad (I am not sure the correct DSDT handlers the BIOS expect to run are called in this case).

-- [[User:Hmh|hmh]] 2006-05-26 13:20 UTC

==Turn on/off Wifi on Fn5 ==
Hi

I hope this is the last question. I use a crude way to activate and deactivate my wificard: I remove and insert the relevant modules, with 2 simple scripts. Now the question is how can I bind Fn5 so, that it turns on and off the wificard? With my approach I need to fire up two scripts, and that I cannot bind to one button. Thanks
[[User:Oub|Oub]] 17:57, 5 March 2006 (CET):

Try a {{cmdroot|cat /proc/acpi/ibm/bluetooth}}. Maybe it returns the state. If not, the other way would be to check if the USB bluetooth controller device is listed in {{path|/proc/bus/usb}} somewhere. It shouldn't be there if bluetooth is switched off and should be there if it is on.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)
----

==Split page?==
This page is getting too long. Maybe we should split it. I'd suggest moving the "Example applications" to a seperate page.

[[User:Pebolle|Paul Bolle]] 22:46, 3 April 2006 (CEST)

==DIY Firefox 1.5 xpi==
Here's how I maneged a Firefox 1.5 compatible plugin (source: google). Note that the wiki eats some of the xml tags (so look at the source too)

$ ls -1R tp41.xpi
tp41.xpi/:
chrome
chrome.manifest
install.rdf

tp41.xpi/chrome:
content

tp41.xpi/chrome/content:
tp41keysOverlay.xul

$ cat tp41.xpi/chrome.manifest
content tp41keys chrome/content/
overlay chrome://browser/content/browser.xul chrome://tp41keys/content/tp41keysOverlay.xul

$ cat tp41.xpi/install.rdf
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">

<Description about="urn:mozilla:install-manifest">
<em:id>tp41keys@tp41keys.org</em:id>
<em:version>1.0</em:version>
<em:type>2</em:type>


<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>1.0+</em:minVersion>
<em:maxVersion>1.5.0.*</em:maxVersion>
</Description>
</em:targetApplication>


<em:name>IBM ThinkPad 41 Keys</em:name>
<em:description>Two Browser Navigation Keys</em:description>
<em:creator>Paul Bolle</em:creator>
<em:homepageURL>http://www.example.com/tp41keys.xpi</em:homepageURL>
</Description>
</RDF>

$ cat tp41.xpi/chrome/content/tp41keysOverlay.xul
<?xml version='1.0'?>
<!DOCTYPE overlay>

<overlay id='tp41keysOverlay'
xmlns='http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul'>

<keyset id='mainKeyset'>
<key id='tp41BackKey' keycode='VK_F21' command='Browser:Back' />
<key id='tp41ForwardKey' keycode='VK_F22' command='Browser:Forward' />
</keyset>

</overlay>

$ cat .mozilla/firefox/*.default/extensions/tp41keys\@tp41keys.org
~/tp41.xpi

==ibm-acpi hint==

I would like to add a hint under ibm-acpi to enable all hotkeys at boot, but I can not seem to get the HINT template to work:

<nowiki>{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}</nowiki>

It outputs:

{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}

Any ideas on how to get this to work? Also, does it even belong in the page?

--[[User:Paul Strefling|Paul Strefling]] 23:22, 10 August 2006 (CEST)

If you use ''ibm-apci'' as a module and have {{path|/proc}} filesystem enabled, you can tune it by
adding to {{path|/etc/modules.d/ibm_acpi}}:

post-install ibm-acpi /bin/echo enable,0x00d0 > /proc/acpi/ibm/hotkey
I added it after ''alias ibm-acpi ibm_acpi''. I'm not sure - if the order make sence. Params can be differ - it is an example.

Also works fine with {{cmdroot|modprobe}} (don't forget to run {{cmdroot|modules-update}} after editing {{path|/etc/modules.d/*}}).

(tested on Gentoo with vanilla kernel).

==Lock Screen with hotkey on models before T60==

In case it's of interest, it's possible to simulate the "lock screen" (Fn+F2) function of T60s on prior models. I wrote a little [http://forums.gentoo.org/viewtopic-p-3814885.html HOWTO] on the Gentoo forums explaining how to configure Fn+F3 to fire up xscreensaver instead of blanking the screen (though this could easily be changed to Fn+F2 instead). This was for my T42 but I presume it'd work on other models too. Perhaps it'd be worth mentioning in the Remarks column of the Fn+F2 row of the table at the top of the article? --[[User:Waveform|Waveform]] 03:42, 2 January 2007 (CET)

== Toggle touchpad with Fn-F8 ==

I often want to switch off the touchpad, since I tend to produce spurious taps while typing, sending my cursor to random places on the screen. To toggle touchpad operation, I use this little script:

#!/bin/sh
#
# toggle touchpad operation
# August 2, 2006
# (c) Michael Schmuker
#
if synclient -l | grep TouchpadOff | grep -q 0; then
synclient TouchpadOff=1;
kdialog --passivepopup "Touchpad is OFF" 2;
else
synclient TouchpadOff=0;
kdialog --passivepopup "Touchpad is ON" 2;
fi

This checks if the touchpad is on or off, and toggles its state accordingly. Note that it uses kdialog to display a notification on the desktop. This obviously works only with KDE, but there certainly is a similar mechanism for other desktop environments.

Now this script needs to be bound to the Fn-F8-key. On Suse 10.2, the ACPI-events produced by the thinkpad special keys are processed by powersaved. You need to edit the file
/usr/lib/powersave/scripts/thinkpad_acpi_events
There, thinkpad-ACPI events are bound to their actions. Where it comes to Fn-F8, just change it to the following (supposed you put the above script to /usr/local/bin/toggleTouchpad and make it executable):
4104) HOTKEY="Fn+F8" #toggle touchpad on/off
/usr/local/bin/toggleTouchpad
;;
Save the file, and the next time you press Fn-F8 you will toggle your touchpad.

Unfortunately, the notification via kdialog is not working when toggling with Fn-F8. If anyone finds out how to solve this: Let us know!

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

2007-01-02T18:47:00Z

Shamuki: /* Features */

How to install ndiswrapper for the ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter

2006-12-18T22:08:43Z

Shamuki: /* No suspend with ndiswrapper */

You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

===Quirks===
====Card gets stuck in 802.11n mode====
I had the machine running under windows, where no WLAN was available. When booting into Linux, the card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. I tried to change settings via iwconfig, without any effect (not even an error message, nothing in the logs). Windows must have left the card in a state where iwconfig cannot con figure it.

I rebooted into Windows and connected to a 802.11g WLAN. Then, the card works again under Linux. If anyone finds out how to reset the card to 802.11g without having to boot windows: Let us know!

{{HINT|Well, yes, it seems I have a workaround for this particular problem. There are some hints in the [http://ndiswrapper.sourceforge.net/mediawiki/index.php/FAQ#How_can_I_set_bit_rate.3F ndiswrapper-FAQ]. As I had the same problem as above, WLAN was unusable before.
Setting ''"iwpriv wlan0 network_type g"'' (or ''"iwpriv wlan0 network_type b"'' as you like) switches the card back to 2.4GHz channels.
}}

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably other versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

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

2006-12-17T12:03:19Z

Shamuki:

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

2006-12-17T11:56:57Z

Shamuki: /* Features */

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

2006-12-17T11:56:09Z

Shamuki: /* Features */

How to install ndiswrapper for the ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter

2006-12-10T11:53:33Z

Shamuki:

You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

===Quirks===
====Card gets stuck in 802.11n mode====
I had the machine running under windows, where no WLAN was available. When booting into Linux, the card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. I tried to change settings via iwconfig, without any effect (not even an error message, nothing in the logs). Windows must have left the card in a state where iwconfig cannot con figure it.

I rebooted into Windows and connected to a 802.11g WLAN. Then, the card works again under Linux. If anyone finds out how to reset the card to 802.11g without having to boot windows: Let us know!

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

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

2006-12-10T11:37:22Z

Shamuki: removed non-functional link

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

2006-12-10T11:35:55Z

Shamuki: /* Linux WiFi driver */

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

2006-12-10T11:35:26Z

Shamuki: added Link to download Windows driver

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

2006-12-10T11:32:13Z

Shamuki: adapted Layout

HOWTOs - Driver Installation

2006-12-10T11:21:32Z

Shamuki: /* Wireless LAN */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page holds information on how to make additional hardware work on your ThinkPad.

The pages linked here hold instructions for installing or configuring certain drivers to make them work with ThinkPad hardware. For an overview of the drivers themselves please look at the [[Drivers]] page.
|}

==Connectivity==
*[[How to setup Bluetooth|Bluetooth]] <tt>(How to enable and configure Bluetooth)</tt>
*[[How to make use of IrDA | IrDA]] <tt>(How to get IrDA working)</tt>

==Graphics==
* [[Additional options for the radeon driver | RADEON Driver for X]] <tt>(Additional options for the radeon driver)</tt>
* [[Fglrx | Proprietary RADEON Driver for X (fglrx)]]
* [[r300 | Open Source RADEON (ATI) Driver for X]]
* [[How to get TV-Out working on ATI graphic cards | TV-out on ATI chips]] <tt>(Get TV-out working)</tt>
* [[How to compile an experimental X server]]

==Input==
*[[How to configure the TrackPoint|TrackPoint configuration]] <tt>(How to make your TrackPoint behave as you wish)</tt>

==PowerManagement==
* [[How to get SpeedStep working on Coppermine-piix4-smi based ThinkPads | SpeedStep on piix4]] <tt>(How to make SpeedStep (cpufreq) work on Coppermine-piix4-smi based ThinkPads)</tt>
* [[How to get SpeedStep working on_P4-class-Celeron_based_ThinkPads | SpeedStep on P4-class Celeron]] <tt>(How to get SpeedStep working on P4-class-Celeron based ThinkPads)</tt>
* [[How to configure cpufreqd | cpufreqd]]{{footnote|1}} <tt>(How to configure the cpufreqd frequency scaling daemon)</tt>
* [[How to use cpufrequtils | cpufrequtils]]{{footnote|1}} <tt>(How to use the cpufrequtils frequency scaling utils)</tt>
* [[How to configure powernowd | powernowd]] {{footnote|1}} <tt>(How to configure the powernowd frequency scaling daemon)</tt>
* [[How to configure powersaved | powersaved]]{{footnote|1}} <tt>(How to configure the powersaved frequency scaling daemon)</tt>

==Safety & Security==
*[[How to enable the fingerprint reader|Fingerprint Reader]] <tt>(How to make pam use the fingerprint reader)</tt>
*[[How to protect the harddisk through APS]] <tt>(How to make automatic emergency disk head parking work)</tt>

==Sound==
*[[Script for configuring the CS4239 sound chip in PnP mode|CS4239 sound chip in PNP mode]] <tt>(How to make it work on the ThinkPad 600E)</tt>

==Wireless LAN==
* [[How to install ndiswrapper for the Intel 2200bg WLAN adaptor | ndiswrapper for Intel 2200bg]] <tt>(ndiswrapper configuration for intel/pro 2200BG)</tt>
* [[How to install ndiswrapper for the IBM 11a/b/g WLAN adaptor | ndiswrapper for IBM 11 a/b/g]] <tt>(ndiswrapper for IBM 11 a/b/g)</tt>
* [[How to install ndiswrapper for the ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter | ndiswrapper for
ThinkPad 11a/b/g/n]]<tt>(ndiswrapper for ThinkPad 11a/b/g/n)</tt>
* [[ipw2100]] <tt>(native Linux driver for Intel 2100)</tt>
* [[ipw2200]] <tt>(native Linux driver for Intel 2200/2915)</tt>
* [[madwifi]] <tt>(Linux driver for atheros chipsets)</tt>
* [[orinoco]] <tt>(Linux driver for Hermes/Prism chipsets)</tt>
* [[hostap]] <tt>(Alternative Linux driver for Hermes/Prism chipsets)</tt>
* [[How to install wpa_supplicant|wpa_supplicant]] <tt>(How to compile and configure wpa_supplicant)</tt>

==Additional Hardware==
* [[How to install the IBM Ultracam II driver | IBM UltraCam II]] <tt>(How to make the IBM UltraCam II work under Linux)</tt>

* [[How to get the internal SD-CARD working]] <tt>(Howto patch and build the modules)</tt>

{{footnotes|
#Don't forget that the newer kernels have fancier cpu frequency governors like OnDemand and Conservative that are easy to configure via SysFS. These governors are adequate in many situations and do not require user-space daemons such as cpufreqd, powersaved, or powernowd. Read more about it on the [[How to make use of Dynamic Frequency Scaling|Dynamic Frequency Scaling page]].
}}

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

2006-12-10T11:16:42Z

Shamuki: moved Howto to appropriate section

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
There's a howto for this driver at [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter]].

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

===Comments===
Help me improve this page! [http://thinkwiki.org/index.php?title=ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter&action=edit Edit] the above page, or post your comments here.

How to install ndiswrapper for the ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter

2006-12-10T11:14:22Z

Shamuki: /* ndiswrapper */

Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network's or ndiswrapper's fault. I was unable to reproduce this, though.

Update: The same prob just occurred to me with the Lenovo driver. I had the machine running under windows, where no WLAN was available. It must have left the card in a state where iwconfig cannot con figure it. Maybe it's related to the 802.11n caps of the card. When I connect to a 802.11g WLAN with windows, the card works again under Linux. If anyone finds out how to reset the card to 802.11g without having to boot windows: Let us know!

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

How to install ndiswrapper for the ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter

2006-12-10T11:13:48Z

Shamuki:

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network's or ndiswrapper's fault. I was unable to reproduce this, though.

Update: The same prob just occurred to me with the Lenovo driver. I had the machine running under windows, where no WLAN was available. It must have left the card in a state where iwconfig cannot con figure it. Maybe it's related to the 802.11n caps of the card. When I connect to a 802.11g WLAN with windows, the card works again under Linux. If anyone finds out how to reset the card to 802.11g without having to boot windows: Let us know!

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

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

2006-12-09T01:15:28Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network's or ndiswrapper's fault. I was unable to reproduce this, though.

Update: The same prob just occurred to me with the Lenovo driver. I had the machine running under windows, where no WLAN was available. It must have left the card in a state where iwconfig cannot con figure it. Maybe it's related to the 802.11n caps of the card. When I connect to a 802.11g WLAN with windows, the card works again under Linux. If anyone finds out how to reset the card to 802.11g without having to boot windows: Let us know!

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

===Comments===
Help me improve this page! [http://thinkwiki.org/index.php?title=ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter&action=edit Edit] the above page, or post your comments here.

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

2006-12-09T01:12:54Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network's or ndiswrapper's fault. I was unable to reproduce this, though.

Update: The same prob just occurred to me with the Lenovo driver. I had the machine running under windows, where no WLAN was available. It must have left the card in a state where iwconfig cannot con figure it. Maybe it's related to the 802.11n caps of the card. When I connect to a 802.11g WLAN with windows, the card works again under Linux. If anyone finds out how to reset the card to 802.11g without having to boot windows: Let us know!

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

===Comments===
Please post your comments here.

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

2006-12-09T01:09:53Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network's or ndiswrapper's fault. I was unable to reproduce this, though.

Update: The same prob just occurred to me with the Lenovo driver. I had the machine running under windows, where no WLAN was available. It must have left the card in a state where iwconfig cannot con figure it. Maybe it's related to the 802.11n caps of the card. When I connect to a 802.11g WLAN with windows, the card works again under Linux. If anyone finds out how to reset the card to 802.11g without having to boot windows: Let us know!

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-08T19:28:35Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network's or ndiswrapper's fault. I was unable to reproduce this, though.

Update: The same prob just occurred to me with the Lenovo driver. I had the machine running under windows, where no WLAN was available. It must have left the card in a state where iwconfig cannot con figure it. Maybe it's related to the 802.11n caps of the card.

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T21:28:36Z

Shamuki: /* ndiswrapper */

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network's or ndiswrapper's fault. I was unable to reproduce this, though.

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T14:22:54Z

Shamuki: /* No suspend with ndiswrapper */

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

====No suspend with ndiswrapper====
The machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test) if the ndiswrapper module is loaded. Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

With Suse 10.1 (and probably older versions), you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T14:20:21Z

Shamuki: /* No suspend with ndiswrapper */

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

====No suspend with ndiswrapper====
When the ndiswrapper module is loaded, the machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test). Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper

On Suse 10.1, you can tell powersaved to unload the module upon suspend. Edit /etc/powersave/sleep and change the values of the following two variables to contain ndiswrapper:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="ndiswrapper"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="ndiswrapper"
UNLOAD_MODULES_BEFORE_STANDBY="ndiswrapper"
If there are already any modules present, separate them with a single space.

For other distros a similar mechanism may exist. Any pointers are appreciated!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T12:20:08Z

Shamuki: /* No suspend with ndiswrapper */

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

====No suspend with ndiswrapper====
When the ndiswrapper module is loaded, the machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test). Unload the ndiswrapper module before suspending:
:~> sudo rmmod ndiswrapper
Maybe there's also a way to tell the suspend machinery to unload the module before suspending and reloading it when waking up. Any hints are welcome!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T12:19:09Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

====No suspend with ndiswrapper====
When the ndiswrapper module is loaded, the machine hangs upon Suspend to RAM (and most likely Suspend to Disk, too, although I didn't test). Unload the ndiswrapper module before suspending. Maybe there's also a way to tell the suspend machinery to unload the module before suspending and reloading it when waking up. Any hints are welcome!

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T12:05:24Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a [[Madwifi]] driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

===madwifi===
[[Madwifi]] has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T12:00:06Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with [http://ndiswrapper.sourceforge.net/ ndiswrapper], a madwifi driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30). Get it at [http://ndiswrapper.sourceforge.net/ ndiswrapper's sourceforge site].

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

===madwifi===
madwifi has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T11:58:23Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with ndiswrapper, a madwifi driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30).

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Enter your Thinkpad model number (mine is 2007VEH), go to "Software and Device Drivers" and search for the "ThinkPad 802.11abgn wireless LAN" driver. Click on the link and download the .exe file.
* Extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

===madwifi===
madwifi has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)

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

2006-12-06T11:55:07Z

Shamuki:

This is for the unknown Atheros device, PCI ID 168c:0024. I only got it working with ndiswrapper, a madwifi driver is not yet available (as of Dec 06, 2006).
__TOC__

===ndiswrapper===
Got it working on my T60 2007VEH by installing the windows driver via ndiswrapper. You need a recent version of ndiswrapper (I used driver version 1.30).

This is the procedure I used:

* Download the Windows driver from [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=HOME-LENOVO Lenovo/IBM's support site]. Search for your Thinkpad model and look out for the "Wireless LAN ThinkPad 11abgn for Windows" driver.
* extract its contents with cabextract:
:~> cabextract 7iwc16ww.exe
Extracting cabinet: 7iwc16ww.exe
extracting DATA1.CAB
extracting DATA1.HDR
extracting DATA2.CAB
extracting IBMTPI.XML
extracting IKERNEL.EX_
extracting IMDRV/WSIMD.CAT
extracting IMDRV/WSIMD.INF
extracting IMDRV/WSIMD.SYS
extracting IMDRV/WSIMDP.CAT
extracting IMDRV/WSIMDP.INF
extracting LAYOUT.BIN
extracting SETUP.EXE
extracting SETUP.INI
extracting SETUP.INX
extracting SETUP.ISS
extracting UNINSTLL.ISS
extracting WINXP_2K/AR5416.SYS
extracting WINXP_2K/NET5416.CAT
extracting WINXP_2K/NET5416.INF
extracting WLLANATH.TPI
* In the WINXP_2K directory, install the driver .inf file with ndiswrapper:
:~> cd WINXP_2K/
:~> sudo /usr/sbin/ndiswrapper -i NET5416.INF
installing net5416 ...
forcing parameter MapRegisters from 256 to 64
[...last line repeats a few times...]
Note that the last line only occurs with a recent version of ndiswrapper. I had to compile ndiswrapper from source to get the new version. This went smoothly on SUSE 10.1 with the kernel-developer selection installed.
* ndiswrapper (run as root) tells you that the driver is installed:
root:~> ndiswrapper -l
net5416 driver installed, hardware (168C:FF1D) present
Strange, the PCI ID changed. ndiswrapper reports it as 168C:FF1D, while lspci -l reports 168c:0024. Don't know what this means.
* load the ndiswrapper module:
root:~> modprobe ndiswrapper
* iwconfig shows the card:
root:~> iwconfig wlan0
wlan0 IEEE 802.11b ESSID:"youknowit"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with KNetworkManager running; it automatically connected to the network. ESSID and Access Point MAC are faked for this howto.

I must add that a few days ago, with another access point, the exact same procedure did not work. The card was tuned to some 5.?? GHz (maybe 802.11n?) and would not recognize the 802.11g network that was present. It also had WEP encryption in effect, which the AP in this howto does not have (it's a VPN). I suceeded to connect with another PCMCIA WLAN card, also driven by ndiswrapper, so it wasn't the network or ndiswrapper's fault. Have to wait until tonight to see if I can reproduce the failure, though.

===madwifi===
madwifi has no support yet for this card (as of Dec 06, 2006). Current models of the MacBook seem to be equipped with this card, too. Support is tracked by [http://madwifi.org/ticket/1001 madwifi ticket #1001]. There you'll also find some useful links. It was my source of information while trying to get this piece of hardware working, so thanks go out to the community at madwifi!

: [[User:Shamuki|Shamuki]] 12:41, 6 December 2006 (CET)