LAN/NIC problem

[tkaiser]

I tried this on my Diet-Pi image.  It didn't make a difference.

• if your board is affected by the GbE issue then it's useless to play around with cpufreq governor. Only work-around is to force Fast Ethemet, only solution is to get the board replaced
  
• DietPi does not use cpufrequtils anyway, there you would have to use 'dietpi-config' to adjust settings. David (DietPi lead) switched some time ago to Armbian as build system on all SBC != Raspberry Pi (so at least relevant kemel patches are incorporated into DietPi) but to be honest I've no idea which cpufreq governor he uses on Pine64 but I fear it's also ondemand (I tried to convince him a while ago from ondemand being a really bad choice for Allwinner BSP kernels, maybe he fixed that in the meantime)
  
• The whole issue here is about one person claiming SBC are not able to exceed laughable 12MB/s due to bus restrictions or whatever. While the real problem is that wrong default settings used with most of the available OS Images prevent higher numbers. Here it's software (settings) that matter, in your case it's a hardware issue. I just wanted to point out (obviously to no avail again) that it's necessary to look for bottlenecks individually since otherwise you have no clue why network performance sucks if network performance sucks
  

Anyway, useless to continue. TL Lim seems to be able to identify the issue now, maybe all affected boards get replaced, maybe new boards are tested before they're sent out, maybe broken OS images will be fixed, maybe this micro community will be able to dismantle from this strange micro reality