| 2008-09-08 13:34:12 |
Michael Rooney |
bug |
|
|
added bug |
| 2008-09-08 13:34:12 |
Michael Rooney |
bug |
|
|
added attachment 'hwdrivers' (hwdrivers) |
| 2008-09-08 23:21:45 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2008-09-08 23:21:45 |
Leann Ogasawara |
linux: statusexplanation |
|
Hi Mike,
Can you attach you dmesg output as well. You may also want to test installing the madwifi package that is available in one of our developers PPA's - https://launchpad.net/~timg-tpi/+archive . Thanks. |
|
| 2008-09-11 12:45:45 |
Michael Rooney |
bug |
|
|
added attachment 'dmesg' (dmesg) |
| 2008-09-11 12:46:12 |
Michael Rooney |
linux: status |
Incomplete |
New |
|
| 2008-09-11 12:46:12 |
Michael Rooney |
linux: statusexplanation |
Hi Mike,
Can you attach you dmesg output as well. You may also want to test installing the madwifi package that is available in one of our developers PPA's - https://launchpad.net/~timg-tpi/+archive . Thanks. |
|
|
| 2008-09-24 00:23:30 |
Michael Rooney |
description |
Using Intrepid Alpha 5 with an Atheros 5212/5213 (as identified by Hardware Test / lspci) and connecting to a WPA 2 Personal wireless network, the connection drops every 5-10 minutes, and when it is connected, the connection is very slow (bitwise, typically 10-100x slower than with Hardy). Often when reconnecting after dropping it will ask for the WPA key again, which is already saved, and will work after one or two times of just pressing Okay. The process ath5k_pci also consumes around 40-85% CPU during the connection process and also intermittently while the connection exists, making the computer unusable during this time (mouse is not very responsive).
This card worked fine on Gutsy and Hardy and did not experience these problems. This problem is easy to duplicate; I can boot into Hardy and have fast and stable wireless, and then boot again into Intrepid and have the experience described above on the same network. Note that I don't know that this issue is restricted to WPA 2 Personal networks; that is just my home network that I have to test.
Strangely enough this bug existed in Alpha 4, and I say strangely because that was Linux 2.6.26 which should have been using a different driver. Originally after doing a fresh install of Alpha 5, I didn't notice this bug, but now after a restart it seems to be back. I wonder if it is possible that it is using the wrong (old, restricted) driver, somehow? I have attached a screenshot of the Hardware Drivers application, which seems to display conflicting messages in the title and body.
Please let me know what further information is necessary.
Intrepid Alpha 5
Linux: 2.6.27.2.2
lspci line: 02:02.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) |
Using Intrepid Alpha 5 with an Atheros 5212/5213 (as identified by Hardware Test / lspci) and connecting to a WPA 2 Personal wireless network, the connection drops every 5-10 minutes, and when it is connected, the connection is very slow (bitwise, typically 10-100x slower than with Hardy). Often when reconnecting after dropping it will ask for the WPA key again, which is already saved, and will work after one or two times of just pressing Okay. The process ath5k_pci also consumes around 40-85% CPU during the connection process and also intermittently while the connection exists, making the computer unusable during this time (mouse is not very responsive).
This card worked fine on Gutsy and Hardy and did not experience these problems. This problem is easy to duplicate; I can boot into Hardy and have fast and stable wireless, and then boot again into Intrepid and have the experience described above on the same network. Note that I don't know that this issue is restricted to WPA 2 Personal networks; that is just my home network that I have to test.
Strangely enough this bug existed in Alpha 4, and I say strangely because that was Linux 2.6.26 which should have been using a different driver. Originally after doing a fresh install of Alpha 5, I didn't notice this bug, but now after a restart it seems to be back. I wonder if it is possible that it is using the wrong (old, restricted) driver, somehow? I have attached a screenshot of the Hardware Drivers application, which seems to display conflicting messages in the title and body.
Towards the bottom of dmesg (attached) there is all sorts of repetitive wireless output such as:
[ 601.255022] ath5k phy0: noise floor calibration timeout (2412MHz)
[ 601.255039] ath5k phy0: ath5k_chan_set: unable to reset channel (2412 Mhz)
[ 601.255048] wlan0: failed to set freq to 2412 MHz for scan
and then plenty of drops like:
[ 541.022613] wlan0: deauthenticated
[ 542.020141] wlan0: authenticate with AP 00:07:85:b3:cb:ee
[ 542.030863] wlan0: authenticated
[ 542.030881] wlan0: associate with AP 00:07:85:b3:cb:ee
Intrepid Alpha 5
Linux: 2.6.27.2.2
lspci line: 02:02.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) |
|
| 2008-09-24 00:23:30 |
Michael Rooney |
title |
Wireless on Atheros 5212/5213 drops often, is slow, and ath5k_pci consumes large amounts of CPU |
Wireless on Atheros 5213A drops often, is slow, and ath5k_pci consumes large amounts of CPU |
|
| 2008-10-06 00:15:18 |
Michael Rooney |
linux: status |
New |
Confirmed |
|
| 2008-10-06 00:15:18 |
Michael Rooney |
linux: importance |
Undecided |
Medium |
|
| 2008-10-06 00:15:18 |
Michael Rooney |
linux: statusexplanation |
|
Thanks coubi64, I will Confirm thanks to your input.
As an update for Leann, after more use with the madwifi it is an improvement but still a definite regression from Hardy. It is slower and doesn't seem to get as strong of a connection; I have had to reboot into my Hardy install to connect to lower signal networks or get faster speeds. |
|
| 2008-11-14 23:11:35 |
Michael Rooney |
linux: status |
Confirmed |
Fix Released |
|
| 2008-11-14 23:11:35 |
Michael Rooney |
linux: statusexplanation |
Thanks coubi64, I will Confirm thanks to your input.
As an update for Leann, after more use with the madwifi it is an improvement but still a definite regression from Hardy. It is slower and doesn't seem to get as strong of a connection; I have had to reboot into my Hardy install to connect to lower signal networks or get faster speeds. |
I did a fresh install of Intrepid today and my wireless seems to work very well out of the box. Since I originally reported this I'll mark it as fixed; if it isn't for others it might be a different issue. |
|
