GeorgeP

With my OPi3 powered from the 'genuine' power adaptor via the power jack I'm not seeing any voltage issues. On no load I see 5.2v at the USB sockets..

Are you really considering building an madm RAID with USB drives? Technically it is possible but I doubt you'll get anything but problems with reliability. It's easier than you may think to compile yourself - check out https://docs.armbian.com/Developer-Guide_Build-Preparation/ If you're looking to 'play' with mdadm as a learning exercise then fine, but if you really value your data I'd suggest you should build a 'proper' raid using an x86 board and good quality SATA drives. On budget SoC boards I'd just rsync my precious data across several physical drives.

There's clearly more to this than it seems : I found this article from back in 2016, which then led me to here. And so now: george@orangepi3:~$ sudo dpkg-reconfigure iputils-ping george@orangepi3:~$ ls -l /bin/ping -rwxr-xr-x 1 root root 73280 Aug 3 2018 /bin/ping george@orangepi3:~$ ping google.com PING google.com (216.58.208.174) 56(84) bytes of data. 64 bytes from lhr25s09-in-f174.1e100.net (216.58.208.174): icmp_seq=1 ttl=57 time=28.7 ms 64 bytes from lhr25s09-in-f174.1e100.net (216.58.208.174): icmp_seq=2 ttl=57 time=76.7 ms What the ???? The discussion thread goes on (and on..) but this is getting a bit beyond me

I just went to build a new image for my OPi3 and found that the 'Buster' option has appeared - I just had to go for it! Everything seemed to have built OK and once I'd applied the WiFi 'fix' from here I was up and running. The issue I've found is that I was unable to ping anything : george@orangepi3:~$ ping 127.0.0.1 ping: socket: Operation not permitted This seems to be because the ping binary apparently should have the SUID bit set, so : george@orangepi3:~$ which ping /bin/ping george@orangepi3:~$ ls -l /bin/ping -rwxr-xr-x 1 root root 73280 Aug 3 2018 /bin/ping george@orangepi3:~$ sudo chmod +s /bin/ping george@orangepi3:~$ ping 127.0.0.1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.118 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.127 ms ^C I don't know if this is an issue with the Armbian build process or perhaps it is being echoed from the Debian Buster sources, and so I'm not sure how/where is the correct place to report it

If it's important - Backup, backup, backup!

Erm... Careful people, that link is to nightly images for the OPi One Plus and not the OPi Three

Guys please remember that this is still very early (alpha) software, and is hi-res video such a high priority? IMHO you need to give the devs some time to look at issues like this - and many of us like to relax at the weekend 🙂

Hi Guys, I'm new to the forum here but have been using [only] Armbian on my various OPi boards for some time. I'm now waiting for an OPi3 board to arrive from Aliexpress and so I've been following this thread with interest. I've now successfully built Stretch images from the dev sources but with no hardware yet to test I'm restricted to keeping up with the posts on here. Many thanks to everyone who has already contributed to what I reckon is going to be a pretty awesome board for the price. George Somerset, UK