mactel-support team mailing list archive

[Alex <alexanderlane@xxxxxxxxx>]

This bug is indeed present in Jaunty and affects AR5008 as well as
AR5418.

I've had far better luck connecting to WEP WAPs using Wicd (over the
shoddy performance attributed to n-m)

Wicd gets me connected to my preferred WAPs from startup -- but I'm
unable to reconnect upon resume (after suspend). Prabhanjan Kambadur
reports the same problem in this very thread. I'll take it to a new
report if that would be appropriate.

0b:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
-Ubuntu Jaunty on MacbookPro 3,1 "Santa Rosa" (dual-boot)
-ath9k is in use

Please let me know what else I can provide in the way of details.

-- 
[ath9k] AR5418 frequently fails to connect to WEP/WPA network
https://bugs.launchpad.net/bugs/278190
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.

Status in The Linux Kernel: Fix Released
Status in Mactel Support: New
Status in “linux” source package in Ubuntu: Triaged
Status in “network-manager” source package in Ubuntu: Invalid
Status in linux in Ubuntu Intrepid: Fix Committed
Status in network-manager in Ubuntu Intrepid: Invalid

Bug description:
The wireless network can be seen, and occasionally connects after a cold boot. Most of the time network-manager complains that the WEP/WPA key is not correct, pops up a dialogue repeatedly.

It may or may not obtain a DHCP lease. However, no data gets transmitted.

Scenario 1: (See comment by Dennis Heinson for another scenario)
Beta release updated 4/10/08 on a gen 2 MacBook Pro (atheros wifi) connecting to a BT home hub with WEP 64 bit encryption (configuration as shipped). No previous problems with Kubuntu 7.10 and the same hardware using self-compiled drivers.

Linux xxxxx-01 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC 2008 x86_64 GNU/Linux
NetworkManager 0.7.0.
03:00.0 Network controller: Atheros Communications Inc. AR5418 802.11abgn Wireless PCI Express Adapter (rev 01)

dmesg output:
[   67.910954] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   89.204588] wlan0: authenticate with AP 00:1f:9f:3d:0f:c5
[   89.405056] wlan0: authenticate with AP 00:1f:9f:3d:0f:c5
[   89.605035] wlan0: authenticate with AP 00:1f:9f:3d:0f:c5
[   89.805054] wlan0: authentication with AP 00:1f:9f:3d:0f:c5 timed out
[  100.984690] wlan0: authenticate with AP 00:1f:9f:3d:0f:c5
[  100.984764] wlan0: authenticate with AP 00:1f:9f:3d:0f:c5
[  100.987561] wlan0: authenticated
[  100.987572] wlan0: associate with AP 00:1f:9f:3d:0f:c5
[  100.990918] wlan0: RX AssocResp from 00:1f:9f:3d:0f:c5 (capab=0x411 status=0 aid=1)
[  100.990927] wlan0: associated
[  100.998059] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  111.684110] wlan0: no IPv6 routers present
[  152.817637] wlan0: disassociating by local choice (reason=3)
[  154.415879] wlan0: authenticate with AP 00:1f:9f:3d:0f:c5
[  154.415976] wlan0: authenticate with AP 00:1f:9f:3d:0f:c5
[  154.418307] wlan0: authenticated
[  154.418316] wlan0: associate with AP 00:1f:9f:3d:0f:c5
[  154.427591] wlan0: RX AssocResp from 00:1f:9f:3d:0f:c5 (capab=0x411 status=0 aid=1)
[  154.427603] wlan0: associated
[  499.651325] wlan0: disassociating by local choice (reason=3)