-
Notifications
You must be signed in to change notification settings - Fork 131
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
[tracking] shim 15.4 critical regressions #165
Comments
So we need 822d07ad4f07ef66fe447a130e1027c88d02a394 if we want Mac support? |
aarch64 builds are really awkward - they will break using binutils versions before 2.35, and even after that they may give unpredictable results. We really need proper toolchain support. |
I guess the better question is, do they want to make a 15.5? |
822d07ad4f07ef66fe447a130e1027c88d02a394 is for really old Macs that won't do SB anyway. But without that patch you'll fail to boot the machine at all |
And I guess we are waiting on 8b59591775a0412863aab9596ab87bdd493a9c1e to be merged or QA'ed? |
Fedora's shim-15.4-4 has fixes for some of the items listed in this issue. But there are two issues we're seeing with a subset of Lenovo and Dell systems that don't yet have upstream issues filed (and I don't understand the problem well enough to file them). |
As this issue is pinned I'd like to draw attention of new submitters to an old comment, calling for cross review between submitters themselves: |
This was a good reminder @realnickel, thanks. If submitters are hesitant to review because they "don't know where to start" they can begin with some of the reviewer guidelines captured here: https://github.com/rhboot/shim/wiki/reviewer-guidelines. |
shim 15.5 is out, closing this. |
Posting this here for awareness of submitters regarding fatal issues that can break boot on machines and other errors of unknown extend.
Critical issues:
Important issues:
Unknown extent:
You might want to hold off submitting shims until there is a 15.5 release, or cherry-pick patches.
The text was updated successfully, but these errors were encountered: