SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
On my netbook here, I did a fresh install of --current.
I cannot get hibernate to work, it seems to fall back to suspend.
In /var/log/pm-powersave.log I get this message:
/usr/lib/pm-utils/power.d/sched-powersave false: success.
Running hook /usr/lib/pm-utils/power.d/wireless false:
Turning powersave for wlan0 off...Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlan0 ; Operation not supported.
Failed
The netbook then seems to fallback to suspend at that point.
from lilo.conf:
image = /boot/vmlinuz-generic-smp-2.6.37.3-smp
root = /dev/sda5
label = Linux
read-only
initrd = /boot/initrd.gz-2.6.37.3-smp
from my mkinitrd.conf:
# mkinitrd.conf.sample
# See "man mkinitrd.conf" for details on the syntax of this file
#
SOURCE_TREE="/boot/initrd-tree"
#CLEAR_TREE="0"
OUTPUT_IMAGE="/boot/initrd.gz"
#KERNEL_VERSION="$(uname -r)"
#KEYMAP="us"
MODULE_LIST="ext4"
#LUKSDEV="/dev/sda2"
#LUKSKEY="LABEL=TRAVELSTICK:/keys/alienbob.luks"
ROOTDEV="/dev/sda5"
#OOTFS="ext4"
RESUMEDEV="/dev/sda6"
#RAID="0"
#LVM="0"
#UDEV="1"
#MODCONF="0"
#WAIT="1"
So unless I'm missing something, I think I have all my bases covered here.
I even went so far as to issue hibernate as root, and the pc simply goes into standby.
Sorry my mistake, I did indeed have the resume= line in my lilo.conf up at the global append line.
I moved it down to the specific kernel as you suggested, reran lilo and still no luck.
What is interesting is:
when pm-hibernate is called, both /var/log/pm-powersave.log and /var/log/pm-suspend.log are updated to the time that I issued the hibernate command. Perhaps because hibernate is called, then fails, then it falls back to suspend; I'm not sure.
There is one line in the hibernate log that seems worth mentioning:
"/usr/lib/pm-utils/pm-functions: line 316: echo: write error: No such device"
And in the suspend log, there are these lines that are worth mentioning as well:
/usr/lib/pm-utils/power.d/sched-powersave false: success.
Running hook /usr/lib/pm-utils/power.d/wireless false:
Turning powersave for wlan0 off...Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlan0 ; Operation not supported.
Failed.
Seeing the wlan0 error there I just issued the hibernate again, and indeed the wifi is not turned off at all.
My netbook uses ath5k and I'm using wicd. I think I'm going to try blacklisting wifi as a test and see if anything changes. Will report back.
business_kid thanks again for all your help. It turns out I had the wrong partition number for swap in my lilo.conf. I cannot believe I didn't catch that, but none the less it works now. Thank again.
You're Welcome - we old fogies have to stick together ;-). I'm doing engineering in College, and old enough to be father to most of the students. Not the lecturers, thankfully.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.