Linux booting problems
Kenny Donahue
kennyd at mc.com
Fri Feb 28 14:37:27 EST 2003
Derek Martin wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Thu, Feb 27, 2003 at 04:05:26PM -0500, Kenny Donahue wrote:
>
>
>>My main questions was why was it trying to load modules when
>>I built it into the kernel? I looked at modules.conf. that's ok.
>>
>>
>
>If you are loading an initrd image with your new kernel, it may
>contain modules for ext3. If so, you will get error messages about
>trying to load them. I have seen this happen on my own system, though
>I do not recall the specific set of circumstances that caused it. It
>may be as simple as you had an existing kernel with the same exact
>version as your new kernel which had a module compiled for ext3, but
>you did not remove the old modules (/lib/modules/<kern ver>).
>
>Running make modules_install does NOT clean up old modules. You have
>to remove them by hand. If you build a new kernel with the same
>version as a pre-existing kernel, but do not change the EXTRA_VERSION
>in the Makefile, and you change some modules so that they are compiled
>into the kernel, it will simply copy your new modules over the old
>ones, without getting rid of stuff that is no longer modular. When
>the system does a depmod -a at boot time, it will generate error
>messages.
>
>
I thought that the module might be coming from the initrd but I removed
the line from
my lilo.conf. I also tried creating a new but I may have screwed that
up. I was manually
deleting the 2.4.7-10custom modules directory.
Thanks,
Kenny
>
>
More information about the gnhlug-discuss
mailing list