Hi Adhyas, On Tue, 2010-06-15 at 00:31 +0200, Avasthi Adhyas (Nokia-NRC/PaloAlto) wrote: > This morning I synced my kernel sources tree and compiled a fresh 2.6.34 > kernel without changing the configurations. The resulting bzImage panics with > 100% frequency. It says Cannot open root device "sda2" or unknown-block(0,0). > Please append a correct root= boot option;
If you are pulling from latest meego-os-base/kernel-source then the resulting kernel is 2.6.35-rc series. You can verify this with the presence of patches/patch-2.6.35-rc3.bz2 file. I know that the sequence_patch.sh creates "tmp/linux-2.6.34-master" directory but that name is wrong! > My extlinux.conf file reads sda2 as root file system for the default > installed image as well as the newly compiled kernel image. The default > installed image with 2.6.33-11 kernel boots fine on sda2. > The steps I follow to compile are these: > > * git pull <kernel sources from meego> > * ./scripts/sequence-patch.sh > * make -f Makefile.conf > * cd tmp/linux-2.6.34-master > * cp ../../kernel-netbook.config .config > * make ARCH=x86 oldconfig (Enter all the way) > * make ARCH=x86; make modules_install > * cp arch/x86/boot/bzImage /boot/extlinux/vmlinuz-2.6.34-netbook > * cp arch/x86/boot/bzImage /boot/vmlinuz-2.6.34-netbook > * edit /boot/extlinux/extlinux.conf to have another entry for this vmlinuz > (boot command copied which says root=/dev/sda2) > * reboot and try to boot to the new image, which panics with 100% frequency > > Is there something I may be doing wrong? I have file Bug 2942 for this. If default kernel-netbook.config fails to boot then that means there is some problem with the kernel configuration and filing a bug is the correct thing :) I got following information from "series" file. Netbook hardware patches Section maintainer: Yong Wang <[email protected]> I have also CC'ed this email to Yong Wang. Cheers, Ameya. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
