Announcement

**toad** · Feb 22, 2011, 12:41 PM

Re: suspend does not work

I'd be interested in your /boot/grub/grub.cfg and /etc/grub.d/40_custom files for starters (please wrap them in quote tags to make them easier to read).

**sisqonrw** · Feb 22, 2011, 01:31 PM

Re: suspend does not work

Hi here are the logs:

Code:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
 load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
 set saved_entry=${prev_saved_entry}
 save_env saved_entry
 set prev_saved_entry=
 save_env prev_saved_entry
 set boot_once=true
fi

function savedefault {
 if [ -z ${boot_once} ]; then
  saved_entry=${chosen}
  save_env saved_entry
 fi
}

function recordfail {
 set recordfail=1
 if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
if loadfont /usr/share/grub/unicode.pf2 ; then
 set gfxmode=640x480
 insmod gfxterm
 insmod vbe
 if terminal_output gfxterm ; then true ; else
  # For backward compatibility with versions of terminal.mod that don't
  # understand terminal_output
  terminal gfxterm
 fi
fi
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
set locale_dir=($root)/boot/grub/locale
set lang=de
insmod gettext
if [ ${recordfail} = 1 ]; then
 set timeout=-1
else
 set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, mit Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	linux	/boot/vmlinuz-2.6.35-22-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro i8042.reset=1 noplymouth max_loop=16
	initrd	/boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, mit Linux 2.6.35-22-generic (Wiederherstellungsmodus)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	echo	'Linux 2.6.35-22-generic wird geladen …'
	linux	/boot/vmlinuz-2.6.35-22-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro single i8042.reset=1
	echo	'Initiale Ramdisk wird geladen …'
	initrd	/boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, mit Linux 2.6.32-28-generic' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	linux	/boot/vmlinuz-2.6.32-28-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro i8042.reset=1 noplymouth max_loop=16
	initrd	/boot/initrd.img-2.6.32-28-generic
}
menuentry 'Ubuntu, mit Linux 2.6.32-28-generic (Wiederherstellungsmodus)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	echo	'Linux 2.6.32-28-generic wird geladen …'
	linux	/boot/vmlinuz-2.6.32-28-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro single i8042.reset=1
	echo	'Initiale Ramdisk wird geladen …'
	initrd	/boot/initrd.img-2.6.32-28-generic
}
menuentry 'Ubuntu, mit Linux 2.6.32-27-generic' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	linux	/boot/vmlinuz-2.6.32-27-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro i8042.reset=1 noplymouth max_loop=16
	initrd	/boot/initrd.img-2.6.32-27-generic
}
menuentry 'Ubuntu, mit Linux 2.6.32-27-generic (Wiederherstellungsmodus)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	echo	'Linux 2.6.32-27-generic wird geladen …'
	linux	/boot/vmlinuz-2.6.32-27-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro single i8042.reset=1
	echo	'Initiale Ramdisk wird geladen …'
	initrd	/boot/initrd.img-2.6.32-27-generic
}
menuentry 'Ubuntu, mit Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	linux	/boot/vmlinuz-2.6.32-24-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro i8042.reset=1 noplymouth max_loop=16
	initrd	/boot/initrd.img-2.6.32-24-generic
}
menuentry 'Ubuntu, mit Linux 2.6.32-24-generic (Wiederherstellungsmodus)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	echo	'Linux 2.6.32-24-generic wird geladen …'
	linux	/boot/vmlinuz-2.6.32-24-generic root=UUID=ccb76a21-0616-465e-bd64-201f04aac97f ro single i8042.reset=1
	echo	'Initiale Ramdisk wird geladen …'
	initrd	/boot/initrd.img-2.6.32-24-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	linux16	/boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set ccb76a21-0616-465e-bd64-201f04aac97f
	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows Vista (loader) (on /dev/sda1)" {
	insmod ntfs
	set root='(hd0,1)'
	search --no-floppy --fs-uuid --set 9a106cb3106c9851
	chainloader +1
}
menuentry "Windows 7 (loader) (on /dev/sda2)" {
	insmod ntfs
	set root='(hd0,2)'
	search --no-floppy --fs-uuid --set 70706d68706d35ce
	chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

Code:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

**jeremy1701** · Feb 22, 2011, 01:39 PM

Re: suspend does not work

This probably is less than helpful, but.... I tried for weeks to get suspend/hibernate working on my latop top with 10.04; never had any luck. With 10.10, it works flawless.

**toad** · Feb 22, 2011, 02:07 PM

Re: suspend does not work

Ooops, perhaps it was the code tags I was after :P

Anyway, I'm missing any reference to a "resume" stanza which might well be the cause of the problem.

We now need other Kubuntu users (of which I'm not one) to corroborate whether any of their grub files specify a "resume=/dev/sd??" at the end of the kernel line.

I need that for Arch for resume to work, but who knows how the *buntus work...

**sisqonrw** · Feb 22, 2011, 02:18 PM

Re: suspend does not work

i know that suspend have works very good. but since some days it doesnt work

**dibl** · Feb 22, 2011, 02:34 PM

Re: suspend does not work

Are you trying to suspend to RAM, or suspend to disk?

Have you reviewed the settings in System Settings > Power Management, related to suspend and hibernate?

**toad** · Feb 22, 2011, 02:41 PM

Re: suspend does not work

dibl, out of interest, do you have a "resume="_path to your swap_ in your grub.cfg? If not there, in any of your /etc/grub.d/ files?

EDIT:

Kernel 2.6.37.1 does have a documented suspend problem, but I reckon that is a bit new for Kubuntu.

**dibl** · Feb 22, 2011, 03:11 PM

Re: suspend does not work

Originally posted by toad

dibl, out of interest, do you have a "resume="_path to your swap_ in your grub.cfg? If not there, in any of your /etc/grub.d/ files?

No. Of course /boot/grub/grub.cfg is built automagically from /etc/default/grub + the configuration scripts in /etc/grub.d/. I suppose you could insert a "resume=xxxx" option in /etc/default/grub on the "GRUB_CMDLINE_LINUX_DEFAULT= " line, but I'm pretty sure it is deprecated for Grub 2 and these newer kernels. I have not needed such a boot option since Grub 2 has been my bootloader (2 desktops and 2 notebooks).

It sounds more like some issue with powerdevil or the video driver.

When you choose K > Leave > Suspend to RAM, what happens? I see a brief message from PowerDevil, and then the screen goes black, drives shut down, and my power LED turns yellow and does a very slow blink to let me know that it is still alive.

**sisqonrw** · Feb 22, 2011, 03:18 PM

Re: suspend does not work

Originally posted by dibl

Are you trying to suspend to RAM, or suspend to disk?

Have you reviewed the settings in System Settings > Power Management, related to suspend and hibernate?

i am using suspend to RAM. I dont change anything on Power Management

**toad** · Feb 22, 2011, 04:03 PM

Re: suspend does not work

@ dibl

Cheers, I realize that all *buntus have the alias update-grub for "grub-mkconfig -o /boot/grub/grub.cfg" and that this command is called automatically on every kernel update but I was still curious as to how they do it

I was thinking of something in /etc/grub.d/ and /boot/grub/grub.cfg is always worth a look at. Point was telling grub where to resume from - I still have no idea how the *buntus do it...

For all its worth I maintain my own grub.cfg and it does not get overwritten. Also there is a kernel bug but that is in a 2.6.37 version but I dare say that is not applicable.

Anyway, over and out

**dibl** · Feb 22, 2011, 05:24 PM

Re: suspend does not work

@toad, as far as I can see, *buntu has pulled the Grub 2 system directly from Debian with the only changes being cosmetic (pull in plymouth splash screens, etc. etc.). The structure of /boot/grub/grub.cfg, /etc/default/grub, and the /etc/grub.d/ files all looks the same. So the scripts called by "sudo update-grub" are working the same as those from Debian.

@sisqonrw, I'm still interested to hear what happens, when you click the K menu, then choose "Leave" and then "Suspend to RAM".

Also, when you look in System Settings > Power Management > Capabilities, does it show that Suspend to RAM is supported?

Finally, what is your graphics chip, and which driver are you using? Have you tried disabling Desktop Effects?

**sisqonrw** · Feb 23, 2011, 06:45 AM

Re: suspend does not work

Originally posted by dibl

@sisqonrw, I'm still interested to hear what happens, when you click the K menu, then choose "Leave" and then "Suspend to RAM".

Also, when you look in System Settings > Power Management > Capabilities, does it show that Suspend to RAM is supported?

Finally, what is your graphics chip, and which driver are you using? Have you tried disabling Desktop Effects?

the screen will be black but my notebook is working. i cant do something. curiously this time it has worked.

it shows suspent to ram.

i have a nvidia geforce GT 320M. no i didnt tried to disable the Desktop Effects. i have to try it. but it works with effects before without any problems. and i want to use effects.

**sisqonrw** · Mar 27, 2011, 01:27 PM

Re: suspend does not work

can someone help me. suspend to ram does not work.

**Xinixs** · Mar 27, 2011, 02:08 PM

Re: suspend does not work

Try what I did in this thread: http://kubuntuforums.net/forums/inde...opic=3115961.0

Announcement

suspend does not work

suspend does not work

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Users Viewing This Topic