From owner-freebsd-stable@FreeBSD.ORG Fri Apr 18 17:49:57 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CE2A6A8 for ; Fri, 18 Apr 2014 17:49:57 +0000 (UTC) Received: from starfish.geekisp.com (starfish.geekisp.com [216.168.135.166]) by mx1.freebsd.org (Postfix) with SMTP id D277C1AE7 for ; Fri, 18 Apr 2014 17:49:56 +0000 (UTC) Received: (qmail 2036 invoked by uid 1003); 18 Apr 2014 17:49:50 -0000 Received: from unknown (HELO ?10.10.2.81?) (tyler@monkeypox.org@64.125.69.200) by mail.geekisp.com with (DHE-RSA-AES128-SHA encrypted) SMTP; 18 Apr 2014 17:49:50 -0000 Message-ID: <535165BD.1010909@monkeypox.org> Date: Fri, 18 Apr 2014 10:49:49 -0700 From: "R. Tyler Croy" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: vt(4) and geli(8) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2014 17:49:57 -0000 On 04/18/2014 08:36, Greg Rivers wrote: > The new vt system console looks really nice. But on hosts that have > geli encrypted devices that prompt for the passphrase at boot, no > keyboard input reaches geli. The keyboard doesn't appear to be dead, > as the caps-lock and num-lock keys toggle; geli just doesn't receive > any input. This is on 10-STABLE amd64 built from yesterday's sources. > "hw.vga.textmode=1" doesn't make any difference. > > Has anyone else encountered this? > I run encrypted ZFS with vt(4) on -CURRENT right now and I've not had any issues with entering my passphrase. There might be a bug fix that ray@ hasn't had a chance to merge from current just yet.