Package: installation-reports Severity: normal Tags: d-i X-Debbugs-Cc: Axel Beckert <a...@debian.org>, Dimitri Ledkov <x...@debian.org>, Debian ARM Mailing List <debian-...@lists.debian.org>, Manuel Traut <ma...@mecka.net>
Boot method: USB Image version: https://cdimage.debian.org/cdimage/bookworm_di_rc2/arm64/iso-cd/debian-bookworm-DI-rc2-arm64-netinst.iso Date: 2023-05-03, several times between noon and evening (CEST) Machine: Thinkpad X13s (ARM) Partitions: didn't come that far Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card: [ ] Configure network: [ ] Detect media: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system: [ ] Install tasks: [ ] Install boot loader: [ ] Overall install: [ ] Comments/Problems: [Note: Had to disable Secure Boot, to be able to boot from my USB 3.0 stick (plugged into the Thinkpad USB-C docking station). Before disabling Secure Boot I could choose it as boot device but I was always immediately returned to the device's boot device selection menu.] After choosing either "expert install" (first and prefered try) or "graphical expert install" (second try and second choice) I saw these three lines and then nothing more happened: EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... Waited 10 minutes at least, i.e. left it alone, did something else and came back later. Even adding the "debug" kernel parameter didn't bring up any more details on what's happening. Ubuntu seems to have had the same problem with Kinetic according to https://www.reddit.com/r/thinkpad/comments/vh1xse/comment/is1pq78/ But Dimitri's Ubuntu Installer Live image lunar-desktop-arm64.iso from https://people.canonical.com/~xnox/ubuntu-concept/full/daily-live/current/ as of 2023-03-07 20:08 booted fine without these issues. It would be nice if Dimitri (xnox@d.o, Cc'ed) could tell us which fix has been applied by him (or Ubuntu) to this image so that we can fix this issue also in Debian, maybe even before the release of Bookworm. (I only read in the recent D-I RC2 annoucement that there is already some support for the X13s, so I haven't tried it beforehand.) -- Package-specific info: [Stripped as — for obvious reasons — the bug report has been written on a different device.]