Thanks Carlos E.R for those interesting hints. Did you mean I should enter "resume=/dev/sda6" in /etc/grub.conf ? I entered it there and then ran /sbin/SuSEconfig but did not find any refernce to "resume" in /var/log/boot.msg or /var/log/messages Am rather edgy about altering configuration files outside Yast. In older versions one had to always run /sbin/SuSEconfig - is there any other way of involving Yast in this case ? Roy
Roy Leembruggen wrote:
Thanks Carlos E.R for those interesting hints.
Did you mean I should enter "resume=/dev/sda6" in /etc/grub.conf ? I entered it there and then ran /sbin/SuSEconfig but did not find any refernce to "resume" in /var/log/boot.msg or /var/log/messages
Am rather edgy about altering configuration files outside Yast. In older versions one had to always run /sbin/SuSEconfig - is there any other way of involving Yast in this case ?
Roy
Roy, You have to enter it in /boot/grub/menu.lst at the end of the 'kernel" line. What i often do is to replace the 'showopts' option to the front of this line (after /vmlinuz). Then the options after 'showopts' will be visible when booting. And of course you can do it with YaST -> System -> Bootloader options Peter Vollebregt
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-10-27 at 22:26 +0200, Roy Leembruggen wrote:
Thanks Carlos E.R for those interesting hints.
A note. You are using Kmail, but somehow threading info was missing from your email: the "in-reply-to" header is not present. Because of that, I did not notice your answer till this moment, by the purest chance.
Did you mean I should enter "resume=/dev/sda6" in /etc/grub.conf
No, in "/boot/grub/menu.lst", where the kernel command line is, assuming you use grub (the default in SuSE). You can do it using Yast (boot loader config) or manually, it doesn't matter. You will have something like this there: ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.3 kernel (hd1,1)/vmlinuz root=/dev/hdb6 vga=0x317 selinux=0 splash=verbose resume=/dev/hda9 showopts initrd (hd1,1)/initrd you only need to add the "resume=..." token there - and no need to run SuSEconfig later, it doesn't apply. Of course, use your right swap partition instead of the "..." dots. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDZBYptTMYHG2NR9URAhMDAJ95gJ5FryF6lX1OrJlecdnYI7L6KgCfbPW9 j+YFVZ8HzVGDNsqIGXr6skQ= =mgvV -----END PGP SIGNATURE-----
On Sunday 30 October 2005 02:38, Carlos E. R. wrote:
.... A note.
You are using Kmail, but somehow threading info was missing from your email: the "in-reply-to" header is not present. Because of that, I did not notice your answer till this moment, by the purest chance.
Sorry When in Windows XP I retrieved some of the suse-linux-e mail and used Outlook Express i.s.o Kmail - perhaps that's how the threading info was missing.
Did you mean I should enter "resume=/dev/sda6" in /etc/grub.conf
No, in "/boot/grub/menu.lst", where the kernel command line is, assuming you use grub (the default in SuSE). You can do it using Yast (boot loader config) or manually, it doesn't matter. You will have something like this there:
###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.3 kernel (hd1,1)/vmlinuz root=/dev/hdb6 vga=0x317 selinux=0 splash=verbose resume=/dev/hda9 showopts initrd (hd1,1)/initrd
you only need to add the "resume=..." token there - and no need to run SuSEconfig later, it doesn't apply.
Of course, use your right swap partition instead of the "..." dots.
--
1) Done that now 2) Also changed one line in /etc/sysconfig/powersave/common # Line below was BOOT_LOADER="" BOOT_LOADER="GRUB"
Cheers, Carlos Robinson
On Friday Peter Vollebregt wrote You have to enter it in /boot/grub/menu.lst at the end of the 'kernel" l ine. What i often do is to replace the 'showopts' option to the front of this line (after /vmlinuz). Then the options after 'showopts' will be visible when booting.
Done that also thanks at the same time in step 1) above Seems to be geeting close - to my surprise following a reboot after steps 1) and 2) above I actually managed subsequent <Suspend> and <Resume> (sort of). Makes no difference whether I use the command line "# powersave -U" or the Logout-->Suspend menu. (the console method shows no error messages and goes very fast into <Suspend>) but the following sequence repeats every time on <Resume> 1) the PC on/off button is pressed. 2) Select <SuSE Linux> on BootItNG boot menu 3) Messages flash by so rapidly that its difficult to keep track, but they do show that swap is actually being read. 4) "Warning: Device not power manageable appears" 5) Monitor power goes off 6) PC hard disk turns off but 'Power on' blue light remains on 7) Switch power off and on again 8) More messages flash by and normal desktop appears /var/log/suspend2disk.log suspend2disk initiated: 2005-10-30 20:55:15 Loaded modules: Module Size Used by ipt_pkttype 5632 1 ipt_LOG 11392 7 ipt_limit 6528 7 speedstep_lib 8452 0 freq_table 8832 0 snd_pcm_oss 67616 0 snd_mixer_oss 24704 1 snd_pcm_oss snd_seq 62864 0 snd_seq_device 13068 1 snd_seq button 11024 0 battery 14212 0 ac 9220 0 nvidia 3704300 12 rfcomm 48536 0 hidp 24320 2 usb_storage 81344 0 l2cap 35328 10 rfcomm,hidp ati_remote 15880 0 lirc_atiusb 22048 0 lirc_dev 18548 1 lirc_atiusb hci_usb 19592 2 bluetooth 57988 8 rfcomm,hidp,l2cap,hci_usb af_packet 31368 2 usblp 17024 0 usbhid 50656 0 edd 14560 0 tda9887 17424 0 tuner 40744 0 saa7134 118996 0 video_buf 26116 1 saa7134 via_rhine 28548 0 v4l2_common 9856 1 saa7134 ohci1394 39348 0 ieee1394 107960 1 ohci1394 v4l1_compat 17796 1 saa7134 mii 9600 1 via_rhine ir_common 12164 1 saa7134 i2c_i801 12812 0 i2c_core 25344 4 tda9887,tuner,saa7134,i2c_i801 videodev 13440 1 saa7134 generic 8452 0 [permanent] ehci_hcd 38920 0 snd_hda_intel 23296 1 snd_hda_codec 95872 1 snd_hda_intel intel_agp 26652 1 agpgart 38476 2 nvidia,intel_agp uhci_hcd 39440 0 usbcore 126848 9 usb_storage,ati_remote,lirc_atiusb,hci_usb,usblp,usbhid,ehci_hcd,uhci_hcd shpchp 100228 0 pci_hotplug 32188 1 shpchp
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-10-30 at 22:42 +0100, Roy Leembruggen wrote:
Seems to be geeting close - to my surprise following a reboot after steps 1) and 2) above I actually managed subsequent <Suspend> and <Resume> (sort of). Makes no difference whether I use the command line "# powersave -U" or the Logout-->Suspend menu. (the console method shows no error messages and goes very fast into <Suspend>) but the following sequence repeats every time on <Resume>
1) the PC on/off button is pressed. 2) Select <SuSE Linux> on BootItNG boot menu 3) Messages flash by so rapidly that its difficult to keep track, but they do show that swap is actually being read. 4) "Warning: Device not power manageable appears" 5) Monitor power goes off 6) PC hard disk turns off but 'Power on' blue light remains on 7) Switch power off and on again 8) More messages flash by and normal desktop appears
But... the suspended desktop, or a newly booted system?
/var/log/suspend2disk.log
You can increase verbosity of this log, it looks incomplete to me. Or perhaps it is not fully written till restore, and restore is failing. Also, some messages go to the kernel log, usually /var/log/messages - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD4DBQFDZhnLtTMYHG2NR9URAmHaAJICqnLy5kWssn99abZ8QWxzJiiSAJ9il59g v0CRkP1OUxKdaBxXtFe3zw== =Mtn8 -----END PGP SIGNATURE-----
On Monday 31 October 2005 14:19, Carlos E. R. wrote:
The Sunday 2005-10-30 at 22:42 +0100, Roy Leembruggen wrote:
Seems to be geeting close - to my surprise following a reboot after steps 1) and 2) above I actually managed subsequent <Suspend> and <Resume> (sort of). Makes no difference whether I use the command line "# powersave -U" or the Logout-->Suspend menu. (the console method shows no error messages and goes very fast into <Suspend>) but the following sequence repeats every time on <Resume>
1) the PC on/off button is pressed. 2) Select <SuSE Linux> on BootItNG boot menu 3) Messages flash by so rapidly that its difficult to keep track, but they do show that swap is actually being read. 4) "Warning: Device not power manageable appears"
Turns out on reading /var/log/messages that the warning "Device not power manageable" occurs even during a normal boot-up, and refers to some other device, not the Monitor. quote "Oct 30 21:07:44 linux kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Oct 30 21:07:44 linux kernel: ACPI-0212: *** Warning: Device is not power manageable" unquote
5) Monitor power goes off 6) PC hard disk turns off but 'Power on' blue light remains on 7) Switch power off and on again 8) More messages flash by and normal desktop appears
But... the suspended desktop, or a newly booted system?
Newly booted system. (Checked by leaving Patience card game on desktop and then suspending) - card game was gone on resume. Never ever had a case where monitor and hard disk are turned off by an Operating System during booting ! Wonder which executable file triggers this event.
/var/log/suspend2disk.log
You can increase verbosity of this log, it looks incomplete to me. Or perhaps it is not fully written till restore, and restore is failing.
Also, some messages go to the kernel log, usually /var/log/messages
-- Cheers, Carlos Robinson
Regards Roy Leembruggen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-10-31 at 20:46 +0100, Roy Leembruggen wrote:
Turns out on reading /var/log/messages that the warning "Device not power manageable" occurs even during a normal boot-up, and refers to some other device, not the Monitor.
quote "Oct 30 21:07:44 linux kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Oct 30 21:07:44 linux kernel: ACPI-0212: *** Warning: Device is not power manageable" unquote
I don't think it matters when suspending to disk, but it would for low power states, or perhaps for suspending to memory.
But... the suspended desktop, or a newly booted system?
Newly booted system. (Checked by leaving Patience card game on desktop and then suspending) - card game was gone on resume. Never ever had a case where monitor and hard disk are turned off by an Operating System during booting ! Wonder which executable file triggers this event.
Suspend to disk and such are controlled by scripts in /usr/lib/powersave/ Try setting in "/etc/sysconfig/powersave/common": POWERSAVED_DEBUG="31" and then watch the logs after suspending. It will need a reboot to activate it, or carefully killing and restarting a few things. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDZpxPtTMYHG2NR9URAtQVAKCND+9OlbMUkfWfCzxTPIWp823HAgCfZeMK MN8TkiKWgBwMQi8X2mt3Rgk= =WMqm -----END PGP SIGNATURE-----
On Monday 31 October 2005 23:35, Carlos E. R. wrote:
......... ......... Suspend to disk and such are controlled by scripts in /usr/lib/powersave/
Try setting in "/etc/sysconfig/powersave/common":
POWERSAVED_DEBUG="31"
and then watch the logs after suspending. It will need a reboot to activate it, or carefully killing and restarting a few things.
-- Cheers, Carlos Robinson
Set DEBUG=31
Debug info in /var/log/messasges (only part pertaining to 'empty values') to save space
linux [powersave]: Info (readConfigFile:114) Empty value in file /etc/sysconfig/powersave/thermal
linux [powersave]: Info (readConfigFile:114) Empty value in file /etc/sysconfig/powersave/cpufreq
linux [powersave]: Info (readConfigFile:114) Empty value in file /etc/sysconfig/powersave/battery
linux [powersave]: Info (readConfigFile:114) Empty value in file /etc/sysconfig/powersave/sleep
.... linux [powersave]: Info (readConfigFile:114) Empty value in file /etc/sysconfig/powersave/common line 63, key 'NOTIFY_METHOD' line 77, key 'ACPI_MODULES' line 89, key ACPI_MODULES_NOT_TO_UNLOAD' line 113, key 'POLLING_INTERVAL' line 124, key 'SCREENSAVER_DPMS_OFF' line 136, key 'SCREENSAVER_BLANKONLY' line 148, key 'POWERBTN_DELAY' line 16, key 'ENABLE_THERMAL_MANAGEMENT' line 34, key 'THERMAL_POLLING_FREQUENCY' line 15, key 'CPUFREQD_MODULE' line 24, key 'CPUFREQD_MODULE_OPTS' line 48, key 'CPU_HIGH_LIMIT'Nov 3 10:04:21 linux [powersave]: Info (readConfigFile:114) Empty value in file /etc/sysconfig/powersave/cpufreq line 62, key 'CPU_HYSTERESIS' line 74, key 'CPU_IDLE_TIMEOUT' line 85, key 'CPU_IDLE_LIMIT' line 95, key 'CONSIDER_NICE' line 107, key 'JUMP_CPU_FREQ_MAX_LIMIT' line 33, key 'BATTERY_POLLING_INTERVAL' line 43, key 'FORCE_BATTERY_POLLING' line 24, key 'UNLOAD_MODULES_BEFORE_SUSPEND2DISK' line 34, key 'UNLOAD_MODULES_BEFORE_SUSPEND2RAM' line 44, key 'UNLOAD_MODULES_BEFORE_STANDBY' line 58, key 'SUSPEND2DISK_RESTART_SERVICES' line 59, key 'SUSPEND2RAM_RESTART_SERVICES' line 60, key 'STANDBY_RESTART_SERVICES' line 75, key 'SUSPEND2DISK_UNMOUNT_FATFS' line 76, key 'SUSPEND2RAM_UNMOUNT_FATFS' line 77, key 'STANDBY_UNMOUNT_FATFS' line 87, key 'SUSPEND2DISK_EJECT_PCMCIA' line 88, key 'SUSPEND2RAM_EJECT_PCMCIA' line 89, key 'STANDBY_EJECT_PCMCIA' line 97, key 'DISABLE_USER_SUSPEND2DISK' line 106, key 'DISABLE_USER_SUSPEND2RAM' line 114, key 'DISABLE_USER_STANDBY' line 124, key 'SUSPEND2DISK_DELAY' line 125, key 'SUSPEND2RAM_DELAY' line 126, key 'STANDBY_DELAY' line 137, key 'SUSPEND2DISK_SHUTDOWN_MODE' line 146, key 'SUSPEND2DISK_RESTORE_CLOCK' line 147, key 'SUSPEND2RAM_RESTORE_CLOCK' line 148, key 'STANDBY_RESTORE_CLOCK' line 159, key 'SUSPEND2DISK_IGNORE_KERNEL_MISMATCH' line 170, key 'SUSPEND2DISK_SWITCH_VT' line 171, key 'SUSPEND2RAM_SWITCH_VT' line 172, key 'STANDBY_SWITCH_VT' data to processthermal_zone, dev_name: THRM, port: 00000081, count: 00000000 By the way, my son running Linux Fedora said his 'Suspend' mode worked after installation without a hitch - wonder why SuSE 10 needs so much user input ? Regards Roy Leembruggen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2005-11-08 at 22:25 +0100, Roy Leembruggen wrote:
Try setting in "/etc/sysconfig/powersave/common":
POWERSAVED_DEBUG="31"
Set DEBUG=31
Is that the setting you used? Perhaps 10 differs from 9.3 in some details.
Debug info in /var/log/messasges (only part pertaining to 'empty values') to save space
.... linux [powersave]: Info (readConfigFile:114) Empty value in file /etc/sysconfig/powersave/common line 63, key 'NOTIFY_METHOD' line 77, key 'ACPI_MODULES'
I don't know what this error, if it is an error, means; I think it is just informative, debug mode is very verbose. I also have similar messages (though fewer), but it works. My intention was to see the messsages just when suspending.
By the way, my son running Linux Fedora said his 'Suspend' mode worked after installation without a hitch - wonder why SuSE 10 needs so much user input ?
In the same hardware? Dunno. Perhaps differente choice of settings, diferent kernel.... Mine worked pretty easily, once I knew what program to use. I think the only settings I had to modify was to enable suspend to disk, it was dissabled. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDcU/YtTMYHG2NR9URAn+TAJ484qxZU045IA2MKcoiHdx6JSNyHwCeOrTz P8xa2yuEixk8fuKFHhL7lR0= =ei2j -----END PGP SIGNATURE-----
participants (3)
-
Carlos E. R. -
Peter Vollebregt -
Roy Leembruggen