You are using the vesafb in 16 bit mode right?
For the moment 16bit is the only supported color depth.

Damn. I knew it had to be something obvious. That's all it was - I had been using vga=0x31B instead of vga=0x31A. Once I changed that, it started working right away. Thanks _________________Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. TsiolkovskyGentoo Radeon FAQ

You should now be able to run bin/vmware-config.pl as before.
Thanks to Petr Vandrovec on news.vmware.com for this patch.

PS: Petr will not be able to put this into any of the vmware.any.any.XX patches unless the reiser4 patch is included in Linus's kernels.

EDIT: Oh, I'm guessing this will break vmware for any kernels that don't have this new reiser4 included - so take care!_________________Asus A8V
AMD64 3500+
1GB XMS3200C2 Pro
120GB Barracuda SATA
Geforce 3

That is certainly the case; only apply the change if using reiser4. It will likely be some time before reiser4 makes it into a kernel proper._________________Website - All sorts of nonsense (some of it actually Linux related)

test9-mm4 is out. I -should- try to restrain myself from working on it until tomorrow night, but maybe I'll get tired of studying and release something._________________Website - All sorts of nonsense (some of it actually Linux related)

Sound's Great!
I'll have to find something really entertaining( or get to work ) to
not look at this thread till tomorrow
How was your exams? I hope you weren't getting distracted.
Can't wait and Thanks again,
Baldy

Hello,
Thanks for everything in advance! I am having some trouble though. I downloaded everything and "digested" the ebuild, but when I emerge it, during the patch process, it stops and constantly asks which file to patch because it cannot find it. Again, thanks for everything!

It's used like this:
lovebuild.sh 9 4 (the two numbers being the test kernel number and the love release number, respectively).

It DOES NOT work right now, because of the patching problem, but hopefully bssteph will fix that soon.

It contains some stuff specific to my machine:
The xdialog 'error' message is used because make-install doesn't detect grub on my machine and stops, asking me to make a bootdisk.
The message notifies me to press 'n'.

Nvidia-kernel, of course, only for nvidia users.

It requires Xdialog (emerge xdialog) and /proc/config.gz to be present, but it's not strictly necessary.

Change '/usr/local/portage' to your overlay directory.

Also, /boot is a separate partition for me, and if yours isn't, then remove the 'mount /boot' line.

The kernel eclass was changed and I forgot about it. Reload the URL, there is a new ebuild.
All the older ebuilds are going to be broken and I'm too lazy to fix them... if you need an old ebuild just rename the current one._________________Website - All sorts of nonsense (some of it actually Linux related)

Workin' great so far. Ran into the same problems with patching as the other posters, but the new ebuild cleared all that up. I'll post if I run into any snags, but so far I haven't had that opportunity.

Oh yeah, I was wondering, are love-sources gonna still be maintained after 2.6.0 actually gets released? Or is this just to hold y'all over until 2.7 starts appearing?

I get a kernel panic at boot (tried to kill init...) with love4. Using the other latest releases I've experienced what I think is poor IO scheduling, making things choppy when some, or little hd activity is present. This was using the cfq scheduler. Any chance this has any relation to the poor hdparm performance?
note: I didn't try love3.
Strangely test5-love3 has provided me with the best performance yet.

It's my understanding that devfs will not be a part of the 2.7 kernels. I assume that this would mean that Gentoo users will need a special patch to run ANY post 2.6 kernel. That is, unless udev, is ready by then, which I doubt. If thats is the case then I think we'll end up with more than just Love-Sources to choose from (though love-sources rocks).

It's my understanding that devfs will not be a part of the 2.7 kernels. I assume that this would mean that Gentoo users will need a special patch to run ANY post 2.6 kernel. That is, unless udev, is ready by then, which I doubt. If thats is the case then I think we'll end up with more than just Love-Sources to choose from (though love-sources rocks).

udev will be ready, hell I used ithe 005 release and it ran just fine - I have great hopes for udev as a devfs replacement,

udev has enough support on LKML as a much better implementation than devfs that it will be ready before 2.7 becomes a real consideration. That leads to the next question. I'm more interested in keeping up with 2.6 for a while than jumping straight to 2.7... I've stuck with 2.[5|6] for a while now, and I'd like to reap the benefits of it before going to 2.7, which I assume will be unfit for serious use right out of the gate.

ledskof:
There are some conflicts in patching love with reiser4, mainly that you'll have to change a couple function calls in fs/reiser4/plugin/cryptcompress.c and fs/reiser4/plugin/file/file.c:

only slight problem is when using my camera to upload pictures using mass storage usb device , I can only do it once! , if i disconnect power to camera I cannot use it anymore until reboot, get this on dmesg
(dont know if this have been long running through other test kernels, just tried my camera out today)

Thats great about udev, I thought that it was not ready for primetime yet. Regarding tatesworld's problem. I cannot get USB mass storage to work 100% correct, but it sounds like your problem can be solved by typing