Benik3

Ah, that's the worse issue, that it doesn't boot at all. I don't know what cause this, on nightly builds it was working again... I stay with the 24.8 version...

The problem is very weird. I tested like 5 RockPi and some worked without issue, some not. They were same HW version and from one batch. Maybe it's some time race... @dgatwood 100Mbit ethernet is still working fine, so you can use it to bring it alive. You can use custom device tree overlay to "force" the right driver to load. See my previous posts.

Another weird thing (on 24.8.3). Eth0 looks working fine (no error in dmesg). When I connect it to router, router shows it in DHCP server leases, but the RockPi doesn't "accept" the IP address (in ip a is no address leased). Eth1 is working fine. EDIT: It's probably some our HW problem. Anyway I tried to build u-boot 2025.04 from mainline, but the problem with ETH0 driver load still persist. so it's not the solution.

I installed and updated the Armbian 25.2.1 Bookworm Minimal / IOT and I found that sometime the board doesn't reboot and hangs. But it looks like the system shutdown successfully: [ OK ] Finished systemd-reboot.service - System Reboot. [ OK ] Reached target reboot.target - System Reboot. [ 1889.239148] watchdog: watchdog0: watchdog did not stop! [ 1889.266560] systemd-shutdown[1]: Using hardware watchdog 'Synopsys DesignWare Watchdog', version 0, device /dev/watchdo0 [ 1889.267571] systemd-shutdown[1]: Watchdog running with a hardware timeout of 10min. [ 1889.341351] systemd-shutdown[1]: Syncing filesystems and block devices. [ 1889.474788] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 1889.484569] systemd-journald[360]: Received SIGTERM from PID 1 (systemd-shutdow). [ 1889.492592] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 1889.502260] systemd-shutdown[1]: Unmounting file systems. [ 1889.505128] (sd-remount)[1430]: Remounting '/' read-only with options 'errors=remount-ro,commit=120'. [ 1889.573116] EXT4-fs (mmcblk0p1): re-mounted 3f584b9a-965c-48cd-8e7c-7bd5320b177a ro. Quota mode: none. [ 1889.584110] systemd-shutdown[1]: All filesystems unmounted. [ 1889.584627] systemd-shutdown[1]: Deactivating swaps. [ 1889.585255] systemd-shutdown[1]: All swaps deactivated. [ 1889.585731] systemd-shutdown[1]: Detaching loop devices. [ 1889.588197] systemd-shutdown[1]: All loop devices detached. [ 1889.588707] systemd-shutdown[1]: Stopping MD devices. [ 1889.589507] systemd-shutdown[1]: All MD devices stopped. [ 1889.589991] systemd-shutdown[1]: Detaching DM devices. [ 1889.590669] systemd-shutdown[1]: All DM devices detached. [ 1889.591153] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached. [ 1889.592001] watchdog: watchdog0: watchdog did not stop! [ 1889.606252] systemd-shutdown[1]: Syncing filesystems and block devices. [ 1889.607708] systemd-shutdown[1]: Rebooting with argument 'now'. [ 1889.689457] kvm: exiting hardware virtualization [ 1889.690011] reboot: Restarting system with command 'now' INFO: PSCI Power Domain Map: INFO: Domain Node : Level 2, parent_node -1, State ON (0x0) INFO: Domain Node : Level 1, parent_node 0, State ON (0x0) INFO: Domain Node : Level 0, parent_node 0, State ON (0x0) INFO: Domain Node : Level 0, parent_node 0, State ON (0x0) INFO: CPU Node : MPID 0x0, parent_node 1, State ON (0x0) INFO: CPU Node : MPID 0x1, parent_node 1, State ON (0x0) INFO: CPU Node : MPID 0x2, parent_node 1, State ON (0x0) INFO: CPU Node : MPID 0x3, parent_node 1, State ON (0x0) DDR version 1.16 20190528 ID:0x805 N In SRX DDR3 333MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB

BTW I found also another weird behavior. I have more of the RockPi E boards. All are 1.21 version and bought in one batch. I have SD card with the trunk 316 Pluck Armbian, and on one board the ethernet doesn't work, but on another 2 yes... Also even more weird thing, on the working board when I install 24.8.3 and the do full-upgrade, it also doesn't work... So maybe it's also some time race of the reset?

Thanks for the reply. I noticed, that in u-boot the ethernet is not detected. So the solution to this problem should be updating the u-boot.

Hi and thanks for reply. I tried to dig more into the ethernet problem. I found that there was already similar problem: https://forum.radxa.com/t/rock-pi-e-board-version-1-21-ethhernet-not-working-in-armbian/15061/4 There are 2 boards of RockPi-E 1.2 (using RTL8211E) and 1.21 (using RTL8211F). So I tested the provided dts and it really helped. After sme trial-tests I found, that the real thing which helps is the compatible = "ethernet-phy-id001c.c916"; So using dts: /dts-v1/; / { compatible = "rockchip,rk3328"; fragment@0 { target-path = "/ethernet@ff540000/mdio"; __overlay__ { ethernet-phy@1 { compatible = "ethernet-phy-id001c.c916"; }; }; }; }; ethernet 0 is working fine. Problem is, that with this dts the older RTL8211E will probably stop to work... Thanks for pointing to the System updates. On 25 Armbian I see it, but on 24.8.3 when I updated only armbian-config, the Updates option is missing:

25.5.0-trunk.316_Rockpi-e_plucky_current_6.12.21_minimal boots, but the problem with ethernet persist. Bootlog with level 7: https://paste.armbian.com/bimosoyupi.yaml

It looks like the problem with not working ethernet after upgrade is after 24.11.1 version, because I now noticed, that I have one device upgraded to 24.11.1 and ethernet is working...

Hi. I have RockPi E v1.21 and I found, that I'm not able to boot image with new kernel 6.12 (tried minimal images 25.2.1 and 24.11.1, USBImager and Balena Etcher, 3 SD cards, different power supplies). With image 24.8.3 it boots normally. Also I found, that after upgrading 24.8.3 to kernel 6.12 the RockPi boots, but Ethernet doesn't work (even LEDs are dead). Another thing which I notice is, that I didn't find any option to disable kernel upgrades, but what I googled, it should be present in armbian-config->system->kernel->Y203. But this Y203 option is missing. Here is successful boot log of 24.8.3: https://paste.armbian.com/ixuvimofis.sql here is boot log of 24.8.3 upgraded to 6.12: https://paste.armbian.com/ahezanixol.sql Here is failing boot of 25.2.1: https://paste.armbian.com/onuhumomob.yaml P.S. on the successful boot of 24.8.3 I didn't have ETH cable connected, that's why there is Network connection timeout!, but it works fine after connecting. What's weird, that both 24.8.3 boots says on the beginning Net: Could not get PHY for ethernet@ff540000: addr -1 No ethernet found. But I assume that's problem only of u-boot, because it's before kernel boot. Thanks!

So the conclusion is, that on PWM2 (GPIO2_A6) is connected Power Management IC (RK805-1) INT pin, so it's not available for PWM, genius...

I enabled higher verbosity level to debug uart. It looks like there is some conflict with I2C, but it doesn't make sense, because PWM2 pin has only 2 functoins - GPIO and PWM. I2C is common with PWM0 and 1... From the log: I will dig more... EDIT: it looks like this pin is used by pmic (from decompiled dtb on running system). But I didn't find pmic in the source codes: https://github.com/armbian/linux-rockchip/blob/0c0949a270027b749ab2c818e7ff61fc542757cc/arch/arm64/boot/dts/rockchip/rk3328.dtsi I'm new in Device Tree, so it takes me some time to get oriented in it... pmic { pmic-int-l { rockchip,pins = <0x02 0x06 0x00 0x65>; phandle = <0x2a>; }; }; EDIT2: Ok, it's under https://github.com/armbian/linux-rockchip/blob/1725188c90e86921c54e72f8b306c2177097256d/arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dts#L334 But what I don't understand is, that I didn't find any reference to this pin control (nor in source code nor in decompiled dtb), so why it is a problem? EDIT3: ok, I found it. I searched for wrong name: &i2c1 { status = "okay"; rk805: pmic@18 { compatible = "rockchip,rk805"; reg = <0x18>; interrupt-parent = <&gpio2>; interrupts = <6 IRQ_TYPE_LEVEL_LOW>; #clock-cells = <1>; clock-output-names = "xin32k", "rk805-clkout2"; gpio-controller; #gpio-cells = <2>; pinctrl-names = "default"; pinctrl-0 = <&pmic_int_l>; But Radxa has this pin from RK805 (or I assume that it's this one) connected to GPIO0_A2 in their schematics (for Rev 1.2):

Hello. I'm trying to get the PWM2 and 3 to work on RockPi E. I made a custom dts to enable PWM2, loaded using armbian-add-overlay: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328"; fragment@0 { target = <0xffffffff>; __overlay__ { status = "okay"; }; }; __fixups__ { pwm2 = "/fragment@0:target:0"; }; }; But the kernel doesn't boot: Any idea? I already tried to enable uart1 using custom dtbo and it works without problem. I'm testing on Ubuntu Noble Minimal/IoT v24.8.3 for Rockpi E running Armbian Linux 6.6.51-current-rockchip64 Thank you