On Sat, 2016-04-02 at 09:38 +0300, Andrei Borzenkov wrote:
01.04.2016 08:16, Dave Howorth пишет:
On Wed, 2016-03-30 at 07:34 +0100, Dave Howorth wrote:
On Tue, 2016-03-29 at 21:16 +0300, Andrei Borzenkov wrote:
OK, so create on openSUSE file /boot/grub2/custom.cfg with content
menuentry "Mint bootloader" { set root=hd0,1 chainloader /EFI/ubuntu/shimx64.efi }
and reboot. You should get this menu entry, and hopefully selecting it will bring up Mint boot menu.
It brings up:
error: disk 'hd0,1' not found.
When I correct it to hd1,1 it loads Mint's grub but when that tries to load Mint, it says:
Bootloader has not verified image. System is compromised
Oh! Are you able to boot Mint at all with secure boot enabled? Try
efibootmgr -n 0002
This /should/ set one time boot option for next reboot only to Mint loader, so no openSUSE will be involved. Are you able to boot it this way?
Yes, that works just fine.
(n.b. paraphrased because the system switches off before I can type the message into the mail).
So no banana yet. Dave
I'll keep trying my other options.
Well I finally got something to work. What a pain. I created a chainloader entry in Mint for openSUSE and that works. I've no idea whether this is optimum but this is what I've got:
menuentry "openSUSE bootloader" { insmod chain insmod btrfs set root=(hd1,1) chainloader /EFI/opensuse/shim.efi }
I was meant to answer earlier, sorry for delay.
The error message you get when you try to chainload Ubuntu shim from openSUSE shim comes from shim itself. As far as I can tell looking at code, it is a bug in shim which is hit when you are doing something like this
shim(1) -> bootloader(1) -> shim(2) -> bootloader(2) -> kernel
The problem is that shim(1) hooks into EFI services but it has no information about bootloader(2), so when bootloder(2) attempts to launch kernel, shim(1) thinks kernel was not verified and blocks this attempt.
I kind of understand what you're saying, but not completely. You're saying that shim(1) is still involved even after it chainloads shim(2)? I thought the whole purpose of chainloading was to pass responsibility to the other boot system?
Now code that does it (at least, code that contains error message you see) appeared in shim 0.9. At least my copy of Ubuntu 14.04 has shim 0.8. Could you verify what shim version you have?
I don't know how to do that and searching the intertubes hasn't helped. The openSUSE shim is whatever comes with Leap 42.1 and the ubuntu shim is whatever comes with Mint 17.3.
If Mint has shim 0.8 it probably explains why chainload in opposite direction works, but that also means that it will most likely stop working when shim in Mint/Ubuntu is updated.
I suggest you open at least openSUSE bug report; the code in question comes partially from SUSE developer, so we have good chances to get it fixed. Please tell bug number here so I could comment on it.
I'll do that. You'll need to tell me what the bug is so I can report it. Before that, you'll need to tell me how to login. I type my username and tell it I've forgotten my password. It says my security question is my mother's maiden name in german, which seems most unlikely, and I don't remember what email address I signed up with a long time ago. And my browser remembers nothing because you've changed your security domain. So I'm stuck. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org