cramfs, kernel-panic...initrd, bootsplash...
 

When compiling a kernel for bootsplash support including monolithic cramfs (compressed rom file system), i get kernel panic ... need to append a correct root=boot option ...


When compiling a kernel with cramfs built in, and as an initrd kernel (make-kpkg kernel-image --initrd --append-to-version=XXxxXX), the kernel panics a few lines later.


When compiling without cramfs, bootsplash still works!
When compiling without cramfs, make-kpkg kernel-image --initrd still works!

I think /sbin/init is getting confused and thinking my root partition is a cramfs and gives me that unable to mount ... blah blah blah.



Would someone tell me if cramfs is really needed!?

:newbie: :confused: :cry:

you need cramfs - otherwise you system can't read initrd. at least that's what i thought....

does bootsplash work (with a background image) without cramfs?

if it does, forget cramfs.

From what I understand, you don't need an initrd if you use ATA/IDE disk controllers and compile your disk controller and your file system into the kernel instead of using a loadable module (and your kernel is < 1.4MB) If you don't need to use initrd, I guess you don't then need Cramfs?

I'm might try and create a kernel that doesn't need Initrd. To do this. I suspect I may wind up using vanilla kernel source instead of Debians patched version with CramFS.

you don't need an initrd if you have everything you need to access your hard drive compiled in the kernel. So, that's disk controllers, and file systems.

You need an initrd for bootsplash.

wellmt,
you can build a initrd-less kernel with debian's source. just disable cramfs (it's in the filesystem section) when using make menuconfig.