Wanted to try this Debian rolling release with Linux v6.18 from https://www.armbian.com/rockpie/ page, but both links there

https://dl.armbian.com/nightly/rockpi-e/Forky_current_minimal
https://dl.armbian.com/nightly/rockpi-e/Plucky_current_minimal

lead to a 404 page on github.com.

Thanks,

Chris

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!

Can help me about orange 3b,

I want to adapt one dts file to my board,

how to correctly indicate the names of the pins, the example gives the following sample entry: https://mjmwired.net/kernel/Documentation/devicetree/bindings/display/panel/sitronix,st7701.txt

reset-gpios = <&pio 3 24 GPIO_ACTIVE_HIGH>; /* LCD-RST: PD24 */

how to correctly fix this for my board?

I am struggling to get the second NIC (1Gbit) to work. The wireless and first NIC (100Mbit)  works

All NIC's connected

I am using Armbian 22.11.0-trunk Bullseye

root@rockpi-e:~# ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 9a:9c:84:a1:77:63  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 41

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.150.1.153  netmask 255.255.255.0  broadcast 10.150.1.255
        ether 9a:9c:84:a1:77:83  txqueuelen 1000  (Ethernet)
        RX packets 511  bytes 40303 (39.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 154  bytes 14296 (13.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 42

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlx60fb004c1ad0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.86.37  netmask 255.255.255.0  broadcast 192.168.86.255
        inet6 fe80::87c1:1dc5:ab7:6e70  prefixlen 64  scopeid 0x20<link>
        ether 60:fb:00:4c:1a:d0  txqueuelen 1000  (Ethernet)
        RX packets 4101  bytes 919466 (897.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 747  bytes 336966 (329.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@rockpi-e:~#

root@rockpi-e:~# nmcli connection show
NAME                UUID                                  TYPE      DEVICE
Wired connection 2  2824d9e9-002b-3206-a9e3-56101ea54125  ethernet  eth1
mesh                0f22274b-554b-47b6-899e-2ae5e1ec9e1a  wifi      wlx60fb004c1ad0
Armbian ethernet    f8b4ca43-7e6f-464a-ab38-9c8744b0dc16  ethernet  --
Wired connection 1  c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70  ethernet  --
root@rockpi-e:~#

root@rockpi-e:~#
root@rockpi-e:~# nmcli connection up c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70
Error: Connection activation failed: The device could not be readied for configuration
Hint: use 'journalctl -xe NM_CONNECTION=c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70 + NM_DEVICE=eth0' to get more details.
root@rockpi-e:~#

root@rockpi-e:~# journalctl -xe NM_CONNECTION=c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70 + NM_DEVICE=eth0
Journal file /var/log/journal/f5dd17308a32431b9d72c3f4257db559/system@488569ec21fd40be8b54f2a0c0f5271d-0000000000000001-0005ec5fc6f64b22.journal is truncated, ignoring file.
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <info>  [1671640567.3994] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <info>  [1671640567.4061] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <info>  [1671640567.4106] device (eth0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <warn>  [1671640567.4252] device (eth0): Activation: failed for connection 'Wired connection 1'

dmesg show:

[ 1519.182778] rk_gmac-dwmac ff540000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 1540.887807] rk_gmac-dwmac ff540000.ethernet eth0: no phy at addr -1
[ 1540.887850] rk_gmac-dwmac ff540000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

Anyone know how to solve it?

we are facing an issue we can not resolve ourselves so we are looking for some help on here... Our Rock Pi E does not restart successfully occasionally.

Running the Rock Pi E with latest official Armbian with a USB soundcard attached. We are capturing audio and distribute the captured audio via "(c)VLC" via network. Since a few months we are facing reboot issues which are persistent but not easily reproducible. Whenever we reboot manually, everything works fine. When rebooting via cron it does often not reboot and get into a freeze state which makes it impossible to connect via SSH nor serial-adapter.

We already tried switching the power source (suspecting a lack of power), adding a powered USB hub in-between and renewing the USB soundcard to eliminate any defects. We also switched SD card and now even switched to eMMC completely.

Also we had in mind that this could be a heat issue, so we installed heatsinks and even a little fan.

I am not 100% sure if this is the only issue since we had some hickups with cvlc, too, which stopped audio streaming suddenly when running for a long time. We had the setup untouched running for a few months, then it started to crash every other week, then like every other day. This is when we came up with a daily reboot to gain some time inspecting what the issue could be.

armbian -u: https://paste.armbian.com/umekijamum

Output on serial right before it freezes: https://paste.armbian.com/sicesorulu.sql

Any ideas?

Is there a way to detect any RAM faults or faults in the underlying Armbian/Kernel  that occured on some unintended reset/power failure?

We did not re-install Armbian yet since this is quite a bit work to get it all done again.

Create file rockchip-uart1.dts

/dts-v1/;
/ {
	compatible = "rockchip,rk3328";
	fragment@0 {
		target-path = "/serial@ff120000";
		__overlay__ {
			pinctrl-0 = < 0x23 >;
			status = "okay";
		};
	};
};

Create file rockchip-otg.dts

/dts-v1/;
/ {
	compatible = "rockchip,rk3328";
	fragment@0 {
		target-path = "/usb@ff580000";
		__overlay__ {
			dr_mode = "otg";			
		};
	};
};

Install and enable overlays:
sudo armbian-add-overlay rockchip-uart1.dts
sudo armbian-add-overlay rockchip-otg.dts

I want to build or get pre-built armbian image for kernel 4.4 with wifi : rtl8723as enabled.

Please help or provide any suggestion to build armbian image for rockpi-e.

Any help or suggestion will be appriciated.

Hence I referred to drivers available in the kernel and found one for the module similar to that of my module (RTL8723BS), cross verified through user manual and datasheets and build it using armbian. 

The driver gets built properly and even initializes upon powerup but it isn't getting into probe. The wifi is interfaced through SDIO to the board. Any idea what might be wrong?

Thanks for your time

Chris

I would like to use the UART on physical pins 3 and 5 (https://wiki.radxa.com/RockpiE/hardware/gpio)

Does anybody know how to activate it? There is an overlay uart4 but it doesn't do what I expected it to do :-)

Thanks

Chris

Access Point created with armbian-config. 

Thank.