Has anyone got this to work in Linux ?

[The Linuxator]

sleep state ?

I have been trying since ever on my Fedora Core 4 Laptop to get lid close events and sleep.sh commands to work , they work but there is a small glitch, let's say I execute /acpi/actions/sleep.sh . My laptop goes to sleep and everything looks just fine, a message comes up telling me
"Stopping tasks==================================="
And then the sleep LED lights up, and evrything goes off, good till now.

But when I press the power button back again, and I get the above message :

"Stopping tasks==================================="
Everything is working just fine except the LCD doesn't take me back to the desktop it just stays black with me staring at the stopping tasks message.

Surely something wrong with the line that restores my video state back to the way that it was, but what's wrong ?

To keep things short here is my slep.sh code :

 

[nweaver]

works on my Dell D810/Ubuntu (although Hibernate decided to puke recently...maybe Suspend is too, havn't used it in a while)

 

[The Linuxator]

Show me your sleep command code please, maybe I'll catch something.

 

[cleverhandle]

Have you searched the web for any information specifically relevant to your model laptop? Power management stuff is highly model-specific - many manufacturers are sloppy in their ACPI implementations, and a lot of relevant details are hidden from OSS developers. I have a crappy Acer laptop from work that, AFAICT, has never been made to sleep/suspend properly in Linux by anybody.

Also, if you can't get proper sleep states working, you might look into "software suspend" as an alternative.

 

[The Linuxator]

Originally posted by: cleverhandle
Have you searched the web for any information specifically relevant to your model laptop? Power management stuff is highly model-specific - many manufacturers are sloppy in their ACPI implementations, and a lot of relevant details are hidden from OSS developers. I have a crappy Acer laptop from work that, AFAICT, has never been made to sleep/suspend properly in Linux by anybody.

Also, if you can't get proper sleep states working, you might look into "software suspend" as an alternative.

I have been following guidelines from thinkwiki.org, however I have observed a certain step that I am missing here. in this page
they say I need to remove framebuffer support completley from the kernel, what is the best way to do that ?

Will setting FRAME_BUFFER_CONSOLE=y in .config ----> FRAME_BUFFER_CONSOLE=m fix it ?

 

[cleverhandle]

Originally posted by: The Linuxator
they say I need to remove framebuffer support completley from the kernel, what is the best way to do that ?

Will setting FRAME_BUFFER_CONSOLE=y in .config ----> FRAME_BUFFER_CONSOLE=m fix it ?

Sure, that should do it. Or just turn off frame buffer support entirely (n - don't even build the module). There's really very little real use for it, at least on x86 machines.

 

[The Linuxator]

Originally posted by: cleverhandle

Originally posted by: The Linuxator
they say I need to remove framebuffer support completley from the kernel, what is the best way to do that ?

Will setting FRAME_BUFFER_CONSOLE=y in .config ----> FRAME_BUFFER_CONSOLE=m fix it ?

Sure, that should do it. Or just turn off frame buffer support entirely (n - don't even build the module). There's really very little real use for it, at least on x86 machines.

🙁 I commented the whole line, but still no go.

 

[The Linuxator]

This thing just started to get on my nerves 🙁

 

[The Linuxator]

nweaver , can you post your sleep script's content , which you use on your Dell ?

 

[cleverhandle]

Originally posted by: The Linuxator
🙁 I commented the whole line, but still no go.

You do understand that you have to rebuild the kernel after changing the configuration, right? And don't just comment it out - change the Y or M to N. Otherwise the option will revert to the default, which may not be what you want.

edit: Also, there are several other framebuffer options in the kernel besides FRAME_BUFFER_CONSOLE. The page you linked implies that you want to make sure every one of them is disabled. I would think that the console frame buffer is probably the important bit, but I'm just reading the directions.