I really don't think you're affected by the same issue as the other bug.
I see there's a BootOrder set (at least, once booted), and there's an
ubuntu entry that looks correct, but that does depend on what you're
supposed to be booting to. The screenshot you include says the system
should be booting from NVMe, but the BootEntry for Ubuntu is not quite
looking the same.
What process did you take to boot to Ubuntu to file the bug?
Usually, for NVMe you should see a BootEntry that includes "nvme(";
doesn't seem to be the case here. Maybe this particular firmware only
likes to use UUIDs as we see there?
** Changed in: shim (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: shim (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750351
Title:
(Thinkpad T470) Boot loop after update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1750351/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
