Created attachment 820 [details] kernel_panic After a layer for a new machine is created using the yocto-bsp tool, the image generated is not starting due to kernel panic. Apparantly there is no filesystem found A screenshot of the qemu screen is attached.
Laurentiu Serban to add build and machine details.
Adding further info: for json file: Build Configuration: BB_VERSION = "1.15.3" TARGET_ARCH = "i586" TARGET_OS = "linux" MACHINE = "qemujson" DISTRO = "poky" DISTRO_VERSION = "1.2+snapshot-20120919" TUNE_FEATURES = "m32 core2" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp meta-json = "1.3_M4:e5c3513ca8abb21eb5e9b8c19d1b9199b14ae07c for yocto-bsp based image: Build Configuration: BB_VERSION = "1.15.3" TARGET_ARCH = "i586" TARGET_OS = "linux" MACHINE = "qemujson" DISTRO = "poky" DISTRO_VERSION = "1.2+snapshot-20120919" TUNE_FEATURES = "m32 core2" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp meta-json = "1.3_M4:e5c3513ca8abb21eb5e9b8c19d1b9199b14ae07c"
Please provide json used.
{"kernel_choice":"linux-yocto_3.4","use_default_kernel":"n","keyboard":"y","qemuarch":"i386","smp":"y","touchscreen":"n","need_new_kbranch":"y","new_kbranch":"standard/base"}
Created attachment 824 [details] meta-json
I mentioned that I suspected this was just the fact that you need to select the deprecated ATA drivers for qemu in order use /dev/hda.
Hmm, ok, but it should pick up the same kernel branch/config that the official qemu 'BSP' picks up, unless something here changed recently.
The default branch for qemu is: standard/common-pc/base Do you think the same should be used for the others?
Oh, yeah, I see now - in the json you're using standard/base - qemux86 needs standard/common-pc/base as you mention. For boot testing, you should use the defaults, which for qemu have been set up to give you something buildable and bootable for testing. Other selections may or many not give you something completely unbootable, which I think is mentioned in the docs. yocto-bsp doesn't give any guarantees about run-time for any of the BSPs, just a buildable starting point. However some of them such as qemu have been set with defaults that should work if chosen, qemu in particular since a qemu BSP would only be useful as a demo in the first place.
Ok, Tom, thank you for the answer. I will modify and retest
As mentioned above, the default inputs weren't used, so this is not unexpected.
Hello Tom, I am using the default options and still have the same issues for i386.
Is this qemu or i386, what hardware are you using, what's the error message? again, other than the qemu images, the result isn't guaranteed to boot on random hardware.
The option is i386. This is how I "inherited" the test case. But in this case, I will remove the test case and ask Song for a feature to cover other things than defaults. Is that ok with you?
I just created an 1386 BSP using all the defaults and booted a core-image-minimal ok on the crownbay. So I don't really know what you're looking for here or what you're expecting. If you're looking for enhancements to the default templates, there is this bug, not sure it's what you want: https://bugzilla.yoctoproject.org/show_bug.cgi?id=2392