I noticed several posts about needing to reboot to restore wifi after a suspend/resume cycle, but I didn't see much for solutions or workarounds. I'm not sure this is exactly the right way to work around this issue, but if you create a script called /etc/pm/sleep.d/50-eee-wifi (be sure it's executable) and give it the contents below, it seems to alleviate the symptom.
All this does is tell Gnome's power manager to unload the wifi driver as the machine suspends and load it again as the machine comes back up. If I'm not mistaken, ACPI is detecting that Gnome's power manager is active and handing off control, so the /etc/acpi/resume.d/ and /etc/acpi/suspend.d/ scripts aren't executing. For reference, this is on a 1005HA running eeebuntu 3.0.1 NBR with a 2.6.29-1-netbook kernel (for the ath9k wifi driver).
#!/bin/bash # # eeepc wifi suspend/resume # Unload the ath9k module on suspend, and reload it on resume #
case "$1" in hibernate|suspend|sleep) rmmod ath9k ;; thaw|resume) modprobe ath9k ;; *) exit $NA ;; esac
Feel free to critique, correct, or show a better way. After several years away from Linux, I'm a bit rusty.
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum