Running on x86

malveo · November 9, 2020, 5:26pm

Hello,

We are running Mender on Yocto Dunfell, months ago we had integrated an old x86 (32bit) device with this following local.conf configuration:

INHERIT += "mender-full"
MENDER_STORAGE_TOTAL_SIZE_MB = "6144"
MENDER_BOOT_PART_SIZE_MB = "256"
MENDER_DATA_PART_SIZE_MB = "2048"
MENDER_STORAGE_DEVICE = "/dev/sda"
MENDER_FEATURES_ENABLE_append = "mender-image-bios mender-grub mender-bios"
MENDER_FEATURES_DISABLE_append = "mender-image-uefi"

and it works smoothly, but by building a new image today, we get this error:

INFO: Creating image(s)...
ERROR: unrecognized bootimg-efi loader:
WARNING: exit cod 1 from a shell command.

also with:

INHERIT += "mender-full-bios"

without MENDER_FEATURES_ENABLE_append and MENDER_FEATURES_DISABLE_append.

produce the same issue.

Please share how to set the correct features to boot on a 32bit Intel class system.

Thank you.

Best,
Mauro

mirzak · November 10, 2020, 10:28am

Hi @malveo.

The error is new to me, and not yet clear what the root cause is.

Which revision of the dunfell branch are you using for meta-mender? What would be interesting to know if it is this PR that introduced an regression?

Can you test reverting meta-mender to 71286ec47fe856179f9aa1bf7f6445c1db4e640c which would be before mentioned PR was merged.

Also could you test with the changes in this PR? Primarily the first commit that is interesting and that could be related to your problem…

malveo · November 10, 2020, 2:19pm

Hi @mirzak,

Thank you, tested reverting to 71286ec47fe856179f9aa1bf7f6445c1db4e640c, build successfully and boot.

Tested with master + PR 1175 same issue:

INFO: Creating image(s)...
ERROR: unrecognized bootimg-efi loader:
WARNING: exit code 1 from a shell command.

Best,
Mauro

drewmoseley · November 10, 2020, 7:33pm

Hi @malveo where are you seeing this issue? Is this a build failure? Can you provide a more thorough build log?

malveo · November 11, 2020, 9:00am

Hi @drewmoseley -

Yes, it is a build failure, here the full log:

gist.github.com

https://gist.github.com/malveo/99dc05076303aaa2ce46c9a5cc69d1d1

gistfile1.txt

ERROR: customer-image-1.0-r0 do_image_wic: Execution of '/home/5267d0dea6/yocto/build/it/develop/tmp/work/ia32machine-customer-linux/customer-image/1.0-r0/temp/run.do_image_wic.45410' failed with exit code 1:
INFO: Creating image(s)...

ERROR: unrecognized bootimg-efi loader:

WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in: /home/5267d0dea6/yocto/build/it/develop/tmp/work/ia32machine-customer-linux/customer-image/1.0-r0/temp/log.do_image_wic.45410
Log data follows:
| DEBUG: Executing python function prepare_excluded_directories

This file has been truncated. show original

Thank you,
Mauro

drewmoseley · November 11, 2020, 2:16pm

Can you provide the contents of /home/5267d0dea6/yocto/layers/custom/meta-customer/meta-customer-distro/recipes-extended/images/customer-image.bb:do_image_wic

And also the output of bitbake -e customer-image?

malveo · October 1, 2021, 4:08pm

Thank you @drewmoseley

Sorry for replaying you back after all these months. I’ve restarted working on x86 devices with Mender in the last few days.

This issue appear with this commit:

and was enforced with this one:

github.com/mendersoftware/meta-mender

Fix `EFI_PROVIDER` being set incorrectly when using certain layers.

committed 09:15AM - 09 Mar 21 UTC

kacf

+3 -4

Use stronger `EFI_PROVIDER` assignment if related classes are set. Since a defau…lt has already been set in some layers, and `?=` assignments work in a first-one-counts fashion, our values do not propogate if we use `?=`. The original motivation and discussion for this fix is here: https://hub.mender.io/t/simple-configuration-dunfell/2991/28 Changelog: Title Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech> (cherry picked from commit e71a2f98ea46b4a10e78604079c4f9092f687356)

that introduces default values for EFI_PROVIDER if some features of Mender are enabled or disables.

If ‘mender-grub’ is enabled, EFI_PROVIDER is set to ‘grub-efi’, but if mender-grub + mender-bios are set, EFI_PROVIDER is ‘null’.

Building an image using ‘mender-full-bios’ class, enable both feature “mender-grub + mender-bios” in meta-mender-core/classes/mender-setup-grub.inc

MENDER_FEATURES_ENABLE_append_x86 = " mender-image-bios mender-grub mender-bios"

the combo mender-grub + mender-bios, set EFI_PROVIDER to null, this consequently trigger an issue when wic is invoked because during the build process on do_image_wic is used the kickstart file genericx86.wks (from ./meta-yocto-bsp/wic/genericx86.wks.in), that inside, use a reference of EFI_PROVIDER as argument for the loader var.

part /boot --source bootimg-efi --sourceparams="loader=${EFI_PROVIDER}" --ondisk sda --label msdos --active --align 1024

And this triggers the error at build-time:

INFO: Creating image(s)...
ERROR: unrecognized bootimg-efi loader:
WARNING: exit code 1 from a shell command.

the delta betwheen bitbake -e on dunfell and on the commit:71286ec47fe856179f9aa1bf7f6445c1db4e640c, confirm the
analisys above, EFI_PROVIDER is ‘null’ .

dunfell · GitHub (dunfell)
71286ec47fe856179f9aa1bf7f6445c1db4e640c · GitHub (71286ec47fe856179f9aa1bf7f6445c1db4e640c)

Using mender-full-bios and removing mender-bios from MENDER_FEATURES_ENABLE fix the issue.

Please do some sanity check around mender-full-bios.class.

Best,
Mauro

malveo · October 5, 2021, 2:24pm

@drewmoseley just un update and errata corrige.

mender-bios is needed for a bootable artifact. It installs the grub bootloader on the resulting image, and with this commit.

github.com/mendersoftware/meta-mender

Fix `EFI_PROVIDER` being set incorrectly when using certain layers.

committed 09:15AM - 09 Mar 21 UTC

kacf

+3 -4

Use stronger `EFI_PROVIDER` assignment if related classes are set. Since a defau…lt has already been set in some layers, and `?=` assignments work in a first-one-counts fashion, our values do not propogate if we use `?=`. The original motivation and discussion for this fix is here: https://hub.mender.io/t/simple-configuration-dunfell/2991/28 Changelog: Title Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech> (cherry picked from commit e71a2f98ea46b4a10e78604079c4f9092f687356)

in conjunction with the default wks file from poky, the build always fail. The only workaround possible is to provide a custom wks file with hardcoded --sourceparams=“loader=grub-EFI”, because EFI_PROVIDER variable is null.

Best,
Mauro

drewmoseley · October 5, 2021, 4:00pm

Hi @malveo,

I’m not quite following what needs to change here. Can you provide a detailed setup of how to replicate the reported issue when building with mender-bios? Ideally if you can provide a pull request that fixes the issue that would be great since I don’t really work with the EFI code much at present.

Drew

kacf · October 6, 2021, 6:29am

I’m also not quite following. EFI and BIOS setups are mutually incompatible, both can’t be used at the same time. Using EFI_PROVIDER in a recipe is a mistake, since there isn’t one when mender-bios is enabled. Are you sure you don’t just need to add this:

IMAGE_FSTYPES_remove = "wic wic.bmap"

malveo · October 6, 2021, 2:04pm

Thank you @kacf and @drewmoseley for the hint.

Topic		Replies	Views
Boot device not found after integration mender into yocto General Discussions yocto , intel , thud	23	3653	September 6, 2019
Intel-uefiimg is not bootable General Discussions yocto , intel , dunfell	1	712	March 10, 2021
Creating flashable mender images for desktop with Yocto General Discussions	3	121	January 18, 2024
Mender and efi-secure-boot on intel-corei7-64 General Discussions yocto	10	1144	May 19, 2022
InitRamfs x86_64 producing mender files General Discussions sumo , thud	2	595	March 8, 2019

Running on x86

Related Topics