Armbian Altlinux for VisionFive V2 (jh7110)

Standard Armbian image boots from usb with my u-boot mods,
with OpenBSD installed on the nvme.
Boot order sd, usb, nvme, emmc, haven’t yet tested emmc.

Therefore TZ=‘Australia/Brisbane’ will be used.
Selected time is now: Fri Sep 1 05:10:21 AEST 2023.
Universal Time is now: Thu Aug 31 19:10:21 UTC 2023.
Is the above information OK?

  1. Yes
  2. No
    #? 1

Generating locales: en_AU.UTF-8
root@visionfive2:~# lsblk
sda 8:0 1 28.7G 0 disk
└─sda1 8:1 1 28.4G 0 part /var/log.hdd
mtdblock0 31:0 0 256K 0 disk
mtdblock1 31:1 0 3M 0 disk
mtdblock2 31:2 0 1M 0 disk
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 16M 0 part
└─nvme0n1p4 259:2 0 238.4G 0 part

Ver 20231003-edge with kernel 6.6-rc4

This version is unrelated to this topic.

1 Like

If the SD card is inserted after the image has been DD’d to NVME the boot gets confused because there are now 2 disks with the same UUIDs, as pointed to by extlinux.conf

The DD utility is used only for Altlinux (as a temporary solution), Armbian uses the standard installation procedure on NVME (using armbian-config), which correctly generate the UUID and configure the system to run and there are no conflicts. And why use two identical systems with SD and NVMe ?