Crash on startup

[leony]

I am very new to Opnsense and purchased a new mini PC with specs below:

Intel Quad Core N100, DDR5 8GB RAM with Intel I226-V Ethernet Controller

However almost everytime I reboot Opnsense it is either stuck at Boot (where it says autoboot 3,2,1, the screen is stuck at 3) or enters kernel panic.

I checked this forum for some solutions, applied suggestions about Bios settings etc.

I replaced the SSD, did memory test, still the same result.

Opnsense seems to work fine when running (I tried 1-2 hours by connecting to the internet) however when rebooted, system crashes.

Where do I start from please? You may request some log files, at what stage and from where do I need to provide them?

[cookiemonster]

I suggest to do a search on this forum for N100. Seems to have to have a firmware that is up to date.

[meyergru]

If you cannot get a BIOS update from your vendor that fixes it, return the device and buy another brand.

[leony]

Thank you for the information, I was not aware of such a problem. Do you recommend a particular mini PC with similar spec or CPU model?

[leony]

If you cannot get a BIOS update from your vendor that fixes it, return the device and buy another brand.

I have got a BIOS update

The crash seems to be fine now however this time every time I reboot, after the BIOS beep, Opnsense does not load?

If I power off the system and turn on, Opnsense loads with no issues. Do you recommend another clean install?

Is there something else I should do?

[cookiemonster]

It sounds like an bios boot device ordering problem. Reboot with monitor/keyboard attached. Check the boot order is set to the disk with OPN installed. Also check that your install is BIOS or eFI and the selection on BIOS must match.

[leony]

Thanks, I've checked and there is only 1 x NVme Drive + with UEFI

I have disabled the boot logo, now I can see attached Image 1 (before this, the screen was blank). Every time I reboot the system, from this stage it does not go forward to the login page.

However, Opnsense boots fine in the end and I can access to the web interface with another device (Image 2)

This now only happens on reboot. If I power on + off, everything works fine.

Let me know the possible causes pls.

[cookiemonster]

All I can guess is that the console needs waking up but that is actually "there". I can't think of a way the console would be only available on boot but not reboot.
Can you try that, reboot, wait for the time when you can get to the UI so the system is fully initialised, then use the keyboard to see if the console (the login prompt in this case) comes up?

Or at a wild guess on a reboot if you are using EFI, that maybe there's a buffer variable kept and is not initialised ? Truly wild guess, thinking aloud here.

[leony]

All I can guess is that the console needs waking up but that is actually "there". I can't think of a way the console would be only available on boot but not reboot.
Can you try that, reboot, wait for the time when you can get to the UI so the system is fully initialised, then use the keyboard to see if the console (the login prompt in this case) comes up?

Or at a wild guess on a reboot if you are using EFI, that maybe there's a buffer variable kept and is not initialised ? Truly wild guess, thinking aloud here.

Thank you, if anyone else has a suggestion I will appreciate. As I said I am new to Opnsense, if I have to send the hardware back and get another one, I will do so.

[cookiemonster]

did you try my last suggestion, what was the outcome ?

[leony]

did you try my last suggestion, what was the outcome ?

Yes your solution has worked. I removed the USB  mouse (kept the keyboard on) and rebooted the system. I can now see the console.

I am not asking the reason (do I need to know?) At the end of the day we would need keyboard, not the mouse using the console?

[cookiemonster]

good. Yes you need keyboard/monitor for console but I imagine you can remove them and plug them back in when required and the console will simply appear again when you "wake it up" with key presses. In reality is not "asleep" nor missing.