bb
07-27-2003, 07:01 PM
I have recently installed Knoppix on my machine using the hdinstall script - it worked great, thanks to all.
I decided to install a new 2.4.21 kernel to replace the 2.4.20-xfs kernel installed by default; no particular reason, except to optimize it for my processor, and also to test out the linux progress patch (from the Debian kernel-patch-lpp package - hides boot messages behind a nice graphic).
The only other changes I made to the kernel were to compile ext3 support into the kernel. I noticed that it didn't seem to be compiled into the default Knoppix kernel, though I was able to boot from that kernel without trouble. I assume that Knoppix uses some different means to boot from an ext3 filesystem, even though the ext3 driver was compiled as a module? (I didn't think you could do this)
In any case, I now get a couple of error messages when booting to my new kernel, as the system is still trying to load the old jbd.o and ext3.o modules, though these are now compiled in. The messages are:
/modules/jbd.o: kernel-module version mismatch
/modules/jbd.o was compiled for kernel version 2.4.20-xfs
while this kernel is version 2.4.21.
/modules/ext3.o: kernel-module version mismatch
/modules/ext3.o was compiled for kernel version 2.4.20-xfs
while this kernel is version 2.4.21.
What is telling the system to try and load these modules? It doesn't seem to cause any problems (but, from an aesthetic point of view it does disrupt the lpp screen).
Thanks,
B
I decided to install a new 2.4.21 kernel to replace the 2.4.20-xfs kernel installed by default; no particular reason, except to optimize it for my processor, and also to test out the linux progress patch (from the Debian kernel-patch-lpp package - hides boot messages behind a nice graphic).
The only other changes I made to the kernel were to compile ext3 support into the kernel. I noticed that it didn't seem to be compiled into the default Knoppix kernel, though I was able to boot from that kernel without trouble. I assume that Knoppix uses some different means to boot from an ext3 filesystem, even though the ext3 driver was compiled as a module? (I didn't think you could do this)
In any case, I now get a couple of error messages when booting to my new kernel, as the system is still trying to load the old jbd.o and ext3.o modules, though these are now compiled in. The messages are:
/modules/jbd.o: kernel-module version mismatch
/modules/jbd.o was compiled for kernel version 2.4.20-xfs
while this kernel is version 2.4.21.
/modules/ext3.o: kernel-module version mismatch
/modules/ext3.o was compiled for kernel version 2.4.20-xfs
while this kernel is version 2.4.21.
What is telling the system to try and load these modules? It doesn't seem to cause any problems (but, from an aesthetic point of view it does disrupt the lpp screen).
Thanks,
B