Crash on first boot

[Heathy65]

I have a brand new PICO PC (MNHO-073) with 2G RAM (soon to be upgraded to 4GB) and a 120GB SSD.  I have downloaded 20.7 and used Rufus to write it to a USB memory stick.  When I turn the solution on it boots fine, getting to the normal/initial dialogue.  However it crashed soon after, consistently (n the same place).  Once crashed it's completely dead (caps lock on/off not responding).  After a power cycle the same happens.

See attached for the output prior to the crash.  Any thoughts appreciated.

Thanks in advance.

[bartjsmit]

I have downloaded 20.7 and used Rufus to write it to a USB memory stick.

Which image did you use? DVD, VGA, Serial or Nano?

Bart...

[Heathy65]

I have used this one

OPNsense-20.7-OpenSSL-vga-amd64.img.bz2

Thanks

[Gauss23]

Boot method UEFI?

[Heathy65]

Yup UEFI.

Actually I think I might know what this is.....

The last line on the display prior to the apparent crash relates to a UART (so reasonable to assume it's something to do with com. ports?).  My unit has both HDMI and a console/com. port and I am using the HDMI (and a USB keyboard).

I am wondering if there's actually no crash, but it's just flipping over to the serial connection and 'away' from the HDMI and keyboard as it boots.

I'm going to plug my PC into console port too, to see.  Also I will try disabling the com. port in the BIOS as another option.

[hfvk]

I had this same issue after I upgraded system's UEFI BIOS few weeks ago. The system did not boot without display connected to the system. With a display, the system booted up perfectly.

My workaround was to disable COM ports from the machine BIOS. Not a perfect solution but works since I don't need them.

[Heathy65]

Ah you I think your scenario is a bit different to mine.  I have the HDMI/keyboard connected and always get a boot, to just past the OPNsense menu, then the display stops.

I have tried disabling the serial port in the BIOS and that doesn't change things.
I have also just tried the 'serial' version of OPNsense (having reenabled the serial port, of course) and still no output on the serial connection.

I think I need to check the wiring on the serial port (it's an RJ45 port), I'm using a standard Cisco RJ45-DB9 cable and have tested it and the serial-USB adapter on another bit of kit.

Other thing I will try is something like pfsense just to see if it's an OPNsense specific issue.

[Heathy65]

So I just tried pfSense and it's exactly the same

[Heathy65]

So I think the console is a red-herring (I now have the exact same behaviour for HDMI or console configuration).   I temporarily installed W10 on the hardware (just to see if there's anything wrong with the hardware) and that's all good, seems to run fine.

Back with OPNsense now, playing with BIOS settings to see if any tweaks will prevent the crash.

[Heathy65]

For anyone else with this issue, I got the fix in the end.

BIOS configuration change.

Advanced -> IT8613 Super IO Configuration -> CIR Controller Configuration -> CIR Controller = Disabled