>I have a kernel building question:
>First must I have an initrd lilo entry to
>boot a scsi device (an adaptec controller).
The initrd must match the kernel *exactly*, i.e., you can't even use anQuote:>If yes, then
>Do I need to build a new initrd for 2.4 kernel.
>Can I use the 2.2 initrd with a 2.4 kernel.
initrd-2.2.14-... with a 2.2.16 kernel.
You *do* have the 2.4 modutils, do you?Quote:>I am upgrading a redhat 7.0 system to use 2.4 kernel.
>When I tried to build a new initrd, it complains it cannot
>find my AIC-7xxx modules. When I config my scsi devices
>as modules I can build a new initrd, but my system won't boot up.
>I get a system panic at boot up complaining
>about a bad root device.
Sure it was - but you really only have to build the driver of the boot-Quote:>When I build the drivers in, it seems to work -
>but I'm not sure why or if that was what made it
>work as I was trying lots of things.
device into the kernel - you could leave the rest as modules.
Should still be possible *if* you have left something as modules.Quote:>So, I am really confused,
>about scsi and initrd, because when
>the drivers are built in
>I cannot then build a new initrd.
One pragmatic solution is to build anything that is needed to boot intoQuote:>I need to do this upgrade to other systems,
>so I need to really understand this.
the kernel and leave the rest (which can be loaded later) as modules.
In that case, you don't need an initrd at all.
Yes. The order should always beQuote:>(Do you really need to first
>build the drivers modular to build
>initrd, then make the drivers
>built-in in order to boot up??
>seems strange, I must be doing something
build kernel, build & install modules, mkinitrd