Project

General

Profile

Actions

Bug #6568

closed

NanoBSD image unconditionally enables comconsole.

Added by Bruce Simpson almost 9 years ago. Updated almost 6 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/30/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

OK, first of all, I appreciate the hard work you guys have done on cleaning up the backend implementation.

However, I am in a tight spot. I'm trying to attach a serial timing device, and I have only one serial port on the target device. I installed the NanoBSD VGA image, expecting it would allow me to disable serial -- it does not, in fact, it goes out of its way to unconditionally enable it.

The usual FreeBSD rubrics simply didn't work -- pfSense kept reverting them, e.g. device.hints were ignored after explicitly setting hw.uart.0.flags=0. So, this appears to be by design, and is as documented. (But that royally hoses those of us trying to attach something like an EndRun device in a datacenter!)

After I eventually figured out what was going on, my only fix was to directly edit /etc/inc/pfsense-utils.inc and put 'return;' at the start of the setup_serial_port() function.

I recognise this issue is difficult to resolve portably; many embedded systems have only one serial port. Moreover, many such devices do not have full modem signalling. Many timing devices present the PPS pulse on other RS232 lines, e.g. DCD.

Alternative console devices would provide a suitable escape route. FreeBSD seems to be behind the curve again here now -- e.g. Linux has native support for USB-based consoles, most often as the device end of USB CDC ACM, and of course the better known USB CDC ECM.

Actions #1

Updated by Bruce Simpson almost 9 years ago

This isn't nearly as much of a problem for me right now -- the offending system has been upgraded to use mSATA, through a SATA + 3.3V regulator board.

So I reinstalled pfSense from memstick onto the SSD, reloaded the config.xml, changed the onboard Realtek NIC out for a PCI-X igb in PCI mode. Good to go. No COM1 overcommit.

However, the problem still remains: how do we deal with the situation where we wish to run pfSense on embedded hardware, the NanoBSD image is a better fit for the use case ongoing, and yet the serial ports are unavailable for its use?

Hopefully I can make some headway on USB based console support. This is something that's been in my backlog for years.

Actions #2

Updated by Jim Pingle almost 9 years ago

NanoBSD won't be around for much longer, you're better off with a full install anyhow in the long run. If you activate the option to put /tmp and /var in RAM it isn't all that different from NanoBSD in terms of disk writes.

Actions #3

Updated by Jim Pingle almost 6 years ago

  • Status changed from New to Not a Bug

NanoBSD has been deprecated for a while now.

Actions

Also available in: Atom PDF