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

            Bug ID: 369077
           Summary: Issues with UEFI dual booting with other Ubuntu OS's
           Product: neon
           Version: unspecified
          Platform: Other
               URL: https://forum.kde.org/viewtopic.php?f=309&t=135496
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Packages User Edition
          Assignee: neon-b...@kde.org
          Reporter: morganco...@gmail.com
                CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

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'

------------------------------------------
root@MS-7758:~# efibootmgr  -v

BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0006,0003,0002,0001,0000,000C,0013,0016,0019,0018,0005,0004
Boot0000* ubuntu       
HD(1,GPT,e09282d1-0ceb-450f-9bbb-ce15704bf86f,0x800,0x5f000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* neon 
HD(1,GPT,e09282d1-0ceb-450f-9bbb-ce15704bf86f,0x800,0x5f000)/File(\EFI\neon\shimx64.efi)
 
Boot0002* archlinux    
HD(7,GPT,b2931b61-aaf5-4f63-bf5d-0c27b32a5b84,0x4570f800,0x64000)/File(\EFI\archlinux\grubx64.efi)
 
Boot0003* opensuse     
HD(9,GPT,62b2fb01-63da-4f1a-ba58-2f3893c679dd,0x6af73800,0x4f000)/File(\EFI\opensuse\grubx64.efi)
 
Boot0004  opensuse-secureboot  
HD(9,GPT,62b2fb01-63da-4f1a-ba58-2f3893c679dd,0x6af73800,0x4f000)/File(\EFI\opensuse\shim.efi)
 
Boot0005* UEFI: Built-in EFI Shell     
VenMedia(5023b95c-db26-429b-a648-bd47664c8012)AMBO                              
Boot0006* Linux Boot Manager   
HD(7,GPT,b2931b61-aaf5-4f63-bf5d-0c27b32a5b84,0x4570f800,0x64000)/File(\EFI\goofiboot\goofibootx64.efi)
 
Boot000C* ubuntu       
HD(1,GPT,e09282d1-0ceb-450f-9bbb-ce15704bf86f,0x800,0x5f000)/File(\EFI\Ubuntu\grubx64.efi)
 
Boot0013* UEFI OS      
HD(9,GPT,62b2fb01-63da-4f1a-ba58-2f3893c679dd,0x6af73800,0x4f000)/File(\EFI\BOOT\BOOTX64.EFI)
 
Boot0016* UEFI OS      
HD(7,GPT,b2931b61-aaf5-4f63-bf5d-0c27b32a5b84,0x4570f800,0x64000)/File(\EFI\BOOT\BOOTX64.EFI)
 
Boot0018* UEFI: KingstonDataTraveler 2.01.00   
PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(5,0)/HD(1,MBR,0x4294967286,0x400338,0x1240)AMBO
 
Boot0019* UEFI: Samsung D3 Station 0200
PciRoot(0x0)/Pci(0x14,0x0)/USB(8,0)/HD(1,MBR,0x4294967171,0x40,0xe8e074c1)AMBO  
------------------------------------------


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


    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.

Reproducible: Always

Steps to Reproduce:
1. install neon (uefi mode)
2. install another ubuntu in UEFI mode


Actual Results:  
I expected that 

after using 

sudo grub-install /dev/sda

In neon I expected it to be make neon's grub the default in the neon uefi entry

Expected Results:  
I expected that 

sudo grub-install /dev/sda would make neon's grub the default from the neon
uefi entry

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to