HI.

Loving neon, I however have one really annoying issue.. This may not be directly neon's fault.

When I install Neon, then install another Ubuntu based OS - for example Mint, The neon UEFI boot entry loads grub from the wrong partition (i.e the Mint one)..

i.e after installing the second os (mint), I have a 'neon' UEFI entry as well as an 'ubuntu' entry - the problem is now either the neon or the ubuntu uefi entry both boot from the mint partition, this means I can load neon from the mint grub, however this is not ideal as say I install a kernel update in neon, the mint grub entry wouldn't register the new kernel image in grub.

Also say I delete mint, this means I have an unbootable neon os....

I tried reinstalling and ensuring that I have a separate efi partition for mint, I even ensured whilst installing mint that I unselected the neon efi boot loader partition (i.e do not use this partition) and it still sticks the UEFI boot files in the neon EFI partition.

My question I guess is : Once I have installed another ubuntu based OS how to I have the neon UEFI entry the 'active' one again ?

If it helps here is the output of 'efibootmgr -v'

Code: Select all

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0001,0000,0006,0007,0005
Boot0000* neon   HD(1,GPT,e09282d1-0ceb-450f-9bbb-ce15704bf86f,0x800,0x5f000)/File(\EFI\neon\shimx64.efi)
Boot0001* ubuntu   HD(1,GPT,e09282d1-0ceb-450f-9bbb-ce15704bf86f,0x800,0x5f000)/File(\EFI\ubuntu\shimx64.efi)
Boot0005* UEFI: Built-in EFI Shell    VenMedia(5023b95c-db26-429b-a648-bd47664c8012)AMBO
Boot0006* ubuntu   HD(1,GPT,e09282d1-0ceb-450f-9bbb-ce15704bf86f,0x800,0x5f000)/File(\EFI\Ubuntu\grubx64.efi)
Boot0007* UEFI: Samsung D3 Station 0200   PciRoot(0x0)/Pci(0x14,0x0)/USB(8,0)/HD(1,MBR,0x4294967171,0x40,0xe8e074c1)AMBO

Any help with this would be welcomed..

I can dual boot with any other distro fine, i.e debian, fedora, opensuse, arch.

I should also point out i'm using UEFI, not secure-boot.

This bug only affects neon

If I load mint (or ubuntu, etc) and do a

Code: Select all

sudo grub-install /dev/sda

Then mint (or whatever distro) takes priority again (as it should)

If you do it with neon, it doesn't - it creates a neon entry but that loads the mint grub - the other way round its fine.

i.e if I install neon then any other ubuntu distro I can no longer boot from the neon efi loader unless I reinstall neon. which means removal of the other os means non-bootable system, with mint at least I could go to a live cd, chroot and fix the bootloader, I cannot with neon.

Its a fairly serious problem.

yossarianuk wrote:Its a fairly serious problem.

Please use this to report bugs: https://bugs.kde.org/

Added a bug report

(let me know if I need to add anything...)

https://bugs.kde.org/show_bug.cgi?id=369077