Laptop no longer suspends after user mod

[count.delmongo]

Hey,

Just wonna say that I've used this site soo much without even having to post, which I think is a testament to how brilliant the community is.. Okay, ass kissing over..

I recently wanted to address the following issue:

When I hibernate my HP Pavilion dv6095ea, running Werewolf, it works fine, as does/did suspend. I say fine, I mean as well as most can expect laptops to!! But I found it annoying that hibernating Fedora caused grub to be modified or whatever so that on next power up, it goes straight into booting back up into Fedora and resuming (I heard it being referred to as 'grub having hook placed on it'???)

Anyways, I found a post saying that if I commented out code in the relevant file, in this case

/usr/lib/pm-utils/sleep.d/01grub

, it would stop the hook. Another post indicated that simply placing

exit 0

at the top of the file would stop this from happening.

So I followed the latter approach and added 'exit 0'.

Since then, suspend/hibernate has stopped working and when I initiate it, it logs me out and i get 4 lines of output as follows:

PM: Preparing system for mem sleep
Stopping tasks ... done.
PM: entering mem sleep
Suspending console(s)

It just sits there, not hung but happy just sitting. I've subsequently removed the line from the top (Duh!!) but it still does it.. So have I broken something else by putting that single 'exit 0' line in the file and then removing it?

I recently updated to 2.6.23.14-115 and can confirm that suspend has worked since the update but not since the twit that I am broke it.

Thanks in advance for advice

[Zero-Override]

i think that it's caused by the exit 0 code it's either not recognized and therefor doesn't exit the program, or the 0 added will stop it from exiting if it is recognized

try commenting out the exit 0 code and see what happens then

oh and welcome to the club i've read the forum for like a year to before i joined up to help someone else

[count.delmongo]

Thanks for the welcome!!

Unfortunately, probably me being too vague as is sometimes the case in life in general, my first course of action after the problem occurred was to undo my changes and to remove the 'exit 0' entirely, leaving the file as it was.

The issue is that I still have the same problem, even AFTER removing the 'exit 0'. That's what is comfusing me...

Put simply: I made a change, the result of which b0rked suspend/hibernate. So I undid the change, still b0rked... = ahhhh!!

I broked it, lol...

???

[count.delmongo]

After subsequent research it appears that it wasn't me that caused the problem. It looks like a new kernel update or something. I have re-installed Fedora 8 and everything is updated, the issue is still there

Checked the system logs, it looks like it has a problem suspending a specific device, refers to something called rfkill_suspend?? A quick check on google turns up absolutely nothing. I thought it maybe wireless related, as quite a few suspend problems are, so I did 'rmmod ndiswrapper' and got rid of wireless stuff but still the same problem.

Heres an example from the logs

Feb 21 10:20:05 localhost kernel: Stopping tasks ... done.
Feb 21 10:20:05 localhost kernel: Suspending console(s)
Feb 21 10:20:05 localhost kernel: suspend_device(): rfkill_suspend+0x0/0x44 [rfkill]() returns -194090335
Feb 21 10:20:05 localhost kernel: Could not suspend device rfkill0: error -194090335
Feb 21 10:20:05 localhost kernel: Some devices failed to suspend
Feb 21 10:20:05 localhost kernel: Restarting tasks ... done.