Re: Kernel 2.6: bootup errors not logged?
- To: firstname.lastname@example.org
- Subject: Re: Kernel 2.6: bootup errors not logged?
- From: Kristian Niemi <email@example.com>
- Date: Sun, 01 Feb 2004 14:27:55 +0200
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <1jk5O-4xNemail@example.com>
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
After the first time I installed the new kernel, it seemed like the
changes I made in /etc/modules didn't matter at all. Nor did modconf
remove the old modules, i.e. the `fatals' bootup reported.
After the second time I installed the (new) kernel, changes I made in
/etc/modules *did* matter. So I probably was doing something wrong the
first time. Modconf still works in the same way though; or not,
depending on the way you look at it. It doesn't remove old modules.
Almost like it doesn't `seem them'? Or maybe it `nowadays' uses another
file than /etc/modules?
Whatever the reasons, editing /etc/modules removed some `fatals'. Some
are left, but whiz by too fast for me to read them, thus I can't remedy
Still seems strange they don't get logged at all ...
Thanks for your help though.
Now that you mention it like this, I remember quite a few modules
that changed, and might have given that exact message at boot time.
Check in /etc/modules for any old modules that
aren't working anymore, and change them in that file.
Otherwise, just run modconf. I think modconf works with
.ko modules nowadays.