Quote:
Originally Posted by rad1er
I think I'm back to believing that in linux resume and wireless is too fussy. It's also aggravating  I am on the road today with this laptop which I though was working, but when I opened it up just now it resumed ok but wireless was not working. Finally (after a few minutes) the network I wanted to connect to was found but it wanted a passphrase-for an open network. I had to reboot and then it worked. If you have to always reboot to get services working-something is wrong. |
Normally it's a question of finding the correct services to stop and start.. If you're system is not on the whitelist it can get tricky to get a good suspend/resume going, but many times you will have success. Don't get too stressed out with it and try when you have time.. if not, booting normally should be quick enough as a 'workaround'.
With openSUSE 11.0 my laptop suspends without extra tuning, but this was the contents of the file that I had placed in the sleep.d for 10.3
Code:
#!/bin/bash
case $1 in
hibernate)
service network stop
modprobe -r ipw3945
sleep 1
;;
suspend)
service network stop
modprobe -r ipw3945
sleep 1
;;
thaw)
echo "oh, suspend to disk is over, we are resuming..."
sleep 1
modprobe ipw3945
sleep 2
service network start
;;
resume)
sleep 1
modprobe ipw3945
sleep 2
service network start
;;
*) echo "somebody is calling me totally wrong."
;;
esac
ipw3945 is my wifi driver that needed to be unloaded and reloaded along with the network service. Notice the module loading before starting the network service and visa versa.
The message I meant to look for would look something like this:
Quote:
|
hub 5-0:1.0: unable to enumerate USB device on port xx
|
..but I'm not seeing that in the logs.
You could compare a copy of /var/log/messages and /var/log/pm-suspend from a good resume against one after lossing mouse and keyboard.
Wishing you luck,
Wj