that bootsplash patch you linked to is corrupted/broken.
either that, or I'm an idiot who is improperly using bzip2 -d to extract the patch.

It turns out that firefox is an idiot. wget saved the day again. I think I'll go file a bug in their bugzilla.

Anyway, I'm going to see if I can integrate this into love sources to save you some work/get this working for me. I'll let you know if I do._________________There is no substitute for experience.
Imperfection indicates a lack of effort.

I took the liberty of incrementing the version to love2, and thought that
it would be a nice touch to change the name to "Fuzzy Bunnies of Ultra-Crazy Doom". Feel free to change it back if you don't like it.

And no, I did not secretly sneak supermount in.

EDIT:
Ebuild for it is at http://darc.ath.cx:81/linux/love-sources-2.6.3-r2.ebuild
Hopefully you can pick this up and put it on your site soon, steel300, as I have very limited bandwidth for uploading._________________There is no substitute for experience.
Imperfection indicates a lack of effort.

So? It's not like the kernel has any fp math going on, you won't notice a thing, good or bad. (Unless some weird gcc bug makes wrong binaries)_________________Think about your breathing.http://floam.sh.nu

holy shit, these patches are hot
just emerged, configed like i though it would be cool, and, IT WORKED!!!
2.6.x series is going straight to the top, and with love-sources, they will wipe out windows on every computer sooner or later

keep on the very, very good work steel, i'm on my next adventure aka bootsplash and framebuffer..._________________geek by nature, linux by choice
i want my avatar back... thank you
:wq

But now, after upgrading from 2.6.0-test11-love1, I lost all files in /dev/dvb.
I do not blame the kernel, I just don't know what I could have done wrong, since I just imported my old config with few manual changes.
My Card is a Hauppauge DVB-S and I would appreciate any help.

I got 2.6.3.love1 to boot after turning off the bootsplash stuff, however, XFree won't start. I've got an NVidia card, and I know that I have to reemerge the nvidia-kernel and that the kernel driver and the glx have to match versions, which they do, but XFree still complains about mismatched GLX and Kernel drivers. I've double checked that my /usr/src/linux link is correct. If I boot back to 2.6.2.love1 and chage the /usr/src/linux link back, it works fine.

I'm just gonna wait for 2.6.3 love sources based off of MM2 and see what happens. But if anyone wants to have a looksy, here's what's at the end of my XFree86.0.log...

I *DID* notice that when I boot to 2.6.2 again and XFree works, the XFree log doesn't mention loading 'vgahw'. But I have no clue why it'd be different. Might a kernel option be set wrong? I had a look at my config and all looks to be in order...but, who knows..._________________-Lunchy

Agent: enable Local APIC support on uniprocessors (under processor type and features).

Enabling this option even when you don't have a local APIC will not normally hurt. (I have heard reports of Bios conflicts, if it's enabled in the kernel you may need to disable in your bios. But this seems rare.)

Actually I am one of those who has this conflict. This is the reason why I always have it disabled. Will try to enable it and see if it compiles though. I can disable it in the bios since I flashed it with an unofficial one

Those warnings are fine. All they do is make the compile process a little noisier._________________Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it.

I *DID* notice that when I boot to 2.6.2 again and XFree works, the XFree log doesn't mention loading 'vgahw'. But I have no clue why it'd be different. Might a kernel option be set wrong? I had a look at my config and all looks to be in order...but, who knows...

Okay new problem: X will not start with the nvidia kernel module. For whatever reason, X says that it cannot load the nvidia module even if I modprobe it by hand. Any ideas? I tried the newest stable and unstable nvidia-kernel and I know it worked for me with vanilla 2.6.1 (or maybe it was 2.6.0, don't remember exactly).

[Edit] I noticed that I have both nvidia.ko *and* nvidia.o. Is this normal? And it is nvidia.o that is loaded when doing a modprobe, not .ko. I tried moving .o and then doing modprobe again but it would not load .ko. Strange!

Agent: do you have bootsplash enabled? The bootsplash patch from steel's build is buggy and has interaction problems. I'm using Darckness's build (with the updated bootsplash patch) and not seeing any problem.

[edit to follow your edit] kill nvidia.o only nvidia.ko should be installed. (least that's all i've got and it works properly). you may need to rmmod nvidia then modules-update before modprobe nvidia again.

Last edited by Dinini on Fri Feb 20, 2004 6:09 pm; edited 2 times in total

@mcoulman: those links are fine. I also got rid of the .o module by unmerging nvidia-kernel then deleting the modules and then reemerging nvidia-kernel. Now I only have nvidia.ko, but X still will not run

@mcoulman: those links are fine. I also got rid of the .o module by unmerging nvidia-kernel then deleting the modules and then reemerging nvidia-kernel. Now I only have nvidia.ko, but X still will not run