The limited transfer rates of 200Mbit/s might be caused by a bad cable or a bad connection (dust in the connector ?). The 2.5G interface is unusable because of the missing hardware soldering fix. It doesn't work without it, at least if you connect it to a 2.5G switch. Did you have a look at the processor utilization while accessing the server ? ZFS is certainly a burden on the CPUs and not known as particularly fast. XFS would be an option (I am still using ext4).

Here is my dmesg about ata errors, [115174.042282] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [115174.044617] ata1.00: configured for UDMA/133 [119440.785506] ata2.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x6 [119440.785537] ata2.00: waking up from sleep [119440.785554] ata2: hard resetting link [119440.785705] ata3.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x6 [119440.785741] ata3.00: waking up from sleep [119440.785765] ata3: hard resetting link [119440.785813] ata4.00: exception Emask 0x0 SAct 0x80000000 SErr 0x0 action 0x6 [119440.785846] ata4.00: waking up from sleep [119440.785869] ata4: hard resetting link [119441.249776] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [119441.253555] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [119441.253794] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [119450.515441] ata3.00: configured for UDMA/133 [119450.515514] ata3: EH complete [119450.734103] ata2.00: configured for UDMA/133 [119450.734159] ata2: EH complete [119450.763936] ata4.00: configured for UDMA/133 [119450.763985] ata4: EH complete [119450.869312] ata5.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x6 [119450.869329] ata5.00: waking up from sleep [119450.869338] ata5: hard resetting link [119451.337659] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [119460.873060] ata5.00: configured for UDMA/133 [119460.873117] ata5: EH complete This basically happens every time I do hdparm -Y /dev/the/drives to put them to sleep, whenever they wake up. For some reason, they wake up within seconds, oh well. The 1gbit interface sucks and gives me only 34MB/s, even with the tx on and so on, in the dmesg there is something relevant about it [ 18.692986] r8152 2-1.4:1.0: checksum fail [ 18.693009] r8152 2-1.4:1.0: unable to load firmware patch rtl_nic/rtl8156a-2.fw (-14) [ 18.744799] r8152 2-1.4:1.0 eth0: v1.12.13 [ 18.744919] usbcore: registered new interface driver r8152 [ 18.776374] r8152 2-1.4:1.0 enx646266d00ac5: renamed from eth0 edit: I fixed the rtl_nic files from the latest linux-firmware, now it can load the firmware and says # dmesg |grep r8152 [ 18.094121] usbcore: registered new device driver r8152-cfgselector [ 18.265347] r8152-cfgselector 2-1.4: reset SuperSpeed USB device number 3 using xhci-hcd [ 18.429147] r8152 2-1.4:1.0 eth0: v1.12.13 [ 18.429410] usbcore: registered new interface driver r8152 [ 18.482268] r8152 2-1.4:1.0 enx646266d00ac5: renamed from eth0 # ethtool -i enx646266d00ac5 driver: r8152 version: v1.12.13 firmware-version: rtl8156a-2 v2 04/27/23 But still, iperf3 says barely 200mbit/s, this is on the 1gbit interface. Another laptop towards same server, on same lan same switch gets 950mbit/s. I have the ondemand governor, and cpufreq settings and affinity in rc.local The 2.5gbit interface is unusable, tried many different options, but at most I can get iperf to finish once or twice, but third time it goes down to 0 and dmesg says reset. But I have only a cat 5e to test with. This helios64 doesnt have the hardware soldering fix.

My guess is, the bulk of the GUI issues stems from the version of Mesa being used. Try the one in their repo; https://gitee.com/bianbu-linux/mesa3d/tree/bl-v2.0.y/

@drewcephus hold down the maskrom button, plug in the power, then plug in the data cable to your computer. I am running the cli tool so it is rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=201 Maskrom The light doesn't blink or anything but itll show up as a device there (and when plugged in to the machine initially even)

Collabora's involvement in Open Source XR development continues to grow today as we welcome the libsurvive project, the open source lighthouse tracking system, into the fold! View the full article