Hi @Vaclav Rada, You can also disable the systemd 'predictable naming convention' of interface naming by adding: net.ifnames=0 to your kernel commandline. This can be done in armbianEnv.txt by adding them to the extraargs variable as follows: extraargs=net.ifnames=0 Would be better to adjust your armbianEnv.txt instead of changing on-disk systemd service unit files, as they will be overwritten whenever an update comes along. I have not seen a situation myself where using the 'new' naming convention for network interfaces would work out better. But perhaps my use cases are not as flashy as other's 🙂 Groetjes,

@atleta I've been seeing that it's a bad idea, it has 8g and I didn't want to completely waste its use, I wanted to help the system's processing or speed in some way but I think it's difficult lol

Which build are you using? Is your internal emmc detected on boot?

Hi, i have a R29_5G_LP3_V1.2 that i brick it, tried reduce the partition from internal emmc, i used rkdeveloptool to fix it, and dont worked! Can i remove the emmc chip and this can work just sdcard boot? Thanks

I was facing the same issue on armbian 24.11., kernel 6.6.62. If you look at the service: cat /etc/systemd/system/helios64-heartbeat-led.service Below, see that the device_name to trigger the led activity is "eth0". [Unit] Description=Enable heartbeat & network activity led on Helios64 After=getty.target [Service] Type=oneshot ExecStart=bash -c 'echo heartbeat | tee /sys/class/leds/helios64\\:\\:status/trigger' ExecStart=bash -c 'echo netdev | tee /sys/class/leds/helios64\\:blue\\:net/trigger' ExecStart=bash -c 'echo eth0 | tee /sys/class/leds/helios64\\:blue\\:net/device_name' ExecStart=bash -c 'echo 1 | tee /sys/class/leds/helios64\\:blue\\:net/link' ExecStart=bash -c 'echo 1 | tee /sys/class/leds/helios64\\:blue\\:net/rx' ExecStart=bash -c 'echo 1 | tee /sys/class/leds/helios64\\:blue\\:net/tx' [Install] WantedBy=multi-user.target But, the ethernet interfaces have different names: ifconfig end0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ... enx646266d00c69: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ... I wanted the led to follow the activity of 1GbE interface, which, in this case, is the "end0". So, adjusting the line in the service file From: ExecStart=bash -c 'echo eth0 | tee /sys/class/leds/helios64\\:blue\\:net/device_name' To: ExecStart=bash -c 'echo end0 | tee /sys/class/leds/helios64\\:blue\\:net/device_name' And then restarting the service did the trick. systemctl daemon-reload systemctl restart helios64-heartbeat-led # systemctl enable helios64-heartbeat-led # the service should be already enabled to start on startup automatically Hope this helps.