Console port on Netgate/Lanner device

hfs

You can change the BIOS-Setting Advanced->Remote Access Configuration->Redirection After BIOS POST to [Boot Loader], otherwise the Lanner-device redirects the VGA-stream to the serial console.

HTH

dzeanah

@hfs:

You can change the BIOS-Setting Advanced->Remote Access Configuration->Redirection After BIOS POST to [Boot Loader], otherwise the Lanner-device redirects the VGA-stream to the serial console.

HTH

Thanks. It was set to Always, and I trued Disabled and Boot Loader, and in each case I'm seeing the same behavior: the serial console goes nonresponsive at the same point in the boot sequence.

hfs

Strange…

Just to verify:

BIOS is set to "[Boot Loader]" 115200,n,8,n
pfSense is set (via GUI) to "Enables the first serial port with 9600/8/N/1 by default, or another speed selectable below" and "115200"

You can verify the pfSense-settings in /boot/loader.conf, it should contain:


boot_multicons="YES"
boot_serial="YES"
comconsole_speed="115200"
console="comconsole,vidconsole"

/boot.config should contain this line:

-D

dzeanah

Correct.
Correct, though the labeling is different (advanced config page)

You can verify the pfSense-settings in /boot/loader.conf, it should contain:
boot_multicons="YES"
boot_serial="YES"
comconsole_speed="115200"
console="comconsole,vidconsole"

Mine only contains```
boot_multicons="YES"
hw.usb.no_pf="1"


> /boot.config should contain this line:
> ```
> 
> -D
> 
> ```

We're good there.

hfs

@Derek:

Mine only contains
boot_multicons="YES"
hw.usb.no_pf="1"
I'm assuming making changes to what you listed will help?

You might give it a shot.

You don't have flow-control enabled on your terminal?

dzeanah

That fixed it. :)

Thanks!

stephenw10

If you're doing manual file editing then use /boot/loader.conf.local instead. You will have to create that file but anything you add there won't be overwritten.
NanoBSD is hardcoded to use com1 for it's console. On my nano box if I set the console to 115200 the only line I see in the loader.conf is:
comconsole_speed="115200"

I am not sure but Netgate (who are VERY close to the project ;)) may have their own images for that box configured slightly differently. I'm sure if you dropped them a line they'd sort this for you quickly. Point them at this thread.

Steve

Edit: What was the fix?

dzeanah

Edit: What was the fix?

I made the changes suggested by HFS.

They may go away on upgrade though, you're right about that. :-[

hfs

You're right, there's a difference between full-install and embedded.

On full-installs (several lanner devices e.g. 7535, 7568, etc. ) it looks like that:

/boot/loader.conf:


boot_multicons="YES"
boot_serial="YES"
comconsole_speed="115200"
console="comconsole,vidconsole"

/boot.config:

-D

On embedded installs (Alix with 9600,n,8,1) it looks like that:

/boot/loader.conf:


comconsole_speed="9600"

/boot.config:

-h

The embedded install is based on the serial-console embedded .img file.

Both embedded and full install survived several upgrades (from 2.0 to 2.0.x… to 2.1-RELEASE) without any further modifications regarding serial console.

stephenw10

Ah interesting.
This is explained here: https://www.freebsd.org/doc/handbook/serialconsole-setup.html
Specifically:

The boot loader will determine whether the internal video or the serial port should become the console by examining the state of -h. This means that if -D is specified but -h is not specified in /boot.config, the serial port can be used as the console only during the boot block as the boot loader will use the internal video display as the console.

It seems as though the Netgate box is setup for dual console (special image) and that somehow in restoring your old config file you ended up removing some part of that setup. Not sure how though. :-\

Steve