Bug#681232: linux-image-3.2.0-3-amd64: Atheros WiFi Adapter couldn't find networks "gain
For what it's worth, the 3.5-1 kernel from experimental works for me
without the pcie_aspm=force option.
cat /proc/version
Linux version 3.5-trunk-amd64 (Debian 3.5-1~experimental.1)
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) )
#1 SMP Thu Aug 2 17:16:27 UTC 2012
lspci -v -xxx -s 07:00.0
07:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x
Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: AMBIT Microsystem Corp. Device 0422
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at b0200000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [60] Express Legacy Endpoint, MSI 00
Capabilities: [90] MSI-X: Enable- Count=1 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Kernel driver in use: ath5k
00: 8c 16 1c 00 07 00 10 00 01 00 00 02 08 00 00 00
10: 04 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 01 50 00 00 68 14 22 04
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00
40: 01 50 c2 01 00 00 00 00 00 00 00 00 00 00 00 00
50: 05 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 90 11 00 40 02 64 00 10 20 0a 00 11 3c 03 00
70: 48 00 11 10 00 00 00 00 c0 03 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.5-trunk-amd64 (Debian
3.5-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version
4.6.3 (Debian 4.6.3-1) ) #1 SMP Thu Aug 2 17:16:27 UTC 2012
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.5-trunk-amd64
root=UUID=9e1f0932-58eb-4450-b269-f390869c741d ro quiet splash
dmesg | grep ath5k
[ 5.348070] ath5k 0000:07:00.0: registered as 'phy0'
[ 6.065246] Registered led device: ath5k-phy0::rx
[ 6.065317] Registered led device: ath5k-phy0::tx
[ 6.065347] ath5k: phy0: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61)
dmesg | grep wlan0
[ 18.499336] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 31.154216] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 32.285974] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 38.692294] wlan0: authenticate with xx:xx:xx:xx:xx:xx
[ 38.696433] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[ 38.697925] wlan0: authenticated
[ 38.704030] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[ 38.706491] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411
status=0 aid=1)
[ 38.706874] wlan0: associated
[ 38.707705] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
I'd also built the 3.4.7 kernel from the sources at kernel.org. This
kernel worked okay for me without the pcie_aspm=force option. Not sure
why I didn't try the 3.4.4 kernel that was in experimental at the time.
I've read about a number of people having this issue thru the 3.3
kernels with various distros, and read the issue was supposedly fixed in
the 3.4 branch. I get the impression it's an upstream issue.
Reply to: