In my environment this resolved, add kernel parameter "acpi=noirq".
My /etc/default/grub kernel paramter line is,
GRUB_CMDLINE_LINUX="acpi=noirq"
]]>So do you not have the problem now (using systemd to suspend)?
]]>Please read what gnidov wrote:
Update
This seem to have nothing to do with the pm-utils scripts. After digging through /usr/bin/pm-suspend, I have found that pm-suspend uses the command
echo -n "mem">/sys/power/state
to put the computer to sleep.
Issuing this command alone was enough to screw up my grub. Now I am looking for what exactly happens when you echo "mem" into /sys/power/state. Any help appreciated.
Update again
The strangest of the strange happened. Instead of restoring grub, it is possible to fix the boot issue simply by removing and reattaching the battery. So, all in all this seems to be some nasty bug in the BIOS.
Yes, reinstalling grub was a solution, but not the only one (neither the easyer), and it worked for me too when I tried it.
I have systemd and now I dont use pm-suspend, but when I used it I had the same problem. Maybe I have to move the post, but This is the only place I found people with the problem I have, so please leave me to ask, and I`ll leave this thread nicely.
P.D: Since English is not my mother language, let me thank you for the writing excercise
]]>By the way, you might want to look into moving away from pm-suspend since you are using systemd.
]]>"The strangest of the strange happened. Instead of restoring grub, it is possible to fix the boot issue simply by removing and reattaching the battery. So, all in all this seems to be some nasty bug in the BIOS."
I dont know if it is really a BIOS bug, but I know (because I tried) the solution is not reinstalling grub.
So Yes, I have the same problem. I just can add that with an updated Archlinux the problem is still there, and instead of removing and reattaching the battery (or reinstalling grub) you have to wait a few minutes to boot again.
I will be writing a new post, so you can be happy.
]]>I did not say anything about reinstalling grub.
You said you had "THE SAME" issue as the OP who had "exactly the problem I have" and that you therefore "prefered [sic.] asking people who had the same problem".
But the OP's problem involved a need to reinstall grub to disk and, moreover, a need to do that via an alternative boot.
Why do you think you are experiencing the same issue as opposed to somewhat similar symptoms?
]]>Yes, i'm using systemd
When I restart the netbook AFTER suspend-and-resume, instead the grub2 menu I get a blinking cursor and after a minute the following message "Reboot and select proper device..", just as the picture of the original message.
Just to clarify:
Case A:
1- power on netbook
2- grub2 menu
3- Login Archlinux
4- shutdown -r now - > netbook restart
5- grub2 menu, and everything ok
6-
Case B (restart after suspend):
1- power on netbook
2- grub2 menu
3- Login Archlinux
4- close lid -> suspend -> power led blinking
5- open lid and press button -> netbook on
6- shutdown -r now - > netbook restart
7- after bios text, instead of grub2 I get a blinking cursor and after a minute the following message "Reboot and select proper device.."
8-
Case C (power on after suspend):
1- power on netbook
2- grub2 menu
3- Login Archlinux
4- close lid -> suspend -> power led blinking
5- open lid and press button -> netbook on
6- shutdown -h now - > netbook powers off
7- press power button -> power on netbook
8- after bios text, instead of grub2 I get a blinking cursor and after a minute the following message "Reboot and select proper device.."
9-
Case D:
1- power on netbook
2- grub2 menu
3- Login Archlinux
4- close lid -> suspend -> power led blinking
5- open lid and press button -> netbook on
6- shutdown -h now - > netbook powers off
7- wait for 30 min
8- press power button -> power on netbook
9- grub2 menu, and everything ok
10-
Are you using systemd?
]]>"Pm-suspend works nicely, the system goes to sleep, after waking it up, everything works. (I had to disable C6 state in the BIOS to work around a previous issue where resume from suspend didn't work). Now only one problem persists: after a pm-suspend my grub doesn't load.
Instead of grub I get the following error message:
Reboot and Select proper Boot device."
I know this is a very old post, but is the exactly the problem I have, so I prefered asking people who had the same problem before starting a new one. Sorry if i shouldn't reopen old posts.
About changes in Arch, now I can say that the problem is still there, despite new kernels and changes.
Thanks!
]]>(What exactly does with the MBR / GRUB / "restart-fairy" when the PC restart ??)
Edit: A minutes ago I suspend the PC, after I tried to restart and doesnt work. I holded the power button to shutdown and 10 minutes after I power on the PC and it boots!. So i think it means you have to plug the battery off, or wait a few minutes to properly restart the pc after a suspend.
]]>