If you haven’t gotten the image yet, this magnet link to the torrent should work without having to login to the google drive.
magnet:?xt=urn:btih:a991922ddc1fa303c5182628264e003c4c1aa092&dn=starfive-jh7110-VF2-VF2_515_v2.3.0-55&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A6969%2Fannounce
Hello together,
now the Debian starfive image runs with wifi ESR 6600u.
My other wifi dongle doesnt work because they need additional kernel options.
So I have the SDcard which matches both SHA sums, and the F***** thing doesn’t boot from SD card. Looking at the partition map, it’s obvious why it won’t boot. There is a note on the GitHub sdcard.img which says what is needed to boot from SD; and the bootloader for this isn’t in that configuration, so I get nothing but:
BOOT fail,Error is 0xffffffff
You literally make the board and left the note in the reference image. This feels deliberate.
Hello LewisCowles
Pretty poor advice really though. (To be clear I’m pointing at this being inconsistency from the manufacturer).
Why for my visionfive2 it works. I can only say what i did when i had this error 
You will find boot jumpers on board. See other topic in this forum.
I Had to change the jumpers in order to get it to boot from the SD in the first place. With the standard images (all other images I’ve tried) it boots. It’s just this debian image from the team, then needing different jumpers seems like an awful experience. If They really are using us as guinea pigs, then we should feed back to them, just how poor this experience is.
Post boot in SPI Flash mode, HDMI works, cursor works, and then the whole thing locks up. No output from SPI unfortunately, no login in GUI, keyboard input only via Putty / COM port forwarding.
Hi.
I flashed the image on a sdcard with Raspberry Pi imager. Its as easy as flash RPi images. After insert the card and power the board, it boots flawlessly. Login as root, then add an user. Connect the ethernet network and install some software to test the repository (synaptic and gparted -btw it doesn’t work). I’ve tried libreoffice calc which run decently. I’m writing down this lines with firefox on the Vision Five 2.
Can anyone else confirm if they have this?
[+0.02s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fre edesktop.Accounts was not provided by any .service files
[+0.02s] DEBUG: Loading user config from /etc/lightdm/users.conf
I’m going to try a re-flash (again), but the image verified. I’ll also try another MicroSD just-in-case
Also seeing
root@starfive:/var/log/lightdm# cat seat0-greeter.log
** Message: 22:03:24.265: Starting lightdm-gtk-greeter 2.0.8 (Aug 17 2021, 15:44:22)
** Message: 22:03:24.266: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf
** Message: 22:03:24.266: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
Excess arguments.
(lightdm-gtk-greeter:662): Gtk-WARNING **: 22:03:29.618: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)
can you tell any more about your setup? Are you using TTL adapter, what power-supply, brand of microSD or eMMC?
-About TTL adapter. No. I’m not using such a thing.
-About the power supply. I’m using the 5 V 6 A purchased with the board on allnet China website.
-The microSD is a 32 GB Sandisk. (flashed with Raspberry Pi imager).
-I purchased a 16 GB eMMC, a reader and the wifi dongle in the same order. The eMMC is now installed on the board and formatted to ext4.
Last night I’ve tried some heavy websites and some desktop configurations to test the overall performance with htop, then i noticed that my board is the 4 GB RAM version. Tried again to check this with “cat /proc/meminfo”,which gave me the same result.
I recommend to check this to anyone who have ordered the 8 GB RAM model.
I’m writing down again this lines with Firefox and the Vision Five 2.
Hello.
I’m trying to connect to a 1680x1050 @60Hz DVI monitor through a DVI-HDMI cable which works perfectly on a Raspberry Pi.
I’ve tried to add the mode with cvt first, then xrandr (–newmode --addmode), but without success when selected.
I keep trying other ways. ¿Can someone give me a clue?.
One of the “Known Issues / Limitation” currently listed in the pdf is “Auto-selection of 4GB/8GB ddr in uboot”, which I interpreted as the software failing somehow to differentiate between 4 and 8 GiB of RAM. Probably best to confirm the part number of 2/4/8GB LPDDR4 chip on the board, and lookup what the hardware really is, at least until the software issue is resolved.
“cat /proc/meminfo” - Using software to check what hardware is there only works correctly when the software is working.
Release jammy-server-visionfive2_20221219 · initdc/rootfs-tools
i tried this image but unfortunately it seems to be missing some functionality (device tree/kernel module?) for display… after setting up kde it get the following when trying to startx (other things seems to run well)
open /dev/fb0: No such file or directory
Hello,
my experience is, boot with SDK shows 8 GB RAM and boot with Debian it shows 4 GB.
I buyed a 8GB board.
Best regards
Damian
Hi,
the -v55 image works on my VisionFive2. Unfortunately, I’m stuck with updating uboot/firmware. There was no procfs, thus I added proc to /etc/fstab. I installed mtd-tools like suggested in the QSG-PDF.
Yet no MTD devices are available, the kernel doesn’t spit out anything usable during booting neither (dmesg | cat mtd).
I really don’t want to setup a tftp environment.
How do I get MTD to start, so I can update the firmware and use the -v69 debian image?
Lost a few hours yesterday only to find out that you are serious about the firmware update. V69 doesn’t boot without the update. I tried switching GPT to MBR on the SDCard and several other things …
Any help here would be appreciated.
Thank you,
Best regards
Dirk
Post Scriptum: The description in the QSG is lacking details on how to boot into tftp at all. Setting to boot switches to UART?
Both ways described do not work to update the firmware.
I had the same case
And wouldnt setup tftp: but finaly did it.
As suggested by @dtometzki i could have compile uboot by myself but wasn’t confident
Then i decided to setup tftp
→ macos (sierra) it is already installed in cli
→ for linux, seems to be one apt install
→ for both you place files in right folder and it should just works
But definitly àll commands in VF2 side were executed through UART.
I have an alternative way if you don’t want to update firmware by tftp.