Sorry, copied wrong image - this one should be it 205.42 MB file on MEGA
Testing just a module is an option but then we add yet another variable to the problem.
1 Like
No problem, this image boots but it looks like it’s using the newer drivers from the CE repository
[ 8.890798@4]- btmtk_sdio_probe Mediatek Bluetooth driver Version=v0.0.1.00_2021011401
The bluetooth behavior is the same, the controller isn’t being detected.
This one is right. It’s the same behavior as v0.0.1.00_2021011401, the bluetooth controller isn’t being detected. I don’t know if it matters, with v0.0.0.53_2018072701_YOCTO the bluetooth service starts before the hardware initialization. Not sure if that sequence of events matters.
With v0.0.1.00_2021011401 and v0.0.0.47_2018012902, the bluetooth service doesn’t start until later when I toggle enable bluetooth. After enabling bluetooth, and rebooting, the service doesn’t start. Even though bluetooth is enabled in the settings, I have to disable/re-enable bluetooth in the GUI to start the bluetooth services.
[ 78.845850@0]- Bluetooth: Core ver 2.22
[ 78.850004@0]- NET: Registered protocol family 31
[ 78.850050@0]- Bluetooth: HCI device and connection manager initialized
[ 78.850747@0]- Bluetooth: HCI socket layer initialized
[ 78.851378@0]- Bluetooth: L2CAP socket layer initialized
[ 78.852063@0]- Bluetooth: SCO socket layer initialized
Another thought, the FireTVStick4k uses Android kernel 4.4. The device I’m currently using with CE (FireTV 2nd gen Cube) coincidently does use Android kernel 4.9, so I could pull the source for those mt7668 drivers instead.
But it seems like both the old 4k stick and v0.0.1.00_2021011401 drivers have the same issue with the BT controller. At least v0.0.0.47_2018012902 might be easier to compare to v0.0.0.53_2018072701_YOCTO to try to figure out what the controller issue is. I’ll see if I can find anything obvious.
I pulled the MT7668 drivers from the FireTV 4k Stick, 2nd gen Cube and Echo Studio.
The FireTV 4k Stick uses Kernel 4.4, and it includes an almost identical version of the CE v0.0.1.00_2021011401 driver. The Echo Studio also used kernel 4.4, with identical drivers to the 4k Stick.
The 2nd gen Cube used Android kernel 4.9. Although the 1st firmware from 2019 has the same driver version as the 4k Stick / Echo Studio, all the Mt7668 drivers after that are significantly different even though they share the same driver version numbers.
Would it be possible to either test the oldest driver for the Cube
2nd gen Cube MT7668 v0.0.1.00_2019111401
/mt7668/FireTVCube/FireTVCubeGen2-7.2.3.4-20210322/mt76x8/
or the newest version for the Cube
2nd gen Cube MT7668 v0.0.1.00_2022121401
/mt7668/FireTVCube/FireTVCubeGen2-7.6.4.6-20230601/mt76x8/
One of the Echo Studios firmware also included a very old and much more basic version of the driver v0.0.0.24_2017052601. Maybe the oldest version has a better chance of compatibility?
/mt7668/EchoStudio/Echo_Studio_src-6.5.3.7-20200324/
I’ve included all the source here
Hello,I update to nightly image (CoreELEC-Amlogic-ng-arm- 20.3-Nexus_nightly_20230816) and I have no bt and not wifi.
My device is Tencent Aurora 4 Pro. Here is the info: Unknown device “/sys/bus/sdio/devices/*”: No such device
I asked customer service and provided feedback to the manufacturer, confirming that the chip is RTL8852BE and the driver link is: GitHub - HRex39/rtl8852be: Realtek Linux WLAN Driver for RTL8852BE
see here BT:GitHub - HRex39/rtl8852be_bt: Realtek Linux Bluetooth Driver for RTL8852BE
rtl8852be Bluetooth wifi6 chip adaptation information Description:Realtek RTL8852BE Combo Module - TechInfoDepot
dmesg | paste: http://ix.io/4DEd
ce-debug:http://ix.io/4DEf
If you need more info, just ask for it.
I forgot to mention that the dtb file used by this device is:
sc2_s905x4_4g_1gbit.dtb (84.8 KB)
Thanks for your great work.
Feedback Tencent Aurora 4 pro, I used CoreELEC-Amlogic-ng.arm-20.3-Nexus_nightly_20230816-Generic.img.gz for the test and found that Bluetooth and wifi drivers were not added, the device uses RTL8852BE driver, please coreelec team to adapt and make wifi and Bluetooth work normally, I am using the dtb file is: sc2_s905x4_4g_1gbit.dtb.
rtl8852be Bluetooth wifi6 chip adaptation information Description:Realtek RTL8852BE Combo Module - TechInfoDepot
dmesg | paste: http://ix.io/4DEd
ce-debug:http://ix.io/4DEf
Thank you coreelec team
Realtek RTL8852BE Combo Module - TechInfoDepot (1).pdf (246.0 KB)
3 images to test, the third one looks very, very basic 
FireTVCubeGen2-7.2.3.4-20210322/mt76x8/sdio
FireTVCubeGen2-7.6.4.6-20230601/mt76x8/sdio
Echo_Studio_src-6.5.3.7-20200324
1 Like
blueyeti2023: Is this RTL8852BE USB or PCIe device? Because according to your previous info it is not SDIO.
Confirmed with the official customer service, it is the chip of RTL8852be, not the interface of usb and pcie.
I will check the information first and contact you later. I need the support of SDIO, right?
The RTL8852BE is a pcie port.
I don’t know if PCIe even works correctly on this kernel.
Sorry blueyeti2023, you are out of luck for now.
That’s all right. I’ll give you an answer tomorrow. Interface information comes from the network. I’ll talk to you tomorrow when the technical answers come back. If you can’t fix it, there’s no other way. Let’s see if we can sort this out tomorrow.
BT interface:UART
WIFI interface:pcie
I hope to get a Bluetooth driver image for me, thank you, I do not use wifi, I use wired, mainly use Bluetooth remote control, thank coreelec team.
No WiFi, it’s not working.
dmesg | paste
http://ix.io/4DXX
lsmod | grep eth
dwmac_dwc_qos_eth 20480 0
stmmac_platform 24576 2 dwmac_meson8b,dwmac_dwc_qos_eth
stmmac 286720 3 mac_meson8b,dwmac_dwc_qos_eth,stmmac_platform
lspci
01:00.0 Class 0280: 14e4:449d
00:00.0 Class 0604: 16c3:abcd
dmesg
tencent android 11 TV dmesg.txt (201.1 KB)
So I should be able to use it on the Coreelec21 version in the future.
Sorry but it doesn’t build with 4.9 kernel.
I’m done with this device. And please don’t ask for this wifi and bt again.
can this driver be added?
Find sources which supports this chip.
would it be something like this?
Try this and post dmesg.
dmesg | paste
I forgot to set SDIO interface - instead USB was used.
But with SDIO it doesn’t build.