CE-22 NO: Looking for users with no working WiFi or BT

Realtek RTL8211F (RGMII interface)
Should just work I think. Post dmesg log - save to file and upload it if paste doen’t work - without network this is not possible :smiley:

1 Like

21.3 has wired network connection, but I dont know what is happening…

CoreELEC:~ # dmesg | paste
cURL error: (28), Operation timed out after 20001 milliseconds with 0 bytes received

21.3

Is it helpful?
Pass: T82cFVbspY

I can’t do that on CE22, because I do not have SSH.

thank you for your patience

device X96 max+ S905X3

CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260511-Generic

I’m experiencing the same problem with Wi-Fi and Bluetooth. Wi-Fi appears first, but when I try to connect, it disappears and after reboot then reappears

I recall having something similar. Wifi password was never accepted when using the “OK” button. However with keyboard connected and not clicking “OK” button but directly hitting “ENTER” on the keyboard the password was accepted.

CoreELEC:~ # udevadm info /sys/bus/pci/devices/* | paste
https://paste.coreelec.org/FreightVenetian
CoreELEC:~ # dmesg | paste
https://paste.coreelec.org/TrailRelocate

[S905X4] PCIe WiFi/BT not working - Broadcom BCM43752 (WiFi 6) initialization failure

Device: Tencent Aurora 4 pro (Amlogic S905X4)
Kernel: Linux 5.15.196
CoreELEC: Amlogic-no (New Order) nightly
WiFi Chip: Broadcom BCM43752A2 (PCIe, WiFi 6, PCI ID: 14E4:449D)


Problem

PCIe WiFi module detected but driver initialization fails:

[dhd] dhd_wifi_platform_load_pcie: dhd_bus_register failed err=-1

No wlan interface created.


Root Cause Identified

NVRAM file mismatch:

  • System uses: nvram_ap6275p.txt (for AP6275P chip)
  • Hardware requires: BCM43752A2 specific NVRAM
  • Expected device ID in NVRAM: devid=0x449d
  • Current NVRAM likely has wrong devid (e.g., 0x43ef for AP6275P)

This causes PCIe bus registration to fail with error -1 (EPERM).


What Works :white_check_mark:

  1. PCIe controller enabled: wifi_dummy: found enabled pcie@f5000000
  2. Firmware files loaded successfully:
  • fw_bcm43752a2_pcie_ag.bin (908KB) ✓
  • config.txt (436 bytes) ✓
  • clm_bcm43752a2_pcie_ag.blob
  1. Driver module loaded: dhdpci(O+)
  2. PCIe device detected: Broadcom BCM43752 (14E4:449D)

What Fails :cross_mark:

[11.506126] [dhd] dhd_conf_set_path_params : Final nv_path=/usr/lib/firmware/brcm/pcie/nvram_ap6275p.txt
[32.994561] [dhd] dhd_wifi_platform_load_pcie: dhd_bus_register failed err=-1
[38.878126] [dhd] dhd_wifi_platform_load_pcie: dhd_bus_register failed err=-1

Driver loads firmware but fails at PCIe bus registration due to NVRAM mismatch.


Diagnostic Links

udevadm info (PCIe devices):
https://paste.coreelec.org/FreightVenetian

Shows: Broadcom BCM43752 802.11ax (14E4:449D) detected on PCIe bus

dmesg (full boot log):
https://paste.coreelec.org/VulgarPainting

Shows: Firmware loading success, then dhd_bus_register failure


Request

Need correct NVRAM file for BCM43752A2 PCIe WiFi module.

Questions:

  1. Where can I obtain the correct NVRAM for BCM43752A2?
  2. Should it be named nvram_bcm43752a2_pcie.txt or use existing name?
  3. Is there a generic template available, or does it need to be board-specific?
  4. Any other configuration changes needed in device tree or config.txt?

Additional Info Available

Can provide upon request:

  • Complete current NVRAM file content
  • lspci output
  • Device tree excerpts
  • Tmate session for remote debugging

Official Questions Answered

  1. Tried latest Nightly? YES (kernel 5.15.196)
  2. Device used? Tencent Aurora 4 pro (S905X4)
  3. Working on ng/ne? NOT TESTED (only tested on no/New Order)
  4. Module type? PCIe WiFi SoC (BCM43752A2)

Thank you!

Didn’t you wrote twice or three times you got it all working?

I tested both Wi-Fi and Bluetooth, but neither works properly. They were fine with Bluetooth just a while ago. Please check the issue. If it can’t be fixed, I’ll just keep using wired connections instead.

[   32.738826] [dhd] CONSOLE: 
[   32.738828] [dhd] CONSOLE: 000000.001 
[   32.738830] [dhd] CONSOLE: RTE (PCIE-MSGBUF) 18.35.387.23.108 on BCM43752 r2 @ 37.4/160.0/400.0MHz
[   32.738832] [dhd] CONSOLE: 000000.001 nvram_init: called again without calling nvram_exit()
[   32.738834] [dhd] CONSOLE: 000000.002 allocating a max of 511 rxcplid buffers
[   32.738837] [dhd] CONSOLE: 000000.007 Default PCIe refclk pad Hysteresis : 0mV
[   32.738839] [dhd] CONSOLE: 000000.017 New PCIe refclk pad Hysteresis: 45mV
[   32.738841] [dhd] CONSOLE: 000000.017 pciemsgbuf0: Broadcom PCIE MSGBUF driver
[   32.738843] [dhd] CONSOLE: 000000.018 nvram_init: called again without calling nvram_exit()
[   32.738846] [dhd] CONSOLE: 000000.020 Reclaim section 0: returned 78264 bytes (pre-reclaim: 322116)
[   32.738848] [dhd] CONSOLE: 000000.023 wl0: phy_radio_attach: RF Band Cap: 2G:1 5G:1
[   32.738851] [dhd] CONSOLE: 000000.071 wl0: Broadcom BCM43752 802.11 Wireless Controller 18.35.387.23.108 (g34a0fd51)
[   32.738853] [dhd] CONSOLE: 000000.071 TCAM: 512 used: 302 exceed:0
[   32.738856] [dhd] CONSOLE: 000000.071 Reclaim section 1: returned 217484 bytes (pre-reclaim: 226736)
[   32.738858] [dhd] CONSOLE: 000000.076 SPLITRX_MODE: 4 tcmsegsize 0 d11rxoffset 0
[   32.738861] [dhd] CONSOLE: 000000.076 ThreadX v5.6 initialized
[   32.738863] [dhd] 
[   32.738863]  ------- DUMPING VERSION INFORMATION ------- 
[   32.738866] [dhd] DHD: Dongle Host Driver, version 101.10.591.84.38 (20241018-2)(2bc03d3)
[   32.738866] /home/docker/build_dir/CoreELEC-22/build.CoreELEC-Amlogic-no.aarch64-22/build/ap6xxx-aml-b2541e247f88e84873041cad9d2605aa4202d352/bcmdhd.101.10.591.x compiled on May 11 2026 at 02:05:36
[   32.738866] 
[   32.738871] [dhd] Firmware: 
[   32.738874] [dhd] 
[   32.738874]  ------- DUMPING CONFIGURATION INFORMATION ------ 
[   32.738876] [dhd] memdump mode: 3
[   32.738879] [dhd] 
[   32.738879]  ------- DUMPING PROTOCOL INFORMATION ------- 
[   32.738882] [dhd] ICPrevs: Dev 7, Host 7, active 7
[   32.738886] [dhd] d2h_intr_method -> PCIE_INTX d2h_intr_control -> D2H_INTMASK
[   32.738889] [dhd] max Host TS bufs to post: 8, posted 0
[   32.738892] [dhd] max INFO bufs to post: 32, posted 31
[   32.738895] [dhd] max event bufs to post: 32, posted 32
[   32.738898] [dhd] max ioctlresp bufs to post: 8, posted 8
[   32.738901] [dhd] max RX bufs to post: 511, posted 448
[   32.738904] [dhd] h2d_max_txpost: 512, prot->h2d_max_txpost: 512
[   32.738907] [dhd] h2d_max_txpost: 2048, prot->h2d_max_txpost: 2048
[   32.738911] [dhd] current_time=   32.738911
[   32.738914] [dhd] ioctl_fillup_time=   27.617270 ioctl_ack_time=   27.616927 ioctl_cmplt_time=   27.616934
[   32.738920] [dhd] 
[   32.738920]  ------- DUMPING INTR Status and Masks ------- 
[   32.738927] [dhd] intstatus=0x1 intmask=0xff d2h_db0=0x12345678
[   32.738934] [dhd] d2h_mb_data=0x0 def_intmask=0xffff 
[   32.738937] [dhd]

After confirmation, the incompatibility issue is caused by upgrading the kernel to 5.15.196 which breaks the corresponding drivers. Looking forward to further optimization and updates in future versions.

With a UGREEN USB-LAN adapter (+3 USB ports) working the LAN on this box.