If possible I would suggest using Debian version 7 as a host for building the image, as this release has been tested on this distro. I have tried to build the image on other distros such as fedora and have encountered problems similar to yours above.
This message was posted on behalf of Intel Corporation
If you build the Yocto image basing it on Quark's BSP 126.96.36.199 (https://downloadcenter.intel.com/download/23197/Intel-Quark-SoC-X1000-Board-Support-Package-BSP-) you don't need follow the steps in https://software.intel.com/en-us/get-started-galileo-linux-step1 as those steps are only required to boot on the eglibc image. You can simply copy the files into the SD card and it should be able to boot.
However, you will have to make sure to rename the image files correctly.
Please check this thread.
The guy also had the same problem, but after switching to Debian 7, the problem was gone.
Now, Debian 7 is updated to 7.11. I don't if this version will work.
I just tried Debian 7.11, but I still got the problem...
What could be the possible reason for this issue? I'm frustrated now.
Before starting building, I got this error, like the thread: Error during BSP Build - Latest Release v1.2
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:
TMPDIR is setgid, please don't build in a setgid directoryTMPDIR is setuid, please don't build in a setuid directory
Then I installed all suggested packages, still got the error. Then I created the file by touch conf/sanity.conf as suggested.
Could this error be the reason?
Could you please check the permissions attached to your whole build directory (i.e. meta-clanton_v1...) by typing: "ls -l" in the directory above meta-clanton_v1.
I've a feeling this is a permissions issue due to this: https://email@example.com/msg54490.html
1 of 1 people found this helpful
Finally, thanks to a developer, the problem is due to grub configuration file.
grub.conf is misconfigured so that it can not load the kernel.
root=/dev/**** is not correct, then change it to the right interface according the command "lsblk", then the problem is solved.
Thanks for all your help.