Bug 245295 - Unable to see entire console after fresh install
Summary: Unable to see entire console after fresh install
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: standards (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-standards mailing list
Keywords: install, regression
Depends on:
Reported: 2020-04-02 20:34 UTC by Chris Hutchinson
Modified: 2020-04-02 23:26 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Chris Hutchinson 2020-04-02 20:34:51 UTC
I'm not sure I'm using the correct "component" here. But
was the closest related to my problem.
Quoted from a message I sent to the current@ mailing list
that received no solution:

OK I just installed a fresh copy of 13 from an official
memstick image. All went as expected. But upon reboot,
I'm missing about 4 to 5 characters on the left hand
side of the screen. I know vesa is built into GENERIC.
But vidcontrol(1) won't help. I've tried both sc(4), and
vt(4). Is textmode no longer supported?

For the record; I'm unable to see some 5 characters on
the left hand side of my screen. This makes reading man
pages, editing config files, or understanding the output
from dmesg, and any other services running. I have
experienced no troubles in the past, as I have always
built rollouts from my build servers, and deployed them
to this, and other servers/machines. This time, I installed
from the official install media. Are users required to have
Intel, or AMD video to get a (fully) working console?

I think as it stands anyone trying FreeBSD for the first
time, and experiencing this problem. Would simply move on
to something else.

Thanks you for any, and all time on this!

Comment 1 Chris Hutchinson 2020-04-02 23:26:08 UTC
Alright. I'm going to close this. As I was finally able
to get a fully working console. The syntax I was using
to enable sc(4) was incorrect.

But as a closing comment. I would like to suggest that
sc(4) be the default used for new installs. It *always*
works. Whereas vt(4) can't yet achieve those same results.

You don't get another chance to make a first impression.
The first impression with sc(4) is more likely to be
an acceptable one, than vt(4). Until vt(4) has become
more polished.



keywords: NOTFIXED