Re: Thinkpad X13s boot loop after install
On Fri, Aug 29, 2025 at 01:57:27PM -0500, Michael Parson wrote:
> On Wed, 20 Aug 2025, Lionel Élie Mamane wrote:
>>> 2) Go back to main screen and Continue, which reboots, get the grub
>>> screen, tries to load the default and it reboots.
>>> I found a thread from May 2023 where someone else reported the same
>>> boot loop.
>>> His solution:
>>>> Something had changed the "debian" EFI boot option to load
>>>> directly grubaa64.efi instead of DtbLoader.efi.
>>>> I added another boot option "Debian-LEM" that loads DtbLoader.efi
>>> Thing is, I can't get back into even the installer or
>>> recovery-mode from the installer image
>> That's not where you have to do that stuff. It happens in the
>> firmware's command line. I don't think the firmware's GUI
>> configuration allows to create/edit entries.
>> See chapter 4 of
>> https://docs.google.com/document/d/1WuxE-42ZeOkKAft5FuUk6C2fonkQ8sqNZ56ZmZ49hGI
>> for inspiration.
> Thanks for that info. Seems somethings have moved around a bit since
> those docs were written.
> Poking around a bit in the Efi shell, Looks like the partition on my
> setup was FS16:\EFI\deiban\shima64.efi
> Changing this to use DtbLoader.efi (which I found on another partition,
> copied it to the same location as the shima64.efi) did not change
> things.
> I removed the 'quiet' entry from grub to see if I could see anything
> else before it reboot and I saw "EFI stub: Generating empty DTB"
> which made me think that it wasn't picking up the
> "sc8280xp-lenovo-thinkpad-x13s.dtb" that you're supposed to copy
> into place based on the Debian Wiki?
> I tried copying that file to the root of FS16: as well as into
> \EFI\debian, same results.
dtbloader.efi expects that file to be named
f249803d-0d95-54f3-a28f-f26c14a03f3b.dtb
and to be placed in \EFI\DTB or \DTB, not sure now. I see the Debian
wiki says something else, to put it into the root named
sc8280xp-lenovo-thinkpad-x13s.dtb
That's probably the/a difference between using
dtbloader.efi
and
shima64.efi
Note that for better robustness, I *added* another boot entry instead
of modifying the automatically created one, so that any later update /
upgrade doesn't touch my boot settings.
Reply to: