I see this after a suspend/resume cycle on a fresh install of Maverick onto an Asus F3Ke laptop. The atheros is apparently an AR5001 rev 01, PCI device ID is 1a3b:1026 which dmesg lists as an AR2425 (MAC 0xe2, PHY 0x70).
echoing 0, then 1, into the rfkill...state does not resolve the problem. Removing the modules and reloading them does not resolve the problem.
Removing the modules, performing a hibernate and restore, and then re-loading the modules *does* work, although somewhat laborious. Likewise removing the modules before a suspend and reloading them after a resume also does work.
As a consequence I have placed a file in /etc/pm/config.d/76-ath5k-modules.conf which says:
SUSPEND_MODULES="ath5k ath"
Not an ideal solution, but with this in place suspend/resume cycles work as expected.
I note that the kernel bug 12080 is CLOSED,UNREPRODUCIBLE and suggests it was fixed way back in 2.6.30 or so, but there's plenty of evidence in this bug report that (a) it still exists in Maverick (kernel 2.6.35) and (b) it is very much reproducible. See: https://bugzilla.kernel.org/show_bug.cgi?id=12080
I see this after a suspend/resume cycle on a fresh install of Maverick onto an Asus F3Ke laptop. The atheros is apparently an AR5001 rev 01, PCI device ID is 1a3b:1026 which dmesg lists as an AR2425 (MAC 0xe2, PHY 0x70).
echoing 0, then 1, into the rfkill...state does not resolve the problem. Removing the modules and reloading them does not resolve the problem.
Removing the modules, performing a hibernate and restore, and then re-loading the modules *does* work, although somewhat laborious. Likewise removing the modules before a suspend and reloading them after a resume also does work.
As a consequence I have placed a file in /etc/pm/ config. d/76-ath5k- modules. conf which says:
SUSPEND_ MODULES= "ath5k ath"
Not an ideal solution, but with this in place suspend/resume cycles work as expected.
I note that the kernel bug 12080 is CLOSED, UNREPRODUCIBLE and suggests it was fixed way back in 2.6.30 or so, but there's plenty of evidence in this bug report that (a) it still exists in Maverick (kernel 2.6.35) and (b) it is very much reproducible. See: https:/ /bugzilla. kernel. org/show_ bug.cgi? id=12080
Regards,
Andrew McMillan