Bug#604613: ath5k driver refuses to get an IP address from dhclient in squeeze
Package:
linux-image-2.6.32-5-amd64
Version: 2.6.32-27
When I use the ath5k
driver, it fails to resolve an IP address from using the dhclient command. Here
are the commands that I entered:
ifconfig eth0 down
ifconfig wlan0
up
iwlist wlan0 scan
iwconfig wlan0 essid default
dhclient
wlan0
These steps worked with Lenny. The card that I'm using is an
SMCWPCI-G based Atheros card, which I believe uses the AR5007G
chipset.
Output from dmesg | grep ath5k:
[
5.689292] ath5k 0000:00:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ
17
[ 5.689353] ath5k 0000:00:09.0: registered as
'phy0'
[ 6.416794] ath5k phy0: Atheros AR2413 chip found
(MAC: 0x78, PHY: 0x45)
Output from kern | grep ath5k:
Nov 22
14:12:05 debian-box kernel: [ 5.621466] ath5k 0000:00:09.0:
PCI INT A -> GSI 17 (level, low) -> IRQ 17
Nov 22 14:12:05 debian-box
kernel: [ 5.621531] ath5k 0000:00:09.0: registered as
'phy0'
Nov 22 14:12:05 debian-box kernel: [ 6.231139]
ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
Nov 22 17:19:45
debian-box kernel: [ 5.766165] ath5k 0000:00:09.0: PCI INT A
-> GSI 17 (level, low) -> IRQ 17
Nov 22 17:19:45 debian-box kernel:
[ 5.766235] ath5k 0000:00:09.0: registered as 'phy0'
Nov
22 17:19:45 debian-box kernel: [ 6.469400] ath5k phy0:
Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
Nov 22 19:34:41 debian-box
kernel: [ 5.689279] ath5k 0000:00:09.0: PCI INT A -> GSI
17 (level, low) -> IRQ 17
Nov 22 19:34:41 debian-box kernel:
[ 5.689345] ath5k 0000:00:09.0: registered as 'phy0'
Nov
22 19:34:41 debian-box kernel: [ 6.299683] ath5k phy0:
Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
Nov 22 19:45:10 debian-box
kernel: [ 5.689292] ath5k 0000:00:09.0: PCI INT A -> GSI
17 (level, low) -> IRQ 17
Nov 22 19:45:10 debian-box kernel:
[ 5.689353] ath5k 0000:00:09.0: registered as 'phy0'
Nov
22 19:45:10 debian-box kernel: [ 6.416794] ath5k phy0:
Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
Output from kern | grep
wlan0:
Nov 22 14:14:52 debian-box kernel: [ 176.720056]
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 22 14:14:54 debian-box
kernel: [ 178.558439] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try
1)
Nov 22 14:14:54 debian-box kernel: [ 178.756014] wlan0: direct
probe to AP 00:15:e9:65:fb:86 (try 2)
Nov 22 14:14:54 debian-box kernel:
[ 178.956008] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 3)
Nov
22 14:14:55 debian-box kernel: [ 179.156007] wlan0: direct probe to AP
00:15:e9:65:fb:86 timed out
Nov 22 19:35:56 debian-box kernel: [
84.311427] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 22 19:37:32
debian-box kernel: [ 180.328121] wlan0: direct probe to AP
00:15:e9:65:fb:86 (try 1)
Nov 22 19:37:32 debian-box kernel: [
180.528011] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 2)
Nov 22
19:37:32 debian-box kernel: [ 180.602991] wlan0: direct probe
responded
Nov 22 19:37:32 debian-box kernel: [ 180.602995] wlan0:
authenticate with AP 00:15:e9:65:fb:86 (try 1)
Nov 22 19:37:32 debian-box
kernel: [ 180.800006] wlan0: authenticate with AP 00:15:e9:65:fb:86 (try
2)
Nov 22 19:37:32 debian-box kernel: [ 181.000007] wlan0:
authenticate with AP 00:15:e9:65:fb:86 (try 3)
Nov 22 19:37:33 debian-box
kernel: [ 181.200006] wlan0: authentication with AP 00:15:e9:65:fb:86
timed out
The only issue I can see is in the last result, which is
reporting authentication problems. However, I really don't know of any way of
correcting the problem. I did, however, test the ath5k module against two other
distros, Fedora 14, and Ubuntu 10.10, which use the 2.6.35 kernel and both were
able to connect successfully. So this may be an upstream problem that was
corrected, but wasn't ported back to this kernel. I don't know for sure because
I'm not a kernel developer.
Anyone willing to take a stab at
it?
Reply to: