How to disable bootsplash, and other questions prompted by custom kernel

[jensend]

I just recompiled the kernel on my new VL5.9 install, and there were some appreciable benefits for this old PII/300 Thinkpad. (I wonder how much of it was because of compiling specifically for the PII and how much of it was just because of switching to a non-smp kernel- I wonder why vector doesn't come with a UP kernel available, especially given that it's targeted more at lower-end hardware than other distros.)

Among the things which the new kernel broke which I have questions about:

• ndiswrapper. All it took to fix it was to grab the sources for 1.48, compile, and install the module, but I hadn't realized it wasn't in the normal kernel sources. What other out-of-tree modules are included in VL by default?
• init display. In paring everything down one of the things I decided was inessential was framebuffer support, and so for the time being the screen goes blank from when the kernel loads to when xdm starts up. I can find loads of documentation regarding how to enable bootsplash related stuff but nothing about disabling bootsplash and getting init to display in the normal fashion. How do I do it?

[The Headacher]

I can find loads of documentation regarding how to enable bootsplash related stuff but nothing about disabling bootsplash and getting init to display in the normal fashion. How do I do it?

You should be able to re-install lilo and choose not to use bootsplash. "vliloconf" is probably the easiest way. However, since you didn't enable framebuffer support you probably still won't see anything until KDM comes up.

[jensend]

Since posting and before noticing that there'd been a reply I found that just doing vga=default in lilo.conf got the regular console back. There's all sorts of bootsplash stuff scattered through the init system, so though I've gone through and commented a fair bit of it out I imagine there'd be more to do before removing the bootsplash package could work.