-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chainload Grub #93
Comments
Hi, it's a Clover related problem and you can try to create a ticket in https://sourceforge.net/projects/cloverefiboot/ and discuss with Clover developers. Because you said an old version can work, you can also try to downgrade Clover by replacing the |
I tried with some old clover version but every clover that can boot mojave seems unable to boot linux and viceversa. Thank you anyway for the advice. |
You shouldn't chainload Grub or any other bootloader, use Clover for booting: |
I know i can load directly linux kernel, but i would like to have grub as a middleware. Btw I think |
ok the driver that prevent linux to boot is AptioMemoryFix, using an old version of this driver make linux bootable again mantaining full support of mojave. I've not tested everything but for now everything seems to work. |
A few days ago i had same problem with this laptop. I've created a workaround for the latest revision (R26) of AptioMemoryFix. It works for me. So, i ask you to confirm that Linux and Windows can be loaded from Clover / OpenCore. And advanced users i ask to check hibernation and nvram in macOS. Check it: AptioMemoryFix-64.efi.zip |
I am using your AptioMemoryFix for booting into Ubuntu and Windows 10 version 1903. |
@denskop 👍Considering creating a pull request to https://github.com/acidanthera/AptioFixPkg? |
I tried to boot grub from clover and it boot correctly but whatever linux kernel I pick it remains stuck loading initial ramdisk. If I boot directly to grub everything works fine and I can enter my ubuntu system. On an past version of your efi folder everything was working. But unfortunately that version of efi folder is not compatible with mojave. I can give you the efi folder mentioned if needed.
The text was updated successfully, but these errors were encountered: