[meta-intel] (no subject)

Stuart Weaver Stuart.Weaver at datapath.co.uk
Tue Sep 16 04:35:02 PDT 2014


Hi all,

I've just made a fresh Yocto/meta-intel repository and created an image based on core-image-sato for valleyisland-32. However when booting, the kernel was panicking as it could not load /initrd. Looking at the image created I found that initrd was not being included. After comparing with an older version of the repositories I had, I found that commenting out the following lines in meta-intel/conf/machine/include/meta-intel.inc solved the issue:

# include the user space intel microcode loading support in the generated images.
# MACHINE_ESSENTIAL_EXTRA_RDEPENDS_append = " intel-microcode iucode-tool"

# For the early boot time kernel microcode loading support,
# merge the microcode data in the final initrd image.
# INITRD_prepend = "${DEPLOY_DIR_IMAGE}/microcode.cpio "

I don't know anything bout intel microcode, and hence would it be possible to explain/point me to some place that has more information about the microcode and how to configure it to create the initrd correctly?

Best Regards,
Stuart

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-intel/attachments/20140916/31b08d9b/attachment.html>


More information about the meta-intel mailing list