What exactly do I have to do to reverse this patch? Do I need to add a line to the ebuild? I ask this because looking at the patch it is wanting to look at linux-2.6.7-rc3-mm1 and when I try to `patch -R < reiser.....` it doesn't have any of those files to look at. So I am assuming I'm doing something wrong.

umm why not have the swuf2 patches in the love ? they are for hibernating stuff in linux ! i think they cud make a great addition..

Bye,
jazz_________________In 2010, M$ Windows will be a quantum processing emulation layer for a 128-bit mod of a 64-bit hack of a 32-bit patch to a 16-bit GUI for an 8-bit operating system written for a 4-bit processor from a 2-bit company that can't stand 1 bit of competition.

Ive checked and that part of the file is identical with the siimage.h from 2.6.6-rc3-love4. Also since I don't have a 3512 could I get away with just commenting it out ot something?

mmm, go into the file and comment out the lines with .device and .vendor

now.. must laugh at oneofone cause I always have this fix mwuahhahahha

-DaMouse

/me beats DaMouse with a winme CD
@Peacefaker using nvidia and it works fine, you need to disable regparm and 4k stacks.
@tsr you need to enable ACPI, looks like its broken in -mm
@jassi they just don't apply.
peace

Reiser4 on / . I have only been running for a few minutes, but this love seemes to be much snappier than the last couple. Once again awsome job on the love _________________The terrible thing about hell is that when you're there you can't even tell as you move through this life you love so you could be there and not even know

I got this too, with 2.6.7-rc3-mm1. Turning ACPI on resolves it for me. Tho we should not need to do this. And not all systems work well with ACPI in the kernel. Maybe getting rid of bk-acpi.patch is another solution, but I'm not sure how to do that and am too lazy to learn right now

It does feel snappier. I guess it is the mm scheduler maybe instead of nicks??? I recently switched from cfq to anticipitory so that might be the reason. Don't know if both are the reason, but anyway good work!!!!

Ok here it goes for me... This are my issues:
1) Have a wacom volito and an Logitech optical mouse + keyboard hub with a 2.6.4 kernel everything works as it should be, with the 2.6.7-rc3-love1 it gets fucked up...i get /dev/input/mice and /dev/input/mouse0 and /dev/input/mouse1 but only my volito works ok...
2) Bootsplash is gone...there is only the menu tittle there...nada...
3) Booting with qingy just leaves the system hung...
Any ideas?
P.S Bootsplash is 0.6-r8 for some funny reason 0.6.1 wont work...i tested it with 2.6.4 and my mouse went crazy (maybe thats also the problem with issue 1 didn't test it on 2.6.7 after the downgrade)_________________Gentoo the rising hope

working here. the new r4 seems to work, bootsplash is working, nvidia is ok...

The only thing that isn't working, and this is an odd one, is Qingy. Instead of launching the app, I get an empty framebuffer console with a blinking cursor. It won't let me change to VT6 either, which hosts an old fashioned agetty.

On the other hand if I boot without the framebuffer, while qingy still won't work, I can at least switch consoles and log in normally.

Apart from that, everything works nicely_________________Don't let THEM immanentize the Eschaton!