Recently I installed Qubes OS version 4.2. However, I have issues with my Wi Fi connectivity as my adapter is not being recognized. For my sys-net service I am using debian-12 with kernel 6.6.2-1.fc37.
root@sys-net:~# lspci | grep Network
00:06.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852
In other topics I read that this adapter is associated with kernel module rtw89_8852be, which in my case is linked to my adapter, however, it still appears as UNCLAIMED.
*-network:0 UNCLAIMED
description: Network controller
product: Realtek Semiconductor Co., Ltd.
vendor: Realtek Semiconductor Co., Ltd.
physical id: 6
bus info: pci@0000:00:06.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress cap_list
configuration: latency=0
resources: ioport:c200(size=256) memory:f2000000-f20fffff
00:06.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852
Subsystem: Lenovo Device 4853
Physical Slot: 6
Flags: fast devsel, IRQ 40
I/O ports at c200 [size=256]
Memory at f2000000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Kernel modules: rtw89_8852be
I can see an error in the kernel logs when the rtw89_8852be module is being loaded.
root@sys-net:~# dmesg | grep rtw
[ 2.317494] rtw89_8852be 0000:00:06.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2
[ 2.331979] rtw89_8852be 0000:00:06.0: loaded firmware rtw89/rtw8852b_fw.bin
[ 2.335329] rtw89_8852be 0000:00:06.0: Firmware version 0.27.32.1 (ef7920a3), cmd version 0, type 1
[ 2.335344] rtw89_8852be 0000:00:06.0: Firmware version 0.27.32.1 (ef7920a3), cmd version 0, type 3
[ 2.335362] rtw89_8852be 0000:00:06.0: MAC has already powered on
[ 2.356903] rtw89_8852be 0000:00:06.0: [ERR]pci config read 719
[ 2.356918] rtw89_8852be 0000:00:06.0: [ERR] pcie autok fail -22
[ 2.356927] rtw89_8852be 0000:00:06.0: failed to setup chip information
[ 2.359618] rtw89_8852be: probe of 0000:00:06.0 failed with error -22
I would be really thankful to hear any ideas how we can fix this issue.