11-16-2019, 06:52 PM
(This post was last modified: 11-16-2019, 07:40 PM by ab1jx.
Edit Reason: new paragraph
)
(11-16-2019, 10:08 AM)Rocklobster Wrote: In my experience the one sure way to rule out faulty hardware is to boot from Armbian https://www.armbian.com/rock64/
I've booted at least six boards that were supposedly dead this way. It's a works out of the box solution.
Yup, thank you, worked like a charm. Went to write my Ayufan image over again and discovered I used a Rock64Pro image instead of a Rock64 one.
Well, the Ayufan image apparently still doesn't boot. But I can't tell. Nothing on the screen, monitor says no signal, and I can't ping it over wifi. I suppose I could stick some script oneliner like
touch booted.txt
in there somewhere and look for a booted.txt file.
I'm wondering if I still need to fiddle with an EDID file. This monitor is newer, it's a Dell SE2216, works with more things. I don't have hardwire internet but I suppose I could dig up a crossover cable. I do know where my serial/debug cable is, I'd need to look up how to connect it. Or it could be booted to some question and won't get past that until I answer it.