From owner-freebsd-current@freebsd.org Sun Jan 15 05:08:27 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4443BCB0836 for ; Sun, 15 Jan 2017 05:08:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BBDD41C42 for ; Sun, 15 Jan 2017 05:08:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id c85so116640231wmi.1 for ; Sat, 14 Jan 2017 21:08:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7XMRAl/Tw7GghsFnIq93MfBkDl1Y1AFYjxv97leRFAo=; b=dItVSNGyRWgF27j6PsB+4p7oD7qtnUcghCCV7yKfPv9A6C+rVPEaeH13QxCwKxIhnH xO8R+3NvXHtU4u/+bWNx7P/buSrv7EZuHDb+mDDS+OXa8zHKbEb820xgkwcQeLfw9byv E4uhujsarjL4Rb6IflrH+DadGYTzY+loor7rzGTckdVq1PDFhT/LM26O3dSXV47We7+o AHoBftAq7jMgcQvQmf7yJbb8G1jk0gpU2jIOHTqEPQeRwhKsebusvslpbzWW9vw0KSBx H8OfwYKiErmacA0cT6EvVx2M7QZywbmK6HwIib4lXI9zaEFCNhVas0omy52hmHdvYedJ IyuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7XMRAl/Tw7GghsFnIq93MfBkDl1Y1AFYjxv97leRFAo=; b=K77fDN4Gjg+dRejv7/WbAUs8f8UOKn+2AMn1jdvnYsGVcLHzzwSROiZEE25mpes3vh 4OR9Fmhl1OGiuzbU6SPHszMn1TOfzOJGSPhEHwEtjcIBRf4f/xJwCt0QhYWclz8TB1oF Q4cYmnxZWYePEhquI0RgcAMI3oKp8OJJyq9Jff0wwDOaastLyVXNBCel0j5SuF5tMvOK VU735Bp2kOEohUmUf2RPbPwOlib1+/eLFue6VK/f0z0d/PAFVajABUD6oz2Pb1AgLy5M v/osf24uhuCt73EUXy2qdWzyIqS2gfH75gXfAIWiCMTW8hOqHdXIU8/of+CH/APcKfiI bf0g== X-Gm-Message-State: AIkVDXIzDi9qWk7CsjJn9L5fbEhaeJI8akSUJxO+bdwo9atB4r/YphoGdAvFP6smUukcmvXk3+LoSClPQSvuvQ== X-Received: by 10.223.151.138 with SMTP id s10mr18076385wrb.65.1484456904487; Sat, 14 Jan 2017 21:08:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.82.162 with HTTP; Sat, 14 Jan 2017 21:08:23 -0800 (PST) In-Reply-To: <587B0381.5090603@gmail.com> References: <96CA08DF-582A-4405-9E65-B19230EA37DA@gmail.com> <587B0381.5090603@gmail.com> From: Adrian Chadd Date: Sat, 14 Jan 2017 21:08:23 -0800 Message-ID: Subject: Re: vt(4) chops off the leftmost three columns To: Ernie Luzar Cc: Kevin Oberman , Matthias Andree , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2017 05:08:27 -0000 heh. As always, patches gratefully accepted. :) -adrian On 14 January 2017 at 21:07, Ernie Luzar wrote: > > 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: >> >> hi, >> >> 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. >> >> >> -adrian >> >> >> On 14 January 2017 at 16:27, Kevin Oberman wrote: >>> >>> On Sat, Jan 14, 2017 at 2:11 PM, Adrian Chadd >>> wrote: >>>> >>>> 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. >>>> >>>> >>>> -adrian >>> >>> >>> 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 >>> E-mail: rkoberman@gmail.com >>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >>> >>> >>>> On 14 January 2017 at 08:57, Matthias Andree >>>> wrote: >>>>> >>>>> 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? > > >