From owner-freebsd-current@freebsd.org Sun Jan 15 02:52:13 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 93BCACAEA4A for ; Sun, 15 Jan 2017 02:52:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 284611DB0 for ; Sun, 15 Jan 2017 02:52:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id r144so125690338wme.1 for ; Sat, 14 Jan 2017 18:52:13 -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=6X/h4eOekHGHRiUx1hUKzAeFozN597vlqpUbrWOp3WA=; b=R9paalprGPQckYEA8G4q9JtAZpjEkQ4LGziV6uuM2c63ipPwJKvMxpDYeY80R++KLC cC7jSyrEApD/6Ax46pxTfmFzRghejWSjjNRizhlOc8bneKTnHogAb+77oJIXgFvmF6Ce XiweZTpCkQ9MWb5EyJsrbW1BWEyYRh2sLzREfGrUgKNNeYWBo0H1wsGKECO77o89HuKz xogIecjR7ach2s9HsuKOx68yX+LAkKJ6ZT+GbVz6Y5z9wLFzoPsGbSi8SnfCriObhgB+ tyMinKQeIq1M12ZCMOXbyER+zUcDmfru6j3fWV7qXJRF0x8rcillT3k2SQDZYUx9p/Vd 6dbw== 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=6X/h4eOekHGHRiUx1hUKzAeFozN597vlqpUbrWOp3WA=; b=hLUqpkFc23AmJYdJDBbMH7jjGLYpDrkhk0YGP999e+wr+yX965N8ysJBQCCTCfuQRN lgVifWYyDrK7Sz0WSNMR32OCGZQaTxhcOPezqZsvUPrJHkWhBYKutFiPWCFHySG2HmNA 5ozwexGQlDnTiDAZiv1C/gmiQ6BAg8g2BGZwnqavWx3sErnTuGhsn8OOAYDxdfw0S1ja AmxAxPwdQfBg3tgCHn97Np4VdaTOubJmLYzganhejZGGLUqirPCHdohb59Sp+sF8Xhwl 60NLzHu1w7iXRTTnr3NCUwPX5sse3mguhLWCKEZZ/pviR9RYkggxAu5kavwJnvNdbR4Q n53A== X-Gm-Message-State: AIkVDXJyNJDTURJQgmyRQJfP5jqxgItMpgoQqKvf5TIji6sv5qna+opT9+7buGNp5HW2tmlFYHhE/UIREeaMww== X-Received: by 10.28.58.204 with SMTP id h195mr6592245wma.116.1484448727981; Sat, 14 Jan 2017 18:52:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.82.162 with HTTP; Sat, 14 Jan 2017 18:52:06 -0800 (PST) In-Reply-To: References: <96CA08DF-582A-4405-9E65-B19230EA37DA@gmail.com> From: Adrian Chadd Date: Sat, 14 Jan 2017 18:52:06 -0800 Message-ID: Subject: Re: vt(4) chops off the leftmost three columns To: Kevin Oberman Cc: 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 02:52:13 -0000 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? >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to >> > "freebsd-current-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >