On 2022-04-13, misc.99...@aleeas.com <misc.99...@aleeas.com> wrote: > > It sounds like you're trying to use the 32bit OpenBSD installer for a >> 64bit cpu. In that case, you would want the AMD64 installer.
Even if that is the case, it's not very likely to change the ACPI parsing. > As far as I remember the CPU is only 32-bit capable. But outputs I gathered > from Linux is telling me otherwise (given below). CPU spec sheet says it could support it, but maybe it's disabled by BIOS. IIRc 64-bit mode on some of the Atoms does not work brilliantly anyway. > To give it a shot, I just tried to boot amd64 install70.img (sha256: > 6bc7f945c2709247d449892c33c0f1b9a31590528572c1e988fef4a7637210e6) on the > machine and this time it didn't even get to kernel panic stage. > > Using drive 0, partition 3. > Loading..... > probing: pc0 mem[634K 2035M a20=on] > disk hd0+ hd1+* >>> OpenBSD/amd64 BOOT 3.53 > boot> > cannot open hd0a:/etc/random.seed: No such file or directory > booting hd0a /7.0/amd64/bsd.rd: 3830471+1598464+3907256+0+704512 > [109+288+28]=0x995530 > entry point at 0xffffffff81001000 > > Then it stops. Pressing Ctrl+Alt+Del or any key doesn't do anything. Only way > is to press the power button to force shutdown. The two main causes of this: - booting on serial console without "set tty com0" in the boot loader - trying to run amd64 on a machine that only supports 32-bit
