Can't boot to Leap - couldn't find vmlinuz

Hi,

Yesterday I installed the newest openSUSE leap OS on my primary hard drive that already contains a working Windows 8.1 partition and Ubuntu. During the initial setup I created a 40gb BRTFS partion and pointed /home to an other EXT4 partition. I mounted /dev/sda1 EFI partition as a /boot/efi.

After the installation I never saw the openSUSE grub. I booted into Ubuntu GRUB that doesn’t contain openSUSE launcher.

I booted to Ubuntu and run a command “grub-update” (and also "grub2-update just to be sure) and it detected openSUSE installation and added it into the boot menu. However, it doesn’t work. I get the error that it couldn’t find vmlinuz.

Error: file 'vmlinuz-4.1.12-1-default' not found

Here are the screenshots of both the error and Grub configs:
http://imgur.com/a/bxvPX
(There are two different openSUSE entries and two different errors)

Here’s the screenshot of files in sda6/boot
http://i.imgur.com/04ngB92.png
(So the images are there!)

Here’s the screenshot from Gparted:
http://i.imgur.com/6CV6xQY.png

I couldn’t find any solution to my problem. I tried running a boot-repair liveCD but it gave me an error that I need to enable an openSUSE grub-efi-amd64-signed repository. Anyway, grub-update finds it so it should work, but maybe the parameters are wrong?

I’m running an UEFI system with a SecureBoot. Disabling SecureBoot doesn’t help (it still boots me into the Ubuntu Grub2 menu and displays the same error)

Any help? :slight_smile:

Did you install with SecureBoot enabled? The Leap 42.1 install DVD has a broken shim.efi that was fixed after the release date.

Most likely the DVD was not able to install an OpenSUSE bootloader, and the Ubuntu Grub is not able to read the BTRFS layout used by Leap.
You might try one of the following:

  1. Install with SecureBoot disabled, do a complete online update, then reboot; if everything is OK you should be able to enable SecureBoot again (if you didn’t build some modules yourself as proprietary video drivers, VirtualBox or VMWare modules or the like, or if you properly signed them with the required procedure).

  2. Install with an EXT4 /root partition, do not install any bootloader (keep the Ubuntu GRUB2), boot to Ubuntu, update Ubuntu GRUB as you did: it should be able to boot Leap from EXT4.

If something else went wrong with the bootloader installation please write back.

  1. Install with SecureBoot disabled, do a complete online update, then reboot; if everything is OK you should be able to enable SecureBoot again (if you didn’t build some modules yourself as proprietary video drivers, VirtualBox or VMWare modules or the like, or if you properly signed them with the required procedure).

Truth be told, I tried installing with SecureBoot disabled in the first place and it didn’t work. Then I installed with SecureBoot on. I also tried setting the other bootloader with Windows

bcdedit /set {bootmgr} path \EFI\opensuse\grubx64.efi (or shim.efi)

but it didn’t do anything.

I may try it again in the evening.

  1. Install with an EXT4 /root partition, do not install any bootloader (keep the Ubuntu GRUB2), boot to Ubuntu, update Ubuntu GRUB as you did: it should be able to boot Leap from EXT4.

Well that’s a bummer. I migrated from a working Tumbleweed EXT4 installation to Leap because I wanted to use properitary drivers and snapper, so this time I formatted into BRTFS.

Well, I will report back in the evening. I hope the first option will work this time. Thanks for you time. If anybody else got any ideas, I would gladly hear them out. It would be great to get things runnin in this config.

Make sure that you switched OFF FastBoot in Windows before you shut down that system. Also be sure that the OpenSUSE installer boots in EFI mode (no menu options to the bottom of the screen).
Before tinkering with the Windows bootloader, you should be able to boot from the EFI menu (maybe accessible by powering on while pressing “ESC” or F2 or something like that) if the OpenSUSE bootloader got properly installed.

If you install in legacy mode and the other OS’s are in EFI mode they won’t see one another. In order to chain all must be in the same mode