From your test, the same 2.6.28 jaunty kernel boots up without initramfs. After I compared the jaunty kernel config with the 2.6.26 debian kernel config. I think in jaunt kernel config we should built-in "Ram block device support" CONFIG_BLK_DEV_RAM=y. This is required by booting up with initramfs.
In 2.6.26 debain kernel config
---
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
---
In jaunty kernel config
---
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
---
Could you please set the jaunty kernel config to the same as debian kernel config? and rebuild the kernel and test again?
Hi Loic,
From your test, the same 2.6.28 jaunty kernel boots up without initramfs. After I compared the jaunty kernel config with the 2.6.26 debian kernel config. I think in jaunt kernel config we should built-in "Ram block device support" CONFIG_ BLK_DEV_ RAM=y. This is required by booting up with initramfs.
In 2.6.26 debain kernel config BLK_DEV_ RAM=y BLK_DEV_ RAM_COUNT= 16 BLK_DEV_ RAM_SIZE= 8192
---
CONFIG_
CONFIG_
CONFIG_
---
In jaunty kernel config BLK_DEV_ RAM=m BLK_DEV_ RAM_COUNT= 16 BLK_DEV_ RAM_SIZE= 4096
---
CONFIG_
CONFIG_
CONFIG_
---
Could you please set the jaunty kernel config to the same as debian kernel config? and rebuild the kernel and test again?
Thanks
-Bryan