I had a look into the wireguard package. The way it’s setup in Debian is incompatible with “vendor” kernels unfortunately.
The sophgo kernel should already have wireguard support so you just need to compile the wg cli. If you run into challenges there let me know and I’ll try to package something specific for the milk-v
I’ve seen you issue but just not had the time to investigate it.
I did not know that the kernel had wireguard support. This board seems like the perfect device for creating a wireguard “hotspot” for example. It could connect as a wireguard client through ethernet and the wireless could serve as an AP. Or a remote but local camera.
Or a wireguard “backdoor” server if anyone is into this sort of thing 
less than 1 watt…
Just because I wanted to see if it could do it: this is HWInfo64 running on the DuoS using box64 and wine64 - on the debian image.
lol. This is so crazy I love it!
So some of the LicheeRV Nano images also contain framebuffer support but between the diffirent images some utilities are missing, i did test with the official display, but the provided flex cables are quite short.
I was hoping to be able to see bootup but this is still missing (dtb)
dmesg | grep fb
[ 2.749994] fb0: reserved mem: start: 0x8b10c000, size: 0x1f4000.
[ 2.750008] fb0: res-reg: start: 0xa088000, end: 0xa088fff.
[ 2.764670] fb0: init per current timing (800x1280)
[ 2.764916] fb0: cvifb frame buffer device
[ 2.764924] fb0: scale(0x0) double_buffer(0)
[21:54]
[ 17.674688] <<-GTP-INFO->> GTP driver installing...
[ 17.677990] <<-GTP-INFO->> GTP start add i2c driver...
[ 17.678119] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[ 17.678130] <<-GTP-INFO->> GTP I2C Address: 0x14
[ 17.678271] <<-GTP-INFO->> Guitar reset
[ 17.794928] <<-GTP-INFO->> IC Version: 911_1060
[ 17.815846] <<-GTP-INFO->> X_MAX: 800, Y_MAX: 1280, TRIGGER: 0x01
[ 17.834097] <<-GTP-INFO->> GTP works in interrupt mode.
The cvitek FB support is in the kernel is minimal, and you won’t get a Linux console on it. You can use some of the example QT apps in the sipeed image to output applications on the framebuffer.
Also - it’s quite a hack how they have implemented it. Uboot initializes the MIPI-TX and panel and Linux just uses what ever is configured.
I’ve dropped from my kernel any of the video subsystem drivers (camera/MIPI/ISP). I might add MIPI Tx support back eventually but with a proper kernel driver when we have mainline support in hopefully 6.10
I installed a Logitech Media Server (LMS 9.0) on the DuoS with your Debian. The DuoS is now serving my music collection to my RPI3 running Squeezelite.
Next step would be to install Squeezelite on the DuoS itself. I would like to use a USB DAC dongle as output for Squeezelite. I have therfore to switch the USB ports, can you explain how to do and how to check?
Debian Images for Duo256/DuoS，what is the default username and password?
username debian / rv
It’s in the readme:
Also in the readme: GitHub - Fishwaldo/sophgo-sg200x-debian: Debian Image for SG200x based boards such as Milk Duo256/DuoS and Sipeed LicheeRVNano
One thing I cannot figure out, what is the tunl0 (if I remember correctly) interface on the DuoS?
I’m also not sure. It’s something that Debian or Network Manager sets up by default?
Thanks for your patience. Learning a lot.
I try to mount the USB drive , but no luck > I followed the readme and put some logs in my pastebin. i will read up upon the autofs not loading, but perhaps you have a idea?
Oh. I missed something in the readme.
After disabling the usg-gadget-* service, you need to enable the usb-switch (if your connecting to the TypeA port):
systemctl enable usb-switch
And reboot.
(Could you create an issue on my repo so I don’t forget to update the readme?)
Thanks. Awesome work!
Any luck on the MIPI-CSI/DSI?
Thanks for your efforts. The usb switch didnt work. I dont see the usb device using lsusb.
The pastebin
You have to disable all gadgets (RNDIS/ACM) before using the usb-switch.
You still have ACM gadget enabled:
dwc2 4340000.usb: bound driver configfs-gadget
(Remember to reboot after enabling/disabling)
I won’t be doing any serious work on Mipi DSI till we have a mainline kernel. Unlikely I’ll work on CSI tho - that’s a lot more work, and I don’t personally have a need for it. (I’ll happily include any drivers for mainline that support it though)