Linux boot entry vanished after Clover update

[StudioK]

I've been running a tri-boot system (all EFI installs): OS X, Windows, Linux. I've installed a newer version of Clover (v2.3k_r3726) to prepare for the update to Sierra. After rebooting, the entry for Linux Mint has disappeared from the boot menu. No other changes were made besides updating Clover.

The version of Clover I replaced was r3270. I've since installed newer editions of Clover (including the one in Multibeast 9), but have the same result: no Linux.

Does updating Clover undo things (like uninstalling drivers I may have installed with the Configurtor)?

 

[kiiroaka]

Disonnect the other two drive OSes and see if Linux comes up. If not, go to a terminal windows and issue a "grub-update" command. If it re-installs GRUB and boots fine, then re-connect the other two drives. If Linux boots fine with the other two drives disconnected then it will probably mean that a Clover EFI file needs to be put back in place, especially if it Ubuntu since Ubuntu's EFI boot loader is a little wonky (it has to reside in an Ubuntu folder, iirc.)

 

[Going Bald]

I've been running a tri-boot system (all EFI installs): OS X, Windows, Linux. I've installed a newer version of Clover (v2.3k_r3726) to prepare for the update to Sierra. After rebooting, the entry for Linux Mint has disappeared from the boot menu. No other changes were made besides updating Clover.

The version of Clover I replaced was r3270. I've since installed newer editions of Clover (including the one in Multibeast 9), but have the same result: no Linux.

Does updating Clover undo things (like uninstalling drivers I may have installed with the Configurtor)?

Did you add to the new Clover install config.plist under Scan Entries an entry to scan for Linux? Do you still have a Linux folder in your EFI partition?

 

[StudioK]

Did you add to the new Clover install config.plist under Scan Entries an entry to scan for Linux? Do you still have a Linux folder in your EFI partition?

Hi Mr. Bald. Good to hear from you.

I do still have an 'ubuntu' folder in /EFI/Clover, just as before the Clover update.
I did not, however, add an entry to scan for Linux. This is an option in the Configurator, correct?

I remember ticking the 'kernel' box, but that didn't help. I'll try instructing it to scan for Linux and get back to you. Thanks for your reply.

 

[norgfach]

To add some clarification:

I ran into the same issue after installing Ubuntu on the same hard drive that already ad macos Sierra and Clover on it.

When I installed Ubuntu with Legacy and UEFI boot enabled in my BIOS, Ubuntu apparently did a Legacy install. Clover would show an option for Linux after the install but Linux wouldn't boot selecting it. In fact, my Linux install was unbootable.

After disabling all Legacy Boot options in my BIOS, I was able to EFI-boot the Ubuntu DVD off a USB DVD drive. After completing the install, I could boot Ubuntu by selecting it from my BIOS's boot option menu (press F12 on boot), but I could NOT see an option for Linux in Clover's boot menu.

I could, however, see a "ubuntu" folder on my EFI partition under the "EFI" directory.

I fixed this by changing the "Linux" option in the "Scan" subsection of config.plist from "false" to "true". This caused Clover to pick up the Linux loader on the EFI partition under "ubuntu" and I now have a Clover menu option to boot my EFI-installed Ubuntu system.

I didn't spot an option for this in Clover Configurator, but maybe I missed it...

 

[StudioK]

Did you add to the new Clover install config.plist under Scan Entries an entry to scan for Linux? Do you still have a Linux folder in your EFI partition?

This solved the problem straightaway.
I hadn't considered trying this because the Linux entry was unchecked before updating to the newer Clover version.

Thanks for solving this for me.

 

[kiiroaka]

Excellent fix, norgfach.