Bug #11776
closed
Overwrite /boot.config and /boot/loader.conf when you use a serial console pfsense installation.
0%
Description
Function setup_loader_settings (https://github.com/pfsense/pfsense/blob/8b424bca02372246210fba3cf36045a704c11ae3/src/etc/inc/pfsense-utils.inc#L1224) setups /boot.config and /boot/loader.conf according to the hardware in use. It uses a list of known hardware to know if it needs to activate "vidconsole" and "comconsole" or only "comconsole". By default, if it's unknown hardware, this function enables "vidconsole" and "comconsole".
This function will overwrite any change that you make to the files, including adding "vidconsole" and "comconsole" when you use a serial console pfsense installation. So, if your device doesn't support "vidconsole" and it isn't specified in the setup_loader_settings, pfsense won't boot.
Pfsense should have a way to override this behavior, if necessary, to support a bigger number of devices.
Updated by Jim Pingle over 4 years ago
- Status changed from New to Rejected
That is normal and expected.
Use /boot/loader.conf.local for your own customizations.
Updated by André Cirne over 4 years ago
I tried to make my own customizations in the boot/loader.conf.local, but doesn't work because it blocks when you have in /boot.config the flag -D for dual display.
The thing is when I install with pfsense serial console installation the PC works, because it creates /boot.config and /boot/loader.conf only with serial console. Then, on the first boot the file that was created by the pfsense installer is overwritten by one with dual console (serial and display).
If I'm using a pfsense serial console installation is because my board only supports serial console. If this is the expected behavior (override the file that was generated by the pfsense serial console installation), why there are two images one with vga console and other with serial console to install pfsense?