Just installed Debian 'Sarge' on my new little Fujitsu P1120 subnotebook...Dual boots with WinXP now. Overall, works great so far!

Now would like to get touchscreen working and suspend (hibernate?) working on it.

So, what should I do or need to get to get these items working?

If there's any good reference info on this somewhere that would be great too!

Thanks for any and all help!

Mark

I am using Fedora Core 3 (2.6.11-1.14_FC3) on a Toshiba S1410-303. So the details might vary slightly from your situation.
First, make sure you have the ACPI module loaded in the kernel:

#lsmod | grep acpi

if it's not there, add "acpi=on" to the kernel parameters at bootup
Also make sure the ACPI daemon is running (to catch ACPI events and handle them):

#ps ax | grep acpi | grep -v grep

should return "/usr/sbin/acpid".
Now we'll need to tell the ACPI daemon to catch the event when laptop lid is closed (or opened) and run a script. To do this we create a file /etc/acpi/events/lid.conf that has following content:

event=button/lid
action=/usr/bin/s3.sh

Next, we'll need to write the /usr/bin/s3.sh script, which should contain:

#!/bin/bash
rmmod [misbehaving module 1]
rmmod [misbehaving module 2]
rmmod [misbehaving module n]
echo 3 > /proc/acpi/sleep
modprobe [misbehaving module n]
modprobe [misbehaving module 2]
modprobe [misbehaving module 1]

Of course you'll need to replace [misbehaving module] with the names of the modules that might cause the suspension to fail. Possible perps are: button, ehci_hcd, uhci_hcd, nvidia, and many others.

#lsmod | less

will provide information about what's loaded, so you can experiment with this a bit. Make sure to SAVE YOUR WORK, as failing to resume will require an unclean shutdown/reboot to get things running again.

Finally, if the suspend/resume is going fine, but the display is not re-initialized properly you can add "acpi_sleep=s3_bios" the kernel parameters to have the BIOS handle the display suspension/resume.

goodluck

one question on the misbehaving modules. when my laptop comes back from suspend, the touchpad loses the ability to do tap clicks. would adding the touchpad module to the s3.sh fix the problem? if so, what is the touchpad module?

THANKS for your help, notwerk!!

Will give this a try and report back later....

Mark

Dear csfalcon,

What kernel are you running? Because tap clicks for touchpads under kernel 2.6.11 are broken, this is fixed in 2.6.12 but this kernel is still in rc4.

If the pad works fine BEFORE suspend and breaks after resume - I am guessing here, so don't take my words for granted - but I think X is not re-initialized properly. You can try VTing and suspending there, then switching back to X after resume.



Dear ArchiMark,

Please note that the instructions provided are for SUSPEND TO RAM...
I noticed in your post that you are also asking about hibernation (supend to disk). So a little word of caution, if you're using a dual boot setup, S4 (suspend to disk) is not recommended, unless you know exactly what you're doing. Personally, I can't risk the data on my laptop and would hate to have to restore from backups, which is why i steered clear of S4 until it is more thoroughly field tested.

S3 however, consumes next-to-nothing in power and provides faster restore time than S4.

You can check out more info on S4 at http://www.suspend2.net/

Hi netwerk,

What do you mean by "try VTing and suspending there"? What does VTing mean? Thanks alot for your help.

You have a number of Virtual Terminals that you can switch to by hitting Ctrl+Alt+[F1-F6]
To get back to the GUI hit Ctrl+Alt+F7