http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c13
Axel Braun
OK, let me clarify situation here:
1. it is not trivial to guess which boot code and where system has it placed ( e.g. in x86 it can be MBR or PBR on any disk ), so yast use value from /etc/sysconfig/bootloader to know what bootloader and where it is installed.
2. For arm we support only EFI booting.
3. In your case it looks like bug in image. It probably use image from kiwi that is from x86_64 which use legacy boot and just modify what is needed. It install grub2 to EFI partition, so it is working, but when yast tries to modify it, it things it uses non-EFI variant which is not supported.
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As
written above, it seemed to be related to the upgrade process
--- Comment #14 from Axel Braun
OK, let me clarify situation here:
1. it is not trivial to guess which boot code and where system has it placed ( e.g. in x86 it can be MBR or PBR on any disk ), so yast use value from /etc/sysconfig/bootloader to know what bootloader and where it is installed.
2. For arm we support only EFI booting.
3. In your case it looks like bug in image. It probably use image from kiwi that is from x86_64 which use legacy boot and just modify what is needed. It install grub2 to EFI partition, so it is working, but when yast tries to modify it, it things it uses non-EFI variant which is not supported.
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As written above, it seemed to be related to the upgrade process -- You are receiving this mail because: You are on the CC list for the bug.