Contribute
Register

Ubuntu 20.04 doesn't boot using Clover

Status
Not open for further replies.
Joined
Sep 21, 2019
Messages
5
Motherboard
Gigabyte Aorus Z390 Pro
CPU
i9-9900K
Graphics
RX 5700 XT
Hello!
I had a dual boot setup on separate SSDs (Catalina + Win10, both UEFI).
Today i installed Ubuntu 20.04 (also in UEFI) on third SSD, with other drives disconnected.
Now when reconnected all of my drives i can boot Ubuntu from BIOS boot menu but not from Clover:
I can see Ubuntu Linux entry in my Clover and it loads GRUB2 just as fine as BIOS boot menu does but after that when i choose Ubuntu i only see a black screen.
 
Is GRUB2 in the Linux drive EFI partition?
 
Yes, it is.
Clover config.plist - GUI=>Scan Entries=>Linux=>True
Screen Shot 2020-05-13 at 4.46.36 PM.png
 
Clover config.plist - GUI=>Scan Entries=>Linux=>True
Yes, it is already set to true. Just updated Clover to latest 5117 and now i have two linux entries. Both however point to the same GRUB2 bootloader and if i choose Ubuntu there i get black screen in both cases.
 
Yes, it is already set to true. Just updated Clover to latest 5117 and now i have two linux entries. Both however point to the same GRUB2 bootloader and if i choose Ubuntu there i get black screen in both cases.
have you tried setting the path to the Grub2 boot file?
 
have you tried setting the path to the Grub2 boot file?
Hi,
I am in the same situation described in the initial post:
- Clover 5119 installed in the macOS Mojave drive EFI partition
- config.plist setted with GUI=>Scan Entries=>Linux=>True
- Ubuntu 18.04 installed in UEFI mode on a separate SSD with GRUB2 in the Linux drive EFI partition
- at startup i have the Ubuntu entry in the clover menu, selecting it i can enter in the GRUB menu but selecting Ubuntu or any other entry (i have different partitions with different linux distributions on the same drive) the GRUB menu disappears but none of them starts.
- using the F12 key at startup Ubuntu (like all other linux distributions installed) starts normally from GRUB menu
- Previously, with the same configuration, using Clover r.4920 the problem never occurred

Please, could you explain how i could try to setting the path to the Grub2 boot file as You suggest (or any other hint)?
 
Hi,
I am in the same situation described in the initial post:
Hi,
FYI I ended up installing fresh vanilla clover for the test purposes and ubuntu were loading just fine.
Then i started to add my custom plist, drivers etc one by one to track down the issue and it turned out to be FwRuntimeServices.efi / AptioMemoryFix.efi (sry, don't quite remember). I guess this driver were messing with NVRAM preventing the normal Ubuntu startup. So i replaced this problematic driver with the one bundled with the latest clover at the moment and that solved my problem.
 
Hi,
FYI I ended up installing fresh vanilla clover for the test purposes and ubuntu were loading just fine.
Then i started to add my custom plist, drivers etc one by one to track down the issue and it turned out to be FwRuntimeServices.efi / AptioMemoryFix.efi (sry, don't quite remember). I guess this driver were messing with NVRAM preventing the normal Ubuntu startup. So i replaced this problematic driver with the one bundled with the latest clover at the moment and that solved my problem.
Thank You for your hint. It allowed me to understand that, perhaps, even in my case, the problem is due to the updates of the OcQuirks.efi + FwRuntimeServices.efi driver (the latter recently renamed OpenRuntime.efi).
Unfortunately I noticed that using the latest version of these drivers I can start linux correctly but I cannot start macOS Mojave.
Which version did you use?
 
Thank You for your hint. It allowed me to understand that, perhaps, even in my case, the problem is due to the updates of the OcQuirks.efi + FwRuntimeServices.efi driver (the latter recently renamed OpenRuntime.efi).
Unfortunately I noticed that using the latest version of these drivers I can start linux correctly but I cannot start macOS Mojave.
Which version did you use?
Currently i use AptioMemoryFix.efi from Clover 5117 Package. I dont use neither OcQuirks.efi nor FwRuntimeServices.efi
 
Status
Not open for further replies.
Back
Top