Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Booting up Intel-core2-32 on 64-bit UEFI #11

Open
njavro opened this issue Aug 9, 2023 · 1 comment
Open

Booting up Intel-core2-32 on 64-bit UEFI #11

njavro opened this issue Aug 9, 2023 · 1 comment

Comments

@njavro
Copy link

njavro commented Aug 9, 2023

Hi,

So I have have followed the README tutorial and was able to successfully build Yocto image with respective Intel BSP.
Initially I built Intel-corei7-64 BSP, flashed it onto a USB stick and booted it up successfully on my machine. To note, my machine is using 64-bit UEFI firmware. However, when I did the same for Intel-core2-32 I am not able to boot at all even though the Yocto build was also successful.

In order to mitigate the issue of Intel-core2-32 having bootia32.efi I have copied bootx64.efi from Intel-corei7-64 image.
That gave me small progress as I was finally able to see boot menu, however after pressing "boot" all I get is the following message: "Failed to execute boot (\bzImage): Unsupported"

I was looking through various documentation and online references to no success. Since Intel-corei7-64 boots fine, and since machine is using 64-bit UEFI I assume the issue arises from trying to boot 32-bit Yocto on 64-bit UEFI.

In current situation I assume 32-bit Yocto bzImage is unsupported by bootx64.efi, however bootia32.efi doesn't even showcase the boot menu but just gets overlooked for second boot option.

I would kindly appreciate if any tips or advices for related issue could be provided.

Thank you!

@cbrake
Copy link

cbrake commented Aug 9, 2023

This repo is a mirror of the official repo: https://git.yoctoproject.org/meta-intel which we use for changes that are not upstreamed yet.

I don't have an answer to your question, but I'm curious -- why do you want to use a 32-bit image?

The world is moving to 64-bit, so this path will be less and less supported as time goes on.

https://tmpdir.org/016/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants