mactel-support team mailing list archive

["Christopher M. Penalver" <christopher.penalver@xxxxxxx>]

Richard, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue?
Can you try with the latest development release of Ubuntu? ISO CD images
are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the
development release from a Terminal
(Applications->Accessories->Terminal). It will automatically gather and
attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the
issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
you've tested the upstream kernel, please remove the 'needs-upstream-
testing' tag. This can be done by clicking on the yellow pencil icon
next to the tag located at the bottom of the bug description and
deleting the 'needs-upstream-testing' text. As well, please comment on
which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not
boot, please add the tag: 'kernel-unable-to-test-upstream', and comment
as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

** This bug is no longer a duplicate of bug 945379
   168c:002b Wireless connection randomly drops -- ath9k

** No longer affects: network-manager (Ubuntu)

** No longer affects: network-manager (Ubuntu Intrepid)

** No longer affects: network-manager (Ubuntu Jaunty)

** No longer affects: linux (Ubuntu Jaunty)

** Attachment removed: "dmesg | grep wlan0"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/278190/+attachment/536507/+files/dmesg.txt

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: mactel-support
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.
https://bugs.launchpad.net/bugs/278190

Title:
  [ath9k] AR5418 frequently fails to connect to WEP/WPA network

Status in The Linux Kernel:
  Fix Released
Status in Mactel Support:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Intrepid:
  Fix Released

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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/278190/+subscriptions