I have in /etc/acpi/acpi_handler.sh this:

2 members found this post helpful.

I have Toshiba Satellite L305-S5946 (with InsydeH2O bios ver 1.9) but had to do a bit of tweaking to get suspend to work with Slackware 13 (-current back then). Suspend-to-ram and suspend-to-disk both work perfectly now. Here's the relevant thread.

pm-hibernate works fine on my system. pm-is-supported --hibernate and --suspend report 0 on my system.

but pm-suspend does not work. after a few seconds the screen goes blank, but then it comes back on after a few more seconds, without any intervention from me. and then my keyboard acts very strangely. The windows key is bound to ~, the right arrow is bound to w, enter is bound to s, for example. i am unable to use my laptop and have hold down the power button to power-off.

i do have a very strange laptop (crappy radeon gfx card), which has been reporting acpi and ide kernel errors for ages, though. i've never tried suspend on any other distros, unfortunately. both suspend and hibernate work fine in windows, mind you.

@tuxrules: I was just looking at that thread! Going to try it out shortly- wish me luck!

I tried removing keyboard and mouse references in xorg.conf. Being an old school X11 user, it seems counter intuitive to remove what used to be vital entries. But I tried it and X worked, but suspend still doesn't come back.

I also tried the vesa driver because of the suggestion of using new video drivers worked for some here, but the result is exactly the same. I'm thinking this has nothing to do with X now.

I also have tried adding boot the boot parameter, append = "acpi_osi=Linux", as suggested here:
http://www.linuxquestions.org/questi...urrent-745907/

The next thing will be to try GrapefruiTgirl's script. We'll see how that goes. I have not tried hibernate, so I'll give that a shot too.

Good news! Using "acpi_osi=linux" in lilo.conf and VBE POST, VBE Mode Restore, and VBE State Restore options in the toshiba fdi file, and a 2.6.30.5 kernel, my L355 has working suspend and working Fn-F6/F7 brightness keys. Not sure if I want suspend on closing the lid, but that works, too. Thanks, manwichmakesameal and tuxrules!

I have tried a myriad of different combinations using people's suggestions and on some of the links sited here. No luck, same issue. The HP Pavilion dv5000 goes into suspend fine and appears to be coming out of it... a little hard disk activity, some lights come on, but not wireless... and then the keyboard and video do not work and I have to do a hard reset. The sys-req REISUB combination also does not work.

I cannot see a difference between what is happening in /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-hp.fdi on Slackware 12.2 and Slackware 13. I have tried various switches with and without the lilo append parameter:
append = "acpi_osi=Linux"

If anyone has any luck with this particular model, please let me know. Also, I'd be interested if anyone has luck with the Dell Latitude D630 as well.

Thanks, everyone, for the great suggestions.

Just to correct the idea that "everyone has it working" that permeates some of the posts in this thread - my laptop will suspend or hibernate, but go straight in a kernel panic on resume (x86_64 arch, from 13.0)

Needless to say I have not dared go near it on my more important machines

Needless to say I am going through the threads here to find what i need to do

When I read this I thought your model, too might have this issue but dv5000 is not listed there. I have a dv6000 which suffers from that problem, my wireless card is dead and 4 times out 5, the screen will be blank at boot. Suspend/resume was working OK but since the screen failures began I get a blank screen on resume. My problem is definitely related to the hardware failure of this model, but you may want to search the HP database to see if there's anything similar about dv5000s.

On the other hand, oddly enough, my Pardus 2009 can suspend to RAM and resume just fine (I use the same kernel -2.6.30- on both systems). So there must be a way to suspend without triggering the problem, but I don't know what it is.

But does this problem show up outside of suspend operations? That is, the display failure? I'm just trying to understand if there are other places where this shows up besides during the suspend operation. I don't have any visible problems with my laptop otherwise.

Thanks for the feedback.

Just to dd my 2 cents : I have a MSI S270 laptop and have just been able to suspend once and then never again (I was actually very surprised to see it resume). I'm running current on it, so it basically Slack 13 32bits right now.
It suspends well (so does /var/log/pm-suspend.log says) but when I power it on, I get a black screen with a blinking prompt and I need to turn it off since no keyboard nor anything else will work. I tried most of the hal quirks but to no avail.
I don't really blame Slack here, as I have the feeling that suspend on Linux in general is still not working quite well and laptop manufacturers do not really help.

Oh, I agree! I don't blame Slackware either. In fact Slackware is the first distribution I have ever seen suspend work! I am going to stick with 12.2 for a while though. I am just too busy to go through an upgrade at the moment and I don't want to create any problems for my work system, my other laptop.

I will be upgrading 3 other servers first, so 5 systems total. I just work on the experimental system to work out the kinks as I have time. The experimental system is a laptop and doesn't have any services I need to have up and running.

Thanks for the feedback. It's much appreciated.

Now that I've completed my upgrades on all my systems I thought I'd add an update. Here are the systems again.

First Laptop: HP Pavilion dv5000 running the radeon graphics driver and a 64 bit Turion, single core processor. This is my Slackware64 test system.

Suspend is still broken on this system. I actually don't care that much. It's an experimental system anyway.

Second Laptop: Dell Latitude D630 with a Core 2 Duo, 64 bit processor. This has Integrated Intel Graphics.

On this second system, I'm sticking with 32 bit Slackware for now. I need Skype and Wine so I'm stuck with it... either that or making a 64 bit system 32 bit ready. Not sure I want to bother at the moment. But back to suspend. It appears to be working perfectly right out of the box. I'm delighted with that because it's my work system and I really like having my stuff ready as soon as I open the lid. If I ever do get this HP Pavilion dv5000 working, I'll let you all know with all the gory specifics.

Thanks again to everyone who responded.

Even i had probs with suspend,after resuming i would get noise from my speakers ,i fixed my sound file and now no problem

Suspend works fine here but I'm an Xfce4 user. Suspend works on all laptops I have installed Slackware on for friends, including my own two (Sony Vaio VGN-C140G and Toshiba Satellite A55-S306).

Are you using an Intel graphics card?

I read through the post and couldn't tell if you tried running slack 13 without an xorg.conf (i.e. let X detect stuff using HAL). Have you tried that yet? On my Sony Vaio VGN-C140G that solved my problems (that and the inclusion of Robby Workman's Intel packs... I was testing since -current, then installed 13.0 when it was released).

Not to be rude or anything, but you might want to include the caveat that you have seen few problems. I've met people who had problems with <insert distro here> and solved them by switching to <insert distro here> without asking for help or telling anyone....

For example, I could say that it works on all laptops, but unless I say "in my experience" or something, I'm over-generalizing, and probably not telling the truth either....

Thanks for your post, sir, but you might want to tell him that this sets it globally, apart from KDE4, and that he might want to tell KDE4 not to worry about the lid switch action so that it (hopefully) doesn't cause a conflict.... I don't know if it would, but I would think two things calling pm-suspend is probably not a welcomed event 8-)