Netgate SG-1000 microFirewall

Author Topic: 2.4.0 does not boot without Monitor  (Read 1549 times)

0 Members and 1 Guest are viewing this topic.

Offline kpa

  • Hero Member
  • *****
  • Posts: 1233
  • Karma: +138/-6
    • View Profile
Re: 2.4.0 does not boot without Monitor
« Reply #15 on: October 15, 2017, 04:25:31 pm »
The console initialization is the BIOS/UEFI's job, the FreeBSD boot code that looks for a usable VGA/UEFI console blindly trusts what it's told about the hardware, if there is no console present it will not try to use one nor will it fall back to serial console on its own.

Offline Breezelaters

  • Newbie
  • *
  • Posts: 3
  • Karma: +1/-0
    • View Profile
Re: 2.4.0 does not boot without Monitor
« Reply #16 on: November 06, 2017, 02:10:04 am »
This just happened to me too on a shuttle XPC:
 - Updated the BIOS, but this did not solve the problem
 - Brute forced BIOS settings
-> by disabling the Serial ports the computer boots normally

Does pfsense 2.4 default to Serial and wait for some sort of connection when there is no monitor?

My two cents...

This fixed my firewall not booting after upgrading to 2.4 for me on a Shuttle DH110 mini PC.  Disabling the serial ports allowed it to boot without a monitor attached to the HDMI port.  Thank you!

BlueKobold

  • Guest
Re: 2.4.0 does not boot without Monitor
« Reply #17 on: November 07, 2017, 02:22:32 pm »
The only way pfSense could be perhaps invited, could be that someone is taking the false image, not matching
or according to his hardware, otherwise it is often related to the hardware or BIOS of this hardware.

pfSense-CE-memstick-serial-2.4.1-RELEASE-arch.img.gz    USB memstick installer (Serial Console)
pfSense-CE-memstick-2.4.1-RELEASE-arch.img.gz             USB memstick installer (VGA Console)

pfSense-CE-2.3.5-RELEASE-size-arch-nanobsd.img.gz           NanoBSD/embedded (Serial Console)
pfSense-CE-2.3.5-RELEASE-size-arch-nanobsd_vga.img.gz    NanoBSD/embedded (VGA Console)

Offline Kenni

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: 2.4.0 does not boot without Monitor
« Reply #18 on: December 10, 2017, 03:38:40 pm »
This just happened to me too on a shuttle XPC:
 - Updated the BIOS, but this did not solve the problem
 - Brute forced BIOS settings
-> by disabling the Serial ports the computer boots normally

Does pfsense 2.4 default to Serial and wait for some sort of connection when there is no monitor?

My two cents...

This fixed my firewall not booting after upgrading to 2.4 for me on a Shuttle DH110 mini PC.  Disabling the serial ports allowed it to boot without a monitor attached to the HDMI port.  Thank you!

+1 :)

Thank you so much, there are definitely some compatibility issues with Shuttle PCs and pfSense 2.4...I'm using a Shuttle DS77U with latest v1.05 BIOS, a clean install of pfSense 2.4.2 (with ZFS), and the BIOS configured for legacy boot (no UEFI).

Everything was working perfectly fine when connected to a screen through HDMI, but once I disconnected the screen, the system never booted to a working state. Disabling the two serial ports in BIOS did indeed fix the issue.

I don't know when pfSense/FreeBSD starts catching ACPI calls (like when you press the power button), but I did notice that when the system wasn't able to boot, a click on the power button resulted in an instant (hard) shutdown. When the system booted successfully, a click on the power button would result in the OS catching the ACPI call and initiated a proper shutdown. Eg. I assume it starts to respond to such ACPI calls briefly after the kernel has initiated, so it could seem like the kernel never took off. I don't have time for further debugging of the issue at the moment, unfortunately, so this workaround will have to do for now.

Offline NRgia

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: 2.4.0 does not boot without Monitor
« Reply #19 on: January 19, 2018, 02:51:30 pm »
One of the machines is a Shuttle XH110. The same issue happens. And I use the same workaround.

The idea is, I want to use a nullmodem serial cable + usb adaptor to connect to the system, in order to be able to update BIOS, or see errors, without attaching a monitor, keyboard.

I mean, why have a serial console if we can't use it.

From the comments above I see that there is no agreement on where the root cause is, Free-BSD or Shuttle BIOS.

Can anybody help further?
« Last Edit: January 20, 2018, 11:49:20 am by NRgia »

Offline jack290

  • Newbie
  • *
  • Posts: 19
  • Karma: +0/-1
    • View Profile
Re: 2.4.0 does not boot without Monitor
« Reply #20 on: January 20, 2018, 05:53:38 am »
I have a motherboard which displays a manufacturers logo when starting the boot process.  The logo display can be turned off in the BIOS,  and the machine will then boot normally with a monitor attached.   However, the machine will not boot without a monitor attached if the logo display is  turned off. 

I set up the machine, obviously with an attached monitor, with the logo display set to off and it booted just fine.   When using the system I do not have an attached monitor and it took some while to figure out why the system hung at boot without the monitor.   The BIOS default is to display the logo - I found out that the system booted without monitor with BIOS defaults, but not with my seemingly small "tweak".

The BIOS is now set to display the manufacturers logo,  no monitor attached,  and the system boots OK.

This may help,

Regards.

Offline NRgia

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: 2.4.0 does not boot without Monitor
« Reply #21 on: February 02, 2018, 10:14:10 am »
I have a motherboard which displays a manufacturers logo when starting the boot process.  The logo display can be turned off in the BIOS,  and the machine will then boot normally with a monitor attached.   However, the machine will not boot without a monitor attached if the logo display is  turned off. 

I set up the machine, obviously with an attached monitor, with the logo display set to off and it booted just fine.   When using the system I do not have an attached monitor and it took some while to figure out why the system hung at boot without the monitor.   The BIOS default is to display the logo - I found out that the system booted without monitor with BIOS defaults, but not with my seemingly small "tweak".

The BIOS is now set to display the manufacturers logo,  no monitor attached,  and the system boots OK.

This may help,

Regards.

I don't see any boot logo on Shuttle pc's, and there are no options to disable the logo anyway. The ideea is, if it was a hardware issue, why the console via com ports it's working on Linux ?