TRay

I've been trying to update the system for 2 days but I can't: sudo apt update Get:1 http://deb.debian.org/debian trixie InRelease [140 kB] Get:2 http://security.debian.org trixie-security InRelease [43.4 kB] Get:4 http://security.debian.org trixie-security/main armhf Packages [88.5 kB] Get:5 https://github.armbian.com/configng stable InRelease [5,467 B] Get:6 https://github.armbian.com/configng stable/main armhf Packages [434 B] Get:3 http://armbian.lv.auroradev.org/beta trixie InRelease [39.4 kB] Get:7 http://armbian.lv.auroradev.org/beta trixie/trixie-desktop all Packages [731 B] Get:8 http://armbian.lv.auroradev.org/beta trixie/trixie-desktop armhf Packages [2,250 B] Get:9 http://armbian.lv.auroradev.org/beta trixie/trixie-utils armhf Packages [8,303 B] Ign:9 http://armbian.lv.auroradev.org/beta trixie/trixie-utils armhf Packages Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Get:10 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB] Get:11 http://deb.debian.org/debian trixie-backports InRelease [54.0 kB] Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Get:12 http://armbian.lv.auroradev.org/beta trixie/trixie-utils all Packages [3,343 B] Ign:12 http://armbian.lv.auroradev.org/beta trixie/trixie-utils all Packages Get:13 http://deb.debian.org/debian trixie/main armhf Packages [12.7 MB] Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Ign:12 http://beta.armbian.com trixie/trixie-utils all Packages Get:14 http://deb.debian.org/debian trixie/non-free armhf Packages [69.9 kB] Get:15 http://deb.debian.org/debian trixie/contrib armhf Packages [50.6 kB] Get:16 http://deb.debian.org/debian trixie/non-free-firmware armhf Packages [6,685 B] Get:17 http://deb.debian.org/debian trixie-updates/main armhf Packages [5,144 B] Get:18 http://deb.debian.org/debian trixie-backports/non-free armhf Packages [1,520 B] Get:19 http://deb.debian.org/debian trixie-backports/contrib armhf Packages [4,348 B] Get:20 http://deb.debian.org/debian trixie-backports/non-free-firmware armhf Packages [3,856 B] Get:21 http://deb.debian.org/debian trixie-backports/main armhf Packages [130 kB] Fetched 13.4 MB in 18s (754 kB/s) Error: Failed to fetch http://beta.armbian.com/dists/trixie/trixie-utils/binary-armhf/Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Error: Failed to fetch http://beta.armbian.com/dists/trixie/trixie-utils/binary-all/Packages.bz2 File has unexpected size (3942 != 3343). Mirror sync in progress? [IP: 23.186.113.5 80] Error: Some index files failed to download. They have been ignored, or old ones used instead.

when send command poweroff or reboot alywas display client_loop: send disconnect: Broken pipe instead in on ArmBian Debian 12: Connection to 192.168.1.12 closed by remote host. Connection to 192.168.1.12 closed. but maybe on Debian 13 now is different message after reboot or poweroff

During installation new Image show on screen following problems: Failed to retrieve unit state: Transport endpoint is not connected _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v26.2 rolling for Orange Pi Zero running Armbian Linux 6.12.63-current-sunxi Packages: Debian stable (trixie) Support: for advanced users (rolling release) Failed to retrieve unit state: Transport endpoint is not connected trying reboot: root@orangepizero:~# reboot Call to Reboot failed: Connection timed out

It seems that the problem has been under consideration since mid-May, so we are waiting for a bootloader update. https://github.com/armbian/build/issues/8197

Hi, yes, I agree, but I am only a user of Armbian and I do not have such skills to do this solution you suggest I can check the available Community Releases of Armbian and check how it works. Community editions, which are issued for testing and updated on average every week?

So maybe it would be enough if the community version of U-Boot were updated to version v2025.07 and it would solve the reboot problem for this SBC, just like it happened for the Orange Pi Zero 3 where updating U-Boot to v2025.04 solved the problem of decoding RAM size on the SBC

While searching the internet for information about the reboot problem, I found this information but I don't know if it is helpful for us?

Is anyone using Linux kernel-edge on an Orange Pi Zero v1? Are they kernel versions 6.14 or 6.16? Does that also cause the reboot problem?

For the Orange Pi Zero v1, it might be recommended to upgrade U-Boot to version v2025.4. I remember having similar problems with the Orange Pi Zero 3, and after the U-Boot update, the reboot works correctly and doesn't shut down the computer.

I see that the reported problem was raised in another topic:

Another phenomenon is also observed on the Orange Pi Zero v1. Issuing the reboot command causes the computer to not restart, requiring the power supply to be turned off and on again.

However, we're seeing a problem with kernel 6.12.x where the first time the computer is turned on, ArmBian doesn't always boot. Only after powering down and turning it back on does the Orange Pi Zero v1 start booting. This problem didn't occur previously on the same hardware, so perhaps updating U-Boot to version v2025.04 would solve the problem. We'd like to ask those who are also making changes to the Orange Pi Zero V1 to update U-Boot.

Thank you for the explanation

Hi I have use v25.8 rolling for Orange Pi Zero3 running Armbian Linux 6.12.35-current-sunxi64 and after run command dmesg I see information on screen So what can I do about it?

@Igor thank you for fixing overlay-prefix problem in current armbin-config now on OZPI V1 and V3 overlays in armbianEnv.txt are without prefix

SBC Orange Pi Zero V1 is still a popular SBC and is still sold on the market, among other things, because it has an integrated sound card and for this reason, a lot of hamradio operators still buy this model because it allows you to build very compact mobile hotspots without having to attach a USB sound card protruding outside the housing and that is why it is very popular and still sold despite the fact that versions V2 and V3 have been released, so it is not an SBC that has completely gone down in history.

Yes, I know about it, but my intention was whether it would be possible to also upgrade the SBC Orange Pi Zero V1 to the newer version of U-Boot

Since U-Boot v2025.04 works very well on Orange Pi Zero v3 and has a shorter boot process time, if there was a possibility to switch to U-Boot v2504 for Orange Pi Zero V1, I would be grateful, as would probably other users of this SBC Regards

Yes, I know about it and I did it right after the update was finished. Maybe it was an isolated case. I did armbin-install again and test 30 reboot again and each one correctly indicated 1Gb RAM 🙂

Thank you. I did an Armbian update where there is a new U-Boot v2025.04 and kernel 6.12.35 and on 10 reboots one after another, one time it showed the RAM size incorrectly instead of 1 GB it gave 2 GB. I see a definite improvement compared to u-boot v2024.xx

I realize that OZPI v3 is supported by the community, but I would like to ask if anyone has information whether u-boot for OZPI v3 will be in version 2025.04 and is the estimated date known? Will armbian-config be fixed for OZPI v3 etc. problem using overlay-prefix in device tree? https://github.com/armbian/configng/issues/592

Yes in overlays i2c3-ph is on system is i2c-1 on OZPI v2/3 boards on pins 3 and 5 So you can check connected devices on pins 3 and 5 i2cdetect -y 1

I confirm that armbian-config has problem with add ovelay prefix to overlays= please look on: https://github.com/armbian/configng/issues/592 So i must add manually devices in amrbinaEnv.txt and for OZPI v3 to use I2C i have overlay_prefix=sun50i-h616 overlays=i2c3-ph

I use the ArmBian version which is updated very often (see below) so if U-Boot v2025.04 for OZPI v3 appears in the current updates it will be possible to check and other users who have OZPI v3 with 1,1.5, 2, or 4 Gb RAM check it

From the information of DietPi users, it appears that they have used UBoot v2025.04 for Orange Pi Zero 3 and it seems that the problem of incorrect detection of RAM size has been solved, especially in the version with 1 MB. It would be valuable if ArmBian was also transferred for Orange Pi Zero 3 to Uboot v2025.04, we could avoid complications during system updates and other processes that need a lot of RAM causing the system to hang up because they try to use memory addresses that are not physically there when the RAM size was incorrectly identified during booting. More info about UBoot v2025.04 with Orange Pi Zero 3: https://github.com/MichaIng/DietPi/issues/7242#issuecomment-2912290816