umiddelb

What UART parameters have you set, especially flow control?

There is an implicit timeout built into uboot which triggers this error messages. I suppose that the newer firmware will circumvent this timeout.

X-Ref:

The ArchLinuxARM-utilite-latest.tar.gz image comes with a 3.0.x kernel, with must be u-booted with bootm instead of bootz.

[alarm@alarm ~]$ sudo networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether degraded configuring 3 eth1 ether routable configured 3 links listed. eth0 (fec) stays at level degraded, when it is getting connected.

and you are right, dhcpcd is not needed at all.

Honestly, I have no idea. I haven't used the fec interface for a while. Now I realized the fec interface doesn't work at all, only the igb interface is usable (neither armbian nor arch).

systemctl enable dhcpcd systemctl start dhcpcd

I've played a little bit with ArchLinuxARM-utilite-latest.tar.gz with following observations: the stock kernel is very old (3.0.X) and uses the traditional bootm scheme (combined kernel+dtb) the linux-armv7 packages provides an up to date kernel (6.2.10), but needs some love in order to comply with the Armbian boot script there was no configuration for eth1 like /etc/systemd/network/eth0.network dhcpcd was disabled, needs to be enabled flash memory access has returned doesn't seem to crash, unlike 6.1.63

igb -> end1 fec -> end0 what is the output of ip a ?

What is the output of dmesg ?

/boot/armbianEnv.txt != /etc/fstab If /etc/fstab was empty, something went wrong. You max extract the contents of Armbian_23.8.1_Cubox-i_bookworm_current_6.1.50.img.xz once again.

The original /etc/fstab from Armbian_23.8.1_Cubox-i_bookworm_current_6.1.50.img.xz looks like this: UUID=8e42c01d-846b-4090-b69e-1b45502b6cc4 / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 As mentioned before, you will need to adjust the UUID unless you have passed it to mkfs.ext4.

Have you checked the UUID for '/' in /etc/fstab ?

Very good! Usually the bootscript doesn't need to be modified if the u-boot environment looks more or less like the one I've posted above (only the MAC addresses should differ) . The 6.1.50 kernel runs smoothly, just extract the 6.1.50-current-imx6.tgz in /