You are not logged in.
I was using this today: http://wiki.archlinux.org/index.php/Sus … usp_method
I hit hibernate in the gnome-power-manager, it went down and I turned it on, only on Arch boot up process I get a message like:
"cannot stat device: <swap partition> please enter the device name or press ENTER to resume"
at the prompt, I type /dev/sda2 (my swap) and it gives me the same msg. All I can do is hit ENTER and get a "ramfs$" prompt, where I can only type exit to reboot ![]()
In my suspend.conf, I have:
resume device = /dev/sda2My /etc/mkinitpcio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="pata_via ata_generic sata_via"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usbinput keymap uresume filesystems"My /etc/suspend.conf:
# This node should have already been created - if not,
# major 10, minor 231.
snapshot device = /dev/snapshot
# Set this to whatever your suspend partition is.
#
# You will not need to provide a resume parameter to your
# kernel when using uswsusp, as this file will be used.
# This neccesitates using a initrd, though!
resume device = /dev/sda2
compress = y
#image size = 350000000
#suspend loglevel = 2
#compute checksum = y
#early writeout = y
# You can only change these if you modified Makefile.diff
# and have the requirements installed.
#splash = y
#encrypt = nEDIT: Here's the result of when I run the command: "mkinitcpio -k kernel26 -g /boot/kernel26.img" from the Wiki:
bobby@dabox:~$ sudo mkinitcpio -k kernel26 -g /boot/kernel26.img:: Begin build
find: /lib/modules/kernel26: No such file or directory
ERROR: module 'pata[-_]via' not found
find: /lib/modules/kernel26: No such file or directory
ERROR: module 'ata[-_]generic' not found
find: /lib/modules/kernel26: No such file or directory
ERROR: module 'sata[-_]via' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
find: /lib/modules/kernel26: No such file or directory
find: /lib/modules/kernel26: No such file or directory
find: /lib/modules/kernel26: No such file or directory
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [keymap]
:: Parsing hook [uresume]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26.img'...SUCCESS
bobby@dabox:~$Don't know if that helps... if more info is needed please ask, I really want to fix this!!! I am currently only getting in via Arch Fallback on the GRUB menu.
Last edited by colbert (2007-12-21 17:09:30)
Offline
Did you add resume=/dev/sda2 to your /boot/grub/menu.lst ?
Offline
No, it is not necessary to add anything to grub config if you use uswsusp. This is a difference with vanilla suspend and tuxonice.
On the contrary, your mkinitcpio output does not look sane to me. Are you running arch default kernel or something else. It seems that it does not find the kernel26. Anyway it does not include the drivers for the hard disk, so it is expected that it does not find the swap partition afterwards.
Mortuus in anima, curam gero cutis
Offline
Well I did a pacman -Syu, and it wound up upgrading the kernel26 package, so I was able to reboot and get back in, but something was off. There was this constant stutter in my system, lagging every few seconds for a brief snap of a second. It was driving me crazy. I killed nearly every process I could, and got fed up so I just reinstalled Arch. Now she's running fine, and I don't plan on messing with hibernate/suspend any time soon again, especially since I didn't really need it in the first place. Was kind of a larf.
Thanks anyway guys.
Offline
Hi y'all!
I have the same issue as described by colbert. I think, we should try to solve this, because reinstalling Arch (and then letting its features left unused) shouldn't be the right way, should it? But since I am not the most advanced guy with Linux (nor Arch), I will step back and wait for others to give us their knowledge. :)
About the lagging: I had that as well but didn't recognize that it came from a suspend problem...
Thanks for the others' help in advance!
Micha
Offline
In which sense the lagging was a suspend problem? This may happen only if it happens after a suspend (to disk?) cycle and may be it is a cache problem. In this case you should try other methods of suspension, as for the article in the wiki.
Moreover, Micha's problem can't be identical with colbert's one, because on the contrary colbert did not manage to resume from suspension, thus its problem of lagging can not be a problem of suspend. Probably it is a problem with one version of the kernel26 version. Which are you using?
Anyway, it is not a good reason to reinstall at all, also because just a reboot (in the case of a suspend problem) solves any lagging which can follow from a suspension cycle. If on the contrary the problem is caused by an upgrade of the kernel, downgrading the kernel is enough to solve it.
Mortuus in anima, curam gero cutis
Offline
Now that you mention it, patroclo7, I think the lagging problem was actually occuring when I was still using Ubuntu Gutsy Gibbon... That was the reason why I got fed up and switched to Arch... (thank god for the lag! ;).
I solved the error (that occured after typing in 'mkinitcpio -k kernel26 -g /boot/kernel26.img') but since I am on another computer right now and don't have the lines I typed in at hand, I'll edit my post later on to help you out. I managed to get fglrx running now but wasn't lucky to resume after the suspend. But that should be solved as well in a matter of days. :)
Edit: For the error try typing
mkinitcpio -p kernel26instead of the above option. In my case, the error message disappeared and everything was fine afterwards.
Last edited by Micha (2007-12-22 12:10:18)
Offline
Ok. In the wiki page about Suspend to Disk there are a couple of tricks for the fglrx driver, in case you want to try them.
Mortuus in anima, curam gero cutis
Offline
Yes of course I would not prefer to reinstall, Mischa is spot on. But I simply could not find a way, it would not let me boot in normally. It was stuck on a resume.
And I found out the lagging was actually my fluxbox. I wiped my /.fluxbox folder and copied back file by file to test, and everything is smooth as a baby's bottom now. It was something in there and now it's gone. It was especially a nuisance as navigating my flux menu was lagging every 2-3 seconds, making it a pain to select items on the menu.
Offline