Red Hat Bugzilla – Bug 169712
mkinitrd breaks processing of kernel boot arguments
Last modified: 2007-11-30 17:11:14 EST
Description of problem:
With initrd created with mkinitrd 5.0.2-1 or 5.0.3-1 arguments like
bootlevel are ignored and a machine boots always to what is specified
in /etc/inittab. This is not the case for an older kernel which I have
here and which is still using initrd done with 5.0.0-1; but if I replace
initrd for this kernel with a new one redone with 5.0.3-1 then an argument
specifying a desired boot level is immediately ignored.
Version-Release number of selected component (if applicable):
mkinitrd-5.0.2-1 and mkinitrd-5.0.3-1
I can't even build a initrd image with older versions of 2.6.13 kernels. I am getting
"cannot find module modprobe (aborting)"
message and nothing is produced. Version 5.0.0 works perfectly but 5.0.2 and .3 does not.
If this is due to kernel incompatibility then there should be a Requisite of some sort.
mkinitrd-5.0.4-1 should have command line parsing working again.