Hi chewitt is there a way to detect full resolution for monitor with 1920x1280p. In RK3399 LE13 image, 1920x1080p was detected instead, while H618 LE13 could detect full resolution.
LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588
-
chewitt -
August 28, 2025 at 8:08 AM -
Thread is Unresolved
-
-
dale I'd guess some changes are needed in the kernel. I'm currently up to my neck in Amlogic things but will add it to Claude's worklist once I circle back on Rockchip topics.
-
Hi chewitt, two RK3399 boot issues I found and fixed on real boards while working on Lakka (which shares the LE Rockchip bootloader setup):
1. NanoPi M4 2GB The 2GB variant uses DDR3 (Samsung K4B4G1646E-BCMA) instead of the LPDDR3 on the 4GB model, so the nanopi-m4 image stops in TPL with "sdram_init: LPDDR3 - 933MHz failed!". Adding a nanopi-m4-2gb entry using the upstream nanopi-m4-2gb-rk3399_defconfig fixes it. Tested on LE master (U-Boot 2026.07). PR: https://github.com/LibreELEC/LibreELEC.tv/pull/11832
2. ROCK 4C+ (V1.41 with different LPDDR4) Same issue as https://forum.libreelec.tv/thread/29774/ : with the mainline TPL there is no UART output at all (confirmed with the current LE master rock-4c-plus image). It boots with the legacy chain (rkbin DDR blob + miniloader + trust, mainline U-Boot proper) using rk3399_ddr_666MHz_v1.30.bin, matching Radxa's statement that the RK3399-T needs the RAM at 666MHz. I added it as a separate "rock-4c-plus-ddr666" board so existing rock-4c-plus users are unaffected. The DDR blob is selected in rkbin/package.mk, next to the RK3328 frequency override. Tested on LE master: boots to Kodi on cold boot and reboot, 4GB RAM. Commit: https://github.com/ShigeakiAsai/L…65eb17339d1cc5e Is this approach acceptable for a PR, or would you prefer something else (e.g. mainline SPL with CONFIG_ROCKCHIP_EXTERNAL_TPL)? -
Apologies, I am sure this is not the correct place to ask,
but will the nightlies work on
-
Will the nightlies work on Ugoos SK3 powered SoC RK3588S2-DV and 8/128 GB on board?
I don't think so. I've not seen any mention of RK3588S2 support in the upstream kernel (only RK3588/RK3588S). The SoC differences are likely minor, but as there is no u-boot defconfig or board dts in the kernel for that box, LE will want to see those pieces in-place before offering support. NB: AFAIK there is no 8K support for RK3588 at the moment (in the to-do list, but not at the top) and DV will likely require some proper reverse engineering. I wouldn't rush out to buy one just yet.
-
I don't think so. I've not seen any mention of RK3588S2 support in the upstream kernel (only RK3588/RK3588S). The SoC differences are likely minor, but as there is no u-boot defconfig or board dts in the kernel for that box, LE will want to see those pieces in-place before offering support. NB: AFAIK there is no 8K support for RK3588 at the moment (in the to-do list, but not at the top) and DV will likely require some proper reverse engineering. I wouldn't rush out to buy one just yet.
Thank You so much for the reply, I will keep my eye on things as I always do.
Cheers again C
-