Originally posted by David the H.
Are you perhaps referring to getting a bunch of "fatal error" messages flashing by during boot up? That happens when your previous kernel used certain modules but your current one doesn't, either because you removed them or you compiled them directly into the kernel. The boot sequence is still trying to load the previous modules list, but of course it's not finding them, so it spits out error codes. You need to edit a file (I believe it's /etc/modules.conf, someone correct me if I'm wrong) to get rid of the invalid entries.
AHA!!!! OK! That makes a lot of sense.
Unfortunately, when I tried to boot up with this kernel compiled like that, it gave all of those failure messages, and then when it finished and X was supposed to load, it just locked up and gave me the black screen (Linux equivalent of the middle finger).
I was pretty careful when using xconfig and I left anything in that I didn't know what it was, so I was really surprised when that happened.
Of course, after the first compilation failed, which took hours rooting through directories in xconfig, I tried to just compile one with only two tweaks: 4GB and no riva framebuffer.
It did the same thing - just locked up.
What I don't understand is why the dorks who make the RPM's with the maintenance releases of Mandrake kernels insist on compiling them with framebuffer support built in. It's the only reason I was trying to compile my own - so I could install nvidia drivers against them.
Even in xconfig framebuffer is commented as being obsolete and "only enable if you want to play with it and it may hurt performance."
So why the heck are they doing that and how do I get them to stop it?
Another question: can I edit modules.conf on my current kernel to reduce the load and boot time and increase performance for the modules I don't need?