balbes150

Version 20230924-current with kernel 6.1.31 work HDMI USB LAN etc

Thanks for testing, I see the bootcmd variable has not been updated. It looks like one line was lost when creating the variable update image. Now I will fix the images and upload them to the site. Replaced the images with corrected versions. Run both images again (reset settings and update variables). After that, everything should work without manual additions.

Version 20230922-edge with kernel 6.6-rc1 I also added images to update the latest official version of u-boot 3.6.1 for SPI\Flash to easily run any system on VF2 from an SD card and NVMe. After switching to u-boot-3.6.1 and updating using the provided update images, you can easily install Armbian on NVMe and run the entire system with NVMe. The procedure for switching to u-boot is 3.6.1. Update u-boot in SPI\Flash according to the instructions from the official VF2 documentation page. Download, write to the SD card and run two images sequentially - first run reset-default-env-uboot-visionfive2-3.6.1.img (after launching the update, wait 10-20 seconds and turn off the power), then write to the SD card and run update_uboot-visionfive2-3.6.1.img (after launching the update, wait 10-20 seconds and turn off the power). After these procedures, you can easily run Armbian SD cards or install it on NVMe (using the standard armbian-config mechanism and choose the installation option on MTD\SATA\NVMe). Please note, for proper installation on NVMe, a section must be prepared there, i.e. the installation process corresponds to the description of the Armbian installation documentation on NVMe. It is possible to add the u-boot upgrade procedure to the standard armbian-config procedure for installing the system on NVMe, so that the whole process takes place automatically, but I have not yet decided whether to add it or leave the u-boot upgrade process in SPI, as described in the documentation for VF2 Please note that these updates do not violate the previous official launch procedure in u-boot SPI\Flash. Link image update https://disk.yandex.ru/d/O4lr6WrGdUvydw

Ver 20230922-edge kernel 6.6-rc1 I added an image to quickly reset all u-boot settings to the factory (default) state without using UART. For details, see the link. https://forum.pine64.org/showthread.php?tid=18344&pid=119853#pid119853

Version 20230920-legacy with kernel 5.15.130

Ver 20230917-edge kernel 6.6.-rc1 for Nezha (Allwinner D1) (HDMI not work)

Version 20230914-legacy with kernel 5.15.130

As far as possible, I will see what can be done.

I checked the startup - the system is working. I pay attention to this message, HDMI does not work for the EDGE kernel. If you need HDMI, use LEGACY and CURRENT versions.

Ver 20230914-EDK2-EFI-edge kernel 6.6-rc1

Ver 20230914-EDK2-EFI-edge kernel 6.6-rc1

Ver 20230911-EDK2-EFI kernel legacy\current\edge On the edge version, HDMI does not work in the kernel itself, but HDMI is supported at the level of the selection menu in GRUB, this allows you to have several different versions of the kernel\system (for example, add a self-assembled EDGE kernel with its own configuration) and choose on the monitor screen which kernel\system to run not using the UART console.

Ver 20230911-EDK2-EFI kernel legacy\current\edge (the startup works from an SD card). On the edge version, HDMI does not work in the kernel itself, but HDMI is supported at the level of the selection menu in GRUB, this allows you to have several different versions of the kernel\system (for example, add a self-assembled EDGE kernel with its own configuration) and choose on the monitor screen which kernel\system to run not using the UART console.

Ver 20230911-EDK2-EFI kernel legacy\current\edge On the edge version, HDMI does not work in the kernel itself, but HDMI is supported at the level of the selection menu in GRUB, this allows you to have several different versions of the kernel\system (for example, add a self-assembled EDGE kernel with its own configuration) and choose on the monitor screen which kernel\system to run not using the UART console.

Ver 20230911-EDK2-EFI kernel legacy\current\edge On the edge version, HDMI does not work in the kernel itself, but HDMI is supported at the level of the selection menu in GRUB, this allows you to have several different versions of the kernel\system (for example, add a self-assembled EDGE kernel with its own configuration) and choose on the monitor screen which kernel\system to run not using the UART console.

which monitor do you use ?

I have not tested the work of u-boot 2.11.5, but with the default u-boot + update, everything works with all kernel versions, including 6.5. Show the UART log of running kernel 6.5 from 2.11.5.

ver 20230904-edge kernel 6.5.1

Version 20230829-current with kernel 6.5. Expanded the list of sound modules and codecs (USB\PCIe).

Version 20230828-legacy with kernel 5.15.127. Expanded the list of sound modules and codecs (USB\PCIe).

I am testing the launch only with the u-boot that comes from the factory (with a single launch of the update), I do not control why the new versions of u-boot do not work correctly. Perhaps the reason for the incorrect operation of HDMI is errors in u-boot 3.x, try to roll back u-boot to version 2.11.5, NVMe works in this version and there have been no reports of problems with HDMI.

for those who want to launch the "official" Armbian (image versions from the official download page), this is very easy to do. Update u-boot according to the instructions in the first message (if you have already done this, you can skip this step). Download the official Armbian image, unpack, burn to the SD card, download https://disk.yandex.ru/d/-yoq6BZqC8ZbAQ and replace the file on the SD card uEnv.txt the correct file. Connect the SD card and turn on the power, the system starts automatically. Important. I do not know how well the official image works and I am not responsible for its work. I only checked the general launch. user@192.168.1.12's password: __ ___ _ _____ _ ____ \ \ / (_)___(_) ___ _ __ | ___(_)_ _____|___ \ \ \ / /| / __| |/ _ \| '_ \| |_ | \ \ / / _ \ __) | \ V / | \__ \ | (_) | | | | _| | |\ V / __// __/ \_/ |_|___/_|\___/|_| |_|_| |_| \_/ \___|_____| Welcome to Armbian 23.8.0-trunk.259 Jammy with bleeding edge Linux 5.15.0-edge-starfive2 No end-user support: untested automated build System load: 9% Up time: 11 min Memory usage: 3% of 3.79G IP: 192.168.1.12 CPU temp: 40°C Usage of /: 9% of 7.3G To run a command as administrator (user "root"), use "sudo <command>". See "man sudo_root" for details. user@visionfive2:~$ cat /proc/cpuinfo processor : 0 hart : 1 isa : rv64imafdc mmu : sv39 isa-ext : uarch : sifive,u74-mc processor : 1 hart : 2 isa : rv64imafdc mmu : sv39 isa-ext : uarch : sifive,u74-mc processor : 2 hart : 3 isa : rv64imafdc mmu : sv39 isa-ext : uarch : sifive,u74-mc processor : 3 hart : 4 isa : rv64imafdc mmu : sv39 isa-ext : uarch : sifive,u74-mc

Everything works for me. What is your model and how is the network connected ? user@192.168.1.12's password: __ ___ _ _____ _ ____ \ \ / (_)___(_) ___ _ __ | ___(_)_ _____|___ \ \ \ / /| / __| |/ _ \| '_ \| |_ | \ \ / / _ \ __) | \ V / | \__ \ | (_) | | | | _| | |\ V / __// __/ \_/ |_|___/_|\___/|_| |_|_| |_| \_/ \___|_____| Welcome to Armbian 23.06 Lunar with Linux 5.15.127-star64 No end-user support: built from trunk System load: 26% Up time: 2 min Local users: 2 Memory usage: 5% of 7.72G IP: 192.168.1.12 CPU temp: 39°C Usage of /: 26% of 15G user@starfive2:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 6c:cf:39:00:5f:60 brd ff:ff:ff:ff:ff:ff altname end0 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 6c:cf:39:00:5f:63 brd ff:ff:ff:ff:ff:ff altname end1 inet 192.168.1.12/24 brd 192.168.1.255 scope global dynamic noprefixroute eth1 valid_lft 7117sec preferred_lft 7117sec inet6 fe80::c01a:8931:d090:102a/64 scope link noprefixroute valid_lft forever preferred_lft forever ********* 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 6c:cf:39:00:5f:60 brd ff:ff:ff:ff:ff:ff altname end0 inet 192.168.1.13/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 7139sec preferred_lft 7139sec inet6 fe80::9613:19ef:65b4:eb8d/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 6c:cf:39:00:5f:63 brd ff:ff:ff:ff:ff:ff altname end1

Version 20230824-legacy with kernel 5.15.127. Expanded the list of Wi-Fi modules (USB\PCIe). Added DTB for 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).

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).