Suspend to Disk geht nicht, Suspend to RAM schon, nachdem dem Kernel beim Start (grub) "acpi_sleep=s3_bios" mitgegeben worden ist. Ein Suspend to ram geht aber nicht mit Suse-Suspend-to-RAM sondern mit dem Befehl: echo mem > /sys/power/state. Bei Suse-Suspend-to-RAM wird nur der Bildschirm gelockt, ich muss dann das Passwort des Users eintippen. Laut /usr/lib/powersave/do_acpi_sleep gibt es ein /var/log/suspend2disk.log, das stimmt aber nicht. (Auch ein /var/log/suspend2ram.log gibts nicht) Laut /var/log/pm-suspend.log das es dann wider Erwarten gibt, gibts Probleme, das die Skripte von einer hda (IDE-Festplatte) ausgehen und nciht von einer SATA: [...] /org/freedesktop/Hal/devices/storage_serial_M006A485500 unregistered /sys/block/hda common_functions: line 36: /sys/block/hda/device/delete: Permission denied ibm_undock hooks/thinkpad/50generic: line 19: echo: write error: No such device ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/30s2disk-check ===== [...] das gesamte /var/log/pm-suspend.log im Anhang. Trotzdem wird später die sda1 als resume-Disk genommen, darauf wird beim Suspend to Disk auch für den Bentutzer auf der Textkonsole sichtbar geschrieben, wenn von 1% auf 100% hochgezählt wird: [...] INFO: checking for suspend-to-disk prerequisites... using userspace suspend method setting resume device to /dev/sda1 setting image size to 956241100 adding these parameters from /etc/suspend.conf: [...] Das Suspend-to-Disk schein zu funktionieren. Auf Konsole 1 erscheint der Text, der von 1% auf 100% hochzählt: Preparing hibernate... suspend: Snapshotting system suspend: System snapshot ready. Preparing to write suspend: Image Size: 363460 kilobyte suspend: Free swap: 2093972 kilobyte suspend: Saving 90864 image data pages (press backspace to abort) ... 100% done (90864 pages) S Das "S" am Ende ist kein Tippfehler von mir, sondern erscheint immer. Dann hängt der Laptop. Eingefroren! Tupfegleicher Fehler bei google schon mal beschrieben: http://www.nabble.com/suspend-to-disk-@-Lenovo-R60-t3125354.html Ein Erfolgsbericht eines Anwenders eines R60: http://www.t-hq.de/linux/SuSE_auf_Tinkpad_R60.html (ob der auch eine SATA hat, frage ich derzeit noch an) Beim Hochfahren nach einem mißlungenen resume-to-disk starte grub sofort Suse 10.2. Grub erscheint nicht! Es liegt also ein teilweise erfolgreicher suspend-to-disk vor. Nur wird beim booten dann nicht resumed, sondern frisch gebootet. Hier das gesamte /var/log/pm-suspend.log: Wed Feb 14 21:32:46 CET 2007: running suspend hooks. ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/00clear ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/01logging ===== suspend initiated: Wed Feb 14 21:32:46 CET 2007 Module Size Used by fglrx 530136 9 nvram 12808 1 ipv6 263584 20 uinput 12800 1 vmnet 45484 3 vmmon 113836 0 snd_pcm_oss 53376 0 snd_mixer_oss 21248 1 snd_pcm_oss snd_seq 60272 0 snd_seq_device 12812 1 snd_seq af_packet 29320 0 cpufreq_conservative 11912 0 cpufreq_ondemand 10892 1 cpufreq_userspace 9088 0 cpufreq_powersave 5888 0 speedstep_centrino 12832 2 freq_table 8832 1 speedstep_centrino ibm_acpi 33024 0 button 10896 0 battery 14340 0 ac 9476 0 apparmor 55572 0 aamatch_pcre 18304 1 apparmor nls_iso8859_1 8320 1 nls_cp437 9984 1 vfat 16640 1 fat 55324 1 vfat loop 20488 0 dm_mod 60184 0 rfcomm 45208 0 hidp 23680 2 l2cap 30976 10 rfcomm,hidp hci_usb 20636 2 bluetooth 57188 8 rfcomm,hidp,l2cap,hci_usb pcmcia 40892 0 ipw3945 191520 1 ieee80211 34632 1 ipw3945 ieee80211_crypt 10112 1 ieee80211 ide_cd 42272 0 cdrom 38432 1 ide_cd ohci1394 37040 0 firmware_class 14080 2 pcmcia,ipw3945 tg3 104580 0 yenta_socket 30348 1 rsrc_nonstatic 17024 1 yenta_socket ieee1394 102584 1 ohci1394 pcmcia_core 43412 3 pcmcia,yenta_socket,rsrc_nonstatic ehci_hcd 34696 0 snd_hda_intel 23060 1 snd_hda_codec 164352 1 snd_hda_intel snd_pcm 86916 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 27908 2 snd_seq,snd_pcm intel_agp 27804 1 uhci_hcd 26892 0 snd 61188 10 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer soundcore 13792 1 snd snd_page_alloc 14472 2 snd_hda_intel,snd_pcm i2c_i801 11660 0 i2c_core 25216 1 i2c_i801 agpgart 35528 2 fglrx,intel_agp usbcore 114896 3 hci_usb,ehci_hcd,uhci_hcd parport_pc 42084 0 lp 15652 0 parport 39752 2 parport_pc,lp ext3 141192 2 mbcache 12804 1 ext3 jbd 70324 1 ext3 sg 38044 0 edd 13892 0 fan 8964 0 ahci 25860 4 libata 119188 1 ahci piix 13700 0 [permanent] thermal 18568 0 processor 34664 2 speedstep_centrino,thermal sd_mod 24576 5 scsi_mod 136712 4 sg,ahci,libata,sd_mod ide_disk 20480 0 ide_core 129992 3 ide_cd,piix,ide_disk total used free shared buffers cached Mem: 1034816 489396 545420 0 12832 302264 -/+ buffers/cache: 174300 860516 Swap: 2094080 0 2094080 ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/05led ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/06autofs ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/10NetworkManager ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/23dock ===== Wed Feb 14 21:32:46 CET 2007: running thinkpad hooks for event undock. x60 undock /org/freedesktop/Hal/devices/storage_serial_M006A485500 unregistered /sys/block/hda common_functions: line 36: /sys/block/hda/device/delete: Permission denied ibm_undock hooks/thinkpad/50generic: line 19: echo: write error: No such device ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/30s2disk-check ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/45pcmcia ===== ejecting PCMCIA cards... ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/50modules ===== trying to unload: button ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/80acpi-fan ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/80videobios ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/94cpufreq ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/95led ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/99Zgrub ===== ===== Wed Feb 14 21:32:46 CET 2007: running hook: /etc/pm/hooks/99info ===== Wed Feb 14 21:32:46 CET 2007: finished suspend hooks. Machine is unknown. This machine can be identified by: sys_vendor = "LENOVO" sys_product = "94615FG" sys_version = "ThinkPad R60" bios_version = "7CETB5WW (2.05 )" See http://en.opensuse.org/S2ram for details. If you report a problem, please include the complete output above. Wed Feb 14 21:32:50 CET 2007: running resume hooks. ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/99info ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/99Zgrub ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/95led ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/94cpufreq ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/80videobios ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/80acpi-fan ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/50modules ===== trying to reload: button ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/45pcmcia ===== inserting PCMCIA cards... ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/30s2disk-check ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/23dock ===== Wed Feb 14 21:32:50 CET 2007: running thinkpad hooks for event dock. ibm_dock hooks/thinkpad/50generic: line 14: echo: write error: No such device x60 dock rescanning /sys/class/scsi_host/host3 rescanning /sys/class/scsi_host/host2 rescanning /sys/class/scsi_host/host1 ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/10NetworkManager ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/06autofs ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/05led ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/01logging ===== ===== Wed Feb 14 21:32:50 CET 2007: running hook: /etc/pm/hooks/00clear ===== Wed Feb 14 21:32:50 CET 2007: finished resume hooks. ... und mein /etc/powersave/sleep: # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # The settings made in this file are ignored. The new method of doing # suspend is pm-utils. All related code will be removed from powersaved # very soon. For more information have a look at # http://en.opensuse.org/Pm-utils ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Description: Configuration of all three sleep modes (S2 is not supported): ## S1 sleep (only ACPI) low wake-up latency, ## S3 (ACPI) suspend to ram or (on APM systems) standby and ## S4 (ACPI) suspend to disk or (on APM systems) suspend. ## ## For some hardware, modules have to be unloaded before entering the ## sleep state. You can configure these in this section. These modules ## will be unloaded in the specified order. Modules which depend on one ## of the specified modules, will also be unloaded. If not all modules ## can be unloaded, entering the sleep state will fail. ## After resuming, the modules that have been unloaded will be reloaded ## in reverse order. ## The same applies for the "SERVICES_TO_RESTART"-variables which defines ## services which have to be stopped before entering a sleep state. ## Path: System/Powermanagement/Powersave/Sleep_Modes ### Type: string ## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper" ## ServiceRestart: # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # These modules will be unloaded before entering suspend to disk # See README.unload-modules for more information. # "NONE" means don't unload any modules. UNLOAD_MODULES_BEFORE_SUSPEND2DISK="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ### Type: string ## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper" ## ServiceRestart: # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # These modules will be unloaded before entering the corresponding # sleep state. See README.unload-modules for more information. # "NONE" means don't unload any modules. UNLOAD_MODULES_BEFORE_SUSPEND2RAM="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ### Type: string ## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537 ndiswrapper" ## ServiceRestart: # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # These modules will be unloaded before entering the corresponding # sleep state. See README.unload-modules for more information. # "NONE" means don't unload any modules. UNLOAD_MODULES_BEFORE_STANDBY="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: string ## Default: "slmodemd irda upsd apcupsd" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # All services that have to be stopped before entering a sleep mode # and restarted after the machine resumes. # If you notice problems of some services that may be related to # suspend/standby, restarting the service may solve the problem. # The names to enter here are simply the filenames of the init scripts # in /etc/init.d. The services are stopped in the order entered here. # They are restarted after resume in the reverse order. # Entering "NONE" disables restarting of services ("" means default). SUSPEND2DISK_RESTART_SERVICES="" SUSPEND2RAM_RESTART_SERVICES="" STANDBY_RESTART_SERVICES="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "yes" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # Should FAT and NTFS filesystems be unmounted before entering # a sleep mode and remounted after the machine resumed? # You should do this for suspend to disk if you want to boot # Windows while Linux is suspended to avoid severe data corruption # on the Windows filesystems. # Note that suspend will fail if the partitions cannot be unmounted. # This may cause problems with external storage media connected during # suspend. # Defaults to yes for suspend to disk, no for suspend to RAM / standby. SUSPEND2DISK_UNMOUNT_FATFS="" SUSPEND2RAM_UNMOUNT_FATFS="" STANDBY_UNMOUNT_FATFS="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # Should PCMCIA cards (CardBus and PC-Card) be ejected before entering # a sleep mode and reinserted after the machine resumed? # This should not be necessary for most CardBus cards, PC-Cards seem to # need this more often. SUSPEND2DISK_EJECT_PCMCIA="" SUSPEND2RAM_EJECT_PCMCIA="" STANDBY_EJECT_PCMCIA="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" ## ServiceRestart: powersaved # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # If /usr/sbin/s2ram is installed but does not know about your machine, # you can force suspend to RAM for unknown machines by setting this # variable to yes. # Be careful, this might crash your machine. # See also the SUSPEND2RAM_ACPI_SLEEP, SUSPEND2RAM_VBE_POST and # SUSPEND2RAM_VBE_SAVE variables. SUSPEND2RAM_FORCE="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: integer(0:3) ## Default: "0" ## ServiceRestart: powersaved # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # If SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can set # the acpi_sleep parameter here. This is a number, 1 means "s3_bios", # 2 means "s3_mode" 3 means "s3bios,s3mode". # These parameters are explained in the kernel sources under # Documentation/power/video.txt # Leaving this empty or setting it to 0 means "don't touch this setting", # you might still have one of the options set from the kernel commandline. # Be careful, this might crash your machine. SUSPEND2RAM_ACPI_SLEEP="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" ## ServiceRestart: powersaved # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # if SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can enable # the equivalent of "vbetool vbestate save/restore" before/after suspend to # RAM with this variable. This does restore the state of the graphics chip # on many machines. # Be careful, this might crash your machine. SUSPEND2RAM_VBE_SAVE="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" ## ServiceRestart: powersaved # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # if SUSPEND2RAM_FORCE is set to yes and s2ram is installed, you can enable # the equivalent of "vbetool post" after suspend to RAM. This reinitializes # the graphics chip on many machines. # Be careful, this might crash your machine. SUSPEND2RAM_VBE_POST="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: string(platform,firmware,shutdown,reboot) ## Default: "platform" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # Specify the shutdown method the kernel uses after suspend-to-disk. # "shutdown" is known to work on most machines, "platform" may work, # too. "firmware" will most likely not work, "reboot" is for # debugging only. Use only if you know what this is for. # This has no effect for userspace suspend. Use /etc/suspend.conf there. SUSPEND2DISK_SHUTDOWN_MODE="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # Should the system clock be reset from the hardware clock after # suspend-to-disk or suspend-to-RAM? This may be unneccessary depending # on kernel version and SUSPEND2DISK_SHUTDOWN_MODE, but will not hurt. SUSPEND2DISK_RESTORE_CLOCK="" SUSPEND2RAM_RESTORE_CLOCK="" STANDBY_RESTORE_CLOCK="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # Should we suspend to disk even if it seems the kernel in /boot # is not matching the running kernel? This is very dangerous, if # the kernels don't match, resume will not work. Use only if you # absolutely need to (e.g. you are compiling a custom kernel). # SUSPEND2DISK_IGNORE_KERNEL_MISMATCH="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # Should we switch to a text console _in userspace_ before entering # a sleep mode? The kernel usually does this anyway, but if you need # to run some initialization code before switching back to X, this # might be handy. Also on ppc, the kernel does not switch, so this needs # to be "yes" there. SUSPEND2DISK_SWITCH_VT="" SUSPEND2RAM_SWITCH_VT="" STANDBY_SWITCH_VT="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: integer ## Default: 500 # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # The size of the image in MB that will be written to disk upon suspend. # A bigger image will make your system feel more responsive after resume, # but take additional time for writing and reading your data. # This value specifies the maximum image size to use. The image can be # smaller if not enough swap is available or memory usage is low, it also # can be bigger if the size is not enough for suspending the machine. # setting it to "0" will restore the old behaviour and always create the # smallest possible image. # This has no effect for userspace suspend. Use /etc/suspend.conf there. SUSPEND2DISK_IMAGE_SIZE="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: string ## Default: "" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # to make sure that there is enough swap available, you can configure an # additional swap partition, which will only be used for suspend. This # partition should not be in /etc/fstab and should not normally be used. # Its size should be the amount of physical RAM the machine has, or at # least SUSPEND2DISK_IMAGE_SIZE. # Enter the device node of this partition here to have it activated before # suspend and deactivated after resume. # You also need to make sure that the resume= boot parameter points to # this partition. SUSPEND2DISK_RESUME_DEVICE="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: string ## Default: "userspace" # # DEPRECATED! Configuration for suspend is done in /etc/pm/config # # choose the method used to suspend to disk. There are two choices: # - the shiny new userspace suspend. Needs the "suspend" package # installed and configured in /etc/suspend.conf. Is much faster # and generally considered "state of the art". Needs a recent kernel # 2.6.17+ # - the old in-kernel suspend, that's proven, reliable and slow. # Since we want to suspend and resume fast, "userspace" is default. SUSPEND2DISK_METHOD="" wer weiss weiter? Gruss Ekkard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-mobile-de+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mobile-de+help@opensuse.org