Bug#1034101: installation-reports: bookworm rc1 successful install to Levono T470

[Cyril Brulebois]

Hi Jeremy,

and thanks for your report.

Machine: Lenovo T470 (20HD)
Had to disable secure boot to get USB to boot, but otherwise,
everything "just worked".

Why is that? We've been supporting Secure Boot for a very long while.


Cheers,

[Steve McIntyre]

Post by Cyril Brulebois
Hi Jeremy,
and thanks for your report.

Machine: Lenovo T470 (20HD)
Had to disable secure boot to get USB to boot, but otherwise,
everything "just worked".

Why is that? We've been supporting Secure Boot for a very long while.

And one of my standard test machines here is my old T470. Jeremy: what
problem are you seeing please?

[Jeremy Davis]

Hi Cyril & Steve,

Apologies about slow reply. I only just found this thread buried in my
'debian bugs' folder (I'm subscribed to ***@debian and obviously don't
have my filters set up as they should be...).

Post by Steve McIntyre

Post by Cyril Brulebois
Hi Jeremy,
and thanks for your report.

Machine: Lenovo T470 (20HD)
Had to disable secure boot to get USB to boot, but otherwise,
everything "just worked".

Why is that? We've been supporting Secure Boot for a very long while.

And one of my standard test machines here is my old T470. Jeremy: what
problem are you seeing please?

FWIW this is my first "proper" UEFI hardware.

The issue I had was that the USB stick (with debian iso copied to it) I
was using wasn't showing up in the (bios/uefi) boot options (f12) as a
bootable device (i.e. wasn't listed as an option).

I was considering trying PXE boot, but I ran across online suggestions
that some USB sticks aren't recognized by BIOS/UEFI with secure boot
enabled. So I disabled secure boot and the USB appeared! :) Everything
worked as expected after that.

Perhaps there was something else going on and it was coincidental that
it worked after disabling secure boot? I just assumed that it was a UEFI
bug(/feature?) and not directly relevant to Debian.

I haven't tried re-enabling secure boot.

Regards,
Jeremy

[Cyril Brulebois]

Post by Jeremy Davis
Apologies about slow reply.

No worries at all.

Post by Jeremy Davis
Perhaps there was something else going on and it was coincidental that
it worked after disabling secure boot? I just assumed that it was a
UEFI bug(/feature?) and not directly relevant to Debian.

That kind of things Steve is more likely to know about.

Post by Jeremy Davis
I haven't tried re-enabling secure boot.

If you can spare a reboot, it'd be interesting to confirm your installed
system is actually SB-capable. It should be, as we install grub-efi-$arch
and shim based on recognizing a system booted under UEFI, so it should be
fine. Of course, if it isn't, turning SB off again should restore booting



Cheers,

[Jeremy Davis]

Thanks for the feedback.

Post by Cyril Brulebois
If you can spare a reboot, it'd be interesting to confirm your installed
system is actually SB-capable. It should be, as we install grub-efi-$arch
and shim based on recognizing a system booted under UEFI, so it should be
fine. Of course, if it isn't, turning SB off again should restore booting…

I have re-enabled secure boot and can confirm that it "just works"! :)

If there is anything else that is of interest that you want me to test
out, please feel free to ask.

TBH, I don't like some of the aspects of newer Gnome, but overall,
Bookworm feels pretty solid.

Great work to you and all the other incredible volunteers that make
Debian possible!

Cheers,
Jeremy

[Debian Bug Tracking System]

Your message dated Sun, 6 Oct 2024 11:18:22 +0200
with message-id <***@mailbox.org>
and subject line Re: #1034101 installation-reports: bookworm rc1 successful install to Levono T470
has caused the Debian Bug report #1034101,
regarding installation-reports: bookworm rc1 successful install to Levono T470
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)