2008/10/16 Daniel Kahn Gillmor <[EMAIL PROTECTED]>: > I'm using kernel 2.6.26, and madwifi for the wireless. madwifi > creates two ethernet devices: wifi0 and ath0. Since i'm using > network-manager, when i echo 1 > /sys/devices/platform/eeepc/wlan && > modprobe ath_pci, both wifi0 and ath0 enter the UP state (according to > "ip link"). > > But i notice that when i put the system to sleep and then wake it up > again, ath0 is "UP", but wifi0 is *not* UP. In this state, i can't > even scan for networks. At the most fine-grained level (with full > superuser powers), i appear to be able to fix this with the command: > "ip link set wifi up". But i'm often not running as the superuser, so > it's quickest to just hit Fn+F2 twice to disable and then re-enable > the wireless (because they both come back up in the UP state). But > why would wifi0 not be up upon wake from sleep? Has anyone else > experienced this? Any suggested workarounds?
I've put a quick "ifconfig wifi0 up" at the end of the sleep.sh script, solves the issue, don't know why it happens but as you observed, bringing up the wifi0 sorts it out. -- Andrew Williams / Nik_Doof w: http://tensixtyone.com/ e: [EMAIL PROTECTED] _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
