FS#28193 - [linux] ath9k wlan0 stopped working after linux-3.2.2. update

Attached to Project: Arch Linux
Opened by Gavin (Glinx) - Tuesday, 31 January 2012, 09:39 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 17 April 2012, 13:36 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 12
Private No

Details

ath9k wlan0 stopped working after linux-3.2.2. update

All looks well during boot – no errors seen.
Network then manager times out.

iwconfig wouldn’t associate with the network (wep)
iwlist wlan0 scan finds my D-Link network
iwconfig wlan0 essid "D-Link" key "*****"
iwconfig still doesn’t associate with the network

No errors seen during this process.
Unfortunately the kernel log has now gone.
I've tired ath9k nohwcrypt=1 from forums (kernel line and modprobe.conf) without success.


Downgrading to linux (and headers) 3.2.1-1 solved problem.

This task depends upon

Closed by  Tobias Powalowski (tpowa)
Tuesday, 17 April 2012, 13:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.3.2-1
Comment by Gavin (Glinx) - Tuesday, 31 January 2012, 09:42 GMT
Line three should read; Network manager then times out.
Comment by Gavin (Glinx) - Tuesday, 31 January 2012, 14:00 GMT
To try and make this bug report complete, I upgraded back to linux-3.2.2 for the logs and also to try downgrading wireless_tools, without success. Interestingly with linux-3.2.2 ;

Tue Jan 31 12:18:20 2012: :: Restoring ALSA Levels [BUSY] Found hardware: "HDA-Intel" "Nvidia MCP77/78 HDMI" "HDA:1106e721,10438345,00100100 HDA:10de0002,10de0101,0010
Tue Jan 31 12:18:20 2012: Hardware is initialized using a generic method
Tue Jan 31 12:18:20 2012: [FAIL]

Why dose; Found hardware: "HDA-Intel" "Nvidia MCP77/78 HDMI"... show up with linux-3.2.2?

Boot log at http://dl.dropbox.com/u/10440533/boot
daemon log at http://dl.dropbox.com/u/10440533/daemon.log
kernel log at http://dl.dropbox.com/u/10440533/kernel.log
Comment by Filippo cucchetto (Cuke) - Wednesday, 01 February 2012, 11:50 GMT
i'm effected by the same issue. I solved reverting to linux-3.2.1-1 too
Comment by Gavin (Glinx) - Thursday, 02 February 2012, 13:02 GMT
Problem fixed!

I'll try to keep this concise. As a one finger typist this could otherwise be stressful.
WEP encryption was the problem. Changing the house router to WPA solved the kernel 3.2.2 issue.
Kernel upgrade now complete.

The bug for this can be seen at; http://thread.gmane.org/gmane.linux.kernel.wireless.general/84582/focus=84626
The patch is being worked on now.

The “Found hardware: "HDA-Intel" "Nvidia MCP77/78 HDMI..." that then showed on kernel 3.2.2 booting was fixed from either re-booting for a second time or, the sound card check and consequent “alsactl store” I did in-between re-booting.

For the first time my D-Link ath9k chipped PCI card now showed a connection speed of 270mb. Usually this was only 54mb, so now in house file transfers should be a lot faster.
One thing I learned though being affected by this bug is that wifi cards have built-in “throttle-down”. See; http://linuxcommand.org/man_pages/iwconfig8.html for all the info.
What this meant for me and possibly others is that when you see network manager or iwconfig (wlan0) reporting low speeds, it may just be doing its correct job. Use 'sudo iwconfig wlan0 bit *M' to keep at your cards top speed, or 'sudo iwconfig wlan0 bit *M auto' to use throttle-down and save power, chip-life, and interference (replace * with your cards rated speed).

All seems good until you realise your connection speed is now very very very slow!
This is where the 'options ath9k nohwcrypt=1' entry in your etc/modprobe.d/modprobe.conf file comes in handy. After a re-boot its back up to full speed again.

iwconfig reports “Tx excessive retries” but I strongly suspect this is caused by the connection speed increase from 54mb to 270mb. I'll test later.

I think this covers all of my confusion and problems over the past few days regarding linux-3.2.2.
I think also the reason for the confused forum threads as well. If you had WEP like me (I live out in the country by the way), time to update all the family iPods, 3DS's, Wii's and cell phones!

Forum thread at https://bbs.archlinux.org/viewtopic.php?pid=1051580#p1051580
Comment by Troy Cotter (trc) - Saturday, 04 February 2012, 06:52 GMT
I am also having issues with this, there is a topic on the forums which I believe would likely be relevant.

https://bbs.archlinux.org/viewtopic.php?pid=1050620
Comment by Gavin (Glinx) - Saturday, 04 February 2012, 10:23 GMT
NOT fixed!

I was premature in my findings,It still slowed down!
By best findings after another day of perfect time wasting are as follows;
wicd with “iwconfig wlan0 power off” - This throttles down to 54mb again(!) and nothing in modprobe.d

@trc
Thank you
Comment by Krishnan (kgas) - Wednesday, 08 February 2012, 14:52 GMT
Did any one try compat-wireless-patched from aur? which works well in my case.
Wireless card details:
05:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
for the records.
Kernel:3.2.5-1-ARCH


Comment by David Bernard (Dav) - Friday, 10 February 2012, 15:13 GMT
Same issue for me with Atheros AR2427 on ASUS EEE PC 1001 PX. dhcpcd Timed out on my wep encrypted wifi.
Comment by Gavin (Glinx) - Friday, 10 February 2012, 19:17 GMT
This was a sad week for me.
After problems with Arch over the past couple of weeks or so with wifi and glibc, and no (that I've seen) official response in the forums or on this bug report regarding the wifi issue, I moved to Debian for a stable trouble free system. Just couldn't wait any longer.
I hope these issues get sorted out soon, and look forward to hopefully returning to Arch in the future. Best wishes to all.
Comment by Troy Cotter (trc) - Friday, 10 February 2012, 22:21 GMT
This is a problem that will be fixed upstream. When you live on the bleeding edge these things can and do happen from time to time. If you aren't ready to apply your own fixes or patches and/or patiently wait for them to be discovered and applied, than Arch Linux might not be for you.

However, I will say it is always sad to see someone leave Arch. :(
Comment by Troy Cotter (trc) - Saturday, 11 February 2012, 07:33 GMT
In the meantime as a workaround I'm using the long term support kernel (linux-lts) which works quite well.
Comment by Eskil Andersen (eskil) - Tuesday, 14 February 2012, 06:13 GMT
If you can't connect to the internet try first removing the ath9k module by typing "modprobe ath9k -r" then do the "modprobe ath9k nohwencrypt=1".
I, myself couldn't get it to work before first removing the module and then adding it back with the nohwencrypt flag.

Comment by Filippo cucchetto (Cuke) - Tuesday, 14 February 2012, 23:22 GMT
Ok what Eskil said is almost correct. I can successfully connect to my ap with
1) modprobe -r ath9k
2) modprobe ath9k nohwcrypt=1 (Eskil used nohwencrypt=1")

for a temporary workaround just add this line to your /etc/modprobe.d/modprobe.conf
options ath9k nohwcrypt=1
Comment by André Ventura (afv) - Friday, 17 February 2012, 20:38 GMT
Thank you so much Filippo! That worked for me (linux 3.2.6-2).
Comment by Troy Cotter (trc) - Saturday, 18 February 2012, 06:45 GMT
I never really had problems with being able to connect to my access point, the issue was with frequent dropped connections and slow speed.
Comment by Vladimir (_v_l) - Thursday, 05 April 2012, 23:39 GMT
I'm not sure if it is related but after I upgraded my notebook to kernel 3.3.1 wifi stops to work, I found several reports about that:
https://www.zarb.org/pipermail/mageia-dev/2012-April/013848.html
http://www.spinics.net/lists/linux-wireless/msg87748.html

P.S. Should I reopen the task vs. new kernel version?
Comment by Lubos Kolouch (kolcon) - Friday, 06 April 2012, 20:28 GMT
I am seeing the same issue with 3.3.1-1 too... works only when downgraded kernel to 3.3-1...
Comment by Troy Cotter (trc) - Friday, 06 April 2012, 20:30 GMT
I experienced the same problem in Gentoo so this is definitely something to be reported upstream.
Comment by Simonas (nagi) - Sunday, 08 April 2012, 18:56 GMT
After upgrade from 3.2.14-1 to 3.3.1-1 it stopped working for me too.
Comment by ofek levinson (ofek) - Wednesday, 11 April 2012, 13:27 GMT
3.3.1-1 was the problem in my case too, for the time being reverting one kernel ver back solved the problem,
though that still is not a solution.
Comment by Cássio Pereira (cpereira) - Friday, 13 April 2012, 22:14 GMT
Hi. I was also hit by this bug on my laptop. It seems 3.3.2 solved this issue. I see two fixes for ath9k in http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.3.2 regarding connection failures.
Comment by Cássio Pereira (cpereira) - Tuesday, 17 April 2012, 12:15 GMT
Ok. I just installed 3.3.2-1 on my laptop and wireless is working again. At least for me this bug is closed.

Loading...