- Notifications
You must be signed in to change notification settings - Fork23
esrt: Decode LastAttemptStatus#219
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This will help us figure out what's going on when a BIOS update fails.Different updates return different values.Signed-off-by: Daniel Schaefer <dhs@frame.work>
9cd69c8 to0ce1c12CompareJohnAZoidberg commentedOct 9, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Ahhh I don't get LastAttempt status on windows yet... Need to figure out how to do that, hopefully it's possible. |
Device Manager shows:
but not the last attempt version and status. |
Done#220 |
| #[derive(Debug)] | ||
| #[repr(u32)] | ||
| pubenumIntelRetimerUpdateErr{ |
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.
These might be slightly difference on different retimer generations.
Have to double-check if our BIOS actually reports that in the ESRT status. |
This will help us figure out what's going on when a BIOS update fails.
Different updates return different values.