The swsusp2 patch does not apply cleanly to the 2.6.11-mm kernel. Do you know how hard it is to do the matches manually?

Depends on how many chunks are failing... suspend2 is a big patchset but usually you don't need all of the patches. Simply take a look at the names, if you don't use bootsplash, then you don't need to apply the bootsplash patch either.

in konsole everything works just fine with 2.6.11-morph2 sources but X freezes constantly,...

Hi EASYdoor,

Suspend-to-disk works with the latest ati-drivers and xorg 6.8.2 if you install vbetool, which is not currently in portage.
The ebuild attached to this bugreport works fine for me: http://bugs.gentoo.org/show_bug.cgi?id=82325
vbetool is used to save/restore the state of the videocard.

Just download the gentoo-sources directory on your PORTAGE_OVERLAY, for example /usr/local/portage/sys-kernel.
And then download the patch files in the distfiles to your /usr/portage/distfiles.
Third step is emerge.
After emerge, you must build the kernel sources using make menuconfig or other things.
If you finish the kernel compile (maybe 'make bzImage modules modules_install install), you will get the new kernel image. The name in the /boot should be vmlinuz-2.6.11.5. With this name, you correct your lilo file or grub file.
This patch files is not perfect, so take your own risk.

does anyone know what the specific patched in gentoo-sources are that conflict with the swsusp2 patch? i'm still using a 2.6.7 kernel just mainly because it was such a pain to patch in this patch properly. it would be really nice if htere were a gentoo-laptop-sources with this patch, or even better if hte vanilla sources would adopt this patchset.

make xconfig or menuconfig (save yourself some time by copying your old .config and do a make oldconfig first!)
make
make modules_install

then install the kernel in boot & updated grub/lilo/etc.

Arbitrarily dropping patch files sounds like a bad idea to me though. We really need a proper merge. If you have gentoo splash installed (splashutils) it's much worse of course.

I agree with you. Arbitrary dropping of patch files is not good. But if you know what the patch files do, it doesn't matter. The inclusion of the software suspend 2 patchset to the kernel tree is desirable, but now it is just our or my desire. By the way, I don't use this patch set any more. Now, I am satisfied with the ACPI suspend (to ram), which is supported by kernel without patch. It works well except a few patch in the user-level.

i couldn't find how to work the wiki that was posted (or rather what i was suppose to add my name to).

i'm interested in more information about this suspend to ram feature. that would also be nice. i think my win xp can suspend to ram for some time before it fully hibernates (ala swsusp2). my battery only lasts about an hour, probably less on this laptop. it's pretty silly how these batteries are

im reading and following the howto
it seems that installing their unofficial ebuild (sys-kernel/suspend2-sources) doesn't actually patch you current kernel sources but rather install new ones... does it differe from gentoo-sources only by the fact that suspend2 is patched in the kernel or is it actually based on a normal 2.6.11.9 kernel (which makes us loose benefit of the patches applied to the 2.6.11 by gentoo-sources)

gentoo-sources differ so much from official/vanilla, that it's usually not possible to apply the suspend2 patchset to gentoo-sources. So I guess this inofficial ebuild (suspend2-sources) installs a vanilla kernel sourcetree first. The only extra patch it contains is an fbsplash or so. Take a look at what it downloads, or directly at the ebuild.

No. It's saying "I couldn't apply a patch. do you want me to undo what I've already done?" This is because these patches don't apply all too well to gentoo-sources.

The easiest thing is to use the vanilla sources. Many of the patches in the gentoo patchset are actually compatible with suspend2, maybe simply try the ones you really need only. The gentoo patchset is downloaded to /usr/portage/distfiles/genpatches-2.6.*.tar.bz2 when you install gentoo-sources.

I think they should add suspend2 in the gentoo patchset (and mark it as experimental) it's a pain in the ass otherwise

no, i'm hesitating: vanilla flavor + suspend2 or gentoo flavor?
will the splashutils work properly with vanilla patched by suspend2 ?
what are the benefits of the gentoo patchset?_________________I am not sending subliminal messages

That's right - the vanilla sources 2.6 used to be called "development-sources" but now they're called "vanilla-sources" as 2.6 is not in dev status any more.

Quote:

I think they should add suspend2 in the gentoo patchset (and mark it as experimental) it's a pain in the ass otherwise

As I said, there seem to be way too many collisions (suspend2 <-> gentoo patchset). Solving these would be a lot of manual work (and maybe even some incompatibilities).

Quote:

no, i'm hesitating: vanilla flavor + suspend2 or gentoo flavor?
will the splashutils work properly with vanilla patched by suspend2 ?
what are the benefits of the gentoo patchset?

I don't know about the latter. The only thing I know is that a well working suspend system is much more important and useful to me than any splash screen
Maybe someone else here could enlighten us regarding this compatibility quostion (splashutils + suspend2)...?

im compiling a kernel with swsup2 and splashutils compatibility
we'll see if it works

my laptop doesn't have a big hdd (like most laptops) so my swap partition is only 430Mb whereas I have 1Gb RAM
i chose to use a file instead of the swap partition to hibernate, anyone has tested it before? does this properly work?_________________I am not sending subliminal messages

It's already there just uncomment it. 1000 is the size of the /suspend_file. You don't need that much if you use compression which is very much recommended.

The first time you try to suspend it should take a while to create the suspend file.

Then configure your grub as follows (from the page above):

Quote:

For the filewriter, you should first prepare your suspend file - this can be done by configuring your hibernate.conf file with the "FilewriterLocation" option, and running hibernate --no-suspend. Then take a look in /proc/software_suspend/resume2 for what to pass to your kernel. You should see something like file:/dev/hda7:0x10011f, in which case you should append "resume2=file:/dev/hda7:0x10011f" as a kernel parameter in your lilo.conf file or GRUB's menu.lst.

ok, thank you very much, although I browsed the whole site of suspend2, it seems I missed out this piece of information!
I will try by the end of the week, not before because I have exams and I need my laptop so I don't want to mess with it

from what i've read @ suspend2's website, bad use of swsup2 can compromise your data (as in screw up your filesystem)
if, say, suspend to file doesn't work for me. I'll go in hibernate mode and won't be able to resume. Ok fine, can I boot normally afterwards? Or will I be screwed and my root fs stuck by the hibernation process for some reason?

I mean, is it safe to give it a try or should I take care to backup my root fs before trying?_________________I am not sending subliminal messages

I mean, is it safe to give it a try or should I take care to backup my root fs before trying?

In my opinion suspend2 is fairly mature (read: I haven't had any problems with it). But as always, backups are good anyway.

Suspending and then not using the image to resume is not very dangerous. That should be no problem if you use a decent filesystem.

You will have a big problem though when you resume from an image that is too old (meaning that you have rebooted before using this image). This most definitely WILL screw up all your filesystems BADLY.

So here's how to screw up your fs (i.e. DON'T DO THIS):
1. suspend
2. reboot, but without using the image from step 1
3. resume from the image from step 1

it's obvious that resuming an image after having rebooted normally will screw things up, I wouldn't try that anyway
from what I understood, you should use the noresume2 option when you want to reboot normally -- I guess this destroyes the suspended data so you can't resume the older session later on

I will try all that tomorrow or after tomorrow
thank you for your advices !_________________I am not sending subliminal messages

sterror: Thanks for the HOWTO, I use LVM + dmcrypt too.
I also tried patching a hardened gentoo kernel (Use PaX) with swsusp2 manually.

Well, it's a sad thing, but after a long day of manually patching things (more than 20 files I believe, which include more than one patch per file), my kernel wouldn't compile (It was the first time I was manually patching a kernel).
Anyway, I'm afraid since I use LVM and encrypted swap, it will be really difficult to get it to work, but it would be a begin if my kernel just compiled. (Backed up everything, so screwing up isn't too bad). As a summary, half of the patches 'merged' cleanly against the 2.6.7 hardened kernel I was using then, some were patches to files I didn't seem to have, some were rather easy to patch manually, and some were too difficult.

So if there are people who have tips for manually patching a kernel, please tell me!

By the way, are kernel patches cumulative? I think so, because if they were independent, it would be possible to add swsusp2 patches to the hardened gentoo patches._________________Registered Linux user #368987

Suspend-to-disk works with the latest ati-drivers and xorg 6.8.2 if you install vbetool, which is not currently in portage.
The ebuild attached to this bugreport works fine for me: http://bugs.gentoo.org/show_bug.cgi?id=82325
vbetool is used to save/restore the state of the videocard.

I am using a 2.6.11 vanilla-flavor with swsusp2-patches, but i am going to try the morph-sources soon.

Enjoy,

Bobo

Thank you very much for your tip - my nx7010 works with the frglx and swsusp2 and vbetool without X-crashes ...
... and the vbetool is in the portage (masked) now!_________________Greetings from Vienna