Hi, Thank you very much. it seems during boot with default ubuntu kernels, CONFIG_BLK_DEV_RAM changed to =m. Correcting it to =y and recompiling kernel fixed the problem. Thanks again. On Fri, Jun 23, 2017 at 8:06 AM, Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote: > 22.06.2017 23:30, Ali H.M. Hoseini пишет: >> Hi, >> >> I'm not sure am I supposed to ask this question here, But I did not >> find anywhere more suitable! >> >> I'm using a complete root fs compressed in gz as my initrd for last >> couple of years. >> until kernel 4.4.x when I chose to boot kernel with my initrd, I got >> these messages in boot process: >> >> ... >> [ 0.000000] Krrne oomman iie: BOOT_IMAGE=vvmlinuz-4.4117 >> initrd=/utvos44.0.6.gz console=tty console=ttyS09900 >> ... >> [ 38.920053] Trying to unpack rootfs image as initramfs... >> [ 39.103577] rootfs image is not initramfs (no cpio magic); looks >> like an initrd >> ... >> >> and system boots correctly. >> >> >> >> But when I switched to kernel 4.9.30, everything went wrong: >> >> .... >> [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.30 >> initrd=/utvos.4.1.0.gz root=/dev/ram0 console=tty console=ttyS0,9600 >> .... >> [ 29.156899] Unpacking initramfs... >> [ 29.330796] Initramfs unpacking failed: no cpio magic >> ... > > You need CONFIG_BLK_DEV_RAM enabled. Looks like it is not define in this > case. -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
