boot errors with new debian kernel
Greetings:
I'm trying to upgrade my debian woody kernel. I was trying to do it the
simple way, using a prebuilt kernel image. My original install Woody kernel
didn't work, either so I built my own to get it going. Now, I'd like to get
in-sysc if possible and use the "standard" kernel. Or at least figure out
why it won't work for my Redhat to Debian education's sake.
Via dselect, I installed the kernel-image-2.4.18-1-686 but I can't get it to
work correctly. It appears to be related to module problems (a guess). I'd
paste the results of the boot messages, but I can't find them logged
anywhere. I looked in "dmesg", /var/log/syslog, etc. Nowhere do I see the
message about Can't locate module in any /var/log/* file. (As an aside, I'd
like to know where to look for that if possible.) The jist of the error
messages is shown in quotes below. They are interspersed with the rest of
the boot messages. The problems see to start right after the mtab "note".
"Note: can't open /etc/mtab"
(but it's there and exists as far as I can see)
"Note: /etc/modules.conf is newer than
/lib/modules/2.4.18-1-686/modules.dep"
(so I booted with this kernel, then I ran depmod -a, got no errors, then
rebooted, did not fix)
"modprobe: Can't locate module *"
"insmod: Note: /etc/modules.conf is newer than
/lib/modules/2.4.18-1-686/modules.dep"
I get the "newer than" messages a dozen or so more times. System boots, but
at least the network card is not up. It is listed as a module I believe in
the modules net dir. Boot with "my" kernel, all works OK. Boot with the
pre-built, all kinds of err messages.
Any help much appreciated!
Thanks,
Scott
P.S. As a side question, how do I tell if I have the matching kernel source
that is correlated to say the 2.4.18-1-686 image? Is kernel-source-2.4.18
always "in-sync" witht the latest similar (2.4.18) kernel?
Reply to: