Atheros AR5008 ath9k cannot connect to WPA

[lambengolmor]

In macbookpro 3.1 the atheros card AR5008 used with ath9k can't access to WPA network. The wireless card is perfectly working on open network

1) Ubuntu 8.10
2) probably the package involved is compat-wireless-ath9k, version 20080916-debgen1
3) I expect the card connects to the router given the right password and the right network
4) The card doesn't connect (if i can give you more technical information just tell me wich command I have to run)

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your bug report didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager. If you have trouble, do not hesitate to ask for more assistance. Thanks in advance.

[ramaxial (ramaxial)]

I have experience the same problem on Ubuntu 9.04 beta on Dell 1420 with Gigabyte GN-WI06N-RH (same chipset ,see link below) using wpa2.

What I have discovered (as far as I can tell) is that when you create the network profile it gets "Pre-Populated" with a wireless key other than the one you gave it. So in essence what appears to happen when you create a wireless network connection the key you give gets "appended" to the end of the pre-populated key as if you were in Bash and used >> command to append the key, so it really has 2 keys back to back in the key field, so it fails. If you create the connection and then go back and change the key to the correct key it work's ( at least for me), although it doesn't report the speed of the connection accurately, it has thus far worked flawlessly...

Bottom line athk9 works great with wpa2 AES except I cant get accurate network speed info.

Card I am using...
##############
http://www.oxfordtec.com/us/p125/GIGABYTE-GN-WI06N-RH-802.11N-a/b/g/n-draft-2.0-miniPCI-wireless---Atheros-AR5008-chipset-AirCruiser-N300-Dual-Band-Mini-Card/product_info.html

I would give you more info (ie dmesg) , but I am using a different machine as I write this. Please let me know if more info is needed..

Regards

[ramaxial (ramaxial)]

Update...

The card works but randomly drops its connection, about every minute or two, shutting down and then re-establishing the connection restores it temporarily. There is a bug report already created for this problem.

[v_lestat (v-lestat)]

this has been an ongoing, NEVER resolved issue with the atheros 802.11n cards since pre 8.04
WHY its still not resolved is enough to make me never use Ubuntu on my laptop. not until they fix this issue.

the issue has been reported mulitple multiple times and why its not fixed is amazingly silly. ignoring issues only loses customers and just gives the Ubuntu team a bad name.

fix the issue, this card has been out for WAY over a year

[Gary (gary-geisbert)]

I'm still seeing this behavior in 9.04 with this:

06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)

For some reason, if you type:

  /etc/init.d/NetworkManager stop

And then use iwconfig to setup the wireless network manually, it works great. I'm currently at starbucks on an open network, so I just typed:

  iwconfig wlan0 essid attwifi
  dhclient wlan0

Seems like NetworkManager has some strange issue with this card...?

[lambengolmor (nicola-feltrin)]

Upgraded to Jaunty, installed linux-backports-modules-jaunty and wicd. Now works fine. (Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01))

[Ryan (ersatzryan)]

I was having the same problems, I installed linux-backports-modules-jaunty and wicd, rebooted and has been working ever since, AR5008X

[Alexander Sack (asac)]

Most likely just using linux-backports-modules-jaunty will also work for networkmanager too.

p.s. Ryan, please keep this wicd stuff out of bugs. Its not helpful even though it might work.

[Luis R. Rodriguez (mcgrof)]

Issue is fixed in lbm, please close.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!