Difference between revisions of "ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter"
(→Draft n support in Linux) |
(changed categorization) |
||
| (63 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
{| width="100%" | {| width="100%" | ||
|style="vertical-align:top" | | |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"> | <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right"> | ||
| − | + | This is a WiFi Adapter that is installed in a Mini-PCI Express slot IBM/Lenovo partnumber 42T0825 [http://www-307.ibm.com/pc/support/site.wss/MIGR-64222.html] | |
| − | This is a WiFi Adapter that is installed in a Mini-PCI Express slot IBM partnumber 42T0825 [http://www-307.ibm.com/pc/support/site.wss/MIGR-64222.html] | ||
| − | + | = Features = | |
* Chipset: Atheros AR5418/AR5008 | * Chipset: Atheros AR5418/AR5008 | ||
* Integrated Mac Processor and Radio Chip: Atheros, unknown model | * Integrated Mac Processor and Radio Chip: Atheros, unknown model | ||
| Line 16: | Line 14: | ||
|} | |} | ||
| − | + | = Identification = | |
| − | To determine the chipset your | + | To determine the chipset your card uses, issue the following commands: |
# update-pciids | # update-pciids | ||
| Line 23: | Line 21: | ||
03:00.0 Network controller: Atheros Communications, Inc. AR5418 802.11a/b/g/n Wireless PCI Express Adapter (rev 01) | 03:00.0 Network controller: Atheros Communications, Inc. AR5418 802.11a/b/g/n Wireless PCI Express Adapter (rev 01) | ||
| − | If you get | + | If you get something different than above despite having the most current PCI IDs, please report it here! |
| + | =ath9k= | ||
| + | There is now active development of a free driver [[ath9k]] that aims to fully support the draft 11n protocol. It is available in the mainline linux kernel starting with 2.6.27 and therefore automatically included in any distribution running this kernel (eg. Ubuntu Intrepid Ibex). The version in this latest kernel however does not support "aggregation" which basically means you will only see a slight increase in speed from the 11g protocol (mesured as 25 Mb/s vs 20Mb/s). If your distribution does not yet include this kernel (aheghm Debian), you'll have to [[How to install the development version of atk9k|jump through a few hoops]]. | ||
| − | = | + | =madwifi= |
| − | + | Madwifi is a native linux driver that used to use a binary-only HAL and so must be compiled separately from the kernel. The HAL has recently been opened up, however with the development of ath9k mentioned above, the future of this project in particular with regard to this chipset is uncertain. It does not support the draft 11n protocol, but will work in "legacy" 11g mode. Support for this chipset was initially planned for release 0.9.4, but this inclusion had to be [http://www.madwifi.org/wiki/Releases/0.9.4#Announcement postponed] as a critical update with a bug fix for compilation with the 2.6.24 kernel was necessary before the pre-release trunk was sufficiently stable. Thus, it is still necessary to download the prerelease snapshot from trunk using subversion. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
There is a [[How_to_checkout_and_install_madwifi_experimental_driver_for_ar5008 | howto]], which describes the procedure for getting the snapshot to work. | There is a [[How_to_checkout_and_install_madwifi_experimental_driver_for_ar5008 | howto]], which describes the procedure for getting the snapshot to work. | ||
| Line 39: | Line 33: | ||
There is an new ticket for this card at [http://madwifi.org/ticket/1243 madwifi-branch, #1243]. | There is an new ticket for this card at [http://madwifi.org/ticket/1243 madwifi-branch, #1243]. | ||
| + | <nowiki>Insert non-formatted text here</nowiki> | ||
| − | + | = Using the Windows Driver in Linux = | |
| − | |||
| − | |||
| − | + | If you have a weak stomach for pre-release software, you can always use "ndiswrapper" (>= 1.29) to wrap the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver] supplied by Lenovo. This isn't as bad as you think. It does work like a charm, but you may have problems if you're using a 64 bit kernel since it's not clear that a 64 bit windows XP driver exists (ndiswrapper currently doesn't support Vista drivers). Here's the [[How_to_install_ndiswrapper_for_the_ThinkPad_11a/b/g/n_Wireless_LAN_Mini_Express_Adapter | Howto]]. | |
| − | |||
| − | |||
| − | + | =Problems/Bugs?= | |
| + | ==[http://en.wikipedia.org/wiki/Non-maskable_interrupt Non-Maskable Interrupt] with madwifi== | ||
| + | {{NOTE|This problem appears to be more or less fixed with recent subversion snapshots. If you are still experiencing this, try upgrading to the latest version.}} | ||
| − | + | A number of folks have reported getting errors while using the experimental madwifi driver with the AR5418. After hours of flawless operation, the Kernel sometimes throws an NMI after which, the wifi dies. Aside from rebooting, suspending (to ram or disk) and resuming seems to be the only method to recover. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | A number of folks have reported getting errors while using | ||
<pre> | <pre> | ||
| Line 110: | Line 64: | ||
[http://sourceforge.net/mailarchive/forum.php?thread_name=20070809145900.GD16023%40hank.org&forum_name=madwifi-users] | [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 | + | {{HINT|There's a [http://madwifi.org/ticket/1017 ticket on madwifi] with some discussion and suggestions for the rx FIFO overrun problem.}} |
| − | === | + | A '''possible''' preventitive measure is issuing the command |
| + | {{cmdroot|iwpriv <device> bgscan 0}} | ||
| + | each time you load the driver. To make this change "permanent", you could add this command to your distribution's ifup networking scripts as described below. | ||
| + | ===Debian=== | ||
| + | Open up {{path|/etc/network/interfaces}} in a text editor and find the entry for your wireless device. Which should look something like | ||
| + | <pre> | ||
| + | iface wlan0 inet manual | ||
| + | wpa-driver madwifi | ||
| + | wpa-roam /etc/network/wpa_supplicant.conf | ||
| + | </pre> | ||
| + | and add the line | ||
| + | <pre> | ||
| + | post-up iwpriv wlan0 bgscan 0 | ||
| + | </pre> | ||
| + | to the end of it where of course you substitute your interface name (e.g., "ath0") for "wlan0". | ||
| − | + | = Hardware switch = | |
| − | + | {{Note_wlan_hardware_switch}} | |
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. | 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}} | * {{R60}}, {{R60e}} | ||
* {{T60}}, {{T60p}} | * {{T60}}, {{T60p}} | ||
| − | * {{X60}}, {{X60s}}, {{ | + | * {{X60}}, {{X60s}}, {{X60_Tablet}} |
* {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}} | * {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}} | ||
| Line 132: | Line 100: | ||
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver at Lenovo] | * [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-66449 Windows driver at Lenovo] | ||
| − | [[Category: | + | [[Category:WLAN Adapters]] |
Latest revision as of 12:26, 16 November 2020
|
This is a WiFi Adapter that is installed in a Mini-PCI Express slot IBM/Lenovo partnumber 42T0825 [1] ContentsFeatures
|
|
Identification
To determine the chipset your card uses, issue the following commands:
# update-pciids # lspci | egrep -i 'network|atheros|wireless' 03:00.0 Network controller: Atheros Communications, Inc. AR5418 802.11a/b/g/n Wireless PCI Express Adapter (rev 01)
If you get something different than above despite having the most current PCI IDs, please report it here!
ath9k
There is now active development of a free driver ath9k that aims to fully support the draft 11n protocol. It is available in the mainline linux kernel starting with 2.6.27 and therefore automatically included in any distribution running this kernel (eg. Ubuntu Intrepid Ibex). The version in this latest kernel however does not support "aggregation" which basically means you will only see a slight increase in speed from the 11g protocol (mesured as 25 Mb/s vs 20Mb/s). If your distribution does not yet include this kernel (aheghm Debian), you'll have to jump through a few hoops.
madwifi
Madwifi is a native linux driver that used to use a binary-only HAL and so must be compiled separately from the kernel. The HAL has recently been opened up, however with the development of ath9k mentioned above, the future of this project in particular with regard to this chipset is uncertain. It does not support the draft 11n protocol, but will work in "legacy" 11g mode. Support for this chipset was initially planned for release 0.9.4, but this inclusion had to be postponed as a critical update with a bug fix for compilation with the 2.6.24 kernel was necessary before the pre-release trunk was sufficiently stable. Thus, it is still necessary to download the prerelease snapshot from trunk using subversion.
There is a howto, which describes the procedure for getting the snapshot to work.
There is an old ticket for this card at madwifi, #1001.
There is an new ticket for this card at madwifi-branch, #1243. Insert non-formatted text here
Using the Windows Driver in Linux
If you have a weak stomach for pre-release software, you can always use "ndiswrapper" (>= 1.29) to wrap the Windows driver supplied by Lenovo. This isn't as bad as you think. It does work like a charm, but you may have problems if you're using a 64 bit kernel since it's not clear that a 64 bit windows XP driver exists (ndiswrapper currently doesn't support Vista drivers). Here's the Howto.
Problems/Bugs?
Non-Maskable Interrupt with madwifi
NOTE!
This problem appears to be more or less fixed with recent subversion snapshots. If you are still experiencing this, try upgrading to the latest version.
A number of folks have reported getting errors while using the experimental madwifi driver with the AR5418. After hours of flawless operation, the Kernel sometimes throws an NMI after which, the wifi dies. Aside from rebooting, suspending (to ram or disk) and resuming seems to be the only method to recover.
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
wifi0: rx FIFO overrun; resetting wifi0: rx FIFO overrun; resetting wifi0: rx FIFO overrun; resetting
See the following threads and bug reports: [2] [3] [4] [5] [6]
Hint:
There's a ticket on madwifi with some discussion and suggestions for the rx FIFO overrun problem.
A possible preventitive measure is issuing the command
# iwpriv <device> bgscan 0
each time you load the driver. To make this change "permanent", you could add this command to your distribution's ifup networking scripts as described below.
Debian
Open up /etc/network/interfaces in a text editor and find the entry for your wireless device. Which should look something like
iface wlan0 inet manual
wpa-driver madwifi
wpa-roam /etc/network/wpa_supplicant.conf
and add the line
post-up iwpriv wlan0 bgscan 0
to the end of it where of course you substitute your interface name (e.g., "ath0") for "wlan0".
Hardware switch
NOTE!
In addition to hard-switching the wireless card, the switch also generates an acpi event on transition from hi->lo and vice versa. It is however the same event in both directions.
