I have a PC Engines apu6b4 that is acting up during the installation process. I want to see if this group has any insight before I try an RMA with the seller.
The apu6b4 (https://www.pcengines.ch/apu6b4.htm) runs an AMD processor and has the standard ports. It uses a micro-USB serial port rather than an RS-232 interface. When loading the 7.3 release installer, I get to a point where "entry point at 0xffffffff8100100" is printed before the device loads the BIOS and starts the POST / boot process again. There isn't much output to use for clues. I run current on an apu2, so I'm wondering if it's the apu6b4 model generally or just my example that is the problem. For comparison, I tried loading Debian stable as well and found that it got partially into the text installer before appearing to hang when I selected a "video" mode. Note that I've never done a serial console installation of Debian. It may be expected behavior. Does anyone have guidance on how to proceed with investigating the problem? Has anyone run OpenBSD on the apu6b4? Here are some relevant screenshots: https://star.sw.gy/pub/boot-loop-1.png https://star.sw.gy/pub/boot-loop-2.png https://star.sw.gy/pub/debian-installer-1.png https://star.sw.gy/pub/debian-installer-2.png Here's the captured output from the boot loop I mentioned: SeaBIOS (version rel-1.12.1.3-0-g300e8b70) Press F10 key now for boot menu Booting from Hard Disk... Using drive 0, partition 3. Loading...... probing: pc0 com0 com1 mem[639K 3325M 752M a20=on] disk: hd0+ hd1+* >> OpenBSD/amd64 BOOT 3.55 boot> cannot open hd0a:/etc/random.seed: No such file or directory booting hd0a:/7.3/amd64/bsd.rd: 3924676+1647616+3886216+0+704512 [109+440424+293 778]=0xa667f0 entry point at 0xffffffff8100100PC Engines apu6 coreboot build 20202509 BIOS version v4.12.0. -- RD
