Map of boot procedure

[edack at kengel.com]

What I have discovered using Fedora and lm_sensors (YMMV) is that modules 
(user defined) must be listed with appropriate flags in modules.conf . IF 
you can get your sound card to work, after the system is running,   usinf 
insmod .... then it will work on boot if you include the commands in 
modules.conf .



> SELECT * FROM users WHERE clue > 0;
0 rows returned

---
Ed Ackerman                    |  It is impossible to make anything
#include <std.disclaimer>      |  foolproof, since fools are
edack at kengel.com               |  so ingenious.

On Sat, 17 Dec 2005, Doug Crompton wrote:

>
> dmesg gives a good deal of info but it does not describe how it boot but
> rather what it boots and the messages those modules return. I meant a
> description or block diagram of what directories and files are being
> looked at and procedures are run to get the information to boot.
>
> This comes up because of the failure of my system to load modules at boot
> that it should and my exasperation in trying to find out why and get it to
> work. If I understood the process a little better it might help.
>
> There is probably a good book on this I just have not come across it yet.
> When I started out with Slackware 10 years ago it was easier to
> understand. I least I thought it was. Maybe I am getting older!
>
> Doug
>
> _______________________________________________
> bclug.org mailing list
> bclug.org at lists.sitelink.com
> http://lists.sitelink.com/mailman/listinfo/bclug.org
> This message was sent to edack at kengel.com
>