New DietPi for VisionFive2

DietPi for Mars has been updated and now works correctly even with the graphical interface. This should be good news for Milk-V which can now save itself the trouble of providing us with snapshots full of bugs that are of no use to anyone.

DietPi_VisionFive2-RISC-V-Sid.img.xz

Did you have any issues with the USB ports? The USB2.0 port in particular?

No, I didn’t realise anything but for now I’ve only used mouse and keyboard.

In the next few days I will try audio via USB, which is the reason why bugs prevent me from using snapshots.

I just flashed it. You’re right. USB 2.0 ports are not working

The new version will be released in two days:

For now they haven’t updated the images, they are still the old ones:

https://dietpi.com/docs/releases/v9_0/

I have updated DietPi to version 9 and it seems like USB 2 goes at 480 Mbps. The graphic environment however has regressed.

Remember that of the USB sockets to the right of the network connector, only the lower one works.

Linux mars 6.1.73 #1 SMP Fri Jan 19 23:20:26 UTC 2024 riscv64 GNU/Linux
christian@mars:~$ lsusb -tv
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:3431 VIA Labs, Inc. Hub
        |__ Port 001: Dev 006, If 0, Class=Vendor Specific Class, Driver=[none], 480M
            ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277]
        |__ Port 002: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 046d:c52f Logitech, Inc. Unifying Receiver
        |__ Port 002: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 046d:c52f Logitech, Inc. Unifying Receiver
        |__ Port 003: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 248a:8367 Maxxter Telink Wireless Receiver
        |__ Port 003: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 248a:8367 Maxxter Telink Wireless Receiver
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
christian@mars:~$ neofetch
       _,met$$$$$gg.          christian@mars 
    ,g$$$$$$$$$$$$$$$P.       -------------- 
  ,g$$P"     """Y$$.".        OS: Debian GNU/Linux trixie/sid riscv64 
 ,$$P'              `$$$.     Host: StarFive VisionFive V2 
',$$P       ,ggs.     `$$b:   Kernel: 6.1.73 
`d$$'     ,$P"'   .    $$$    Uptime: 11 mins 
 $$P      d$'     ,    $$P    Packages: 590 (dpkg) 
 $$:      $$.   -    ,d$$'    Shell: bash 5.2.21 
 $$;      Y$b._   _,d$P'      Resolution: 1366x768 
 Y$$.    `.`"Y$$$$P"'         Terminal: /dev/pts/0 
 `$$b      "-.__              CPU: (4) @ 1.500GHz 
  `Y$$                        Memory: 86MiB / 3872MiB 
   `Y$$.
     `$$b.                                            
       `Y$$b.                                         
          `"Y$b._
              `"""

From today the new image is available, it is no longer necessary to download the previous one and update it:
https://dietpi.com/downloads/images/testing/DietPi_VisionFive2-RISC-V-Sid.img.xz

I haven’t had any luck with DietPi on my CM Lite’s. MilkV image (mars-cm_debian-desktop_sdk-v3.6.1_cm4-io-board_sdcard_v1.0.6.img) works but DietPi seems to use a different partition setup that the official image. I was able to combine the MilkV and DietPi images by overwriting the root partition. This made DietPi boot but without networking. Trying to remedy that was fruitless as both the serial interface and USB/HDMI didn’t respond to using my arrow keys to try and navigate the setup menus.

Not sure if I need to flash uBoot perhaps like on VF2 though opted to hold off on that for now since the official image, though a far cry from DietPi (I run one on a PINE and it’s great), does work “out of the box”.