Messages in this thread | | | From | "Norman Diamond" <> | Subject | 2.6.0 swsusp | Date | Sun, 28 Dec 2003 11:33:12 +0900 |
| |
On a machine with working ACPI, I compiled 2.6.0 with Software Suspend (Experimental).
1. Help information says that the next boot can be done with "resume=/dev/swappartition" or with "noresume". It does not say how the swsusp command decides which swap partition to save to. The man page (which still isn't sure if the command is named swsusp or suspend) also doesn't say. How can I guess which swap partition to designate at resume time? For the moment this is a hypothetical question because I haven't needed to make a second swap partition on this machine yet.
2. When I forgot to say either "resume" or "noresume", the kernel detected that it could not use the swap partition, but it did not offer the possibility to resume. Surely it could detect early enough that the swap partition is not usable for swap but is usable for resume, and could ask the user whether to do a "resume" or "noresume".
3. When swsusp completed its writing, it decided that my ACPI BIOS could not power off automatically. I wonder why. No other OS has trouble powering off this machine. Also on machines with older APM BIOSes, no OS had trouble powering off the machines, not even Linux with APM drivers. So I could hold the power switch for 4 seconds and the BIOS beeped a warning before powering off, but I wonder why it was necessary.
By the way on this machine, the keyboard's hotkey Fn+F7 correctly causes hibernation performed by the BIOS, and Fn+F10 correctly causes suspend to RAM. In both cases the power key correctly causes a resume, with resume from hibernation being done by the BIOS. Even though this is an ACPI machine, the BIOS still has hibernation (using a dedicated partition) because it was originally sold with Windows 98. On my previous crash box with APM, hotkeys Fn+F7 and Fn+F10 (and others) got broken by 2.6.0-test kernels and could only be fixed by booting 2.4.nn kernels. Since I sold my previous crash box, I can't check if 2.6.0 solved that breakage or if APM still necessitates using 2.4.20.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |