Problem with driver for Realtek 8852be Wi-Fi pci card

[sapfeer0k]

I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong.

I have a fan-less media pc that has PCI WI-FI adapter rtl8852be.

I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized.

First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg:
[ 15.034783] rtw89_8852be 0000:03:00.0: enabling device (0000 -> 0003)
[ 15.061504] rtw89_8852be 0000:03:00.0: no suitable firmware found
[ 15.061543] rtw89_8852be 0000:03:00.0: failed to recognize firmware
[ 15.061557] rtw89_8852be 0000:03:00.0: failed to setup chip information
[ 15.075283] rtw89_8852be: probe of 0000:03:00.0 failed with error -2

Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info:
[ 16.501540] rtw89_8852be 0000:03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin
[ 16.503083] rtw89_8852be 0000:03:00.0: enabling device (0000 -> 0003)
[ 16.567443] rtw89_8852be 0000:03:00.0: xtal si not ready(R): offset=41
[ 16.567470] rtw89_8852be 0000:03:00.0: no suitable firmware found
[ 16.567494] rtw89_8852be 0000:03:00.0: failed to recognize firmware
[ 16.567509] rtw89_8852be 0000:03:00.0: failed to setup chip information
[ 16.572860] rtw89_8852be: probe of 0000:03:00.0 failed with error -2

I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones:

Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853
HP laptops have 8852be has PCI 10ec:b852:103c:88e3

Mine is: PCI 10ec:b852:10ec:b852

Any suggestions are welcomed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.23
ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3
Uname: Linux 6.5.0-1009-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Sun Dec 10 21:46:40 2023
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4
InstallationDate: Installed on 2023-09-15 (86 days ago)
InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
 Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: SDZ X133
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-1009-oem N/A
 linux-backports-modules-6.5.0-1009-oem N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.23
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/12/2023
dmi.bios.release: 1.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: PC_STICK_8G_D8R2
dmi.board.asset.tag: Default string
dmi.board.name: X133
dmi.board.vendor: SDZ
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: SDZ
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPC_STICK_8G_D8R2:bd05/12/2023:br1.20:svnSDZ:pnX133:pvrDefaultstring:rvnSDZ:rnX133:rvrDefaultstring:cvnSDZ:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Notebook
dmi.product.name: X133
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: SDZ

[sapfeer0k (sapfeer0k)]

I contacted device manufacturer, they provided me a driver in .tar.gz format, any chance to sign it to use with secure boot ?

I am going to attach this driver just in case someone would need it for their's Higole PC

[Juerg Haefliger (juergh)]

Sorry, no. We can't just pull in any random driver and sign it for secureboot. We'd have to report this to upstream but you need to verify first that the problem still exists with latest kernel and firmware.

Can you test the latest mainline kernels from:
https://kernel.ubuntu.com/mainline/

You might want to test v6.6 fist, if that fails v6.7-rc5.

They're unsigned so you need to temporarily disable secureboot in the BIOS.

[sapfeer0k (sapfeer0k)]

Thanks for the response,

Using kernel:
Linux slasher 6.6.0-060600-generic #202311151808 SMP PREEMPT_DYNAMIC Thu Nov 16 06:04:00 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I have the same error:
[ 16.995301] rtw89_8852be 0000:03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin
[ 17.084211] rtw89_8852be 0000:03:00.0: enabling device (0000 -> 0003)
[ 17.152030] rtw89_8852be 0000:03:00.0: xtal si not ready(R): offset=41
[ 17.152052] rtw89_8852be 0000:03:00.0: no suitable firmware found
[ 17.152076] rtw89_8852be 0000:03:00.0: failed to recognize firmware
[ 17.152090] rtw89_8852be 0000:03:00.0: failed to setup chip information
[ 17.158335] rtw89_8852be: probe of 0000:03:00.0 failed with error -2

Using kernel:
Linux slasher 6.7.0-060700rc5-generic #202312102332 SMP PREEMPT_DYNAMIC Sun Dec 10 23:41:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
[ 17.073979] rtw89_8852be 0000:03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin
[ 17.074321] rtw89_8852be 0000:03:00.0: enabling device (0000 -> 0003)
[ 17.133952] rtw89_8852be 0000:03:00.0: xtal si not ready(R): offset=41
[ 17.133980] rtw89_8852be 0000:03:00.0: no suitable firmware found
[ 17.134004] rtw89_8852be 0000:03:00.0: failed to recognize firmware
[ 17.134018] rtw89_8852be 0000:03:00.0: failed to setup chip information
[ 17.150375] rtw89_8852be: probe of 0000:03:00.0 failed with error -2

Please advise the next steps.

[sapfeer0k (sapfeer0k)]

Hi,

I contacted manufacturer and they have told me that most likely wifi module is broken. They sent me a replacement and it works out of the box now. So I think this bug can be closed.

[Po-Hsu Lin (cypressyew)]

Close this as per reporter's comment in #5.