bt and wifi boot up failed with tegra-firmware-rtl8822

[limeng-linux]

Hi Matt Madison

there is a commit in meta-tegra layer as below
commit bd32621
Author: Matt Madison matt@madison.systems
Date: Sun May 3 05:54:32 2026 -0700

devkit-wifi: pair tegra-specific BT firmware with driver

with this commit, there is error reported as below:
12.464108] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.65ab490.20240531-141726
[ 12.464112] rtk_btcoex: rtk_btcoex_init: version: 1.2
[ 12.464114] rtk_btcoex: create workqueue
[ 12.464204] rtk_btcoex: alloc buffers 1792, 2432 for ev and l2
[ 12.464313] usbcore: registered new interface driver rtk_btusb
[ 12.473512] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[ 12.473517] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[ 12.473563] bluetooth hci0: Direct firmware load for rtl_bt/rtl8822cu_fw.bin failed with error -2
[ 12.473567] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8822cu_fw not found

root@nvidia-orin-agx:/lib/firmware# dmesg | grep rtw88_8822ce
[ 12.806044] rtw88_8822ce 0001:01:00.0: enabling device (0400 -> 0403)
[ 12.809185] rtw88_8822ce 0001:01:00.0: Direct firmware load for rtw88/rtw8822c_fw.bin failed with error -2
[ 12.809191] rtw88_8822ce 0001:01:00.0: failed to request firmware
[ 12.809204] rtw88_8822ce 0001:01:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2
[ 12.809206] rtw88_8822ce 0001:01:00.0: failed to request firmware
[ 12.809210] rtw88_8822ce 0001:01:00.0: failed to load firmware
[ 12.809212] rtw88_8822ce 0001:01:00.0: failed to setup chip efuse info
[ 12.809214] rtw88_8822ce 0001:01:00.0: failed to setup chip information
[ 12.863480] rtw88_8822ce 0001:01:00.0: probe with driver rtw88_8822ce failed with error -22

although the BT driver is from nvidia-kernel-oot, but it wants to get the rtl_bt/rtl8822cu_fw.bin that from linux-firmware-rtl8822.
In addition, wifi driver also wants to get rtw88/rtw8822c_fw.bin that is from linux-firmware-rtl8822, too.

So, could you please tell me what issue cause you to add this commit?

thanks,
Limeng

[madisongh]

See #2185, specifically #2185 (comment)

[madisongh]

That dmesg output... is it from that sato build off the demo distro? If so, then I don't understand why the upstream rtw88-8822ce driver is being used instead of the rtl8822ce driver from the NVIDIA out-of-tree package. The default in wrynose should be to use the NVIDIA/Canonical 5.15 kernel and the drivers out of the NVIDIA_WIFI setting, rather than LINUX_WIFI.

[madisongh]

Just ran a test build myself -- demo-image-base, rather than -sato, but that shouldn't matter. I'm getting the correct driver.

Kernel config:

../5.15.185+git/linux-p3737_0000_p3701_0005-standard-build$ grep RTW .config
# CONFIG_RTW88 is not set
# CONFIG_RTW89 is not set

and in the image manifest:

.../1.0/deploy-demo-image-base-image-complete$ grep -E '(rtl88|rtw88|rtk-btusb)' *.manifest
demo-image-base-p3737-0000-p3701-0005.rootfs-20260602104005.manifest:nv-kernel-module-rtk-btusb-5.15.185-l4t-r36.5-1033.33+g9c6d5c8154da p3737_0000_p3701_0005 36.5.0
demo-image-base-p3737-0000-p3701-0005.rootfs-20260602104005.manifest:nv-kernel-module-rtl8822ce-5.15.185-l4t-r36.5-1033.33+g9c6d5c8154da p3737_0000_p3701_0005 36.5.0
demo-image-base-p3737-0000-p3701-0005.rootfs-20260602104005.manifest:nv-kernel-module-rtl8852ce-5.15.185-l4t-r36.5-1033.33+g9c6d5c8154da p3737_0000_p3701_0005 36.5.0
demo-image-base-p3737-0000-p3701-0005.rootfs-20260602104005.manifest:tegra-firmware-rtl8822 armv8a_tegra234 36.5.0+20260115194252
demo-image-base-p3737-0000-p3701-0005.rootfs.manifest:nv-kernel-module-rtk-btusb-5.15.185-l4t-r36.5-1033.33+g9c6d5c8154da p3737_0000_p3701_0005 36.5.0
demo-image-base-p3737-0000-p3701-0005.rootfs.manifest:nv-kernel-module-rtl8822ce-5.15.185-l4t-r36.5-1033.33+g9c6d5c8154da p3737_0000_p3701_0005 36.5.0
demo-image-base-p3737-0000-p3701-0005.rootfs.manifest:nv-kernel-module-rtl8852ce-5.15.185-l4t-r36.5-1033.33+g9c6d5c8154da p3737_0000_p3701_0005 36.5.0
demo-image-base-p3737-0000-p3701-0005.rootfs.manifest:tegra-firmware-rtl8822 armv8a_tegra234 36.5.0+20260115194252

The NVIDIA OOT drivers paired with the NVIDIA firmware.

[limeng-linux]

Sorry, I made a trick to the NVIDIA yocto project
The branch of my current project is wrynose. but I check the code of tegra-demo-distro layer, in master branch, there is code as below in tegrademo.inc
TEGRA_DEFAULT_KERNEL ?= "linux-yocto"
PREFERRED_PROVIDER_virtual/kernel:tegra = "${TEGRA_DEFAULT_KERNEL}"
In order to avoid to create a new nvidia yocto project with master again, in the my current project with wrynose branch, I set TEGRA_DEFAULT_KERNEL = "linux-yocto" in local.conf directly, and then build project with linux-yocto kernel. For this BT/WIF issue, I think it has same effect of creating new project with master branch.

I will create a new project with master branch, and check this issue again.

thanks,
Limeng

[limeng-linux]

I built a new nvidia yocto project, with master branch, there is error as below

root@p3737-0000-p3701-0005:~# dmesg | grep rtw
rtw88_8822ce 0001:01:00.0: Direct firmware load for rtw88/rtw8822c_fw.bin failed with error -2
rtw88_8822ce 0001:01:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2
rtw88_8822ce 0001:01:00.0: failed to request firmware
rtw88_8822ce 0001:01:00.0: enabling device (0000 -> 0003)
rtw88_8822ce 0001:01:00.0: failed to request firmware
rtw88_8822ce 0001:01:00.0: failed to load firmware
rtw88_8822ce 0001:01:00.0: failed to setup chip efuse info
rtw88_8822ce 0001:01:00.0: failed to setup chip information
rtw88_8822ce 0001:01:00.0: probe with driver rtw88_8822ce failed with error -22

thanks,
LImeng

[madisongh]

Hmm, OK, then it does look like the right solution is to include both the linux-firmware- and tegra-firmware- packages when using the upstream kernel, so the upstream wifi driver and the NVIDIA OOT Bluetooth driver can both get what they're looking for.