balbes150

Ver 20230925-current kernel 6.1.31 work HDMI LAN USB etc

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.

Images for Visionfive-2. https://disk.yandex.ru/d/YDBZD53WnCk1Ig Important. For the system to work correctly, you need to update the bootloader in SPI\flash once (the switch for selecting the device to run should be set to “qspi” 0,0 , this is the default state when delivered from the factory). To do this, download the image from the link https://disk.yandex.ru/d/zsqznfa1ySI2gw burn it to the SD card, connect it to VF2 and turn on the power, wait 2 minutes and turn off the power. After that, you can write an ArmbianTV image to the SD card, connect it to VF2 and the system will start automatically. The next steps are usually the initial setup of Armbian. In versions with DE (IceWM XFCE). even video playback in the window works (fullscreen mode does not work) through the Parole player. Analog audio output is enabled by default, to switch to HDMI audio, use the settings via Volume Control as usual.

Test version of images 20230622-legacy for star64. https://disk.yandex.ru/d/eEC4riP1jBWCeg Important. For the system to work correctly, you need to update the bootloader once. To do this, download the image from the link https://disk.yandex.ru/d/zsqznfa1ySI2gw burn it to the SD card, connect it to Star64 and turn on the power, wait 2 minutes and turn off the power. After that, you can write an ArmbianTV image to the SD card, connect it to Star64 and the system will start automatically. The next steps are usually the initial setup of Armbian. In versions with DE (IceWM XFCE). even video playback in the window works (fullscreen mode does not work) through the Parole player. Analog audio output is enabled by default, to switch to HDMI audio, use the settings via Volume Control as usual. root@192.168.1.51's password: ____ _ __ _ _ / ___|| |_ __ _ _ __ / /_ | || | \___ \| __/ _` | '__| '_ \| || |_ ___) | || (_| | | | (_) |__ _| |____/ \__\__,_|_| \___/ |_| Welcome to Armbian 23.06 Jammy with Linux 5.15.115-star64 System load: 3% Up time: 3 min Memory usage: 3% of 3.80G IP: 192.168.1.51 CPU temp: 39°C Usage of /: 17% of 7.1G RX today: 19.4 KiB [ 10 security updates available, 12 updates total: apt upgrade ] Last check: 2023-06-22 12:32 [ General system configuration (beta): armbian-config ] Last login: Thu Jun 22 12:32:24 2023 root@star64:~# 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 root@star64:~# neofetch .-/+oossssoo+/-. root@star64 `:+ssssssssssssssssss+:` ----------- -+ssssssssssssssssssyyssss+- OS: Ubuntu 22.04.2 LTS riscv64 .ossssssssssssssssssdMMMNysssso. Host: Pine64 Star64 /ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 5.15.115-star64 +ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 4 mins /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 509 (dpkg) .ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 5.1.16 +sssshhhyNMMNyssssssssssssyNMMMysssssss+ Resolution: 1920x1080 ossyNMMMNyMMhsssssssssssssshmmmhssssssso Terminal: /dev/pts/0 ossyNMMMNyMMhsssssssssssssshmmmhssssssso CPU: (4) @ 1.500GHz +sssshhhyNMMNyssssssssssssyNMMMysssssss+ Memory: 118MiB / 3893MiB .ssssssssdMMMNhsssssssssshNMMMdssssssss. /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ +sssssssssdmydMMMMMMMMddddyssssssss+ /ssssssssssshdmNNNNmyNMMMMhssssss/ .ossssssssssssssssssdMMMNysssso. -+sssssssssssssssssyyyssss+- `:+ssssssssssssssssss+:` .-/+oossssoo+/-. root@star64:~#

Version 20230401 with kernel 6.2 (pancsf-midstream). With HDMI USB support. https://disk.yandex.ru/d/W8pOOhizVjq91A To enable HW acceleration, install the mesa package with the forced overwrite option or an archive to enable acceleration for wayland. To enable wayland acceleration, you need to replace the files in the /usr/lib/aarch64-linux-gnu directory with the contents of the archive (with file replacement). After that, acceleration will work with wayland. X11 and wayland acceleration works the same way on Debian Sid (the images are the same as Ubuntu). After starting the system and initial configuration, replace the files from the archive in the same way and acceleration will work. The results of running in Debian Sid Gnome for x11 and wayland. dpkg -i --force-overwrite mesa_23.0.0-dev-2_arm64.deb After installation and reboot, HW acceleration will work in x11 and wayland. Please note, this is a test version of mesa for the initial evaluation of the work, some of the functions do not work in it and there may be bugs. With x11, the system works more stably, but the test results are lower than in gnome+wayland. deb\archive https://disk.yandex.ru/d/h8c-Y2FfAvx76g