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

seems good now, I’m not at home but I see wlan0 from ip a command

CoreELEC:~ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP8000> mtu 1500 qdisc mq qlen 1000
    link/ether 30:a6:12:1e:05:4a brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.186/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP8000> mtu 1500 qdisc mq qlen 1000
    link/ether fe:fd:fc:97:00:25 brd ff:ff:ff:ff:ff:ff
4: p2p0: <NO-CARRIER,BROADCAST,MULTICAST,UP8000> mtu 1500 qdisc mq qlen 1000
    link/ether fe:fd:fc:9f:00:25 brd ff:ff:ff:ff:ff:ff

Will test the link and the bandwidth later, thanks!

The box restarted in safe mode for some reason, but after a reboot it started normally again.

Wi-Fi connects, but I’ve been disconnected twice while streaming a movie. The bandwidth also seems low for Wi-Fi 6, even when testing right next to the box:

[  5] local 192.168.1.99 port 44276 connected to 192.168.1.150 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  29.5 MBytes   247 Mbits/sec    0   1.13 MBytes       
[  5]   1.00-2.00   sec  27.2 MBytes   229 Mbits/sec    0   1.45 MBytes       
[  5]   2.00-3.00   sec  29.0 MBytes   243 Mbits/sec    0   1.45 MBytes       
[  5]   3.00-4.00   sec  28.2 MBytes   237 Mbits/sec    0   1.78 MBytes       
[  5]   4.00-5.00   sec  27.8 MBytes   233 Mbits/sec    0   1.78 MBytes       
[  5]   5.00-6.00   sec  27.1 MBytes   228 Mbits/sec    0   1.78 MBytes       
[  5]   6.00-7.00   sec  29.8 MBytes   250 Mbits/sec    0   1.78 MBytes       
[  5]   7.00-8.00   sec  27.8 MBytes   233 Mbits/sec    0   1.78 MBytes       
[  5]   8.00-9.00   sec  28.4 MBytes   238 Mbits/sec    0   1.78 MBytes       
[  5]   9.00-10.00  sec  27.5 MBytes   231 Mbits/sec    0   1.78 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   282 MBytes   237 Mbits/sec    0            sender
[  5]   0.00-10.02  sec   280 MBytes   235 Mbits/sec                  receiver

iperf Done.

Performance isn’t better on the Android side either, so I suspect the integrated antennas might be poor.
Would it be better to connect using p2p0 or wlan0?

edit:
Something is wrong, can’t get a stable link:

[  5] local 192.168.1.99 port 56760 connected to 192.168.1.150 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  8.25 MBytes  69.2 Mbits/sec    1    393 KBytes       
[  5]   1.00-2.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  5]   2.00-3.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  5]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  5]   4.00-5.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  5]   5.00-6.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  5]   6.00-7.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  5]   7.00-8.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  5]   8.00-9.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  5]   9.00-10.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  8.25 MBytes  6.92 Mbits/sec    3            sender
[  5]   0.00-20.64  sec  5.01 MBytes  2.04 Mbits/sec                  receiver

iperf Done.

Terminal sharing still active if you want to test another binary.

Just tested EA6621QT_SEEKWAVE_R00005.bin as calibration file (renamed to be loaded). Now the connection is stable at ~240 Mbit/s on 5Ghz and ~70 Mbit/s on 2.4Ghz.
I also put in firmware directory the 3 files aml_wifi_rf.txt, aml_w2_rf_0640_0111.txt and aml_w2_rf_0640_0332.txt. But as there’s no mention in dmesg I think the only benefit comes from the other calibration file loaded.

EDIT:
I spoke too soon, I’m still getting disconnected.
Will need to wait for a better driver I beleive :confused:
Thank you very much for your valuable time.

Ask your manufacturer.

will do, thanks

Maybe you can try with firmware files from here CSC Armbian for RK322x TV box boards - Page 94 - Rockchip CPU Boxes - Armbian Community Forums

But if driver is correct than firmware files should be copied from Android.

Hi, also have an unsupported realtek usb wifi device:

[  341.497677@3]  usb 1-1: new high-speed USB device number 4 using xhci-hcd
[  341.646138@3]  usb 1-1: New USB device found, idVendor=0bda, idProduct=1a2b, bcdDevice= 0.00
[  341.646156@3]  usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  341.646163@3]  usb 1-1: Product: DISK
[  341.646169@3]  usb 1-1: Manufacturer: Realtek
[  341.653087@3]  usb-storage 1-1:1.0: USB Mass Storage device detected
[  341.655197@3]  scsi host0: usb-storage 1-1:1.0
[  342.861047@3]  scsi 0:0:0:0: CD-ROM            RTK      Driver Storage   2.03 PQ: 0 ANSI: 0 CCS
[  342.864461@3]  sr 0:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy
[  342.864486@3]  cdrom: Uniform CD-ROM driver Revision: 3.20
[  342.883016@3]  sr 0:0:0:0: Attached scsi CD-ROM sr0
[  342.884278@3]  sr 0:0:0:0: Attached scsi generic sg0 type 5
[  342.982718@3]  usb 1-1: USB disconnect, device number 4
[  343.769651@3]  usb 1-1: new high-speed USB device number 5 using xhci-hcd
[  343.918277@3]  usb 1-1: New USB device found, idVendor=0bda, idProduct=c832, bcdDevice= 0.00
[  343.918296@3]  usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  343.918303@3]  usb 1-1: Product: 802.11ax WLAN Adapter
[  343.918311@3]  usb 1-1: Manufacturer: Realtek
[  343.918317@3]  usb 1-1: SerialNumber: 00e04c000001
[  343.921673@3]  usb 1-1: Unsupported device

Seems to be RTL8852CU. Any plan to add a driver?

Thanks,

The files are unavailable now, I tried to compile the github repo but no chance for me.
There are these two calibration files that I would have liked to test.

EA6521QT_SEEKWAVE_R00005.bin
EA6621Q_SEEKWAVE_R00005.bin

For now I have tested EA6521QF_SEEKWAVE_R00005 and EA6621QT_SEEKWAVE_R00005.bin which seems better (I have fewer disconnections with this one).

github repo is for rockchip and doesn’t compile
my driver in the image is from other source

You need to be registered on forum to download files. Anyway, here they are: https://test.coreelec.org/vpeter/EA6521QF_armbian.zip

ok tested the 4 calibration files, no chance here. I monitored the bandwitch for each of them but I got disconnected randomly during the test. Link is robust on idle though.

EA6521QF_SEEKWAVE_R00005.bin - 80-120 Mbps / disconnected after 35 seconds
EA6521QT_SEEKWAVE_R00005.bin - 230-260 Mbps / disconnected after 4 seconds
EA6621Q_SEEKWAVE_R00005.bin - 90-150 Mbps / disconnected after 52 seconds
EA6621QT_SEEKWAVE_R00005.bin - 60-160 Mbps / disconnected after 12 seconds

Rockchip thread mentions a file named skw_bootcoms.ko which is not loaded here. Can it be needed?

EDIT: Tried to find files related android side:

130|ross:/ # find / -path /proc -prune -o -name '*skw*' -print
/data/misc/bluedroid/skwbdaddr.txt
/sys/kernel/tracing/events/skwifi
/sys/kernel/tracing/events/skwifi/skw_hw_adma_tx_done
/sys/kernel/tracing/events/skwifi/skw_msg_rx
/sys/kernel/tracing/events/skwifi/skw_rx_irq
/sys/kernel/tracing/events/skwifi/skw_rx_del_ba
/sys/kernel/tracing/events/skwifi/skw_rx_update_ba
/sys/kernel/tracing/events/skwifi/skw_rx_add_ba
/sys/kernel/tracing/events/skwifi/skw_rx_handler_seq
/sys/kernel/tracing/events/skwifi/skw_rx_force_release
/sys/kernel/tracing/events/skwifi/skw_rx_reorder_release
/sys/kernel/tracing/events/skwifi/skw_rx_reorder
/sys/kernel/tracing/events/skwifi/skw_rx_data
/sys/kernel/tracing/events/skwifi/skw_rx_expired_release
/sys/kernel/tracing/events/skwifi/skw_rx_reorder_timeout
/sys/kernel/tracing/events/skwifi/skw_rx_set_reorder_timer
/sys/kernel/tracing/events/skwifi/skw_tx_runing
/sys/kernel/tracing/events/skwifi/skw_tx_info
/sys/kernel/tracing/events/skwifi/skw_tx_xmit
/sys/kernel/tracing/events/skwifi/skw_tx_add_credit
/sys/kernel/debug/skwifi
/sys/kernel/debug/skwsdio
/sys/kernel/debug/tracing/events/skwifi
/sys/kernel/debug/tracing/events/skwifi/skw_hw_adma_tx_done
/sys/kernel/debug/tracing/events/skwifi/skw_msg_rx
/sys/kernel/debug/tracing/events/skwifi/skw_rx_irq
/sys/kernel/debug/tracing/events/skwifi/skw_rx_del_ba
/sys/kernel/debug/tracing/events/skwifi/skw_rx_update_ba
/sys/kernel/debug/tracing/events/skwifi/skw_rx_add_ba
/sys/kernel/debug/tracing/events/skwifi/skw_rx_handler_seq
/sys/kernel/debug/tracing/events/skwifi/skw_rx_force_release
/sys/kernel/debug/tracing/events/skwifi/skw_rx_reorder_release
/sys/kernel/debug/tracing/events/skwifi/skw_rx_reorder
/sys/kernel/debug/tracing/events/skwifi/skw_rx_data
/sys/kernel/debug/tracing/events/skwifi/skw_rx_expired_release
/sys/kernel/debug/tracing/events/skwifi/skw_rx_reorder_timeout
/sys/kernel/debug/tracing/events/skwifi/skw_rx_set_reorder_timer
/sys/kernel/debug/tracing/events/skwifi/skw_tx_runing
/sys/kernel/debug/tracing/events/skwifi/skw_tx_info
/sys/kernel/debug/tracing/events/skwifi/skw_tx_xmit
/sys/kernel/debug/tracing/events/skwifi/skw_tx_add_credit
/sys/devices/platform/soc/fe088000.sdio/mmc_host/mmc2/mmc2:8800/mmc2:8800:1/skw_ucom.3.auto
/sys/devices/platform/soc/fe088000.sdio/mmc_host/mmc2/mmc2:8800/mmc2:8800:1/skw_ucom.9.auto
/sys/devices/platform/soc/fe088000.sdio/mmc_host/mmc2/mmc2:8800/mmc2:8800:1/skw_ucom.8.auto
/sys/devices/platform/soc/fe088000.sdio/mmc_host/mmc2/mmc2:8800/mmc2:8800:1/skw_ucom.7.auto
/sys/devices/platform/soc/fe088000.sdio/mmc_host/mmc2/mmc2:8800/mmc2:8800:1/skw_ucom.10.auto
/sys/devices/platform/soc/fe088000.sdio/mmc_host/mmc2/mmc2:8800/mmc2:8800:1/skw_ucom.5.auto
/sys/devices/platform/soc/fe088000.sdio/mmc_host/mmc2/mmc2:8800/mmc2:8800:1/skw_ucom.4.auto
/sys/devices/virtual/workqueue/skw_txwq.1
/sys/bus/platform/devices/skw_ucom.3.auto
/sys/bus/platform/devices/skw_ucom.9.auto
/sys/bus/platform/devices/skw_ucom.8.auto
/sys/bus/platform/devices/skw_ucom.7.auto
/sys/bus/platform/devices/skw_ucom.10.auto
/sys/bus/platform/devices/skw_ucom.5.auto
/sys/bus/platform/devices/skw_ucom.4.auto
/sys/bus/platform/drivers/skw_ucom
/sys/bus/platform/drivers/skw_ucom/skw_ucom.3.auto
/sys/bus/platform/drivers/skw_ucom/skw_ucom.9.auto
/sys/bus/platform/drivers/skw_ucom/skw_ucom.8.auto
/sys/bus/platform/drivers/skw_ucom/skw_ucom.7.auto
/sys/bus/platform/drivers/skw_ucom/skw_ucom.10.auto
/sys/bus/platform/drivers/skw_ucom/skw_ucom.5.auto
/sys/bus/platform/drivers/skw_ucom/skw_ucom.4.auto
/sys/bus/sdio/drivers/skw_sdio
/sys/bus/workqueue/devices/skw_txwq.1
/sys/module/amlogic_mmc/holders/skw_sdio
/sys/module/skw_sdio
/sys/module/skw_sdio/parameters/skw_log_num
/sys/module/skw_sdio/parameters/skw_log_size
/sys/module/skw_sdio/holders/skw
/sys/module/skw_sdio/drivers/platform:skw_ucom
/sys/module/skw
/sys/module/amlogic_wireless/holders/skw_sdio
/sys/module/cfg80211/holders/skw
/vendor/etc/bluetooth/skwbt.conf
/vendor_dlkm/lib/modules/skw.ko
/vendor_dlkm/lib/modules/skw_sdio.ko

EDIT2: I tested iperf3 with Android, and the only thing it does better is reconnect very quickly after a disconnection. The speeds are poor (~80 Mbps) and unstable. That chip is just garbage.
Thanks for your help anyway. I will just giveup at this point.

1 Like

This is the usual way when try to use unsupported hardware…

Is there any chance such a driver exists for a kernel like CE-NO? RTL8852CU is very fast on my computer.

Probbaly. But someone needs to add it.
Faster will be to use different stick.

1 Like

I haven’t yet found a thread where the supported chipsets for CE-NO are mentioned. That could be useful to help us choose an efficient stick that works.

Found this wifi: rtw89: Add support for RTL8852CU [LWN.net]
Perhaps an update of an existing driver would suffice ?

There is no RTW89 in current CE used Linux.
I only know the RTW88 downstream.

Edit:
It’s maybe this: GitHub - morrownr/rtw89: Linux drivers for Realtek Wi-Fi 6/6E and Wi-Fi 7 adapters and cards

But it’s for kernel 6, we have 5.15…

from the readme :
Note that if you use this driver on kernels older than 5.15, the enhanced features of wifi 5 and wifi 6 are greatly crippled as the kernel does hot have the capability to support the new packet widths and speeds.

I understand that we might have a chance to get this driver working with 5.15? That would greatly improve Coreelec’s compatibility with recent wifi sticks.

btw, I tried to compile the .ko module from GitHub - morrownr/rtl8852cu-20240510: Linux Driver for USB WiFi Adapters that are based on the RTL8832CU and RTL8852CU Chipsets - v1.19.2.1 - 20240510 but I need a clearer toturial to do so. Coreelec Toolchain is beyond my expertise.

Just tried the recent nightly of NO (CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250825-Generic) and I got BT back but no wifi. I’m not too sure how to post logs without wifi. I’m on a S905X4 HK1 RBOX X4

Try this image: https://test.coreelec.org/vpeter/CoreELEC-Amlogic-no.aarch64-22.0-Piers_devel_vpeter_w1.tar

I’m not too sure how to use that since I’m upgrading from NG to NO.