Radxa-cubie-a5e second Ethernet port not work after update  Armbian 25.11.0-trunk.259.

 

Quote

[   22.495764] sun55i-gmac200 4510000.ethernet: deferred probe timeout, ignoring dependency
[   22.495788] sun55i-gmac200 4510000.ethernet: probe with driver sun55i-gmac200 failed with error -110
 

 

Edited September 29, 20251 yr by Samixa

Providing logs with 

armbianmonitor -u

 helps with troubleshooting and significantly raises chances that issue gets addressed.

https://paste.armbian.com/nocivefiki
 

Hi,

I tested with the version 25.11.0-trunk.129 and the second network port worked with this.

 

https://paste.armbian.com/hasewoloti

same problem， and 25.11.0-trunk.129 img dont work

Edited October 7, 20251 yr by Nob0dy

On 10/7/2025 at 7:40 PM, Nob0dy said:

same problem， and 25.11.0-trunk.129 img dont work

 

Hello Nob0dy , 

If you use 25.11.0-trunk.129 after cold reboot you must make soft reboot then second Ethernet port work.

Ok, it works, but is there a solution to this problem?

4 hours ago, Nob0dy said:

Ok, it works, but is there a solution to this problem?

Maybe this -> https://github.com/torvalds/linux/commit/a15f095b590bcc1968fbf2ced8fe87fbd8d012e0

Thank you very much. You are my superman.

Hi, if you compile your kernel with "CONFIG_SUN55I_PCK600" set, you'll have the second ethernet port. But you'll loose the wifi adapter, just like in the trunk.129.

I've just tried https://dl.armbian.com/radxa-cubie-a5e/Trixie_edge_minimal
Ethernet-Port besides USB-C blinks if connected, but looks like no IP requested.
The other keeps dark if connected, pressing Button for long does nothing.
I don't understand where other images to find, A5E not in:
https://armbian.atomonetworks.com/dl/
What image ist know working, what is SSH Login
Thank You

1 hour ago, iwl said:

I don't understand where other images to find

 

There are no other images available at the moment. Regarding this, there is some initial but incomplete work in progress here:
https://github.com/armbian/build/pull/8831

We can’t merge it in its current state, as it still requires a significant amount of additional work and refinement. Unfortunately, this means there isn’t a quick solution right now, so we’ll need to wait until the implementation is completed and validated.