[meta-intel] (no subject)

[Tom Zanussi]

On Tue, 2014-09-16 at 11:35 +0000, Stuart Weaver wrote:
> 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?
> 
Hi,

This shouldn't be your problem - the recent microcode commits are to
blame.  I pulled them in on the condition that there would be an opt-out
mechanism available asap.  If this can happen on a per-machine basis, it
should actually be an opt-in only feature.

I've just filed a bug for this:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6730

If this isn't just a case of a simple bug, I'll revert the patchset.


Thanks,

Tom

> Best Regards,
> Stuart
> 
> 
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud
> service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________