ath5k broken after jaunty beta upgrade

[gkornelson]

Since upgrading to Jaunty Beta 1 this morning, my wireless (AR5006EG) has stopped working properly. It shows all of the networks and can connect, but typically begins failing intermittently afterwards. The Network Manager icon says that it is always connected, but my connection seems to hang for a long time before going again. I am getting terribly slow speeds now as well. My connection is 10 Mbps up/down, and I can get these speeds in Windows and on my other laptop, but since the upgrade to Beta this morning on my eeePC I have not been able to get anywhere near these speeds, and often no speed at all as my transfers just stop and hang for a while. This driver has been working fine for the last two weeks while I have been using Jaunty Alpha 6.

At least one other person appears to be having the same issue since upgrading:
<http://ubuntuforums.org/showthread.php?t=1108016>

My syslog keeps outputting the following line while the internet is hanging:

ubuntu kernel: [ 3441.231316] ath5k phy0: unsupported jumbo

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: ASUSTeK Computer INC. 1000H
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcCmdLine: root=UUID=dceab5f3-fb78-4e7a-bc14-93db15bf1ae3 ro quiet splash
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux

[Leann Ogasawara (leannogasawara)]

Hi gkornelson,

Can you try installing the linux-backports-modules-jaunty package? The reason I ask is that it has an updated compat-wireless stack. Please let us know if this helps resolve the issue. Thanks.

[gkornelson (gkornelson)]

Installing linux-backports-modules-jaunty package seems to have fixed these issues. I'm still seeing the occasional "unsupported jumbo" error, but at least the card seems to be running at full speed now. Thanks! I'll let you know if anything changes.

[gkornelson (gkornelson)]

My wireless has now gone back to spitting out the "unsupported jumbo" error and operating extremely slowly. Seems to work fine one minute, and then break the next.

[David Jobet (david-jobet)]

Hello, after having upgraded from intrepid (ath_hal + ath_pci) to jaunty (ath5k), I experience exactly the same issue.
When I do a /etc/init.d/networking restart I have more or less 1min to use the connection at full speed, and then it just disconnect or becomes painfully slow (sometimes < 1ko/sec).

Please help, my multimedia workstation is now useless !

lspci -v gives :
06:02.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)
        Subsystem: D-Link System Inc Device 3a18
        Flags: bus master, medium devsel, latency 168, IRQ 18
        Memory at e0000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: ath5k
        Kernel modules: ath5k

uname -a gives :
Linux vador 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

apt-cache showpkg linux-backports-modules-jaunty gives :
Package: linux-backports-modules-jaunty
Versions:
2.6.28.11.15 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_jaunty_main_binary-i386_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_jaunty_main_binary-i386_Packages
                  MD5: 38c0a1e32af36ac7d0d14b1e9989b240

Reverse Depends:
Dependencies:
2.6.28.11.15 - linux-backports-modules-jaunty-generic (5 2.6.28.11.15)
Provides:
2.6.28.11.15 -
Reverse Provides:

In /var/log/messages I have multiple instances of :
ath5k phy0: unsupported jumbo

[Don Newell (ducky12432)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.