E900V22C with S905X2

Help & Support Installation & Booting
1

Device Information:

  • Device Model: E900V22C

  • SoC: Amlogic S905X2

  • RAM: 2GB DDR4

  • Ethernet: 100M Ethernet Port

  • Wireless/Bluetooth Adapter: UWE5621DS

  • CoreELEC Version: CoreELEC 22.0-Piers_alpha2

  • DTB File: G12A_s905x2_2g.dtb

Issue 1: Ethernet Port Not Working (IP Acquisition Failure)

When connecting the device via the wired Ethernet port on CoreELEC 22.0-Piers_alpha2, the Ethernet interface keeps restarting repeatedly. The symptom is that the Ethernet port disappears intermittently, and the system gets stuck in a loop of “Obtaining IP address” forever. Eventually, it fails to establish a network connection entirely.

Notably, the Ethernet function worked perfectly on the previous version CoreELEC 22.0-Piers_alpha1. The issue only emerged after upgrading to alpha2.

Issue 2: Missing Driver for UWE5621DS Wireless/Bluetooth Adapter

The device is equipped with the UWE5621DS wireless + Bluetooth combo adapter, but CoreELEC 22.0-Piers_alpha2 does not include the corresponding driver. As a result, neither Wi-Fi nor Bluetooth can be used.

According to my research, the Linux 5.15 kernel natively supports the UWE5621DS adapter, and the driver name is uwe5631-aml. Could you please integrate this driver into the CoreELEC 22.0-Piers build? The E900V22C is still a widely used device among the community, and adding this driver would greatly improve the user experience for many users.

Looking forward to your feedback and fixes. Thank you!

2

Hello @Freestyle. :waving_hand: Did you try Nightly build maybe?
Because from Search on “UWE5621DS” I see a CE-NO discussion and work about UWE5621DS, and uwe5631-aml driver you mention, just from 2025-11-24. Very fresh. :crossed_fingers::slightly_smiling_face:

3

Hi nocturnal,

I tested the latest Nightly build yesterday and observed some updates on the issues:

  1. Ethernet Progress & Remaining Problem: The Ethernet interface no longer restarts frequently (which is an improvement from alpha2), but it automatically obtains an APIPA IP address in the range 169.254.x.x. As a result, the device still cannot access the internet (no valid network connectivity).

  2. Wireless/Bluetooth Status: Regarding the UWE5621DS adapter, since Nightly still doesn’t load the uwe5631-aml driver automatically, Wi-Fi and Bluetooth remain unavailable. Unfortunately, due to the Ethernet connectivity issue (no valid IP), I can’t establish an SSH connection to manually load the driver for testing—this limits my ability to verify if the driver would work properly once loaded.

Looking forward to your further investigation and fixes. Thanks again for your efforts!

4

What happens if you assign a static ip in CE setup from a range held in your router?

5

Hello bazzle,

I also tried configuring a static IP address, saved the settings, but still couldn’t connect to the network. The issue persists even after rebooting the device.

6

Wifi will work when you add this to your used DTB:

You will also need to use latest CE-NO nightly.

LAN? No idea as there are less than no G12A with ethernet devices used with CE.
When you get Wifi working you can put the device online by tmate so we can take a look:

1 Like
7

I’ll give it a try once I get home later. Thank you very much!

1 Like
8

I spent quite a long time testing after getting home. I used the latest Nightly build, added the code to the DTB file, and rebooted the device—but Wi-Fi still didn’t activate. Could it be that I made a mistake in the operation?

9

Not sure, I will ask the foggy glass ball.

10

Hi Portisch,

I’m sorry to bother you, but I’d like to follow up on the uwe5631-aml driver issue. I’ve indeed spent a great deal of time testing it, but haven’t had any success getting it to work. So I suspect that the uwe5631-aml driver may not be integrated into the system—what do you think about this?

11

You have better chances to get answer and help from someone if you provide logs. No matter how much time you do something, other people cannot guess what is going on within your device without logs. :wink:

12

Yes, you’re absolutely right. Through my testing, I’ve confirmed two things:

  1. When my TV box runs CoreELEC 22.0-Piers_alpha2, the 100M Ethernet port cannot connect to the network.

  2. CoreELEC 22.0 does not include the uwe5631-aml driver.

Additionally, my device currently cannot connect to the network, so it’s not easy for me to export the logs.:sweat_smile:

13

Temporarily use a USB WiFi or Ethernet adapter to get logs. UART is also a harder option.

You could also add a line to your /storage/.config/autostart.sh to copy the logs somewhere on the CE USB Stick/SDcard, so that you can later plug it into your computer to grab them.

14

I apologize for the slight delay due to purchasing a USB-to-Gigabit Ethernet adapter. I can now connect my TV box to the network via this adapter.

I have uploaded the logs—could you please check if any additional information is needed?

https://paste.coreelec.org/OklahomaFrida

Additionally, I’m rephrasing my issues below for clarity:

I tested the latest Nightly build yesterday and observed some updates on the issues:

  1. Ethernet Progress & Remaining Problem: The Ethernet interface no longer restarts frequently (which is an improvement from alpha2), but it automatically obtains an APIPA IP address in the range 169.254.x.x. As a result, the device still cannot access the internet (no valid network connectivity).

  2. Wireless/Bluetooth Status: Regarding the UWE5621DS adapter, since the Nightly build still doesn’t load the uwe5631-aml driver automatically, Wi-Fi and Bluetooth remain unavailable. Unfortunately, due to the Ethernet connectivity issue (no valid IP) earlier, I couldn’t establish an SSH connection to manually load the driver for testing—this limited my ability to verify if the driver would work properly once loaded.

Thank you.

15

Then I modified the DTB file and copied the following code into it:

&sd_emmc_a {
	brcmf: wifi@1 {
		compatible = "sprd,unisoc-wifi";
	};
};

After powering on the device, I connected to it via SSH and entered the following commands:

modprobe uwe5621_bsp_sdio
modprobe sprdwl_ng
modprobe sprdbt_tty

I found that I was able to connect to 2.4G Wi-Fi, but could not connect to 5G Wi-Fi at all. Additionally, Bluetooth failed to turn on.

Below are the new logs.https://paste.coreelec.org/EnemaDaybreak

16

Easiest and fastest way is to enable tmate:

Connect also the 100mbit LAN by cable for testing purpose.

17

I have opened tmate and filled in my Connection name as Freestyle.
Thank you.

18

Wifi is working now. You missed reg = <1> in the wifi@1 node.
Let’s see about Eth when I get more time.

mf
fdtput /flash/dtb.img -c /sd2@ffe05000/wifi@1
fdtput /flash/dtb.img /sd2@ffe05000/wifi@1 -t s compatible 'sprd,unisoc-wifi'
fdtput /flash/dtb.img /sd2@ffe05000/wifi@1 -t i reg 1
sync
reboot
19

Also internal 100MBit ethernet is working now.
The fix is included with next nighlty 20251218.

But after update you will need to modify your dtb.img to enable the Wifi driver again.

tmate session can be stopped now, thx!

1 Like
20

Thank you very much!