Ulrich

Problem solved... My ignorance... For inexplicable reasons, u-boot was updated without an error message, but actually NOT written to the SD card. The ancient version apparently cannot start without uImage. Now I have manually written the SD card - more precisely an image of it - with the new u-boot and then wrote a new SD card from that image, uImage can be deleted and it runs...

Everything works, but I don't know why (;-) I upgraded to a new kernel 6.12.34-current-meson64 and also to the current u-boot. If I take a look at a current armbian image, every image.. vmlinux.. etc. is available in the boot folder, but no uImage. In my boot folder, however, in addition to the these files in the current armbian image, in my boot folder is still is a uImage from 2022. uname -r -> 6.12.34-current-meson6 So the current kernel is loaded and everything works. But if I now delete the uImage from 2022, the computer no longer boots. How does a current armbian image manage to boot without uImage? Is a uImage created at the first start? Manually I have created a new uImage via mkimage -A arm -O linux -T kernel -C none -a 0x01080000 -e 0x01080000 -n "Linux" -d ./vmlinuz-* ./uImage and the computer boots again, without uImage and only with the vmlinuz files not. Long story - can I leave it like that, or is there a way to boot without uImage.

Armbian Armbian 22.11.4 Jammy on Odroid C4 boot from SD card system on an ext4 SSD. First of all - everything I need works correctly... However, I have a question about the SD card. During the first installation on the SSD disk, the system hung on the first reboot and you could see from the console that the SD card with UUID=61748c7e-b234-40e8-b6b6-592f845c3699 was being waited for. After the timeout, the only way to fix the "error" was to log into the system via terminal. Long story - only after commenting out the SD card in the fstab on the SSD: UUID=61748c7e-b234-40e8-b6b6-592f845c3699 /media/mmcboot ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 0 /media/mmcboot/boot /boot none bind 0 0 the system booted from the SSD as requested. Since then, the SD card is not mounted and just shows up as: Disk /dev/mmcblk0: 30.61 MiB, 32096256 bytes, 62688 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes at fdisk -l. No UUID etc nothing... The SD-Card is 32G and is readable on other systems... Question now - is this normal? Can I live with that? Can it be fixed? A "curiosity" - after booting from the SSD and updating the kernel to 6.0.13, the update ended up on both the SSD and the unmounted SD card. How - is a mystery to me (;-)