Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #1676 (new defect)

Opened 14 years ago

Last modified 14 years ago

Atheros AR5006EG behaves very erratically

Reported by: anonymous Assigned to:
Priority: minor Milestone:
Component: madwifi: other Version: trunk
Keywords: AR5006EG, unsupported Cc:
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

I outlined most of the problems in a mail to madwifi-users:

Along with the problems described there, I have the following issues:

  • Usually when trying to associate, the driver simply scans through the available frequencies and never finds the AP, while the same device with ndiswrapper finds the same AP immediately
  • If it does successfully associate with an AP, it takes 20-30 seconds to do so.

I have all the latest updates for kubuntu and the most recent (as of noon or so on November 30th) svn release of madwifi. There are no errors or log messages to signify that it might not be loading or running correctly.

Change History

12/04/07 15:55:01 changed by mentor

  • description changed.
  • summary changed from Atheros AR5006EG behaves very eratically to Atheros AR5006EG behaves very erratically.

12/04/07 16:02:08 changed by mentor

This is the contents of the referenced email:-

That's the error that repeats over and over again when I try to connect to a wireless network using wpa_supplicant and madwifi drivers. I've intermittently gotten success in fixing it, but everything always comes back to this error. Every once in a while, wpa_supplicant will toss in a "Association request to the driver failed" just for kicks.

Some information that might help:

OS: Kubuntu Gutsy

From lspci: 02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

Madwifi svn driver revision (It happens with the stable release too): 2756

WPA supplicant version: 0.5.8

Called with: sudo wpa_supplicant -D madwifi -i ath0 -c APlist/wpa_supplicant.conf -B (APlist is where the config is stored)

When I replace "-D madwifi" with "-D wext", it works for unencrypted networks but not encrypted networks.

Verbose output of error:

<2>Authentication with 00:00:00:00:00:00 timed out.
<1>Setting scan request: 0 sec 0 usec
<2>Trying to associate with 00:17:0e:08:55:13 (SSID='anl-cert' freq=2412 MHz)
<1>Cancelling scan request
<1>RSN: using IEEE 802.11i/D9.0
<1>WPA: using GTK TKIP
<1>WPA: using PTK CCMP
<1>WPA: using KEY_MGMT 802.1X
<1>Setting authentication timeout: 10 sec 0 usec
<2>Authentication with 00:00:00:00:00:00 timed out.

Does anyone have an idea of what could be causing this? WPA works when I use Knetworkmanager, so I don't think it's the driver itself, or else the GUI manager wouldn't work either.

I also have a few less-pressing issues:

Issue 1: When I attempt to associate with an access point that cannot be seen by my card, the bit rate is set to 5mb/s instead of 0kb/s. This suddenly started happening today, and never happened before today.


elliott@elliott-desktop:~/code/wireless$ sudo iwconfig ath0 essid "Doesn't Exist"
elliott@elliott-desktop:~/code/wireless$ sudo iwconfig ath0 ap EE:EE:EE:EE:EE:EE
elliott@elliott-desktop:~/code/wireless$ sudo ifconfig ath0 down
elliott@elliott-desktop:~/code/wireless$ sudo ifconfig ath0 up
elliott@elliott-desktop:~/code/wireless$ iwconfig ath0 
ath0 IEEE 802.11g ESSID:"Doesn't Exist" Nickname:""
     Mode:Managed Frequency:2.422 GHz Access Point: EE:EE:EE:EE:EE:EE
     Bit Rate:5 Mb/s Tx-Power:18 dBm Sensitivity=1/1
     Retry:off RTS thr:off Fragment thr:off
     Power Management:off
     Link Quality=0/70 Signal level=-89 dBm Noise level=-89 dBm
     Rx invalid nwid:8351 Rx invalid crypt:0 Rx invalid frag:0
     Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I've written code that relies on the bit rate being zero or nonzero to tell whether or not it has associated correctly, so this obviously breaks it. How do I fix this?

Issue 2: Speaking of using the bit rate to tell whether or not I am associated, is there any more reliable way to associate? I'm finding the "Set the essid and ap through iwconfig" method to be highly unreliable, as an AP that's 10 yards away with absolutely no obstructions might be reported as down once in every 8 or 9 tests, while the signal quality of that AP remains solid. I'd like to see a program that I can run that will go in, handle association, and return when and only when it was concretely sure that either association was successful or it would never be successful, and indicate the result in the output. Think of the way dhclient works, only with associating with an AP instead of IP configuration. Does a program like this exist, either driver-specific for Madwifi or more general?

Thanks for your help.

12/04/07 17:14:58 changed by mrenzmann

  • description changed.

(follow-up: ↓ 5 ) 12/20/07 10:34:35 changed by vic!

hi i also have a Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter ....wifi card thing... and i cant get it to work with ubuntu gutsy 7.10 its been really irritating. i see that you atleast got it to work partially.. is there a way you could help me any feed back is appreciated... here is a link to my original post in the ubuntu forums htt p:/ /ubuntuforums dot org/showthread.php?t=643750 well thanks!


(in reply to: ↑ 4 ) 12/20/07 10:38:00 changed by mrenzmann

Replying to vic!:

hi i also have a Atheros Communications, Inc. AR5006EG ... and i cant get it to work

This does not seem to match the topic of this ticket. It might be another case of what is described at lengths in #1192 and for which a experimental solution is available in #1679. If that does not help, please contact our regular support channels. Thanks.