Discussion:
[Bug 229235] vt(4) of 11.2-RELEASE is broken with hardware dependent
(too old to reply)
b***@freebsd.org
2018-06-22 18:18:53 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235

Bug ID: 229235
Summary: vt(4) of 11.2-RELEASE is broken with hardware
dependent problem.
Product: Base System
Version: 11.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: ***@FreeBSD.org
Reporter: ***@utahime.org

With the commit of r335510 releng/11.2 switched to -RELEASE. So I updated one
of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE.

But when I rebooted I found OS boot messages are not displayed on console while
OS itself has booted successfully. To be exact,

1. BIOS message are displayed.
2. Boot menu of FreeBSD is displayed.
3. Kernel boot starts but after 'Booting...' no following messages are
displayed.
4. After OS has booted console stays unusable.

Kernel configuration is as follwing.

----------------------------------------------------------------------
***@maybe[2006]% uname -a
~
FreeBSD maybe.home.utahime.org 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335513:
Fri Jun 22 16:12:12 JST 2018
***@maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE
amd64
***@maybe[2007]% cat /usr/src/sys/amd64/conf/MAYBE
~
#
# MAYBE -- Local kernel configuration file of maybe for FreeBSD/amd64
#
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD$

include GENERIC

ident MAYBE

# ZFS support
options ZFS

# PF support
device pf #PF OpenBSD packet-filter firewall
device pflog #logging support interface for PF

#
# Temperature sensors:
#
# coretemp: on-die sensor on Intel Core and newer CPUs
#
device coretemp
***@maybe[2008]%
----------------------------------------------------------------------

I tried GENERIC kernel but the problem still happened.

HWs are,

M/B: ASUS N3150I-C (https://www.asus.com/us/Motherboards/N3150IC/)
Display: EIZO FlexScan L565
(http://www.eizoglobal.com/support/db/products/model/L565)

M/B and display are connected with analog VGA.

I have another 11.1-RELEASE-p11 amd64 environment working as guest of
VirtualBox whose host is 64bit Windows 10. So I updated it to 11.2-RELEASE like
my home server in question. But in this case console worked fine just as it was
11.1-RELEASE-p11. So the problem seems to be hardwear dependent.

I added above lines to /boot/loader.conf and rebooted system. Then all boot
messages are displayed and console works fine.

----------------------------------------------------------------------
# Load SysCons driver
kern.vty=sc
----------------------------------------------------------------------

So I'm certain somthing is wrong with vt(4) of 11.2-RELEASE.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-06-22 20:35:50 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235

Rick Macklem <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org

--- Comment #1 from Rick Macklem <***@FreeBSD.org> ---
I see something similar when running a fairly recent head, where the
SVGA screen is blank.
In my case, power cycling the monitor would bring things up until I
switched virtual consoles.

Using "sc" I don't see the problem, so I switched my kernel config to it,
since I got tired of power cycling the monitor.

In this case, my hardware is old P4 stuff (it just says vgapci0:
VGA-compatible-display in dmesg when I boot with "sc").
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-06-22 20:58:42 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235

Chris Hutchinson <***@bsdforge.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@bsdforge.com

--- Comment #2 from Chris Hutchinson <***@bsdforge.com> ---
The same is also often true for Nvidia cards -- no matter the
age. So as a rule I _always_ include sc(4) in my KERNCONF. I'm also
not terribly excited about the overall output/capabilities of vt(4)
aside from the more easily achieved resolution, and refresh rates.
It doesn't play well with my editor(s), nor can I copy/paste. The
buffering is lacking... But I have nothing to bring to the table
to improve things. So I can't *really* complain. I just use sc(4). :-)
I might also add; I applaud the efforts to accomplish as much as
*was* accomplished with vt(4). It isn't an easy task.

--Chris
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...