Ver 20230818-legacy - fix 8Gb RAM
2 Likes
Version 20230824-legacy with kernel 5.15.127.
Expanded the list of Wi-Fi modules (USB\PCIe).
Added DTB for VisionFive V2 models with 4 GB of RAM (for use on 4GB models - rename the DTB file or edit /boot/extlinux/extlinux.conf with a 4 GB indication).
1 Like
Sorry, but the link for Altlinux is not working.
The images are common to Star64 and Visionfive V2, you just write to the SD card, you don’t need to change anything, the system automatically selects the correct DTB. Important, the u-boot update must be installed and the switch to the 0.0 SPI\flashe position
Thanks.
Description of how you can easily run official Armbian images without changing the factory position of the switch (flash 0,0).
1 Like
Version 20230828-legacy with kernel 5.15.127.
Expanded the list of sound modules and codecs (USB\PCIe).
1 Like
Version 20230829-current with kernel 6.5.
Expanded the list of sound modules and codecs (USB\PCIe).
2 Likes
Hi Balbes i would like to try out Armian.
What version would be better, the official armbian version with the txt file patched or the ArmbianTV version with the modified Kernel?
Also if i have firmware 3.04 do i still need to patch it ?
Thanks
I recommend the ArmbianTV version with LEGACY core, it has good support for all equipment, including HDMI. If you only need a server, you can use any version, taking into account which hardware should work (not everything works on the CURRENT and EDGE versions).
I haven’t checked these loader versions. You can try to start the system yourself without installing the update, if it works, you do not need to run the update.
Version 20230920-legacy with kernel 5.15.130
Ver 20230922-edge kernel 6.6-rc1
Details of the description of the transition to the u-boot version 3.6.1 with support for launching Armbian from an SD card and installing on NVMe. (updating u-boot to SPI\Flash to run any system from SD card and NVMe).
Ver 20230923-edge kernel 6.6-rc2
Added u-boot 3.6.1 update image with support for the former “uenvcmd” command.
This allows you to run Altlinux without changing the settings files, as well as install Altlinux on NVMe. To install Altlinux on NVMe, it is enough to start any system from an SD card (Armbian or Altlinux or any other system that supports NVME), download, unpack the desired version of Altlinux and burn the resulting IMG image with the DD utility to NVMe. When the SD card is disconnected, the NVMe system will automatically start.
1 Like
Version 20230924-current with kernel 6.1.31 work HDMI USB LAN etc
1 Like
Altlinux ver 20230929 add image DE LXDE and LXQT
1 Like
Standard Armbian image boots from usb with my u-boot mods,
Armbian_23.8.1_Visionfive2_jammy_edge_5.15.0.img
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?
- Yes
- No
#? 1
Generating locales: en_AU.UTF-8
root@visionfive2:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
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 ?