Re: [opensuse-arm] New kiwi and firmware=custom problem
Le 04/04/2018 à 10:48, Marcus Schäfer a écrit :
Hi,
It seems that new kiwi does not support u-boot (non EFI/Grub2) images? Is there a solution/workaround? I have not ported plain u-boot support to the next generation kiwi, because of the effort to move all boards to efi boot. u-boot basically works as the EFI firmware being capable to load the grub efi module(s).
Yes, but not all boards are supporting EFI with U-Boot. Especially Arndale because "Samsung's bl1 lies at sector 1, overlapping with the EFI GPT, so we can not use EFI". Maybe for other boards, we may use the EFI config in kiwi, but still boot using u-boot script? (I will give it a try)
One of the changelog entries I have here is this:
Date: Fri Mar 18 10:23:07 2016 +0100
Delete obsolete support for uboot
arm boot is using grub2 efi images loaded by a firmware. The firmware could be uboot but due to the non generic way to setup the board that it loads the firmware all of these tasks are handled by custom scripts called via the kiwi editbootconfig / editbootinstall script hooks. Therefore kiwi itself does not have to setup or install uboot
iirc this was one result of a conversation with Alex some time ago, not sure though. In our integration test example for the panda board I can see those kind of scripts:
https://github.com/SUSE/kiwi/tree/master/build-tests/arm/test-image-panda-oe...
If this is going to become a problem we should start a discussion what parts are missing in the builder
Alex, you may give us more information, maybe? Guillaume
Thanks
Regards, Marcus
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 04.04.18 11:08, Guillaume Gardet wrote:
Le 04/04/2018 à 10:48, Marcus Schäfer a écrit :
Hi,
It seems that new kiwi does not support u-boot (non EFI/Grub2) images? Is there a solution/workaround? I have not ported plain u-boot support to the next generation kiwi, because of the effort to move all boards to efi boot. u-boot basically works as the EFI firmware being capable to load the grub efi module(s).
Yes, but not all boards are supporting EFI with U-Boot. Especially Arndale because "Samsung's bl1 lies at sector 1, overlapping with the EFI GPT, so we can not use EFI".
This is not true. For those boards, we can still use EFI, but need to convert to MBR. This is done in uboot-image-install.in in section "Convert GPT to MBR if necessary". The only case I'm aware of where EFI is not a viable option is when we rely on U-Boot that is delivered with the system, but doesn't have efi_loader enablement. Apart from moonshot and midway I'm not aware of any such system still alive.
Maybe for other boards, we may use the EFI config in kiwi, but still boot using u-boot script? (I will give it a try)
That should also work, yes. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 04.04.2018 um 11:14 schrieb Alexander Graf:
On 04.04.18 11:08, Guillaume Gardet wrote:
Le 04/04/2018 à 10:48, Marcus Schäfer a écrit :
It seems that new kiwi does not support u-boot (non EFI/Grub2) images? Is there a solution/workaround? I have not ported plain u-boot support to the next generation kiwi, because of the effort to move all boards to efi boot. u-boot basically works as the EFI firmware being capable to load the grub efi module(s).
Yes, but not all boards are supporting EFI with U-Boot. Especially Arndale because "Samsung's bl1 lies at sector 1, overlapping with the EFI GPT, so we can not use EFI".
This is not true. For those boards, we can still use EFI, but need to convert to MBR. This is done in uboot-image-install.in in section "Convert GPT to MBR if necessary".
The only case I'm aware of where EFI is not a viable option is when we rely on U-Boot that is delivered with the system, but doesn't have efi_loader enablement. Apart from moonshot and midway I'm not aware of any such system still alive.
Is 32-bit Allwinner working with UEFI by now? Last time I tried it still fell apart and thus needed boot.scr. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 04.04.2018 um 14:38 schrieb Andreas Färber <afaerber@suse.de>:
Am 04.04.2018 um 11:14 schrieb Alexander Graf:
On 04.04.18 11:08, Guillaume Gardet wrote: Le 04/04/2018 à 10:48, Marcus Schäfer a écrit :
It seems that new kiwi does not support u-boot (non EFI/Grub2) images? Is there a solution/workaround? I have not ported plain u-boot support to the next generation kiwi, because of the effort to move all boards to efi boot. u-boot basically works as the EFI firmware being capable to load the grub efi module(s).
Yes, but not all boards are supporting EFI with U-Boot. Especially Arndale because "Samsung's bl1 lies at sector 1, overlapping with the EFI GPT, so we can not use EFI".
This is not true. For those boards, we can still use EFI, but need to convert to MBR. This is done in uboot-image-install.in in section "Convert GPT to MBR if necessary".
The only case I'm aware of where EFI is not a viable option is when we rely on U-Boot that is delivered with the system, but doesn't have efi_loader enablement. Apart from moonshot and midway I'm not aware of any such system still alive.
Is 32-bit Allwinner working with UEFI by now? Last time I tried it still fell apart and thus needed boot.scr.
Why does it fall apart? I‘m not aware of anything specific to Allwinner devices that would make it fail. Alex
Regards, Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 04.04.2018 um 14:53 schrieb Alexander Graf:
Am 04.04.2018 um 14:38 schrieb Andreas Färber <afaerber@suse.de>:
Am 04.04.2018 um 11:14 schrieb Alexander Graf:
On 04.04.18 11:08, Guillaume Gardet wrote: Le 04/04/2018 à 10:48, Marcus Schäfer a écrit :
It seems that new kiwi does not support u-boot (non EFI/Grub2) images? Is there a solution/workaround? I have not ported plain u-boot support to the next generation kiwi, because of the effort to move all boards to efi boot. u-boot basically works as the EFI firmware being capable to load the grub efi module(s).
Yes, but not all boards are supporting EFI with U-Boot. Especially Arndale because "Samsung's bl1 lies at sector 1, overlapping with the EFI GPT, so we can not use EFI".
This is not true. For those boards, we can still use EFI, but need to convert to MBR. This is done in uboot-image-install.in in section "Convert GPT to MBR if necessary".
The only case I'm aware of where EFI is not a viable option is when we rely on U-Boot that is delivered with the system, but doesn't have efi_loader enablement. Apart from moonshot and midway I'm not aware of any such system still alive.
Is 32-bit Allwinner working with UEFI by now? Last time I tried it still fell apart and thus needed boot.scr.
Why does it fall apart? I‘m not aware of anything specific to Allwinner devices that would make it fail.
I didn't figure out and I haven't heard from anyone since. Probably missing memory reservations? IIRC my Cubietruck got into GRUB but had problems loading the kernel, hanging. Jetson TX1 was another case where UEFI was not working. It aborts and resets when loading GRUB. Dragonboard 410c was another such case I reported in the past. Theoretically they're all fixable, but right now there are a couple platforms where UEFI in U-Boot is not working. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Alexander Graf -
Andreas Färber -
Guillaume Gardet