From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:36:58 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8BD616A401; Tue, 2 May 2006 17:36:58 +0000 (UTC) (envelope-from anders@FreeBSD.org) Received: from totem.fix.no (totem.fix.no [80.91.36.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DB8A43D48; Tue, 2 May 2006 17:36:58 +0000 (GMT) (envelope-from anders@FreeBSD.org) Received: by totem.fix.no (Postfix, from userid 1000) id 804408DB14F; Tue, 2 May 2006 19:36:56 +0200 (CEST) Date: Tue, 2 May 2006 19:36:56 +0200 From: Anders Nordby To: Pawel Jakub Dawidek , stable@FreeBSD.org, Maksim Yevmenkin Message-ID: <20060502173656.GA2335@totem.fix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 User-Agent: Mutt/1.5.11 Cc: Subject: geom_eli and kbdmux, enemies? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:36:58 -0000 Hi, Just upgraded 6.1-RC2 on my laptop. Having kbdmux now enabled by default, I was completely unable to boot due to having a geom eli encrypted filesystem. My encrypted filesystem was initialized with the geli -b option, to have the kernel ask for passphrase upon boot. I have tried using geom_eli as a kernel module and having it included in the kernel. If combined with kbdmux, geom_eli fails to read the passphrase from the keyboard. Nothing happens. I have to turn off the laptop, and use a live CD to rescue the system. By using geli_devices in rc.conf, and having the geli rc script attach my encrypted filesystem, I can type the passphrase just fine. But then it's a userland program asking for it. I can live with that, but I take it this is a bug that should be fixed? Should be fixed before 6.1 is out the door? Cheers, -- Anders.