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 
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
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 
- PCIe controller enabled:
wifi_dummy: found enabled pcie@f5000000 - Firmware files loaded successfully:
fw_bcm43752a2_pcie_ag.bin(908KB) ✓config.txt(436 bytes) ✓clm_bcm43752a2_pcie_ag.blob✓
- Driver module loaded:
dhdpci(O+) - PCIe device detected: Broadcom BCM43752 (14E4:449D)
What Fails 
[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:
- Where can I obtain the correct NVRAM for BCM43752A2?
- Should it be named
nvram_bcm43752a2_pcie.txtor use existing name? - Is there a generic template available, or does it need to be board-specific?
- 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
- Tried latest Nightly? YES (kernel 5.15.196)
- Device used? Tencent Aurora 4 pro (S905X4)
- Working on ng/ne? NOT TESTED (only tested on no/New Order)
- 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.
not sure what exactly “no working WiFi” means, but mine dies after some heavy traffic on am9. i will try the next days to reproduce and then collect the logs
Can you find KINHANK/ORBIT G1 android14 firmware?Maybe it’s helpfull ,since it uses AP6275PR3 chip.
Although it maybe be kernel 5.4 with android 14,but the hope is still there. 
hello , i am using C5 with no working WiFi or BT;
i function well, for movie playback, with youtube-addon however there is often garbled image/artifacts. not sure why this happens; it is also not with every stream, but most often. it could be beccause a eMMC is attached, but not positive about it, because it happened also previously.
otherwise, veryplyeased with the image. thank you very much.
C5 does not have BT nor WiFi.
Device: X88 Pro X5M (Amlogic S905X5M / s7d, 4GB, 1Gbit)
CoreELEC: 22.0-Piers_beta1 (Amlogic-no, kernel 5.15.196)
dtb: s7d_s905x5m_4g_1gbit.dtb
Status: WiFi works fine (5GHz, connected). Bluetooth is not detected at all.
The combo chip is a Seekwave SV6160 over SDIO, handled by the EA6X21QX package:
[SKWSDIO INFO] check_chipid: Chip id:SV6160 used SDIO10
[SKWBOOT]:firmware: /lib/firmware/skw/SWT6621_DRAM_SDIO.bin /lib/firmware/skw/SWT6621_IRAM_SDIO.bin
I did some digging before posting, and I think this one is a missing driver rather than a
configuration issue — happy to be corrected.
No HCI device is ever registered:
# hciconfig -a -> (empty)
# ls /sys/class/bluetooth/ -> (empty)
bluetooth.ko is loaded and bluetoothd runs, but there is no transport driver, so BlueZ has
zero adapters.
skw_sdio exports the BT hooks, but nothing claims them:
# grep skw.*bt_service /proc/kallsyms
ffffffc0016c7554 t skw_start_bt_service [skw_sdio]
ffffffc0016c7668 t skw_stop_bt_service [skw_sdio]
Both are EXPORT_SYMBOL_GPL in skwutil/skw_boot.c, and skw_sdio_bind_BT_driver() is called
in skw_sdio_main.c, but there is no consumer module installed — only skw_sdio.ko (bus) and
skw.ko (WiFi) are shipped. dmesg confirms the WiFi side binds and the BT side never does:
[SKWSDIO INFO] skw_sdio_bind_WIFI_driver: wifi_pdata bus_type:0x0
[SKWLOG]:skw_bt_state_event_init enter
[SKWSDIO WARN] skw_sdio_cp_service_ops: service not support!
The chip’s BT service is therefore never started. The skw_ucom char devices do get created
(/dev/BTCMD, /dev/BTDATA, /dev/BTAUDIO, /dev/BTBOOT, class btcom) and open fine, but
writing an HCI Reset to /dev/BTCMD returns -EIO. ucom_ioctl() only closes the port, so
there is no userspace path to start the service either.
As far as I can tell the upstream source at github.com/daeiron/ea6x21qx_driver only contains
drivers/seekwaveplatform (SDIO bus) and drivers/skwifi (WiFi) — no Bluetooth component at
all. On Android the BT side is driven by a closed Seekwave vendor HAL that talks to
/dev/BTCMD / /dev/BTDATA directly, which would explain why BT works there and not here.
Two smaller things I noticed while looking, in case they are relevant:
-
The NV/calibration blob is requested but missing (it is not in the upstream
firmware/
directory either, so this may be expected):Direct firmware load for SEEKWAVE_NV_SWT6621S.bin failed with error -2 [SKWBOOT_ERR]: NV image request_firmware SEEKWAVE_NV_SWT6621S.bin failShipped instead are
EA6521QF_SEEKWAVE_R00005.binandEA6621QT_SEEKWAVE_R00005.bin. -
No s7d/s7/s6 dtb declares Seekwave, so the driver falls back to defaults:
[SKWBOOT_WARN]:no BT_antenna setting [SKWBOOT_WARN]:no DTS setting [SKWBOOT]:seekwave_boot_parse_dt, chipen:964 gpio_out:-1 gpio_in:-1 ret=-16The
aml_btnode is the genericamlogic, aml-bt(reset/btwakeup/hostwake GPIOs + rfkill),
with no transport attached. The wifi node also still carries
OF_COMPATIBLE_0=brcm,bcm4329-fmac, which looks like a leftover rather than the real chip.
So my reading is that BT on this chip needs a Seekwave BT driver that has never been published,
and there is nothing to enable on the CoreELEC side. Is that consistent with what you know? If
Seekwave BT support is not realistic, I am happy to just use a USB dongle — I mainly wanted the
SV6160 documented in this thread for the next person with an X88 Pro X5M.
Full logs:
dmesg: https://paste.coreelec.org/2/78g6
udevadm: https://paste.coreelec.org/2/BoZR
Search forum, I am sure there does no driver exist in public.
Buy supported device by CE next time.
Hi,
I have issue with the latest Coreelec beta,
This is my os info
CoreELEC:~ # cat /etc/os-release
NAME="CoreELEC"
VERSION="22.0-Piers_beta1"
ID="coreelec"
VERSION_ID="22.0"
PRETTY_NAME="CoreELEC (official): 22.0-Piers_beta1"
HOME_URL="https://coreelec.org"
BUG_REPORT_URL="https://github.com/CoreELEC/CoreELEC"
BUILD_ID="1eebf0e15a722755db4611904d4062039a2c3a18"
DISTRO_ARCH="Amlogic-no.aarch64"
DISTRO_BUILD="official"
DISTRO_PROJECT="Amlogic-ce"
DISTRO_DEVICE="Amlogic-no"
I have the odroid n2+ developer board, which I use it as a coreelc streaming device
This device has external usb to wifi adapter which doesn’t work
Bus 001 Device 006: ID 0bda:f179 Realtek Semiconductor Corp. RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter
CoreELEC:~ # find /usr/lib/modules -iname "*8188f*"
CoreELEC:~ #
I have attached the dmesg log as well for your reference
CoreELEC:~ # dmesg | grep -i usb
[ 1.222387] usbcore: registered new interface driver usbfs
[ 1.222413] usbcore: registered new interface driver hub
[ 1.222434] usbcore: registered new device driver usb
[ 1.329584] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.330110] usbcore: registered new interface driver uas
[ 1.330148] usbcore: registered new interface driver usb-storage
[ 1.330205] usbcore: registered new interface driver usbserial_generic
[ 1.330218] USB Serial support registered for generic
[ 1.330646] usbcore: registered new interface driver xpad
[ 1.330997] usbcore: registered new interface driver uvcvideo
[ 1.333372] usbcore: registered new interface driver usbhid
[ 1.333377] usbhid: USB HID core driver
[ 1.334085] usbcore: registered new interface driver snd-usb-audio
[ 2.156563] ### usb_main_init() start
[ 2.156727] call amlogic_new_c2_usb2_v2_driver_init() success
[ 2.156804] call amlogic_new_c2_usb3_v2_driver_init() success
[ 2.156855] call amlogic_new_usb3_v3_driver_init() success
[ 2.157027] amlogic-new-usb2-v2 ffe09000.usb2phy: USB2 phy probe:phy_mem:0xffe09000, iomap phy_base:0xffffffc00bdad000
[ 2.157123] call amlogic_new_usb2_v2_driver_init() success
[ 2.157176] amlogic-new-usb3-v2 ffe09080.usb3phy: This is normal phy
[ 2.158026] amlogic-new-usb3-v2 ffe09080.usb3phy: USB3 phy probe:phy_mem:0xffe09080, iomap phy_base:0xffffffc00bdd5080
[ 2.158203] amlogic-new-usb3-v2 ffe09080.usb3phy: Failed to get pcie_bgp
[ 2.164691] call amlogic_new_usb3_v2_driver_init() success
[ 2.164746] call amlogic_usb2_m31_drv_init() success
[ 2.164799] call amlogic_usb3_m31_drv_init() success
[ 2.164863] call aml_usb3_phy_drv_init() success
[ 2.165287] amlogic-new-usb2-v2 ffe09000.usb2phy: Not usb-phy-trim-reg
[ 2.171112] amlogic-new-usb2-v2 ffe09000.usb2phy: Not usb-phy-trim-reg
[ 2.180426] amlogic-new-usb2-v2 ffe09000.usb2phy: Not usb-phy-trim-reg
[ 2.184112] amlogic-new-usb2-v2 ffe09000.usb2phy: Not usb-phy-trim-reg
[ 2.190840] xhci-hcd-meson xhci-hcd-meson.0.auto: new USB bus registered, assigned bus number 1
[ 2.191039] xhci-hcd-meson xhci-hcd-meson.0.auto: new USB bus registered, assigned bus number 2
[ 2.191043] xhci-hcd-meson xhci-hcd-meson.0.auto: Host supports USB 3.0 SuperSpeed
[ 2.191102] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 2.191107] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.191109] usb usb1: Product: xHCI Host Controller
[ 2.191111] usb usb1: Manufacturer: Linux 5.15.196 xhci-hcd
[ 2.191114] usb usb1: SerialNumber: xhci-hcd-meson.0.auto
[ 2.191321] hub 1-0:1.0: USB hub found
[ 2.191475] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.191507] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[ 2.191510] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.191513] usb usb2: Product: xHCI Host Controller
[ 2.191515] usb usb2: Manufacturer: Linux 5.15.196 xhci-hcd
[ 2.191517] usb usb2: SerialNumber: xhci-hcd-meson.0.auto
[ 2.191650] hub 2-0:1.0: USB hub found
[ 2.192055] call amlogic_crg_drd_usb2_drv_init() success
[ 2.192108] call amlogic_crg_drd_usb3_drv_init() success
[ 2.192263] ### usb_main_init() end
[ 2.192320] dwc_otg: usb0: type: 2 speed: 0,
[ 2.448039] usb 1-1: new high-speed USB device number 2 using xhci-hcd-meson
[ 2.598390] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=93.04
[ 2.598400] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.598402] usb 1-1: Product: USB2.1 Hub
[ 2.598405] usb 1-1: Manufacturer: GenesysLogic
[ 2.639338] hub 1-1:1.0: USB hub found
[ 2.724167] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd-meson
[ 2.746803] usb 2-1: New USB device found, idVendor=05e3, idProduct=0620, bcdDevice=93.04
[ 2.746816] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.746821] usb 2-1: Product: USB3.1 Hub
[ 2.746824] usb 2-1: Manufacturer: GenesysLogic
[ 2.767370] hub 2-1:1.0: USB hub found
[ 3.016030] usb 1-1.2: new high-speed USB device number 3 using xhci-hcd-meson
[ 3.140338] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=f179, bcdDevice= 0.00
[ 3.140349] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.140352] usb 1-1.2: Product: 802.11n
[ 3.140355] usb 1-1.2: Manufacturer: Realtek
[ 3.140357] usb 1-1.2: SerialNumber: 00E0372F665D
[ 3.248043] usb 1-1.3: new full-speed USB device number 4 using xhci-hcd-meson
[ 3.373415] usb 1-1.3: New USB device found, idVendor=1915, idProduct=1025, bcdDevice= 1.00
[ 3.373429] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.373432] usb 1-1.3: Product: USB Composite Device
[ 3.373435] usb 1-1.3: Manufacturer: XING WEI 2.4G USB
[ 3.508165] XING WEI 2.4G USB USB Composite Device as /devices/platform/ff500000.dwc3/xhci-hcd-meson.0.auto/usb1/1-1/1-1.3/1-1.3:1.2/0003:1915:1025.0001/input/input2
[ 3.568414] hid-generic 0003:1915:1025.0001: input,hidraw0: USB HID v2.01 Keyboard [XING WEI 2.4G USB USB Composite Device] on usb-xhci-hcd-meson.0.auto-1.3/input2
[ 3.570014] XING WEI 2.4G USB USB Composite Device Mouse as /devices/platform/ff500000.dwc3/xhci-hcd-meson.0.auto/usb1/1-1/1-1.3/1-1.3:1.3/0003:1915:1025.0002/input/input3
[ 3.570200] XING WEI 2.4G USB USB Composite Device Consumer Control as /devices/platform/ff500000.dwc3/xhci-hcd-meson.0.auto/usb1/1-1/1-1.3/1-1.3:1.3/0003:1915:1025.0002/input/input4
[ 3.628690] XING WEI 2.4G USB USB Composite Device System Control as /devices/platform/ff500000.dwc3/xhci-hcd-meson.0.auto/usb1/1-1/1-1.3/1-1.3:1.3/0003:1915:1025.0002/input/input5
[ 3.629072] XING WEI 2.4G USB USB Composite Device as /devices/platform/ff500000.dwc3/xhci-hcd-meson.0.auto/usb1/1-1/1-1.3/1-1.3:1.3/0003:1915:1025.0002/input/input6
[ 3.629342] hid-generic 0003:1915:1025.0002: input,hidraw1: USB HID v2.01 Mouse [XING WEI 2.4G USB USB Composite Device] on usb-xhci-hcd-meson.0.auto-1.3/input3
[ 3.732061] usb 1-1.4: new full-speed USB device number 5 using xhci-hcd-meson
[ 3.891306] usb 1-1.4: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
[ 3.891339] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 7.548365] usbcore: registered new interface driver btusb
[ 513.423620] usb 1-1.2: USB disconnect, device number 3
[ 527.492029] usb 1-1.2: new high-speed USB device number 6 using xhci-hcd-meson
[ 527.616320] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=f179, bcdDevice= 0.00
[ 527.616327] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 527.616330] usb 1-1.2: Product: 802.11n
[ 527.616332] usb 1-1.2: Manufacturer: Realtek
[ 527.616335] usb 1-1.2: SerialNumber: 00E0372F665D
Could you please add the driver for RTL8188FTV?
Thanks
swtbt4l is available on GitHub.
also, Neardi Wi‑Fi Adaptation Guide | Neardi
Hi!
I bought two X88 Pro X5M players because I read that their stock cooling isn’t bad; both came with the S905A CPU. I’ve been using them for a few weeks with the current CoreELEC 22 NO betas. Bluetooth doesn’t work on them, but that’s no surprise, and I don’t miss it anyway. Wi-Fi doesn’t work either—I don’t even know what Wi-Fi chip is inside—so that’s not surprising either.
My main issue—and I know it’s not a Wi-Fi problem—is that no matter how I use the search function, I haven’t found any information pointing me in the right direction regarding why I can’t turn the boxes on with the IR remote after shutting them down from CoreELEC. Is this the standard situation for everyone, or just me? Whether I shut the players down completely from stock Android or Slimbox 14 Android, I can turn them on with the remote; however, if I shut them down or put them to sleep from CoreELEC, I can’t turn them back on. Tweaking config.ini and remotewakeup codes seems pointless because that would require BL30/301 injection, which isn’t available in NO version, right? I tried to reverse-engineer the shutdown/startup process from Android, but that’s beyond my capabilities.