#1103240 installation-reports: The installer hangs on detecting hardware. Installation cannot complete.

#1103240#5
Date:
2025-04-15 09:55:30 UTC
From:
To:
(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: https://cdimage.debian.org/cdimage/trixie_di_alpha1/amd64/iso-cd/debian-trixie-DI-alpha1-amd64-netinst.iso
Date: <Date and time of the install>

Machine: Gigabyte X870E Aorus Ice Pro. AMD Ryzen 9 9900X CPU
Partitions: <df -Tl will do; the raw partition table is preferred>


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

Initial boot:           [O]
Detect network card:    [E]
Configure network:      [ ]
Detect media:           [O]
Load installer modules: [O]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Detect hard drives:     [E]
Partition hard drives:  [ ]
Install base system:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [E]

Comments/Problems:
I could not figure out how to export an installation log using the documentation,
https://www.debian.org/releases/stable/amd64/ch05s04.en.html
Note that I do not have an internet connection during the installation, since the network card fails
to load.


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.

#1103240#10
Date:
2025-04-15 10:36:43 UTC
From:
To:
Hi,

Am 15. April 2025 11:55:30 MESZ schrieb anders <anderslinux@proton.me>:
[...]

Maybe try a newer image from
<https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/>


Holger

#1103240#15
Date:
2025-04-15 11:43:49 UTC
From:
To:
How does the installer hang ? Is it a hard freeze or is it still
possible to switch to other consoles with Ctrl+Alt+F2 to F4 ? If the
latter, you can
- switch to tty4 and see the latest logs
- switch to tty2 or tty3, start a shell, read the full log in
/var/log/syslog or mount a FAT-formatted USB drive and copy the log onto it.

#1103240#20
Date:
2025-04-17 17:34:23 UTC
From:
To:
[Please reply to the bug mail address, not only mine]

This is the same trixie alpha 1 image as in your initial bug report.
Holger suggested to try an image from
<https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/>,
which includes a more recent kernel than the trixie alpha 1 image.
... cut CPU register dump ...

It looks like the kernel panic is related with ath12k which is the
driver for your wireless controller.

This is interesting.

Driver module ath12k and possible firmware in firmware-atheros.

In your initial report lspci identifies it as RTL8125.
Driver module r8169 and possible firmware in firmware-realtek.

I think it is a UEFI firmware bug.

r8169 is the driver for your ethernet controller family. Some models
require firwmare from package firmware-realtek, some do not. But here I
do not see missing firmware errors, it looks like the driver does not
know your specific model.

If you installed without any firmware I would have expected missing
firmware (from firmware-amd-graphics) errors for an AMD GPU, but these
errors are different.
available in firmware-atheros.

The normal sequence in the installer when firmware is needed by a
network controller:
- load modules
- bring up and down network interfaces
- parse kernel logs for missing firmware
- find and install missing firmware
- unload and reload modules

the fact that the kernel panic does not happen without firmwares
suggests me that the bug may be triggered by either of the following
actions with r8169 or ath12k:
- unload the module when firmware is missing
- load the module when firmware is present
- bring the network interface up

You can easily test the first action with:
modprobe -r r8169
modprobe -r ath12k

(I recommend to do it in emergency or rescue mode or in the installer
shell to avoid an unclean filesystem if it causes a kernel panic)

Your hardware seems recent, so a more recent kernel may help.

#1103240#25
Date:
2025-04-18 11:43:04 UTC
From:
To:
[Please reply to 1103240@bugs.debian.org and not only me, really]

Did you previously try to install the package firmware-atheros ?
The files in ath12k/WCN7850/ look the same as the ones provided by
firmware-atheros.

Which version ?

This file is neither in the kernel repository nor the firmware-atheros
package. Maybe it is optional. Anyway it seems that the kernel does not
panic when the ath12k is loaded or unloaded and ath12k firmware files
are present.

I'd like the installer not to crash on your hardware, so anything that
can help narrow the possible causes is welcome.

#1103240#30
Date:
2025-05-02 16:44:53 UTC
From:
To:
In which conditions ? In the installer or the installed system ?
With or without atheros firmware present ?

So the issue persists is the latest installer release.

This option was useful only with modules for very old non-plug'n'play
devices. Now all needed modules are loaded automatically.

#1103240#35
Date:
2025-06-17 13:16:45 UTC
From:
To:
Same here,

my laptop hangs while detecting hardware. I've tried the graphical and expert
mode, also the testing netinst and testing live.

The machine is a new Lenovo T14s with AMD Ryzen Pro 7.

#1103240#40
Date:
2025-08-29 05:09:25 UTC
From:
To:
I can reproduce this with the Trixie release installer on my Lenovo
Thinkpad T14 Gen 5 (AMD) laptop. I was able to work around the bug,
without disabling the WCN785x/ath12k wifi chip in the BIOS, by
connecting via wired ethernet (r8169) and booting up the live image,
and running the installer from there. After installation, wifi works
fine.