If you have a gigabit connection attached to LAN and it shows up as gigabit: that sounds like everything is working as expected?
That's correct. But I was replying to someone who said they had issues with the speed being 100mbit or something on the RC releases.
That was me, i was complaining about seeing my wan uplink establish at 100Mb/s and not 2.5Gb/s, but after changing Ethernet cable that issue went away, so i deleted my message 
I’m now seeing the wan interface go down regularly, which is very annoying, but i don’t have any reason to think it’s because of the E52C itself, i will try yet another cable to connect it to the GPON to see if that fixes it.
That sounds like an annoying issue. My wan seems stable.
Do you see anything in the logs?
Disabling EEE (Energy Efficient Ethernet) with ethtool --set-eee wan eee off seems to have solved the issue.
Need to see how to make this stick.
I have this in the logs:
Thu Mar 5 10:22:49 2026 kern.warn kernel: [ 777.222914] Ethtool ioctl interface doesn't support passing EEE linkmodes beyond bit 32
Thu Mar 5 10:42:47 2026 kern.warn kernel: [ 1975.065203] Ethtool ioctl interface doesn't support passing EEE linkmodes beyond bit 32
Thu Mar 5 10:42:57 2026 kern.warn kernel: [ 1984.390133] Ethtool ioctl interface doesn't support passing EEE linkmodes beyond bit 32
but i saw that only now and i’m not too sure how to interpret the logs as i don’t have the timestamp for installing ethtool and the turning EEE off (IIRC ethtool --set-eee wan eee off was run at 10:42 but not sure).
That seems strange. Who is your isp?
Community Fibre. It's likely more due to the ONT that the ISP though.
@abhi can you provide the steps to enable all four cores with OpenWRT? I ran stress-ng on all four A76 cores for multiple hours without issues with Armbian (which enables them by default, which is IMHO a bad idea) so I’m confident that all of them work fine.
I know that the code parts in uBoot which disable these cores have to be removed, but I have no idea where uBoot is integrated into the image. If that is e.g. a separate partition, if one could simply replace that partition without having to create a whole new openwrt image
It seems the device reboots when I restart the network service. Can someone verify this?
It doesn't happen every time, but it seems to occur with a high probability.
service network restart
Edit: It seems like a power issue. Is the device unable to receive the C-to-C PDO 5V 3A? After switching to an A-to-C QC3.0 charger, the rebooting problem has disappeared.
I think it really needs a good power supply and thick wires. As I attached it to my lab PSU with I think a 20cm long 0.34mm² cable, voltage dropped alot when the cores were utilized. Bought the “old” RPI 5.1V / 3A power supply which uses 18 AWG and never looked back
I’m using an Anker 511 30 Watt charger and had absolutely no problems with it so far.
Almost all of the chargers I own are genuine Samsung products. 25W, 45W, 50W duo, and 65W trio. Among these, only the A port of the 65W charger works stably with the E52C. I suspect that unlike third-party chargers, the Type-C port supports fewer protocols—USB PD 3.0+PPS and QC4.0—so issues arise if the device, like the E52C, does not support PD negotiation. In fact, these chargers work without any problems with the NanoPi R6S.
Samsung chargers really seem to be designed only for "charging." They don't seem suitable for use as power adapters.
I ordered a 5V 3A dumb c-type adapter. I think it will be similar to yours.
I’ve been using one of these for over a month with no issues. They are marketed for Raspberry Pi5 but work just fine on an E52C.
Samsung chargers only support very basic protocols. I think chargers that support multiple protocols wouldn't have this problem.
anker 67w
ugreen 65w
beseus 65w
samsung 65w
I wonder if anyone has tried connecting an Apple charger. As far as I know, Apple chargers only support USB PD without PPS, so their compatibility is lower than Samsung's.
If that works, I don't understand why there is a problem with the Samsung charger.
According to the schematic provided by Radxa, it uses a RK806 PMIC without further quirks. Don't see a component there which would understand anything different than raw voltage. But check your cables. As said, initially I was using a lab supply and still it wasn't able to start up properly because of too thin wires
My opinion is just a guess. I have already tried 3A 5A TB3 USB4 cables.
Edit: Hmm, it is true that the 45W charger has an issue where the device reboots, but it seems the problem with the other chargers was with the Ethernet driver, not the power supply.
In the case of the kmod-r8125-rss driver, the port resets if I open many connections using iperf3. I thought this was a power issue. Maybe when I tested the other chargers, the rss driver was installed on either e52c or r6s.
[ 139.329166] r8125 0003:31:00.0 wan: NETDEV WATCHDOG: CPU: 5: transmit queue 1 timed out 6190 ms
[ 139.329943] r8125 0003:31:00.0 wan: Transmit timeout reset Device!
[ 139.379125] r8125 0003:31:00.0 wan: Device reseting!
[ 143.370714] r8125: wan: Link is Up - 2.5Gbps/Full
Also, the r6s's 1Gbps port resets during the UDP burst test regardless of the driver. It appears these issues acted in combination while I was conducting various tests.
- samsung 45W charger actually has a rebooting issue. (ep-t4510)
- kmod-r8125-rss driver resets if many TCP connections are opened. (iperf3 -c 192.168.50.1 -P 30 -t 30)
- nanopi r6s 1gbps port resets during the UDP burst test. (iperf3 -c 192.168.50.1 -u -b 500m -P 5). 2.5gbps port is fine with "-b 1000M -P 5".
I have one with their old fork of openwrt. Would you mind sharing the instructions to wipeout with a fresh install?
Follow the instructions at
Most difficult thing for me was the USB-A A cable. I used an USB-C to A cable instead with a notebook which had an USB-C connector.
You have to use gunzip as described to unpack the Openwrt image you downloaded
Got one today.
Directly flash the EMMC with custom built openwrt firmware image using instruction on Radxa website here https://docs.radxa.com/en/e/e52c/other-os/openwrt/install-os
Manually migrate config files from old nanopi R2S and up and running in 2 hours.
Runs much cooler than the R2S.