-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
OcBootManagementLib: Add guard for static mImageLoaderCaps
- Loading branch information
1 parent
909008c
commit c6060b2
Showing
1 changed file
with
12 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this commit, the recovery from Ventura and Sonoma no longer starts.
Catalina Recovery, on the other hand, starts with an extra long delay.
This wasn't a problem with previous builds.
Greetings Coban
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you are sure this is replicable and tied to this commit, please can you provide a debug error log of a failing boot.
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, should have thought of that before :)
I repeated the whole thing with the debug version of the build.
Recovery Catalina starts delayed.
Recovery Ventura does not start
Recovery Sonoma does not start
The last two end with the error message only in the Debug build;
"OCB: load/start unsupported ordering, 6DEC2298 != 709F3318"
With the release version there is no message, just a black image.
MacOS itself, all 3 versions, can start normally.
Here are the logs.
Greetings Coban
Archiv.zip
PS: I have to go to work and can't be able to reply until late tonight.
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can replicate the issue. Thank you for the report. Actually this does not mean that the change here was incorrect, but means that a more comprehensive fix for the issue identified is needed. To follow.
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CobanRamo - The subsequent commit should resolve the issue.
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks guys and girls...
Great support...
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you confirm that all the recoveries where you saw problems are back to normal, when you have a chance?
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Of course I can, but only again tonight.
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to have it tested, and apparently it's working again.
All recoveries start again normally.
Thanks Mike.
c6060b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for quick report and quick tests - appreciated.