AR5212 not enabled

[Evan Prodromou]

When I boot up my computer with a AR5212/AR5213 with very latest 2.6.22-14 kernel (as of this date) in gutsy, the wireless adaptor isn't recognized (no ath0).

I tried modprobe'ing ath_hal manually, to no effect (lots of missing symbols).

Twiddling with the "Restricted Drivers Manager" shows the atheros chip installed, but has it in red (disabled). No indicator as to how to enable it.

Only way I could get it to work was to fall back to 2.6.22-13 kernel.

(And, yes, I'm fully aware that gutsy is unstable, and that it's available for testing only. This is your testing and here is your bug report! Enjoy.)

[Jim Tarvid (tarvid)]

I have a similar problem with an 8470WD card. ath0 fails to associate.

A simple but inelegant workaround is to do ifdown ath0 followed by ifup ath0

root@hans:/etc/network# dhclient
There is already a pid file /var/run/dhclient.pid with pid 10383
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Listening on LPF/ath0/00:20:a6:52:0c:f2
Sending on LPF/ath0/00:20:a6:52:0c:f2
Listening on LPF/eth0/00:0d:56:39:cd:ba
Sending on LPF/eth0/00:0d:56:39:cd:ba
Sending on Socket/fallback
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 4
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.20.1
bound to 192.168.20.121 -- renewal in 40398 seconds.
root@hans:/etc/network# ping 192.168.20.1
PING 192.168.20.1 (192.168.20.1) 56(84) bytes of data.
From 169.254.7.77 icmp_seq=1 Destination Host Unreachable
From 169.254.7.77 icmp_seq=2 Destination Host Unreachable
From 169.254.7.77 icmp_seq=3 Destination Host Unreachable

--- 192.168.20.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3010ms
, pipe 3
root@hans:/etc/network# ifdown ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 11747
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:20:a6:52:0c:f2
Sending on LPF/ath0/00:20:a6:52:0c:f2
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.20.1 port 67
root@hans:/etc/network# ifup ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:20:a6:52:0c:f2
Sending on LPF/ath0/00:20:a6:52:0c:f2
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.20.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.20.1
bound to 192.168.20.112 -- renewal in 42919 seconds.
root@hans:/etc/network# ping 192.168.20.1
PING 192.168.20.1 (192.168.20.1) 56(84) bytes of data.
64 bytes from 192.168.20.1: icmp_seq=1 ttl=64 time=0.919 ms
64 bytes from 192.168.20.1: icmp_seq=2 ttl=64 time=0.897 ms

--- 192.168.20.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.897/0.908/0.919/0.011 ms
root@hans:/etc/network#

There are lots of other atheros bug reports about and lots of recommendations to try various heroics, many of which are harmful.

I do not know where the problem lies.

Usual info follows:

root@hans:~# dmesg | gr...

[Harsh Singh (hisingh1)]

Try hardy... maybe the problem is solved

[Michael Nagel (nailor)]

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!