animous

Bingo. Worked with USB ethernet! Thanks!!! Now waiting for my serial to usb cable to arrive from China to better understand why my orangepi won't boot when I compile the same .img, but with F2FS instead of ext4. Most likely I'll be posting again in 3-4 weeks.

@Stuxnet: The kernel is getting written as part of the whole image file using Etcher on OSX. @Igor: Wired. Obviously I doubt the CPU is getting used much during that download, but just in case I ran some stress tests (--cpu 4 --vm 1 --io 1 --hdd 1), to eliminate the variable of thermal regulation because of the CPU overheating. All pass.

Running on Virtualbox-compiled Armbian_5.32_Orangepiplus_Ubuntu_xenial_dev_4.11.5.img. I installed docker and am trying to run a pihole container. Because it's a new image, it tries to download it. But it never gets to the end, because it always freezes. OrangePi+ stops answering pings and I have to hard reboot. Here's almost what it looks like before locking up. I've also had it lock up during file transfers, differs from one time to the other. I have a Samsung Evo+ Class 10 32GB. I have tried different 5V/2.4A power supplies. I quickly checked logs in /var/log, but crash, stack trace or anything. Do I have to manually apply the 0001-sunxi-h3-Fix-PLL1-setup-to-never-use-dividers.patch patch from megous/linux when building my image? Any pointers on how to debug and get rid of these lockups would be greatly appreciated. Thanks!