If genkernel produces an initrd of greater than 4096 (default ramdisk size), booting will fail with end-of-device read errors. Genkernel apparently does not increase ramdisk size or provide a warning. This is less a problem for HD installs that do not require an initrd, but it's a show-stopper for a livecd. Reproducible: Always Steps to Reproduce: 1. Use a configuration that results in an initrd > 4mb 2. Boot using the initrd, preferrably by making and using a livecd. Actual Results: Several errors about reading beyond the end of the device, and then a kernel panic due to init termination. Expected Results: If the initrd will not fit within the default ramdisk size, genkernel should probably increase default ramdisk size in the kernel config or automatically pass a kernel parameter in the loader to increase ramdisk size on boot.
What genkernel version? %> grep 4096 /usr/share/genkernel/genkernel [ "${INITRD_SIZE}" -ge 4096 ] && print_info 1 " ramdisk=8192"
This is with 3.0.2g The line to increase ramdisk size does not appear to be functioning, as the resultant kernel still has a 4096k default ramdisk size.
I just double-checked with genkernel and the kernel boot parameters, and I think that may be the problem right there. "ramdisk=8192" should read "ramdisk_size=8192". The former being, I believe, an invalid parameter.
Hrm, what kernel version?
2.4.27-hardened-r2
Ok, fix in genkernel-3.0.2c, should reach rsync shortly. Please reopen this bug if you have any problems. Thanks!