please share a working tumbleweed grub2 entry!

russell_hay · October 9, 2015, 2:00pm

Hi all,

have had to change my dual-boot system (ElementaryOS and OpenSuse Tumbleweed) to boot from Elementary - so can someone share a working grub2 entry for Tumbleweed so i can see what the options should be and I’ll manually update grub2 within ElementaryOS so I can get back into Tumbleweed.

Note - whatever I tried, I could not get OpenSuse to detect the ElementaryOS installation - therefore have had to move to the eOS bootloader - which detects OpenSuse Tumbleweed just fine, but the grub2 options stop it booting.

anyway -can someone share a working grub2 entry for Tumbleweed please - and yes I know I’ll have to amend the HDD UUID’s etc.

Thx.

arvidjaar · October 9, 2015, 2:13pm

Actually,

linux /boot/vmlinuz
initrd /boot/initrd

should be pretty much enough. You may add resume=/dev/your/resume/device if you plan to suspend to disk.

I could not get OpenSuse to detect the ElementaryOS installation

Is it Linux based? Care to open bug report so it can be fixed?

gogalthorp · October 9, 2015, 2:15pm

Be sure both OS’s boot the same mode. ie both EFI or both legacy. You can’t chain OS if they use different modes

russell_hay · October 9, 2015, 2:32pm

arvidjaar:

Actually,
linux /boot/vmlinuz
initrd /boot/initrd
should be pretty much enough. You may add resume=/dev/your/resume/device if you plan to suspend to disk.

Is it Linux based? Care to open bug report so it can be fixed?

Hi,

I will recreate it soon(ish) so I can report it - when it happened it did seem to be a common issue as I could google for the issue. os-prober would find the other linux distro, but when grub was updated it wouldn’t be included.

So - rather than creating a manual entry I wanted to see if ElementaryOS’s version of grub2 would see OpenSuse. Of course it’s really Ubuntu 14.04 under the skin.

Just need to get OpenSuse from panicing during boot

arvidjaar · October 9, 2015, 2:51pm

May be; but fixing it needs Elementary OS and some other OS installed. Set of users who have it does not necessary intersect with set of users who can debug (and fix) detection in os-prober :). As you have possibility to at least provide diagnostic information, we have some chance.

russ_hay · November 18, 2015, 3:04pm

Just to close this off - I’ve submitted the bug for this, it’s Bug 955628. Took me a while to get around to recreating it and in the interim have moved over to Tumbleweed.