-
Notifications
You must be signed in to change notification settings - Fork 41
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
OpenDuet 0.8.8 and later cannot boot Linux EFISTUB #2371
Comments
It's quite unusual to have OpenDuet set up as anything other than a way to boot into OpenCore as bootloader. Please could you provide a log of OpenCore as far as this failure, if this is your setup, if not could you please clarify your setup (e.g. is it set up to point directly at a Linix distro with Linux installed BOOTx64.efi?). EDIT: In fact, I believe it's very unusual and would require modified code and own build. Therefore OC debug log which would have (and does) include the error would have helped, however... |
I can replicate the error - thanks for the report. |
@XRevan86 - Please can you confirm that the build at https://github.com/acidanthera/OpenCorePkg/actions/runs/7595331858 fixes the issue? |
@mikebeaton, yes, this works, thank you. |
I didn't mention it because it didn't matter when reproducing the issue. |
OpenDuet is not able to boot Linux 6.7 now, saying Looking at the changelog I see these changes related to EFISTUB: torvalds/linux@50dcc2e, torvalds/linux@01b1e3c, torvalds/linux@50d7cdf, torvalds/linux@0163843 |
I can replicate the issue with Nitrux (I just picked up the first distro which I Googled which is shipping with it; I guess could have also have tried to upgrade some standard distro to bleeding edge). It's looking quite like an error at the kernel build end. (Not to say that 6.7 won't boot on standard loaders - it does - but to say that the layout looks broken all the same.) Which distro or which bleeding edge kernel build is showing the issue for you? |
I have confirmed that the issue exists in bleeding edge kernels for Ubuntu and Fedora and in 6.8rc as well as 6.7. We still believe that the problem lies at the kernel end and have raised an issue: https://lore.kernel.org/linux-efi/CAHzAAWQ6srV6LVNdmfbJhOwhBw5ZzxxZZ07aHt9oKkfYAdvuQQ@mail.gmail.com/T/#u |
This has been accepted as an issue in the Linux kernel EFI support, and a fix is being released (and eventually back-ported to all the kernels it applies to): https://lore.kernel.org/linux-efi/cover.1707141974.git.baskov@ispras.ru/T/#t
If you need to use one of these kernels prior to any fix being backported, you will have to use OpenDuet pre-0.8.8. |
This is resolved in Linux kernel 6.8 rc4 and up, by this commit torvalds/linux@e6f39a9 |
Starting with the version 0.8.8 OpenDuet refuses to boot any Linux kernel (including Unified Kernel Image).
The only thing that is printed out when executing the kernel is the word
unsupported
.The bug is strictly within OpenDuet, OpenCore is not affected.
Possibly related to #2363.
The text was updated successfully, but these errors were encountered: