You can add these things to the vt to-do list
Change the default font to look like sc.
Add copy/paste function like sc has.
Add splash screen support like sc has.
Adrian Chadd wrote:
no, the vt_vga backend doesn't yet do VESA.
I keep meaning to sit down and fix this, but life and wifi gets in the way.
On 14 January 2017 at 16:27, Kevin Oberman <rkober...@gmail.com> wrote:
On Sat, Jan 14, 2017 at 2:11 PM, Adrian Chadd <adrian.ch...@gmail.com>
It depends(tm). I think the VT code just does "640x480x4bpp" and lets
the BIOS sort it out. A lot of things don't cope well with 640x480
these days - they try autodetecting picture edges, but a black border
makes that very difficult.
Can you use vidcontrol(1) to change to something better? 1600x900, maybe?
(Note, I have not tried this and I know that vt does not support a lot of
vidcontrol functionality, but starting X sets the display to 200x56
characters on my laptop.)
Kevin Oberman, Part time kid herder and retired Network Engineer
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On 14 January 2017 at 08:57, Matthias Andree <matthias.and...@gmx.de>
Am 14.01.2017 um 00:11 schrieb Alan Somers:
I take it back. The first three columns _are_ rendered, but they
don't show up on some monitiors. It's as if those monitors require a
minimum amount of overscan on the left side of the screen, and vt(4)
doesn't provide enough. Can that be tuned?
Once upon a time, I've seen similar things on Linux, but with fewer
pixels offset, when switching framebuffer drivers - back then, the
scanning-VGA-timing was an issue. Is there any way to tweak the row and
column timings, with blank periods, viewport offsets and thereabouts?
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"