Bug#1103240: installation-reports: The installer hangs on detecting hardware. Installation cannot complete.
[Please reply to the bug mail address, not only mine]
On 17/04/2025 at 14:04, anders wrote:
I tried to use a newer image per suggestion from Holger Wansing,
https://cdimage.debian.org/cdimage/trixie_di_alpha1/amd64/iso-cd/debian-trixie-DI-alpha1-amd64-netinst.iso
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.
It is a hard freeze, but I if I switch to other consoles with
Ctrl+Alt+F2 to F4 prior to the freeze, I get the following last printed
logs before the freeze. Note that this was copied by hand, I let ...
indicate output that I have omitted on that line.
[74.323429] RIP: 0010:ath12k_hal_srng_access_begin+0x10/0x30 [ath12k]
... cut CPU register dump ...
[74.324313] PKRU: 55555554
[74.324388] Kernel panic - not syncing: Fatal exception in interrupt
[74.324493] Kernel offset: 0x28200000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[74.324658] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ] ---
It looks like the kernel panic is related with ath12k which is the
driver for your wireless controller.
I managed to get the installation to finish by setting the boot
parameter firmware=never, and getting a USB internet connection via my
phone. Neither the Wifi module nor the ethernet connection seem to work
(both are embedded in my motherboard Gigabyte Aorus X870E Pro Ice).
This is interesting.
Wifi module: Qualcomm Wi-Fi 7 QCNCM865
Driver module ath12k and possible firmware in firmware-atheros.
Ethernet controller: Realtek 2.5GbE LAN chip (I can't seem to find better specifications)
In your initial report lspci identifies it as RTL8125.
Driver module r8169 and possible firmware in firmware-realtek.
Perhaps unsurprisingly, I now have a few errors outputted by dmesg. I list these below. Note that I am using the motherboard GPU.
[ 4.750486] integrity: Problem loading X.509 certificate -22
[ 4.750514] integrity: Problem loading X.509 certificate -22
I think it is a UEFI firmware bug.
[ 5.320526] r8169 0000:0d:00.0: error -ENODEV: unknown chip XID 688, contact r8169 maintainers (see MAINTAINERS file)
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.
[ 5.409187] hub 12-0:1.0: config failed, hub doesn't have any ports! (err -19)
[ 8.487181] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <psp> failed -19
[ 8.487346] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <dm> failed -19
[ 8.487470] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <gfx_v10_0> failed -19
[ 8.487584] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <sdma_v5_2> failed -19
[ 8.487695] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <vcn_v3_0> failed -19
[ 8.487795] amdgpu 0000:78:00.0: amdgpu: Fatal error during GPU init
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.
[ 14.071653] ath12k_pci 0000:0c:00.0: firmware: failed to load ath12k/WCN7850/hw2.0/firmware-2.bin (-2)
[ 14.071655] ath12k_pci 0000:0c:00.0: firmware: failed to load ath12k/WCN7850/hw2.0/firmware-2.bin (-2)
[ 14.071658] ath12k_pci 0000:0c:00.0: firmware: failed to load ath12k/WCN7850/hw2.0/firmware-2.bin (-2)
[ 14.157807] mhi mhi0: Error loading firmware: -2
[ 14.157843] ath12k_pci 0000:0c:00.0: failed to set mhi state: POWER_ON(2)
[ 14.157856] ath12k_pci 0000:0c:00.0: failed to start mhi: -110
[ 14.157861] ath12k_pci 0000:0c:00.0: failed to power up :-110
[ 14.208360] ath12k_pci 0000:0c:00.0: failed to create soc core: -110
[ 14.208375] ath12k_pci 0000:0c:00.0: failed to init core: -110
[ 14.580814] ath12k_pci 0000:0c:00.0: probe with driver ath12k_pci failed with error -110
The ath12k wireless driver module requests a firmware which is is not
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)
Would it be constructive to built a new kernel from within this Debian version, and switching to that kernel ?
Your hardware seems recent, so a more recent kernel may help.
Reply to: