I had similar issues in the past. Just recently my main R4S did not boot a fresh snapshot built, then I took the very same SD card, inserted it to my second R4S and it worked. I stored the exact same build on a different SD card and it also worked on the main router. So far I did not want to open it and connect an UART table to see what happens.
I do not believe this is related to the voltage issue some people are describing, since reboot works absolutely normal.
Thnx for the reply. I don't know if anybody got 24.10.0-rc2 running.
Without conformation maybe I'll just skip trying to test it further.
I can try tomorrow, pretty sure it works fine since I run a snapshot pretty close to rc1 and did not face any issues. Will confirm ~tomorrow.
Installed 24.10-rc2 on my backup R4S. It booted without any problems and was stable while testing (I shut it down again after approx. 1 hour).
Does you apply cpu overclock patch ? I noticed sometime eth port not come online with cpu overclock patch.
Hi, is there an option to overclock the cpu for a higher version than OpenWrt 22.
Save this patch to folder ".../target/linux/rockchip/patches-6.6"
From 04202df5cb497b1934c95211cf43784ef62245a4 Mon Sep 17 00:00:00 2001
From: Tianling Shen <cnsztl@immortalwrt.org>
Date: Mon, 18 Oct 2021 12:47:30 +0800
Subject: [PATCH] rockchip: rk3399: overclock to 2.0/1.5 GHz
It's stable enough to overclock cpu frequency to 2.0/1.5 GHz,
and for better performance.
Co-development-by: gzelvis <gzelvis@gmail.com>
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
---
arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
--- a/arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi
@@ -33,6 +33,10 @@
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1125000 1125000 1250000>;
};
+ opp06 {
+ opp-hz = /bits/ 64 <1512000000>;
+ opp-microvolt = <1250000>;
+ };
};
cluster1_opp: opp-table-1 {
@@ -72,6 +80,10 @@
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1200000 1200000 1250000>;
};
+ opp08 {
+ opp-hz = /bits/ 64 <2016000000>;
+ opp-microvolt = <1250000>;
+ };
};
gpu_opp_table: opp-table-2 {
Hi @leeandy
I got the idea, I tried making my own compilation a while ago but it didn't work out.
Just to share, 1,8/2,2 works successfully for me, I can share my parameters if needed.
Regards,
Nope, I don't apply any overclock patches or whatever. Just un-edited downloads from OpenWRT source.
23.x runs fine, but with 24.x or snapshots ETH1 refuses to come online. Tried again today, but no succes. Even with different SD-card, cable or powersupply, outcome stays the same.
Guess I'll stick with 23.x now, it runs fine. Will try again when 24.x comes out of beta.
Very strange, as said, recent snapshot is running perfect on my main router, and RC2 worked absolutely fine on my backup router. Did you build rc2 from source or simply download it?
I simply download from the firmware selector. With or without custom packages (stats, sqm, adblock), no working ETH1 for me...
-edit- even tried a different program to flash the SD card. Always the same outcome. I don't know what else to try. Thnx for asking 
Strange indeed. I would be surprised if that’s the issue, but worth a try: Do you have an Enterprise edition? I did my two tests on Enterprise edition, but I also have a „normal“ one (don’t ask, went crazy with those devices 
) and could give it another try tomorrow with this one.
I have the "normal" edition. Would be nice if you tried, but then.... If there indeed was a structural issue with the R4S, this topic would be flooded with posts. Guess I stand alone with this "No ETH1" issue. Maybe I got a hardware glitch, dunno.
Still happy my R4S works with 23.X (and all versions prior) as long as 23.X support is not dropped, I'll be fine.
I’ll try for you tomorrow. Might sound stupid, but try a different network cable … a version update should not matter, but another thing to rule out.
Already tried (bypassed switch to directly connect R4S to pc with different cable) still same outcome, all fine on 23.X but nothing with 24.rc or snapshot.
It's almost funny 
I'm stuped trying to figure out what's wrong, while I know I don't really need to upgrade (because 23.X is fine).
Tell me how you applied the patch that didn't work ? I applied with snapshot compile myself and it worked.
@leeandy I could tell you I download the 24.rc FriendlyARM NanoPi R4S 4GB LPDDR4 image from https://firmware-selector.openwrt.org/ doublecheck sha256sum, flash with balenaEtcher and poweroff the R4S trough SSH before swapping cards. Even trying both EXT4 and SQUASHFS images, but I don't see where I could have made a mistake there.
@wjwj I seem to have narrowed my issue down to a glitchy R4S model.
I got my R4S working by having to manually reconnect powercable when ETH1 won't come online. Sometimes I need to re-connect (powercyle) a few times before it works (but 24.rc works). Most times even a reboot command from luci, won't make it reboot perfectly (no ETH1).
Strange thing is with 23.X a reboot always goes perfect and both ETH0 and ETH1 come online. The issue only occurs with 24.X or snapshot.
I've decided to stick with 23.X becouse then my R4S works perfectly. I don't think it has anything to do with faulty programming from OpenWRT. I guess my single R4S is just a little glitchy on latest kernel, while other R4S models work fine.
Thnx both for your replies and questions. For now I'm I bit done with fiddling, troubleshooting and swapping SD-cards. I'll stick with 23.X and update when a official 23.X patch comes available
Try my snapshot build to see problem persist ?, it work ok with my R4S.
Thnx for keeping up the troubleshooting, but it is what it is....
Your shapshot has SHA256: 83688ef76d36a89df989fab26a375c8d7cf12baa2d497d9e2af02dc2c0f89e06
The problem persists. I had to powercycle it 3 times for first boot, after restoring config I had to powercycle it 2 times. Reboot command trough luci also won't make it reboot perfectly.
I have to keep hit-and-miss powercycling it untill ETH1 comes online.
Again, after swapping back my 23.X SD-card, it runs perfect when I plug in the USB-C or give it a reboot command trough luci.
(Yes, even when I flash the SD-card that runs perfectly on 23.X to 24.X the problem persists)
The problem only occurs when you restore the config from v23.x to snapshot ?