when I updated the ArchLinux live-USB kernel recently (starting from a vanilla 1.1.3 live-USB), to version 4.0-1 (via pacman -Syu), the B3's WiFi adaptor failed to start up. To check this wasn't a kexec (or systemd)-related issue, I then built kernel 4.0.0 on the vanilla (1.3.2) Gentoo image (from gentoo-sources-4.0.0), and experienced exactly the same problem.
If I run (on Gentoo; I get the same on Arch):
Code: Select all
b3 ~ # uname -a
Linux b3 4.0.0-gentoo-b3 #1 Fri Apr 24 17:40:02 BST 2015 armv5tel Marvell Kirkwood (Flattened Device Tree) GNU/Linux
b3 ~ # dmesg | grep -C 1 ath
[ 13.196776] pci 0000:00:01.0: enabling device (0140 -> 0142)
[ 13.196830] ath9k 0000:01:00.0: enabling device (0140 -> 0142)
[ 13.307852] ath: phy0: Couldn't reset chip
[ 13.307877] ath: phy0: Unable to initialize hardware; initialization status: -5
[ 13.307904] ath9k 0000:01:00.0: Failed to initialize device
[ 13.308014] ath9k: probe of 0000:01:00.0 failed with error -5
[ 13.352647] cfg80211: World regulatory domain updated:
Code: Select all
b3 ~ # lspci -v
00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e0000000-e00fffff
Prefetchable memory behind bridge: 00000000-000fffff
01:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Qualcomm Atheros Device 309a
Flags: fast devsel, IRQ 85
Memory at e0000000 (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
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Kernel modules: ath9k
Code: Select all
b3 ~ # uname -a
Linux b3 3.18.6-gentoo-b3 #4 Tue Feb 10 14:42:20 GMT 2015 armv5tel Marvell Kirkwood (Flattened Device Tree) GNU/Linux
b3 ~ # dmesg | grep -C 1 ath
[ 12.947406] pci 0000:00:01.0: enabling device (0140 -> 0142)
[ 12.947460] ath9k 0000:01:00.0: enabling device (0140 -> 0142)
[ 13.373798] ath: EEPROM regdomain: 0x60
[ 13.373818] ath: EEPROM indicates we should expect a direct regpair map
[ 13.373849] ath: Country alpha2 being used: 00
[ 13.373864] ath: Regpair used: 0x60
[ 13.412364] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 13.413361] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xe1ea0000, irq=85
[ 13.432889] ath9k 0000:01:00.0 wlp1s0: renamed from wlan0
[ 13.433837] systemd-udevd[916]: renamed network interface wlan0 to wlp1s0
Code: Select all
b3 linux # dmesg | grep -C 5 ath
[ 11.566271] input: gpio-keys as /devices/platform/gpio-keys/input/input0
01:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Qualcomm Atheros Device 309a
Flags: bus master, fast devsel, latency 0, IRQ 85
Memory at e0000000 (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
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: ath9k
Kernel modules: ath9k
Does anyone have any ideas? I'm afraid I'm a bit swamped with RISC-V stuff at the moment >< However, since Arch Linux live-USB users will automatically get the new kernel if they run pacman -Syu, and thereby find that their WiFi has stopped working, I'm keen to get a fix out for them (or at least a temporary version pin for the kernel and headers via an IgnorePkg stanza in /etc/pacman.conf...).
The (Gentoo) 4.0.0 kernel's .config I generated using make olddefconfig from the 1.3.2 image's version (3.18.6 kernel). That old (3.18.6) .config (where WiFi works fine) is available here. The 4.0.0 .config is available here, and a simple diff between them here.
Any help much appreciated!!
best,
sakaki