https://bugzilla.novell.com/show_bug.cgi?id=434910
User aj@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=434910#c9
--- Comment #9 from Andreas Jaeger 2008-10-14 00:36:29 MDT ---
I'm pasting the comment completely, it does not really help - it shows that we
have here a different situation IMO. Bug #423068 had a corrupt initrd but I
don't think this is the case here
Full text of comment 8 of bug #423068:
The request_module message with binfmt-0000 clearly shows that initrd on the
boot media is corrupt somehow -- the bytes that identify the binary format of
the executable that is being loaded are all zeros.
I have therefore downloaded SLED-11-DVD-i386-Alpha3-mini.iso, extracted initrd
from it, and did
gunzip < initrd | cpio -i --make-directories
to inspect the contents of the initrd. It apparently seems to be corrupt, all
the important files seem to have zero length:
$ ll ./init
-rwxr-xr-x 1 jikos users 0 2008-09-09 11:28 ./init
$ ll ./sbin/modprobe
-rwxr-xr-x 1 jikos users 0 2008-09-09 11:28 ./sbin/modprobe
Therefore I would say this is not a kernel problem, but rather a corrupted
initrd image being generated for the installation kernel image on i386.
We have verified that installing the kernel-default RPM on a already running
system with older userspace produces correct initrd image and kernel is booting
correctly, so this is probably really issue of a utterly corrupted initrd on
installation image.
Re-assigning to Steffen. Steffen, if you find my analysis to be incorrect or
you are not the person to handle this, please re-assign back to
kernel-maintainers.
Thanks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.