From owner-freebsd-current@FreeBSD.ORG Wed Nov 5 14:34:19 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4C3CC125 for ; Wed, 5 Nov 2014 14:34:19 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E2892A6 for ; Wed, 5 Nov 2014 14:34:18 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id sA5Ea7L0031690; Wed, 5 Nov 2014 06:36:08 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: Gary Jennejohn In-Reply-To: <20141105101951.48542120@ernst.home> References: <544E7679.7070207@FreeBSD.org> <54590B3E.2070701@dumbbell.fr> , <20141105101951.48542120@ernst.home> From: "Chris H" Subject: Re: HEADS UP: Enabling vt(4) by default Date: Wed, 05 Nov 2014 06:36:08 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit Cc: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuUMOpZHJvbg==?= , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 05 Nov 2014 14:34:19 -0000 On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn wrote > On Tue, 04 Nov 2014 18:01:41 -0800 > "Chris H" wrote: > > > On Tue, 04 Nov 2014 18:22:06 +0100 Jean-Sebastien Pedron > > wrote > > > > > Hello! > > > > > > As announced a week ago, vt(4) is now the default console driver in > > > 11-CURRENT as of r274085. > > > > > > You may have to update your console settings in /etc/rc.conf. During > > > boot, /etc/rc.d/syscons will indicate what you need to do. > > > > > > The original HEADS UP mentioned several known issues. Among them, the > > > following were fixed: > > > > > > o A video mode can be selected using the following tunable in > > > /boot/loader.conf: > > > kern.vt.fb.default_mode="1024x768" > > > > > > This only works when using a KMS video driver. It's not > > > supported by the VGA backend. See vt(4) man page for further > > > documentation. > > > > > > o The keyboard was not working when kbdmux(4) was disabled. This > > > is fixed. > > > > > > o After loading a KMS driver, the text cursor was in the middle of > > > the kernel messages. The problem was that the cursor position was > > > not updated after the change in window size. This is fixed. > > > > > > Up-to-date information can be found on the wiki page: > > > https://wiki.freebsd.org/Newcons > > > > > > If you want to keep using syscons(4), you can add the following line to > > > /boot/loader.conf: > > > kern.vty=sc > > > > > > Thank you to everyone who tested and reported problems! Please continue > > > to do so, especially if you find the need to go back to syscons. > > > > No. Thank _you_! :) > > > > I was unable to determine from the wiki. But do all these wonderful > > new features also work with the nVidia blob, under vt(4)? > > I'm currently building a new 11-CURRENT from the 10-26 iso, as I write > > this, and was wondering if the graphics mode at higher resolutions was > > now possible using the nVidia blob. > > > > No, video mode won't work with the nVidia blob. That requires > a KMS (in-kernel) driver. Thank you for the reply, Gary. Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck? Thanks again. --Chris > > -- > Gary Jennejohn