Sorry for the delay,
Ive tried a few different power supplies, my laptop uses a usbc 65w charger and I have another generic adapter which claims to be 60w. Unfortunately I dont have a usb power monitor so I cant know for sure what the h618 is getting, but my phone goes into fast charging mode on both adapters, and my laptop seems to treat both equally too.
65w seems a bit overkill for this board anyways, so I made up a 15w 5v regulator to power the board via GPIO (which is how I’d ideally use this board, but I for what I have in mind it wouldn’t be a huge deal to add a usbpd source module)
Im not physically close to my router, so Im sharing the connection via my windows computer (from which Ive been using sd card foramtter and win32 disk imager.) My laptop (linux) has no issues connecting to the internet through all these dongles.
I also found my mini hdmi adapter, although unfortunately I cant capture HDMI.
Having said all this, Im still facing issues.
DietPi is getting somewhere, Ive gotten it to boot but never on the first try. It doesnt really output anything on the serial console, just what I was seeing before and then maybe eventually a login prompt. HDMI shows that its making it through resizing the disk (occasionally it freezes here after the resize itself finishes. If it takes longer than 20min to expand the filesystem 16gb, especially if the heartbeat/cursor stops, I consider it to have failed). Generally it makes it pretty far, it seems to get stuck at time-set.target - System Time Set
, the heartbeat keeps going and the cursor is blinking, but after a long time there is no progress.
After many attempts, I get it to boot. Those 3 packages are already held, (I ran the command to mark them as held anyways) and apt upgrade ignores those packages. I also set the governor to conservative, but its still running uncomfortably warm. Im using the heatsink that came in the kit, Ive been working to get my 3D printer going again, and when that happens Im going to work out how to get a fan to cool the board too. (Unfortunately my seller seems to have sent me the wrong metal case and the metal lugs dont line up.)
Maybe it gets too hot during boot? The room im testing in isnt particularly warm, but that might explain why it boots pretty consistently after the governor is set to conservative.
Once it boots, it boots fairly consistently. It just takes a while (45+ seconds) for it to start the networking hardware (something like Job ifup@eth0.service
) Different power supplies dont seem to have an effect. I have an img that boots, so I just dd that back onto the sd card if/when something breaks.
Here is a benchmark from that img:
Generic Device (aarch64) | IP: fe80::205:1bff:fe95:d32e
┌──────────────────────────────┤ DietPi-Config ├───────────────────────────────┐
│ DietPi-Benchmark | https://dietpi.com/survey#benchmark : │
│ - CPU Performance : Duration = 10.74 seconds (lower is faster) │
│ - CPU Temp : Idle = 61'c | Full load = 90'c │
│ - RootFS : Write = 6 MB/s | Read = 20 MB/s │
│ - RAM : Write = 610 MB/s | Read = 737 MB/s │
│ │
│ Additional benchmarks: │
│ - Custom Filesystem : Write = Not tested MB/s | Read = Not tested MB/s │
│ - Network LAN : Transfer rate = Not tested MB/s │
│ │
│ ●─ DietPi-Benchmark ──────────────────────────────────── │
│ DietPi-Benchmark : Starts CPU, RAM and IO benchmark suite. Scores can be │
│ ●─ Additional benchmarks ─────────────────────────────── │
│ Custom Filesystem : Benchmark IO performance from a selection of mounted d │
│ Network LAN : Benchmark LAN performance using 2 DietPi systems. │
│ │
│ │
│ <Ok> <Back> │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
( Interestingly, im unable to shutdown the system. Reboots work, but shutdown errors out:
root@DietPi:~# shutdown
Failed to connect to bus: No such file or directory
)
I havent had any success with armbian. It always seems to get stuck while booting. After imaging the sd card, it always gets stuck at Starting Journal Service...
or [ *** ] A start job is running for Armbian memory supported logging (3s / 29s)
. Power supply didnt really seem to make much difference here.