(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: Debian GNU/Linux 12.11.0 "Bookworm" - Official amd64 NETINST with firmware 20250517-09:51
Date: June 29, 10 PM

Machine: Lenovo ideapad 330S-15IKB

Partitions: <df -Tl will do; the raw partition table is preferred>

derald@debian-lenovo:~$ sudo fdisk -l
Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: SAMSUNG MZ7LN128
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FD895AE2-B14E-46B0-8AC9-314AE103CA34

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1050623   1048576   512M EFI System
/dev/sda2  1050624   2050047    999424   488M Linux filesystem
/dev/sda3  2050048 250068991 248018944 118.3G Linux filesystem


Disk /dev/mapper/sda3_crypt: 118.25 GiB, 126968922112 bytes, 30998272 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/debian--lenovo--vg-root: 27.94 GiB, 29997662208 bytes, 7323648 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/debian--lenovo--vg-swap_1: 976 MiB, 1023410176 bytes, 249856 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/debian--lenovo--vg-home: 89.36 GiB, 95944704000 bytes, 23424000 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 7.34 GiB, 7876902912 bytes, 15384576 sectors
Disk model: USB Flash Drive
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x47446751

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1  *        0 1372159 1372160  670M  0 Empty
/dev/sdb2        4540   23579   19040  9.3M ef EFI (FAT-12/16/32)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [ OK ]
Detect network card:    [ OK ]
Configure network:      [ OK ]
Detect media:           [ OK ]
Load installer modules: [ OK ]
Clock/timezone setup:   [ OK ]
User/password setup:    [ OK ]
Detect hard drives:     [ OK ]
Partition hard drives:  [ OK ]
Install base system:    [ OK ]
Install tasks:          [ OK ]
Install boot loader:    [ OK ]
Overall install:        [ E - on reboot, BIOS bug creates continual output stream while user tries to input passphrase for encrypted volume ]

Comments/Problems:

I thought that the installation failed because rebooting the system created a continual output stream of BIOS errors. In fact, one can enter the
encryption key and proceed with booting the system. I tried to re-install the system 4 or 5 times, to see if my partitions were managed improperly.
This error only occurred when installing using encrypted LVM.


Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.

Looks like a simple configuration change solved the problem for me. I found a guide on the internet for how to change the boot splash settings on GRUB.

All the best,

Derald

Chemistry, Materials Science, Climate Resilience
https://www.linkedin.com/in/deraldtucker

Sent with [Proton Mail](https://proton.me/mail/home) secure email.

Which BIOS bug ?

I do not see why encrypted LVM would trigger a BIOS bug. Maybe you do
not see it without encryption because the system boots too quickly.

Which splash setting did you change ? Doesn't it just hide the error
message ? It may still be flooding your logs. If it is a kernel message,
you can check with dmesg.

Forwarding your reply to the bug report.

ACPI bug. Usually these messages happen only once at startup and are not
repeated.

So depending on the error frequency the log files might end up filling
your disk space.