Re: problems with madwifi and Atheros AR5418
Le (on) Thursday 04 September 2008 02:40, Celejar a écrit (wrote) :
>> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> This line generally appears when the card comes on-line; if all goes well,
> it should soon be followed by something like 'ADDRCONF(NETDEV_CHANGE):
> eth0: link becomes ready'
>
Well, the whole point is, it isn't followed by any "link becomes ready"
message (unless I modprobe -r ath9k && modprobe ath9k, which is a pain).
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> eth0: direct probe to AP 00:17:5a:4f:31:c0 try 1
> eth0 direct probe responded
> eth0: authenticate with AP 00:17:5a:4f:31:c0
> eth0: authenticated
> eth0: associate with AP 00:17:5a:4f:31:c0
> eth0: RX AssocResp from 00:17:5a:4f:31:c0 (capab=0x401 status=0 aid=53)
> eth0: associated
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
It's exactly what happens on my box /after/ I removed and reprobed the
driver, and what I would like to happen automatically.
> I'm not much of an expert, but here are a couple of suggestions:
>
> Try disabling WEP, and see if the problem persists.
It does.
> Try configuring the interface manually, without DHCP:
> ifconfig wlan0 up
> iwconfig wlan0 essid xxxxxxxx
> ifconfig wlan0 x.x.x.x
>
I tried. I doesn't change anything. The chip remains "non associated" to any
AP, and the only things I can see in syslog is the above mentionned "links
is not ready" message when I try tu use dhclient. Static IP configuration
doesn't work either.
Unless somebody comes with an idea about what I'm doing, I'll assume this is
a problem with the driver and report on ath9k-devel.
Thanks for your suggestions,
Manuel.
Reply to: