-
Notifications
You must be signed in to change notification settings - Fork 412
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
HP Elitebook 865 G10 fails to offer release for reinstall #7010
Comments
I'm presuming @darkbasic this is 1.9.15 fwupd release right? Can you please share verbose daemon output ( |
Should be 1.9.16ish from the backport branch. I'll post the output later today. |
I tried to reproduce it using a different system (Framework 13) on fwupd 1_9_X commit ad2aec9 but that has a firmware on a non standard remote. I can't reproduce.
|
I'm pretty sure the reinstall button was being rendered before in Gnome Software, otherwise I wouldn't have risked downgrading to test a regression. I suspect HP might have changed something on LVFS. |
Maybe the GUID changed during the upgrade? We certainly need verbose logs to make sense of why things are happening |
Dumb question but are you sure you have the LVFS testing enabled? Does it show up in |
Yes it does. |
Specifically as |
My hypothesis is that the firmware was in the stable channel and you had lvfs-testing disabled. It rolled out some people installed it and there must have been some number of issues reported that forced it to automatically demote to My ACL at fwupd.org doesn't let me see the details for the HP firmware, so I don't know if this is true. @hughsie can you check it? And if it did get demoted - can we see if it was because of a bunch of people running fwupd-efi 1.5? If so; it should probably be re-promoted because we know that fwupd-efi 1.5 issues are caused by an old gnu-efi. |
You're completely right: I saw it was in the remotes but I didn't check if it was enabled because I enabled testing a long time ago and took it for granted. Somehow it got disabled (maybe after the temporary upgrade to 2.0?) and in the meantime the fw has been demoted to the testing branch. |
HP EliteBook 8x5 G10 Notebook PC V82 0x1030900 still looks to be in stable to me -- it was moved from embargo to stable on 2024-02-06.
Weird. What do you get if you download the .cab file (link in this comment) and then do |
1.4.10.0 is the release we're talking about tho. |
Ohh my mistake! In that case it's easy; fwupd auto-demoted the firmware back to testing as it had 61% success. The failures do seem to be of the form "failed to run update on reboot: expected 0x01040a00 and got 0x01030900" -- and both have Is fwupd-efi ready to be released? If so, I can tag a new build and then do an LVFS known issue for 1.5 |
Is gnu-efi 3.0.18 in Fedora yet? If so; I think we should make a hard requirement on 3.0.18+ right now. It was waiting for that. That's the last thing I think needed. |
Fedora 41 yes, Fedora 40 is in freeze. The latter I can buildroot-override tho, so go for the hard dep please. |
Okay let's wait to close until we tag a new fwupd-efi and get a known issues on lvfs for that version. |
fwupd-efi 1.6 is tagged |
@hughsie did you get the known issue on 1.5 added? |
@superm1 something like this? |
link points to https://github.com/fwupd/fwupd/wiki/LVFS-Triaged-Issue:-fwupd%E2%80%90efi-1.5-and-old-gnu%E2%80%90efi if you want to wordsmith that a bit. |
Looks great thanks. Can you also double check if there are any others that fit the pattern and got auto demoted? |
That's harder, will do! |
Only two matched, neither demoted. |
I fear the issue is not in Gnome Firmware.
Originally posted by @darkbasic in #6956 (comment)
The text was updated successfully, but these errors were encountered: