Bug 1057142

Summary: Bootloader module shows error message on RPi1 (armv6l)
Product: [openSUSE] openSUSE Tumbleweed Reporter: Freek de Kruijf <freek>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED WONTFIX QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log.tar.xz

Description Freek de Kruijf 2017-09-05 06:52:03 UTC
Created attachment 739399 [details]
y2log.tar.xz

Using the JeOS image 2017.05.23-Build1.1 for the RPi1 (armv6l).
When running yast in ncurses to change the bootloader without any update I get the error message:
Error
Execution of command "[["/usr/bin/grub2-editenv", "list"]]" failed.
Exit code: 1
Error output: /usr/bin/grub2-editenv: error: cannot find a GRUB drive for /dev/mmcblk0p2.  Check your device.map.

Comparing the content of device.map with the content on my RPi3 it looks OK.

I am able to continue and I get the default "GRUB for EFI", (this is odd, the RPi1 is not an EFI device) which I change for GRUB2
After that I get the message:
Error
Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.
Details: unsuported architecture arm
Caller:  /usr/share/YaST2/lib/bootloader/stage1_proposal.rb:266:in `block in <class:Stage1Proposal>'

Obviously the architecture is armv6l.
Comment 1 Ladislav Slezák 2017-09-05 08:39:29 UTC
Unfortunately RPi1 is not supported by YaST. YaST supports only aarch64 EFI based boards. 

On RPi1 you have configure booting manually. You can find some booting hints at https://en.opensuse.org/HCL:Raspberry_Pi#Installing_the_openSUSE_Tumbleweed_image
Comment 2 Freek de Kruijf 2017-09-05 15:58:11 UTC
(In reply to Ladislav Slezák from comment #1)
> Unfortunately RPi1 is not supported by YaST. YaST supports only aarch64 EFI
> based boards. 
> 
> On RPi1 you have configure booting manually. You can find some booting hints
> at
> https://en.opensuse.org/HCL:
> Raspberry_Pi#Installing_the_openSUSE_Tumbleweed_image

This is quite unclear. The section about known issues does not specify how to set these parameters and mkimage is an unknown command and zypper se mkimage does not show a package to install.
Comment 3 Freek de Kruijf 2017-09-05 20:35:09 UTC
(In reply to Freek de Kruijf from comment #2)
> This is quite unclear. The section about known issues does not specify how
> to set these parameters and mkimage is an unknown command and zypper se
> mkimage does not show a package to install.

I found the package u-boot-tools which contains this application.
Executing the mentioned mkimage comand line on the original boot.script produced a new boot.scr which was different from the original one.
Rebooting the system with this new generated boot.scr did not succeed.