I have installed Gutsy64bit on this machine from scratch. Now this system can hibernate (it did so several times this week) and even suspend to disk without "too much problems".
For hibernation I did anything, it just worked. To make suspend working I had to work:
I tried to add this i8042.nomux to the boot parameters (edit /boot/grub/menu.lst and append this to the kopt commented in the stanta and execute "update-grub"). Now the system can suspend to ran and the mouse works as expected. However, the LID closure event is not sent, and I cannot convince the machine to suspend when I close the LID.
Adding the parameter i8042.reset does the trick. I don't have enough statistics yet, but about 90% of the time the LID closure event is sent properly.
I have installed Gutsy64bit on this machine from scratch. Now this system can hibernate (it did so several times this week) and even suspend to disk without "too much problems".
For hibernation I did anything, it just worked. To make suspend working I had to work:
I tried to add this i8042.nomux to the boot parameters (edit /boot/grub/menu.lst and append this to the kopt commented in the stanta and execute "update-grub"). Now the system can suspend to ran and the mouse works as expected. However, the LID closure event is not sent, and I cannot convince the machine to suspend when I close the LID.
Adding the parameter i8042.reset does the trick. I don't have enough statistics yet, but about 90% of the time the LID closure event is sent properly.
I have documented this in https:/ /wiki.ubuntu. com/LaptopTesti ngTeam/ Lenovo3000N100_ 0768 , and the original idea came from the Gentoo Wiki: http:// gentoo- wiki.com/ HARDWARE_ Lenovo_ 3000_N100
I would be glad if someone can explain what those options do :)