On Fri, 15 Dec 2000, Edward S. Marshall wrote:
> Hmm. "CONFIG_IDE=m"?
>
> So now basically everyone with ordinary PC hardware gets to use initrd?
>
> A word to the wise: if you don't currently need initrd to get your system
> online, don't blindly upgrade to 2.4.0-0.43.4; do:
>
> mkinitrd -v /boot/initrd-2.4.0-0.43.4.img 2.4.0-0.43.4
>
> And then add the following line to the appropriate image stanza of
> lilo.conf:
>
> initrd = /boot/initrd-2.4.0-0.43.4.img
Yeah, that got me too. I did notice the trend to modulize everything from
the changelogs, but creating initrd isn't usually enough:
---
# /sbin/mkinitrd -f -v /boot/initrd-2.4.0-0.43.4.img 2.4.0-0.43.4
Using modules:
Using loopback device /dev/loop1
/sbin/sash -> /tmp/initrd.PeIApz/bin/sash
/sbin/insmod.static -> /tmp/initrd.PeIApz/bin/insmod
---
Whoops. No drivers loaded on it at all (because they're in the kernel
and aren't detected)..
Even the good ol' fashioned way seems to fail; fails after modprobe for
block-major-3 fails:
---
# /sbin/mkinitrd -f -v --preload ide-mod --with ide-disk
/boot/initrd-2.4.0-0.43.4.img 2.4.0-0.43.4
Using modules: ./kernel/drivers/ide/ide-mod.o
./kernel/drivers/ide/ide-disk.o
Using loopback device /dev/loop1
/sbin/sash -> /tmp/initrd.39Vfti/bin/sash
/sbin/insmod.static -> /tmp/initrd.39Vfti/bin/insmod
/lib/modules/2.4.0-0.43.4/./kernel/drivers/ide/ide-mod.o ->
/tmp/initrd.39Vfti/lib/ide-mod.o
/lib/modules/2.4.0-0.43.4/./kernel/drivers/ide/ide-disk.o ->
/tmp/initrd.39Vfti/lib/ide-disk.o
Loading module ide-mod with options
Loading module ide-disk with options
---
Unless there are _very_ good reasons for modulizing IDE, I'd back out
ASAP. This _will_ create headaches for a _lot_ of people.
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
