Skip to contentSkip to conversation

mkinitrd

DISCUSSION Dave Mehler 4 participants 4 messages Apr 18, 2003

lore
Share & tools
lore
#0 lore raw

Hello,
Same deal as before, on my rh9 box i have mkinitrd version 3.4.42-1 Is this sufficient for running a 2.5 kernel? I heard there was some
update to mkinitrd i might have to get, which might explain why the system is hanging after the initrd image, but have not been able to find it. Thanks.
Dave.

#1 lore raw
Quoted 7 lines · Dave Mehler

Hello,
Same deal as before, on my rh9 box i have mkinitrd version 3.4.42-1 Is this sufficient for running a 2.5 kernel? I heard there was some
update to mkinitrd i might have to get, which might explain why the system is hanging after the initrd image, but have not been able to find it. Thanks.
Dave.

Dave, I recall reading there are problems with building an ext2 initrd because of the small size, and it seems that ext3 is fine at the moment. Just try to tweak the initrd script to do a ext3 (add -j to the mke2fs).

Search for "Recent changes broke mkinitrd" on lkml for more details.

Greets, Antonio.

ps. I'm having problems running make menuconfig under gnome-terminal,
and so filled a bugreport on bugzilla.redhat.com

xterm works fine at least

#2 lore raw
Followup to:  <[email protected]>
By author:    Antonio Vargas <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 5 lines

Dave, I recall reading there are problems with building an ext2 initrd because of the small size, and it seems that ext3 is fine at the moment. Just try to tweak the initrd script to do a ext3 (add -j to the mke2fs).

Why ext2 as opposed to romfs or cramfs?

-hpa

Signature · 3 lines
<[email protected]> at work, <[email protected]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
#3 lore raw
In reply to Dave Mehler
Quoted 4 lines · Dave Mehler

Same deal as before, on my rh9 box i have mkinitrd version 3.4.42-1 Is this sufficient for running a 2.5 kernel? I heard there was some
update to mkinitrd i might have to get, which might explain why the system is hanging after the initrd image, but have not been able to find it.

It needs to be patched to find modules with the new suffix... the simplest way is to probably change the reference for $modName.o.gz to $modName.ko.

Bill