From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 6 13:02:36 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C758106566B for ; Tue, 6 Mar 2012 13:02:36 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id D3A208FC17 for ; Tue, 6 Mar 2012 13:02:35 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so4326983wgb.31 for ; Tue, 06 Mar 2012 05:02:34 -0800 (PST) Received-SPF: pass (google.com: domain of rwmaillists@googlemail.com designates 10.180.14.37 as permitted sender) client-ip=10.180.14.37; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rwmaillists@googlemail.com designates 10.180.14.37 as permitted sender) smtp.mail=rwmaillists@googlemail.com; dkim=pass header.i=rwmaillists@googlemail.com Received: from mr.google.com ([10.180.14.37]) by 10.180.14.37 with SMTP id m5mr23032538wic.19.1331038954899 (num_hops = 1); Tue, 06 Mar 2012 05:02:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=SVzat993nKBx+/FzoRM/UbL4kTkGigkT2dj+kod19Pc=; b=gBG1X6qAz9tW/KRlT9ws0xriXmYfbily3hSIe4nB5RGSD4ATuDyE81ujtvsJKngMhu lM205eozkQHpxEl0bMVJo++MBZ0nhAvCuGIa062/RAgtwmojIWtZq2YbGqYKoN4IGmCm zxJyhBsOucoIHBtObcfjnRUzcZKI56WJSZB8m7Lznjt3ztBekg+ffoNsrpEi/VxgBDo0 CMDpzLv7cChDrwqzP7N0dCMHkHzi4STNZrmP3SzB1FHXKrVIHMs0pE3hm3esqXxlcOi7 d9E9Ei/hl/qZXBsBZ90xd7ryBc+RWH+MM4MPsSPokJpC4vkiGBoOzQovPVn+YrulbHYZ psdw== Received: by 10.180.14.37 with SMTP id m5mr18090733wic.19.1331037456839; Tue, 06 Mar 2012 04:37:36 -0800 (PST) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk. [87.194.105.247]) by mx.google.com with ESMTPS id fw5sm27916747wib.0.2012.03.06.04.37.34 (version=SSLv3 cipher=OTHER); Tue, 06 Mar 2012 04:37:35 -0800 (PST) Date: Tue, 6 Mar 2012 12:37:32 +0000 From: RW To: freebsd-hackers@freebsd.org Message-ID: <20120306123732.098d481a@gumby.homeunix.com> In-Reply-To: References: <4F55A0EA.8000300@gmail.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Graphical Terminal Environment X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 13:02:36 -0000 On Tue, 6 Mar 2012 10:31:49 +0100 Bj=F6rn Oelke wrote: > Am 06.03.2012 um 06:48 schrieb Brandon Falk: > > I havent tried tmux yet, but on my system im only able to get 80x40 > > with vidcontrol on one monitor. But with xterm in xorg i can get > > 319x89 per monitor. Until i get about half of that, i wont be > > convinced to use something existing. Anyways, I'm off to sleep. >=20 >=20 > Have you tried VESA's SC_PIXEL_MODE? It's a kernel option and IIRC it > works on amd64 since 8.1. `vidcontrol MODE_282` gave me 1280x1024 > pixels. But to be honest, this was about two years ago. Since I did this recently, you need to build with=20 options VESA options SC_PIXEL_MODE Then run vidcontrol -i mode to get a list of modes. Choose one and then run vidcontrol with something like: -g 160x64 MODE_283 where 160x64 comes from dividing the mode's font size into its resolution. You can make that automatic by adding allscreens_flags=3D"-h 2000 -g 160x64 MODE_283" to rc.conf BTW does anyone know what the character at the end of the size field is in the "vidcontrol -i mode" output, I'm seeing "D","P" or "4" on the graphics modes.