-
Notifications
You must be signed in to change notification settings - Fork 45
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
OpenLinuxBoot fails to process loader\entries\*.conf of Fedora 41 due to GRUB variables #2440
OpenLinuxBoot fails to process loader\entries\*.conf of Fedora 41 due to GRUB variables #2440
Comments
@AlexFullmoon - Could you send the OpenCore log using PS: Am I right that you have set LINUX_BOOT_LOG_VERBOSE using OpenLinuxBoot flags for the debug log you sent, even though that is not shown in the EFI? |
Done, here: opencore-2024-11-01-193153.txt
Oops, yes, my bad. Must've been opened in editor when I copied it. Nothing else changed, I believe, but just in case I'll reupload. https://seaf.moonlightwell.ru/f/1fecb48d0bce42b7a917/ |
I've found this causing problems for another project way back in 2019: error10/kexec-reboot#11 Unlike sd-boot, we already do (partially) extract grub vars since they're quite often used in BootLoaderSpecByDefault files. We support expanding grub variables only for We will also need to work around this bug (we normally assume that a missing variable is an error condition; I imagine we should initialise these two variables to empty values when they are not present, on some flag which is enabled by default) and we also need to add code to support having multiple initrds in one |
@AlexFullmoon - Could you confirm that the version in |
@mikebeaton Yes, it works. |
OpenLinuxBoot fails to process loader\entries\*.conf files on Fedora 41 due to Fedora adding some GRUB variables (related to TuneD).
Specifically, in Fedora 40 conf files look like this:
And in Fedora 41:
Attached boot log, but here's the issue:
Only detected boot option remains rescue mode, which does not have those variables in F41.
This could be circumvented by removing those variables (as suggested here), but that would probably disable some TuneD functionality.
opencore-2024-11-01-070424.txt
If necessary, EFI is here: https://seaf.moonlightwell.ru/f/f34bac86e643485a8ba4/
The text was updated successfully, but these errors were encountered: