Op dinsdag 5 september 2017 14:00:33 CEST schreef Andreas Färber: > Am 05.09.2017 um 12:11 schrieb Freek de Kruijf: > > Op dinsdag 5 september 2017 08:53:02 CEST schreef Freek de Kruijf: > >> Op maandag 4 september 2017 14:28:24 CEST schreef u: > >>> On 04.09.17 11:49, Freek de Kruijf wrote: > >>>> I used the latest JeOS image 2017.05.23-Build1.1 for the RPi1 (armv6l) > >>>> on > >>>> a SD card and booted the system, which went OK. > >>>> > >>>> After that I did a "zypper dup --no-recommends" on that system which, > >>>> at > >>>> the end, shows the following message: > >>>> > >>>> Output of grub2-arm-uboot-2.02-6.1.armv6hl.rpm %posttrans script: > >>>> update-bootloader: 2017-09-04 11:31:09 <3> update-bootloader-1244 > >>>> > >>>> run_command.274: '/usr/lib/bootloader/grub2-efi/install' failed with > >>>> exit > >>>> code> > >>>> > >>>> 1, output: > >>>> <<<<<<<<<<<<<<<< > >>>> target = arm-efi > >>>> ls: cannot access '/sys/firmware/efi/efivars': No such file or > >>>> directory > >>>> + /usr/sbin/grub2-install --target=arm-efi --no-nvram --removable > >>>> Installing for arm-efi platform. > >>> > >>> Can you try to run this command on its own? If it still fails, run it > >>> with strace -f and upload the output somewhere (or look at it and search > >>> for failures)? > >>> > >>> Thanks! > >>> > >>> Alex > >> > >> The RPi1 is not EFI system, so I wonder why the target should be arm-efi. > >> > >> # /usr/sbin/grub2-install --target=arm-efi --no-nvram --removable > >> Installing for arm-efi platform. > >> /usr/sbin/grub2-install: error: cannot find a GRUB drive for > >> /dev/mmcblk0p2. Check your device.map. > >> > >> # more /boot/grub2/device.map > >> (hd0) /dev/disk/by-id/mmc-SDC_0x49910339 > >> > >> # ls /dev/disk/by-id/ > >> mmc-SDC_0x49910339 mmc-SDC_0x49910339-part1 mmc-SDC_0x49910339-part2 > >> mmc- SDC_0x49910339-part3 > >> > >> When running yast in ncurses to change the bootloader without any update > >> I > >> also get the same 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. > >> > >> I am able to continue and I get the default "GRUB for EFI", 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. > >> > >> Submitted bug#1057142: > >> https://bugzilla.opensuse.org/show_bug.cgi?id=1057142> > > Got answer: > > > > --- Comment #1 from Ladislav Slezák <[email protected]> --- > > 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 > > I had started preparing arm for yast2-bootloader but I needed to wait > until a yast2-core pull request got merged and packaged and I haven't > followed up since. Basically we need to check all (Ruby?) code paths in > there that check for aarch64 or arm64 and decide whether to extend those > to arm as well - any volunteer? > > That is independent of the GRUB error. > > Regards, > Andreas
I tried the suggested steps mentioned in issues following the above section in the wiki and added how to get the application mkimage. I executed the mentioned mkimage command line using the original boot.script. The resulted boot.scr differs from the original boot.scr. Doing a reboot with the newly generarted boot.scr failed. -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
