COM1 default port but I need COM0
-
Hello all
I'm tring to install pfsense in a hardware called nethesys security box s25, it uses a mb called MB-5330 A V1.0B, i found no documentation but it seems exactly like this one:
http://www.lannerinc.com/products/x86-network-appliances/desktop/fw-5330I downloaded and installed (dd) in a 16Gb compact flash the image pfSense-CE-2.3.2-RELEASE-4g-i386-nanobsd.img
I can access the mobo BIOS via serial port 115000 8N1 using a CISCO console cableMY problem is that after bios I can see nothing.
Could be the problem that the mobo creates COM0 port and pfsense wants COM1 port?the output of dd command is ok and before dd'ing the image I cleaned up the cf card
thanks -
Anything here? https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_with_an_alternate_console
Some of this might help too: https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Serial_Console
You should also have these available:
comconsole_port="0x3F8"
comconsole_speed="115200"IIRC 0x3F8 was "COM1" and 0x2F8 was "COM2"
There was, traditionally, no "COM0"
-
There's a shitty issue with NanoBSD builds which stick the serial console to first port, and that's somehow hardcoded in the bootloader and cannot be changed. It used to be customizable back in the 2.2 and before versions, but since 2.3, this is hardcoded. Which sucks, because I can't use my GPS receiver on serial port for NTPd time syncing because of that.
It may be similar issue here…The full install version doesn't have this limitation.
-
As far as I know the boot loader serial port parameters have always been customizable via a /boot.config file. Has this really changed recently?
-
/boot/loader.conf.local
-
Thank all
I'm trying. the firs step will be download another imageAlessandro
-
@kpa:
As far as I know the boot loader serial port parameters have always been customizable via a /boot.config file. Has this really changed recently?
In NanoBSD since 2.3, this file resets to defaults every time you reboot, and it has been told us in these forums that this is by design like so.
i had to switch to full install on embedded hardware because of this.