I get boot messages flying by on the screen that don't show up in dmesg.

I imagine that this is part of the stage one bootup (li), but where can I find the output of this?

TIA...

"I get boot messages flying by on the screen that don't show up in dmesg."

Try looking in the log files in /var/log/*

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

If lilo is hosed you aren't running a linux kernel yet, so there is no way to capture it to a logfile.

Normally, though, all you get is a few very quick things on screen then:
li
li
li
li. . .

Lots of "Li" lines on the screen.

Thanks for the ideas, but I boot OK...I just see some messages fly by in the first part of boot that I can't find anywhere...and they aren't in the logfiles.

...something about not finding some modules.

Ok, here's the deal. When the kernel is loading, it parses the different configuration files on your machine--one of which is /etc/modules.conf.

If everything is working properly after boot up, and you can't find anything which appears to be broken, ignore the messages. They apply to modules which may be supported by the kernel, but unused in your system. You may have the service, filesystem, or related daemon to the modules mentioned in the warnings turned off in your configuration. In this case, the modules are supported by the kernel--but not mentioned in /etc/modules.conf. This will give you warnings--and even error messages because anything in Linux which fails is supposed to fail with error messages.

Again, as the result of the fact that the kernel isn't completely loaded, errors involving kernel modules at boot-up aren't logged unless you use a debugger. It isn't necessary unless you find something which doesn't work. Even if something is broken; if it is obvious, there isn't a need to run a debugger. You just look to see if the module is available, and if the correct links are in place. Then you run the respective tool for the configuration of whatever happens to be broken.

Avoid doing any direct editing of configuration files if a tool is available. Most machines which are reduced to a boat-anchor or paper weight have had manual "tweaking" of configuration files by someone "who knows what they are doing".

If anything IS broken, now you know where to start. You can then assume that either the incorrect module is being loaded--one that doesn't match the system map--for the hardware on the machine--or--the module which is needed for whatever you find that is broken isn't available in /lib/full-kernel-name modules directory. Of course, the usual suspect is a mis-configuration of sound devices. Sometimes if you are experimenting with using a frame-buffer device for console and it isn't exactly right you can get errors or an unusable machine. But you didn't mention that.