Although 4K@30fps is supported and we have improved the desktop performance, there is still frame drop issue during video playback . Thus, it is recommended to switch to 1080p60 resolution for a smooth video playback experience.
Advised to update u-boot binary if booting from QSPI in order to support multi-kernel switching at bootmenu.
Please avoid runningapt upgradeas it will override the existing customized mesa and linux-libc-dev versions provided.
This debian image contains FFmpeg, Firefox and VLC by default.
Please update the SPI flash to the latest SPL/U-Boot binaries if you would like to try nvme booting (set boot mode as QSPI boot).
I installed SD card image and it’s working fine.
I installed nvme ssd image but it’s not working.
I saw the ssd image size is half oh SD card image size.
Will we have a new ssd image ?
cd /home/user/Downloads; chmod u+x ./install_package_and_dependencies.sh;././install_package_and_dependencies.sh
apt-get install btop neofetch
rebooted
Ok after all that, I went into system monitor and checked out the memory at my disposal.
BUG REPORT it was indicating 4GB instead of 8GB.
I recall others resolving this issue long ago.
Here’s the link indicating there was a way to fix this:
Here’s the actual recipe:
I pasted the steps in case you can’t reach github.
Hi,
If anyone still experience this type of bug even with updated softwares, this is what I was adviced to do when fixed mine:
1. Decompile your source dtb:
`cd /tmp; dtc -I dtb -O dts /sys/firmware/fdt -o vf2.dts` # on system booted up, or place path to your dtb in place of `/sys/firmware/fdt`. Ignore any warnings it produces. If `dtc` tool is not installed, try installing it: `apt install device-tree-compiler` or how dtc is named in your distro. Alternatively, `dtc` from Linux kernel tree also can be used (you have to run `make menuconfig` first to produce executable).
2. Edit vf2.dts: Find section which starts with `memory@4`. Your line of interest is `reg = <0x00 0x40000000 0x01 0x00>;` or `reg = <0x00 0x40000000 0x1 0x00>;`. You shall replace it with `reg = <0x00 0x40000000 0x02 0x00>;`. Notice `0x02` and not `0x01`.
3. Compile file back: `dtc -I dts -O dtb -o /boot/dtbs/starfive/vf2.dtb vf2.dts`. Again, if no errors and only warnings, you're good to go.
4. Boot with modified `vf2.dtb`: in U-Boot prompt you might want to `setenv fdtfile starfive/vf2.dtb` followed by `saveenv`. YMMV.
It worked fine for me this way.
Neither of the ethernet ports work for me.
I have the 8GB VF2 V1.2 (100MB and 1GB ethernet) and used the micro SD image.
Went back to the March image, and ethernet works.
Here’s what it looks like on my laptop:
cissy@cissy-flex5-fc38sb:~/Downloads$ grep -n -H “Device:” AmdRyzen5_glxinfo.txt
AmdRyzen5_glxinfo.txt:53: Device: AMD Radeon Graphics (radeonsi, renoir, LLVM 17.0.6, DRM 3.57, 6.8.9-200.fc39.x86_64) (0x1636)
cissy@cissy-flex5-fc38sb:~/Downloads$ grep -n -H “OpenGL renderer string:” AmdRyzen5_glxinfo.txt
AmdRyzen5_glxinfo.txt:75:OpenGL renderer string: AMD Radeon Graphics (radeonsi, renoir, LLVM 17.0.6, DRM 3.57, 6.8.9-200.fc39.x86_64)
Bottom Line: I don’t see any VF2 hardware rendering happening yet. VF2 seems to still be using software rendering as explicitly stated with softpipe. Please correct me if I’m wrong.
I would like to highlight: Failed to load ‘/dtbs/starfive/jh7110-starfive-visionfive-2-v1.3b.dtb’ /dtbs/starfive: doesn’t exist (-2)
Actually further down it does load something successfully: Retrieving file: /extlinux/extlinux.conf 1386 bytes read in 7 ms (193.4 KiB/s) U-Boot menu 1: Debian GNU/Linux bookworm/sid 6.6.20-starfive 2: Debian GNU/Linux bookworm/sid 6.6.20-starfive (rescue target) Retrieving file: /initrd.img-6.6.20-starfive 10402331 bytes read in 455 ms (21.8 MiB/s) Retrieving file: /vmlinuz-6.6.20-starfive 9521399 bytes read in 417 ms (21.8 MiB/s) Retrieving file: /dtbs/6.6.20/starfive/jh7110-starfive-visionfive-2-v1.3b.dtb 54960 bytes read in 12 ms (4.4 MiB/s) [ 0.000000] Linux version 6.6.20-starfive (root@leo-virtual-machine) (riscv64-unknown-linux-gnu-gcc (g2ee5e430018) 12.2.0, GNU ld (GNU Binutils) 2.40.0.20230214) #1 SMP Sun May 5 22:39:25 CST 2024
Nobody said, flashing the new firmware would do anything with rendering. It fixes the memory detection and perhaps other init problems because the DTB is not correctly found if u-boot is not the current one.
That article is not about the visionfive 2 at all but about general SDL usage. That’s not applicable here because the GPU drivers for the VF2 are not in a really working state and that is the reason for it not to work.
EDIT:
I’m writing a game myself currently and that one is using SDL2 too. Well, compiled it on my VF2 and it works…slow, but it works. So that is this time not related to the GPU drivers in general.
I was also having trouble with the same problem.
By the way, today I was able to resolve the above issue and get it working from NVME.
The solution is to copy the SD’s OS partition to his NVME’s OS partition.
Not really. Open source drivers are in 6.8+ and the image as 6.6.20 has the newest kernel with the closed source driver in it (unchanged since 5.5 kernel series as far as I know).
Tho, if you look at the webgl sample page you’re getting approx. 7 fps on aquarium with the default settings (1000x1000, 500 fish). But still softpipe rendering.
My guess is, that it only will get better when the new mesa integration and the open source drivers are mature enough which, as far as I understood, is not the case yet.
