You are not logged in.
Pages: 1
Hi,
I cant hibernate on arch. When I try to hibernate the computer just shuts down and the state is reset upon reboot. When I boot the following error is generated:
ERROR: resume: no device specified for hibernation I have configured initramfs based upon the instructions in the Power management wiki by adding the resume hook after udev.
I have configured the kernel parameters in /etc/default/grub based upon instructions in the GRUB and Kernel parameters wikis. Note that I have also tried to configure the kernel parameters using the uuid of my swap partition to no avail.
GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/sda5" I then ran
sudo grub-mkconfig -o /boot/grub/grub.cfg Last edited by tjcurra2 (2015-09-26 19:55:59)
Offline
Have you recreated the initcpio image?
What does "cat /proc/cmdline" return?
Last edited by lucke (2015-09-26 19:57:47)
Offline
Thanks for the prompt response!
I have recreated the initcpio image using
sudo mkinitcpio -p linux cat/proc/cmdline returns
BOOT_IMAGE=/vmlinuz-linux root=UUID=3c8f8285-2fcc-4089-beee-08fdc34ec38f rw quiet since root is by uuid I first tried to configure the kernel parameters using the uuid of my swap partition, but it got the same result as using the path.
Offline
/proc/cmdline shows you the kernel line that you booted with - it lacks the resume parameter.
What does "grep resume /boot/grub/grub.cfg" show? Do you see the resume parameter in GRUB menu?
Offline
I do not see the resume parameter in the GRUB menu.
grep resume /boot/grub/grub.cfg returns
linux /vmlinuz-linux root=UUID=3c8f8285-2fcc-4089-beee-08fdc34ec38f rw resume=UUID=e5be4d21-dab9-49b6-85e8-9cf04dda3027 quiet
linux /vmlinuz-linux root=UUID=3c8f8285-2fcc-4089-beee-08fdc34ec38f rw resume=UUID=e5be4d21-dab9-49b6-85e8-9cf04dda3027 quiet
linux /vmlinuz-linux root=UUID=3c8f8285-2fcc-4089-beee-08fdc34ec38f rw resume=UUID=e5be4d21-dab9-49b6-85e8-9cf04dda3027 quiet
Offline
Well, some entries in your GRUB have a resume parameter, although not the one you set in /etc/grub/default.
What does "sudo grub-mkconfig -o /boot/grub/grub.cfg" show?
Offline
sudo grub-mkconfig -o /boot/grub/grub.cfg shows
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
Found fallback initramfs image: /boot/initramfs-linux-fallback.imgOffline
Please post your /etc/default/grub, /boot/grub/grub.cfg and the output of "ls -l /boot/grub/grub.cfg".
Offline
I'm not sure if this information is pertinent to this issue, but I dual boot arch on a macbook and I copied the boot.efi image to a separate partition formatted to HFS+ so that GRUB is loaded upon boot by default.
Offline
/etc/default/grub:
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=e5be4d21-dab9-49b6-85e8-9cf04dda3027 qu$
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console/boot/grub/grub.cfg:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
elsels -l /boot/grub/grub.cfg:
-rw------- 1 root root 5320 Sep 26 17:07 /boot/grub/grub.cfg Offline
You didn't paste the files fully, but I can see you have "resume=UUID=e5be4d21-dab9-49b6-85e8-9cf04dda3027" in /etc/default/grub (you talked about "resume=UUID=/dev/sda5" in your first post), and this is what grep found in /boot/grub/grub.cfg. If you're not seeing the resume parameter in the GRUB menu, then perhaps your /boot/grub/grub.cfg isn't read (and some other grub.cfg is, maybe on an EFI boot partition?).
I don't know much about EFI.
Offline
Yeah, I should have mentioned that I changed it back to the UUID since that is what was recommended in the wiki. I'm thinking that the problem must stem from the mac EFI boot.
Offline
Pages: 1