• Content Count

  • Joined

  • Last visited

About johanvdw

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Okay, perhaps I should limit the scope: is there an sbc (or set top box) which can take hdmi in and encode it? I have seen orangepi rk3399 has an input port, but is it supported?
  2. Hi, I wonder if anyone has experience using an sbc (or tv box) for remote controlling a server. I think the necessary pieces are there on many boards (many have camera inputs which could perhaps be used for video, it looks like some even have an hdmi in). I found this [1] project, but it uses some extra hardware I'd like to avoid. Has anyone done anything similar? Note I'm mostly looking into this to gain knowledge, not to put this in production in a real world situation.
  3. Too late now, but I save all of my configuration using etckeeper . You will not regret doing the same.
  4. You don't need to specify hwaddress if you use kernel 5.0 or later, as the changing mac address was addressed.
  5. HDMI audio for H6 is not yet supported in the mainline linux kernel, and nobody is currently working on it --> see
  6. I don't think you need the whole config, the commit which fixes reboot is just this one:
  7. If you have a connection from linux to linux, you could also consider wireguard. It performs much faster than openvpn.
  8. AFAIK openvpn only uses one core, not sure how this is on ARM, but at least on intel, it would mean that only one core is actually on a high frequency.
  9. You can actually override the mac address in your networking configuration. This is how I do it: edit /etc/network/interfaces and add eg: auto eth0 iface eth0 inet static address netmask gateway dns-nameservers hwaddress ether 69:de:92:ea:1f:e9 And then disable network manager and reload networking: systemctl disable NetworkManager systemctl restart networking For me the major remaining issue to use this is the fact that the board still shuts down on reboot.
  10. I did some more measurement using that case. Moving the fan to 3.3 volt makes it virtually silent (I hardly hear it at 1m distance). Under full load (armbianmonitor -z in a loop) power consumption actually is never above 4W, so I think that with a large heatsink you could probably keep this cool even passively. Anyway, with that case and a tiny ceramic heatsink (one similar to these one ) CPU temperature stayed below 65 (with the fan is at 3.3 volt). With a slightly larger heatsink temperatures would remain even cooler I guess.
  11. I have tested that kit, though with another heatsink. It kept temperatures below 50°C but was a bit noisy. I'm going to try if it still performs well at 3.3V instead of 5V.
  12. I ran this on a 5.0.2 kernel, and the results are even better: johan@orangepioneplus:~$ openssl speed -evp aes-128-cbc Doing aes-128-cbc for 3s on 16 size blocks: 22994546 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 64 size blocks: 18305176 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 9596358 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 3415788 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 8192 size blocks: 490837 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 16384 size blocks: 247789 aes-128-cbc's in 3.00s OpenSSL 1.1.0j 20 Nov 2018 built on: reproducible build, date unspecified options:bn(64,64) rc4(char) des(int) aes(partial) blowfish(ptr) compiler: gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS -DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/lib/ssl\"" -DENGINESDIR="\"/usr/lib/aarch64-linux-gnu/engines-1.1\"" The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-128-cbc 122637.58k 390510.42k 818889.22k 1165922.30k 1340312.23k 1353258.33k I don't really know how to interprete this numbers, but for 8192 and 16384 bytes, this even beats my i7-7500U, which I find strange.
  13. I can confirm this works for me as well. It might be useful to say you should also run boot after these commands to continue booting.
  14. Ok, found it myself:
  15. And what would be the recommended way to go back to a previous version (without starting from scratch) (Quite sure this is somewhere in a FAQ, but I had no luck finding it)