Re: Initrd - cramfs image is not being recognized by 2.4.20 kernel

[Keith Goettert]

My support of cramfs was complied into the kernel, but it still would not work.  A very telling sign that it was compiled in was its complaint that it couldn't find a valid filesystem in the boot messages (which according to my readings is also a disputed and unresolved bug/feature.)  Now I have redone the initrd image as an uncompressed ext2 fs.  I am still not home free (many many errors that need to be checked) but it does appear to be mounting it.  STAY TUNED this is going to be a HOWTO when I'm done.  I can't believe the number of hours this has taken! Thomas Krennwallner wrote: Hi! On Wed Dec 17, 2003 at 07:07:14PM -0800, Keith Goettert wrote: I have a kernel built from kernel.org source. I have included support for ramdisk, initial ramdisk, and cramfs. I built a ram disk image using mkinitrd The vanilla linux kernels don't support cramfs. See mkinitrd(8): By default mkinitrd will generate a CRAMFS image. This is not cur- rently supported by Linux. However, the Debian prepackaged kernels have been patched to support it. You can also generate an initrd image of another type by changing the MKIMAGE setting in mkinitrd.conf. So long Thomas