Bug #8978
closedvidconsole is invalid for efi booted systems
100%
Description
The loader values 'console="vidconsole"'or 'console="vidconsole,comconsole"'are invalid for systems booted UEFI where that does not exist. Instead console should be 'efi'.
That means if you enable a serial console on an efi booted system where VGA is primary you lose access to the boot loader menu.
See also: https://github.com/freenas/freenas/pull/1142 and https://forum.netgate.com/topic/136177/serial-console-on-uefi-minnowboard-aka-mbt-4220
Updated by Jim Pingle about 6 years ago
Looks like we'd have to check like they did on FreeNAS, if sysctl -n machdep.bootmethod
returns UEFI then we can set the video console to efi
instead of vidconsole
.
I'm not seeing any other reliable way to check if the boot console is efi.
Updated by Anonymous about 6 years ago
- Target version changed from 2.4.4-GS to 2.4.4-p1
Updated by Jim Pingle about 6 years ago
- Status changed from New to 13
- Assignee set to Jim Pingle
Updated by Jim Pingle about 6 years ago
- Status changed from 13 to Feedback
- % Done changed from 0 to 100
Applied in changeset 2f73f2f9eca656c2de5b836f4d0292186147e788.
Updated by Steve Wheeler about 6 years ago
- Status changed from Feedback to Resolved
Tested against:
2.4.5-DEVELOPMENT (amd64)
built on Tue Nov 06 11:45:54 EST 2018
With serial console enabled loader.conf shows:
kern.cam.boot_delay=10000 boot_multicons="YES" boot_serial="YES" console="efi,comconsole" comconsole_speed="115200" autoboot_delay="3" hw.usb.no_pf="1"
No both consoles show correctly. No longer seeing the console error at the start.