https://bugzilla.novell.com/show_bug.cgi?id=223722 ------- Comment #14 from seife@novell.com 2006-12-04 04:59 MST ------- (In reply to comment #13)
I was thinking about "boot, install 5 additional kernel versions, suspend". Well, then this scenario is as well unsupported as you didn't reboot after those kernelupdates.
Wrong. This is supported as long as the original kernel image (the one that is running _now_ ist still available in /boot and an entry for it exists in menu.lst. At least this is supported up to now and i'd like to keep it that way (just because i install an additional kernel for debugging, i do not want to loose the ability to suspend)
No, the changed kernel won't even be able to resume. That's why we refuse to suspend in this case. Then it should also be refused in your case above where you have 5 kernelupdates.
Wrong. It is not "kernelupdates", it is "additional kernel". Following scenario: Boot with: Opensuse-10.2 Windows Opensuse-10.2-failsafe. You decide to build some additional kernels to test some new features, but not now, so you install them. Afterwards you have got: kernel-2.6.19-mm1 kernel-2.6.19-mm2 kernel-2.6.18-mm3-reallyfsckedupdebugpatch Opensuse-10.2 Windows Opensuse-10.2-failsafe. With the "index", you are no longer able to suspend. With my method (find the matching kernel), you are still able to suspend. We'll discuss this. :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.