not really fixing your crash but try disable intelfb0* at the boot prompt. This is a standard workaround for issues with graphics hardware. It will leave you with very basic console graphics, but I'm guessing you plan to just not use the monitor except for configuring. (I don't mean to say fixing this wouldn't be good, just that this might get you going. I have been thinking about protectli devices as my apu2 is getting slower every year :-)
Thanks Greg. I was able to work around it with something similar:
disable i915drmkms*
The side effect is no boot info displayed using a monitor until
you get the login prompt. And yes, I was only configuring it with
monitor, so this workaround is good for now.
Thankfully this device has a builtin serial port I could use for
a serial console, and I was able to get the kernel crash info. I
was able to then realize why the install was frozen with a blank
monitor.
I filed 'kern/58504'.
> I have been thinking about protectli devices as my apu2 is getting slower every year :-)
Yes, same for this older Protectli with its Celeron :-) I had OpenBSD running on it for many years as a router. I recently gave an Intel N100 based device a try with dual 2.5Gb RTL8125 NICs and so far it has been a stable replacement. Amazing what you can get these days for under $200 -- and with a generous return policy if it doesn't work out!
-Joel