Comment 5 for bug 1750351
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
The packages themselves are not buggy. This appears to be an issue caused by firmware doing exactly what it is told and designed to do.
I didn't notice that earlier, but there's a "Boot Order Lock" option in Lenovo's firmware, and it is set to Enabled in the screenshots you provided.
Automated boot fallback can only work if the BootOrder can be changed, as that is what it used to let the system boot directly to disk, then rebuild the 'ubuntu' entry, and reboot to get into it.
If you disable 'Boot Order Lock' and remove the hold on the packages, I expect the system to successfully update, and boot to Ubuntu successfully. At the very least, it will definitely help ensuring fallback works without multiple reboot.
I'm still not sure if there isn't also a latent issue caused by NVMe, but I think this will get us one step in the right direction :)