My system was like follows. Windows 7 on /dev/sda3 and Kubuntu on /dev/sda6 with swap on /dev/sda5.
Kubuntu packet management system was somehow damaged and i couldn’t fix it. I had problems installing i386 packages which i needed. So I decided to reinstall. Because I start my Linux experience in the early 90s with SUSE I decided to return to SUSE once more and see how it developed.
I tried to create a bootable USB-stick using “Linux live USB creator” it detected SUSE but wasn’t able to create a proper bootable USB-stick. so I came back to the suse page and found the tutorial mentioned in my frist few posts. I knew about the problem that UEFI would not work with the USB-stick, but I decided to try with legacy and fix the bootloader from a live cd capable of booting with UEFI. I knew Kubuntu would be able to. So I did install SUSE and took care that nothing but the root partition of kubuntu (/dev/sda6) would be formatted and that no changes to the partition table were made.
That left me with a system like this. And thats why I think that GRUB and not GRUB-efi is installed. But probraly I am wrong. Can you comment on this?
I will try your suggestion now.
sudo efibootmgr -c -d /dev/sda -p 1 -L openSUSE -l ‘\EFI\opensuse\grub.efi’ gave me the following output:
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0004,0000,0002,0001,0003
Boot0000* ubuntu
Boot0001* Hard Drive
Boot0002* Windows Boot Manager
Boot0003* UEFI: USB
Boot0004* openSUSE
sudo efibootmgr -v gave me the following output:
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0004,0000,0002,0001,0003
Boot0000* ubuntu HD(1,800,32000,9acb5611-b302-47c8-a1b2-c114462f9c0d)File(\EFI\ubuntu\grubx64.efi)
Boot0001* Hard Drive BIOS(2,0,00)
Boot0002* Windows Boot Manager HD(1,800,32000,9acb5611-b302-47c8-a1b2-c114462f9c0d)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0003* UEFI: USB ACPI(a0341d0,0)PCI(1a,0)USB(1,0)USB(1,0)HD(1,800,ef5800,6da034c0)
Boot0004* openSUSE HD(1,800,32000,9acb5611-b302-47c8-a1b2-c114462f9c0d)File(\EFI\opensuse\grub.efi)
Rebooting and selecting opensuse in the boot menu now drops me to a grub shell:
GNU GRUB version 2.00
Minimal BASH like line editing is supported ...
After all better than grub rescue shell 
Once again I chrooted into my openSUSE installation. Beeing chrooted i ran the command grub2-efi-install which updated the “boot table” and installed grub2-efi.
Nothing changed though I am still greeted with a grub2 promt.
I never used the grub2 prompt. Any ideas?
Unfortunately, we still do not know, where this GRUB2 came from (i.e. whether this is openSUSE one), but …
- which $prefix this grub has? Issue “set” in grub shell and look for value of “prefix” variable.
- you could use “ls” to check what it sees. Top level will be drives, and you are interested in partition 6 which should be (hd0,6) or (hd0,gpt,6). If you do see it, check (hd0,6)/boot whether you see your kernel and initrd (should be mlinuz-3.4.6-2.10-desktop and initrd-3.4.6-2.10-desktop). if you do you could try to boot it by using
linux (hd0,6)/boot/vmlinuz-3.4.6-2.10-desktop root=/dev/sda6
initrd (hd0,6)/initrd-3.4.6-2.10-desktop
boot
Please recheck partition numbers.
Or you could try to check whether grub.cfg is found, for grub2-efi it is under /boot/grub2-efi. I am not surprised if installation put it in wrong directory though, so it may be under /boot/grub2. Then “configfile (hd0,6)//boot/grub2/grub.cfg” may even bring you shiny menu …
“set” in grub shell gives me:
...
prefix=(hd0,gpt6)/boot/grub2-efi
...
root=hd0,gpt6
...
ls (hd0,gpt6)/boot gives this (perhaps some other files)
vmlinuz, vmlinuz-3.4.6-2.10-desktop, vmlinuz-3.4.6-2.10-desktop.gz, initrd, initrd-3.4.6-2.10-desktop, initrd-3.4.6-2.10-desktop.gz, System.map-3.4.6-2.10-desktop, sysctl.conf-3.4.6-2.10-desktop, symvers-3.4.6-2.10-desktop
ls (hd0,gpt6)/boot/grub-efi gives
x86_64-efi/
which holds many *.mod files amongst others normal.mod and linux.mod but no video.mod
Issuing these commands openSUSE boots and starts the post installation system configuration. It fails in some (three) things, which I couldn’t see all (e.g. auto update during configuration). Networking is not working, but eth0 is listed in ifconfig so may be it’s just misconfigured.
This worked exactly how you expected. Your are a genius. The only boot entry in grub.cfg seems to be openSUSE linux. But that should be easy to solve by editing grub.cfg. Do you think I can copy grub.cfg to (hd0,gpt6)/boot/grub-efi ?
No. It should not be there in the first place. Something went really wrong. Can you make available content of /var/log/YaST2?
Make sure you completed installation, install grub2-efi and reinstall bootloader. Verify that you are booted in UEFI mode before that (/sys/firmware efi exists and efibbootmgr works). Make sure you installed efibootmgr (installing gptfdisk makes sense too, I do not trust parted, it is too high level tool).
What do you mean by “make available”? Should I create a tarball and somehow send it to you?
Should I create a tarball and somehow send it to you?
Yes, upload somewhere. Compressed, please 
arvidjaar, you got a private message …
During system start two things fail, one things fail, one thing aborts:
Failed to start LSB: VirtualBox Linux Additions kernel modules [FAILED]
Failed to start Network Manager [FAILED]
Dependency failed. Aborted start of Network Manager Wait Online ABORT]