[Please reply to 1103...@bugs.debian.org and not only me, really]

On 18/04/2025 at 00:14, anders wrote:

I copied the wrong link from the e-mail thread. The image I installed
on my second attempt was the one from
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/

I managed to get the wifi module to work by copying the ath12k folder
and the rtl_nic folder from the linux-firmware repository
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/

into /usr/lib/firmware and ran "sudo update-initramfs -u"

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.

I then tried to build a custom kernel from the Debian kernel source as 
described here,

Which version ?

https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html

The GPU related errors have disappeared (although this might be unrelated).

I then downloaded the Realtek driver for the 8125 ethernet controller,

https://www.realtek.com/Download/List?cate_id=584

I ran the autorun script. Then I signed the driver module r8125.ko with a MOK 
and loaded it with insmod. After doing this the ethernet connection works.

While the wifi module works, I still obtains some errors when unloading and 
reloading the module ath12k,

[ 2692.621781] ath12k_pci 0000:0c:00.0: firmware: failed to load 
ath12k/WCN7850/hw2.0/firmware-2.bin (-2)
[ 2692.621785] ath12k_pci 0000:0c:00.0: firmware: failed to load 
ath12k/WCN7850/hw2.0/firmware-2.bin (-2)
[ 2692.621787] ath12k_pci 0000:0c:00.0: firmware: failed to load 
ath12k/WCN7850/hw2.0/firmware-2.bin (-2)

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.

You gave the following instructions,

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

If it is of interest to you, I am willing to reinstall and check this on a 
fresh install, where I haven't made a mess. However, I am leaving on vacation 
and it will therefore be a week before I can find the time.

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

Reply via email to