-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, In my laptop I have Win 10, OS 13.1, and 42.2 RC2; the later just installed and doesn't boot. In 13.1 I have grub 1, with this entry that has worked for years: title openSUSE Factory (/dev/sda9) via chainloader rootnoverify (hd0,8) chainloader +1 but now produces this error: Error 13: Invalid or unsupported executable format press any key to continue The documentation says: 13 : Invalid or unsupported executable format This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD). which I fail to understand. There should not be a kernel there, but grub2. Attached is the information from bootinfoscript. In partition sda9 is installed Leap 42.2 RC2, and grub "should" be installed just there, but I am not sure it was. The RC2 installer has changed and I'm unsure what it did. I'll describe it. Leap 42.2 RC2 boot settings (installation settings window) (/dev/sda9) (photos available) +++---------------- Booting The installer will not modify the MBR of the disk. Unless it already contains boot code, the BIOS won't be able to boot from this disk. * Bot loader type: grub2 * Enable trusted boot: no * Change location: * Do not install bootcode into MBR (install) * Warning: No location for bootloader stage 1 selected. Unless you know what you are doing please select another location * Order of hard disks: /dev/sda, /dev/sdb - ----------------++- This is wrong, so I click on "Booting" and modify it. +++---------------- Boot code options (photo available on request) Boot loader Location [ ] Boot from master boot record [X] Custom boot partition [/dev/sda9 ] [ ] Set active flag in partition table for boot partition [ ] Write generic boot code to MBR [ ] Enable trusted boot support - ----------------++- Notice that changing the tab clears the modification in this tab. I have to select "Accept", which renders: +++---------------- Booting The installer will not modify the MBR of the disk. Unless it already contains boot code, the BIOS won't be able to boot from this disk. * Bot loader type: grub2 * Enable trusted boot: no * Status location: /dev/sda9 ("/") * Change location: * Do not install bootcode into MBR (install) * Order of hard disks: /dev/sda, /dev/sdb - ----------------++- On previous years, there was a list of choices to boot from, like "boot from root partition", which is what I wanted to do. I can not permit the installer to modify the MBR, which is customized. Touch it and booting breaks. Now there is a line where to type the "custom boot partition". It is possible that YaST did not write the grub images at all anywhere. So I'm not totally sure of what happened. If the problem is in grub1 in the main system (13.1) or in the new 42.2 grub 2. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlgnxsIACgkQja8UbcUWM1xXggD/ZRWPgYKEdW2H5sI/39j0Qn/Q EHb/YonqT53lEuhAnzoA/14bToOg4IfgPvIZCGnfpIebK8wH1Qk9Ox2bXyY83Pgn =hom6 -----END PGP SIGNATURE-----