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 #1316 (new defect)

Opened 15 years ago

Last modified 15 years ago

Can't connect to AP - PowerPC, AR5005GS (AR2414)

Reported by: Assigned to:
Priority: minor Milestone:
Component: madwifi: other Version: v0.9.3
Keywords: Cc:
Patch is attached: 0 Pending:


I have an embedded system with a PowerPC (freescale MPC5200). Now I try to use a wlan card with the AR5005GS chipset on this embedded system.

Compiling and loading of the modules works fine (thanks, that was a great work). When loading the driver he says wifi0: Atheros 5212: mem=0x40000000, irq=0 . Is this correct, because my card has another chipset?

But i can't connect to our access point. Other wlan cards are working fine - with the same system, at the same place.

What I do:

iwconfig ath0 essid "<name>" key "s:<asciikey>" 
iwconfig ath0 

I get the following output

ath0      IEEE 802.11b  ESSID:"<name>"
          Mode:Managed  Channel:0  Access Point: 00:00:00:00:00:00
          Bit Rate:0kb/s   Tx-Power:0 dBm   Sensitivity=0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:<hexkey>   Encryption mode:restricted
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Afterwards, when I call: ifconfig ath0 up I get the following messages:

wifi0: ath_chan_set: unable to reset channel 7 (2442 MHz) flags 0xc0 'Hardware didn't respond as expected' (HAL status 3)
wifi0: ath_chan_set: unable to reset channel 2 (2417 MHz) flags 0xc0 'Hardware didn't respond as expected' (HAL status 3)
... <for all channal numbers> ...

What can I do?

Thanks Widi

Change History

(in reply to: ↑ description ; follow-up: ↓ 2 ) 05/16/07 06:42:58 changed by mrenzmann

Replying to

Is this correct, because my card has another chipset?

Yes. AR5002 and later are reported as 5212, so this is expected behaviour.

(in reply to: ↑ 1 ) 05/21/07 20:38:21 changed by anonymous

Hello mrenzman,

thank you, for your message. Now I know, that the driver is loaded correct.

But what means the meassage 'Hardware didn't respond as expected'? Isn't my card supported?


(follow-up: ↓ 4 ) 05/22/07 12:05:29 changed by

card is supported, problem is somewhere else - if card would not be supported it will throw another HAL status. Problem could be in broken HAL for that platform, or something is broken in driver - that IRQ 0 seems to me a bit odd, if you put there another card - working one - it is be on IRQ 0 too ?

(in reply to: ↑ 3 ) 05/23/07 10:45:05 changed by

Replying to

it is be on IRQ 0 too ?

Yes, I have a working (but discontinued) card with an Agere chipset. That card uses IRQ 0 too and works fine. Using IRQ 0 is little bit strange, but our board is designed that way.