jimt

Thanks! It would be helpful if armbian-install somehow checked that before offering the btrfs option. (This is just an interim solution until I figure out what went wrong with a recent Rock 5B upgrade that keeps it from booting and took many of my home services offline. So I will live with ext4 for now, but I thought I should report the problem.)

``` ❯ sha256sum Armbian_25.11.1_Orangepi5*img 6cb1e6ed97dc41170db8406b056ecbf422f8801261e13b07da4dae3b45a81ab3 Armbian_25.11.1_Orangepi5_noble_vendor_6.1.115_minimal.img 5781fec6fa812fca1f99e79a42b0312bf4403a2a590dec84458dcfbabd28cd13 Armbian_25.11.1_Orangepi5_trixie_vendor_6.1.115_minimal.img ```

I got my Orange Pi 5 out of the drawer today and discovered that it would not boot from NVMe after armbian-install if I used btrfs, but it boots fine with ext4. I tried both the Minimal/IOT Ubuntu 24.04 and 25.11.1 Trixie Minimal/IOT images with 6.1.x kernels. (I updated each to 25.11.2 before doing the armbian-install of both the system and the mtd image.) P.S. A minor quibble, but it was annoying that the numbering of the continents/countries during setup and the ordering of the SPI bootloader options during armbian-install were different between the Trixie and Noble images. I had to actually read. 🙈

I notice my VIM3 Pro negotiated 12V power when running the originally supplied Android image or the Rescue image, but when using Armbian 23.02.2 Jammy with Linux 6.1.11-meson64 it stays at 5V.

Thanks! That allows chrony to run on my board.

I tried setting SKIP_BOOTSPLASH=yes from Hidden options for advanced users of the Build Options page, but the Armbian splash screen still appears. Since I have to ask here, I am obviously not an advanced user. 🙃 How do I eliminate the boot splash screen as I am building/testing images? ./compile.sh \ BOARD=visionfive2 \ BRANCH=edge \ RELEASE=lunar \ BUILD_MINIMAL=no \ BUILD_DESKTOP=no \ KERNEL_CONFIGURE=no \ SKIP_BOOTSPLASH=yes \ CARD_DEVICE="/dev/sdb"

On Armbian_23.5.0-trunk.140_Visionfive2_lunar_edge_5.15.0.img.xz chrony fails to start: May 02 23:24:48 visionfive2 systemd[1]: Starting chrony.service - chrony, an NTP client/server... May 02 23:24:48 visionfive2 chronyd[1874]: chronyd version 4.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGN> May 02 23:24:48 visionfive2 chronyd[1874]: Using right/UTC timezone to obtain leap second data May 02 23:24:48 visionfive2 chronyd[1874]: Fatal error : Failed to load seccomp rules May 02 23:24:48 visionfive2 chronyd-starter.sh[1872]: Failed to load seccomp rules May 02 23:24:48 visionfive2 systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE May 02 23:24:48 visionfive2 systemd[1]: chrony.service: Failed with result 'exit-code'. May 02 23:24:48 visionfive2 systemd[1]: Failed to start chrony.service - chrony, an NTP client/server. So I am using ntpdate (from ntpsec-ntpdate) at boot.