S1 Suspend almost working with 2.4.19 and 2.5.44 on Travelmate 360

DISCUSSION Phil Messenger 2 participants 3 messages Oct 31, 2002 2 messages not in the archive ACPI

lore

Share & tools

lore

Phil Messenger

author

2002-10-31 01:12 UTC #0 lore raw

After much fiddling, I've almost got S1 suspend working on the above system, with one caveat:

2.4.19 and 2.4.20-(pre11 | rc1):

System suspends, backlight isn't turned off. System resumes and is active on the network, so I can SSH into it, but the keyboard and touchpad apparently aren't reinitialised properly and won't respond. Note that the system hasn't hung, but the keyboard and mouse are "frozen".

2.5.44:

System suspends, backlight isn't turned off, system resumes and is active on the network. The keyboard is again hung, but if I cycle the input drivers (rmmod then modprobe i8042, atkbd) it responds again. I've actually written a small script which turns the backlight off using DPMS, suspends the system, then cycles the input drivers on resume. I'd much rather use 2.4 though - PCMCIA is utterly broken on this machine in 2.5, wheras it's only a bit broken in 2.4.

Is this a known problem? If so, are there any work-arounds? Or if it isn't, is there anything I can do to help debug it? I don't know much about ACPI and the Linux implemntation and I don't have enough time to sit down and understand it so I'm not sure where to start... Cheers,

Phil.

-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en

A message that is not in the archive (sent off-list or not yet received): [email protected]

Ducrot Bruno

2002-10-31 11:03 UTC #2 lore raw

Quoted 20 lines · Phil Messenger

After much fiddling, I've almost got S1 suspend working on the above system, with one caveat:
2.4.19 and 2.4.20-(pre11 | rc1):
System suspends, backlight isn't turned off. System resumes and is active on the network, so I can SSH into it, but the keyboard and touchpad apparently aren't reinitialised properly and won't respond. Note that the system hasn't hung, but the keyboard and mouse are "frozen".
2.5.44:
System suspends, backlight isn't turned off, system resumes and is active on the network. The keyboard is again hung, but if I cycle the input drivers (rmmod then modprobe i8042, atkbd) it responds again. I've actually written a small script which turns the backlight off using DPMS, suspends the system, then cycles the input drivers on resume. I'd much rather use 2.4 though - PCMCIA is utterly broken on this machine in 2.5, wheras it's only a bit broken in 2.4.

Quoted 5 lines

Is this a known problem? If so, are there any work-arounds? Or if it isn't, is there anything I can do to help debug it? I don't know much about ACPI and the Linux implemntation and I don't have enough time to sit down and understand it so I'm not sure where to start... Cheers,

There is two way that you can try:
1- if you use gpm, try to see if disabling it can help (there is also a little workaround, but I do not remember which) 2- try to do as if you were under Windows NT, by changing \_OS. You can do that in the ASL, or in the source in

linux/drivers/acpi/include/platform/aclinux
change the line:

#define ACPI_OS_NAME "Linux"
by:

#define ACPI_OS_NAME "Microsoft Windows NT"

The '2-' alone helped me in order to have a proper S1 support, and is now in my ASL so that I do not have to redo this change.

A better workaround should be to reinitialize the AUX driver.

Signature · 10 lines

Ducrot Bruno
http://www.poupinou.org        Page profaissionelle
http://toto.tu-me-saoules.com  Haume page


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en

A message that is not in the archive (sent off-list or not yet received): 20021031110318.GA27413-j6u/t2rXLliUoIHC/UFpr9i2O/[email protected]

Phil Messenger

author

2002-10-31 19:48 UTC #4 lore raw

Well, I had a complete brain fart. Just running kbdrate is enough to reset the keyboard and mouse on 2.5 and 2.4. I'm going to give 2- a try though, just as soon as I've fixed the cardbus support. :/

Thanks,

phil.

Quoted 30 lines · Ducrot Bruno

Quoted 4 lines · Phil Messenger
After much fiddling, I've almost got S1 suspend working on the above system, with one caveat:
2.4.19 and 2.4.20-(pre11 | rc1):
Quoted 10 lines
System suspends, backlight isn't turned off. System resumes and is active on the network, so I can SSH into it, but the keyboard and touchpad apparently aren't reinitialised properly and won't respond. Note that the system hasn't hung, but the keyboard and mouse are "frozen".
2.5.44:
System suspends, backlight isn't turned off, system resumes and is active on the network. The keyboard is again hung, but if I cycle the input drivers (rmmod then modprobe i8042, atkbd) it responds again. I've actually written a small script which turns the backlight off using DPMS, suspends the system, then cycles the input drivers on resume. I'd much rather use 2.4 though - PCMCIA is utterly broken on this machine in 2.5, wheras it's only a bit broken in 2.4.
Is this a known problem? If so, are there any work-arounds? Or if it isn't, is there anything I can do to help debug it? I don't know much about ACPI and the Linux implemntation and I don't have enough time to sit down and understand it so I'm not sure where to start... Cheers,
There is two way that you can try:
1- if you use gpm, try to see if disabling it can help (there is also a little workaround, but I do not remember which) 2- try to do as if you were under Windows NT, by changing \_OS. You can do that in the ASL, or in the source in
linux/drivers/acpi/include/platform/aclinux
change the line:
#define ACPI_OS_NAME "Linux"
by:

Quoted 9 lines

#define ACPI_OS_NAME "Microsoft Windows NT"
The '2-' alone helped me in order to have a proper S1 support, and is now in my ASL so that I do not have to redo this change.
A better workaround should be to reinitialize the AUX driver.