From owner-freebsd-stable@FreeBSD.ORG Mon Oct 6 21:23:57 2014 Return-Path: Delivered-To: freebsd-stable@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 A1D4833C for ; Mon, 6 Oct 2014 21:23:57 +0000 (UTC) Received: from sasl.smtp.pobox.com (smtp.pobox.com [208.72.237.35]) by mx1.freebsd.org (Postfix) with ESMTP id 4CAB3C37 for ; Mon, 6 Oct 2014 21:23:56 +0000 (UTC) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 9F8E81365F for ; Mon, 6 Oct 2014 17:19:52 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; s=sasl; bh=7QIlQb19YbMqDDpkCWQfAohdbFk=; b=rEhOGIK S8jOrvfsOb4RcZTQ8Ffa4jXRMfb7xt2WmlkqVigoaklhvuwDhQWeUBFDB/58uo23 PqQ/gcJ/t/z/dr7oOuaKgpDtC7RWEXUDDigB41tA5ezFu7m98AeChIfkNkGd1Bnu hBPXMfG+ga9dREnv/FtVwXICfw2KeTjpkpzI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=sasl; b=RNDFnvO73EStWlmCLEEOqLu3qZe9SeT+z /TeSmDTPUKfdg4W0XIMLytNOV0etuhQCHOJxzzVfycRuBz9nfu0zhAqSRfFCN07u gD59uKjPPCzN6RtdjVhfSy8L2qoWJBKoOSN5DikseGgty/lALhTNeTPLPz8joX6Z QyelZWKR/w= Received: from pb-smtp1. (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 980E91365E for ; Mon, 6 Oct 2014 17:19:52 -0400 (EDT) Received: from localhost (unknown [50.90.2.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 3ED1F1365C for ; Mon, 6 Oct 2014 17:19:52 -0400 (EDT) Date: Mon, 6 Oct 2014 17:19:51 -0400 From: Chris Nehren To: freebsd-stable@freebsd.org Subject: Re: USB keyboard not recognized during boot Message-ID: <20141006211951.GD24785@satori.lan> Mail-Followup-To: freebsd-stable@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0hHDr/TIsw4o3iPK" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Pobox-Relay-ID: 82CDB6CC-4D9E-11E4-B89C-855A93717476-49531120!pb-smtp1.pobox.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2014 21:23:57 -0000 --0hHDr/TIsw4o3iPK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 06, 2014 at 13:59:12 -0700, Daniel wrote: > My problem stems from not being able to use my keyboard during the geli > password prompt for the encrypted root drive. >=20 > This is not a new issue: >=20 >=20 > - https://forums.freebsd.org/viewtopic.php?f=3D4&t=3D40965 > - > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D11610+0+current/freebs= d-questions > - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D131415 >=20 >=20 > Both people who have had the problem aside from me mention that the issue > did not exist pre FreeBSD-9.1 >=20 > At this time I'm wondering what I should do. I really would like to have = my > root encrypted. The actual bug hasn't moved for quite some time. Should I > open up a new one? >=20 > Since my motherboard does not have non-USB keyboard options, I'm not able > of encryption on root. >=20 > Does anyone have ideas? suggestions? I have tried waiting and then type, > but nothing has helped. How can I move this forward? >=20 > Motherboard: http://www.amazon.com/gp/product/B00FM4M7TQ I have a Supermicro X10SAE, also using GELI-encrypted root ZFS. I have found that, comical as it may seem, mashing the keyboard during the system's initial device probing allows me to hit enter at the password prompt (which gets printed in between some of the USB device probes) and then enter the password properly. I'm running on: FreeBSD behemoth 10.1-RC1 FreeBSD 10.1-RC1 #0 r272473: Fri Oct 3 14:56:28 = UTC 2014 root@behemoth:/usr/obj/usr/src/sys/GENERIC amd64 Here's my /boot/loader.conf: geli_ada0p4_keyfile0_load=3D"YES" geli_ada0p4_keyfile0_type=3D"ada0p4:geli_keyfile0" geli_ada0p4_keyfile0_name=3D"/boot/encryption.key" geli_ada2p4_keyfile0_load=3D"YES" geli_ada2p4_keyfile0_type=3D"ada2p4:geli_keyfile0" geli_ada2p4_keyfile0_name=3D"/boot/encryption.key" aesni_load=3D"YES" geom_eli_load=3D"YES" vfs.root.mountfrom=3D"zfs:rpool/ROOT/default" zfs_load=3D"YES" zpool_cache_load=3D"YES" zpool_cache_type=3D"/boot/zfs/zpool.cache" zpool_cache_name=3D"/boot/zfs/zpool.cache" So, it "works" for me, but I need to be attentive during boot or I see the same problems that you do. --=20 Chris Nehren --0hHDr/TIsw4o3iPK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJbBAABAgBFBQJUMwd3PhSAAAAAABUAIHBrYS1hZGRyZXNzQGdudXBnLm9yZ2Nu ZWhyZW4rZnJlZWJzZC1zdGFibGVAcG9ib3guY29tAAoJEBHA+GJAM0vPNycP/3Ar BzJCkmNDNK2cdQ1BRfs4RP7jB70dFjMGlv6bu63dSQkcUnwU4WX7M3f5BS7I3WnI cdbl0pKmVilnA2B/fCLwS6weHd3uAuCYntcSYYEf/z17GxhvdiiWxgU3O+Nb6mPJ dQ9FVs3IFxC7Qt/+yfIzSbsHJ9upL8mn8ASyvINh8UlcJZcLHngyduGpu5ZE1LL2 isAQBNaEps1AxZzRAOPe+xz6qFpVe5xIBvcaSperupasnmomC05HtUsiIS4hmsXr /sqeBT//gPSNEONeSi3CMataSE/sGYMOlNCChRujDtfYhgcmxVy2j7x6f6oS2nzG zQnkQL/2RCI+lRdAV/8ZM+lYsSRt+3IAHnRj6QSimAD606xtKU3ildmrJhhcMRI1 f2ePhRedwaf8cOR+dn/BRPubSxo0tytydf6Qjw0Mkn7SXSszUReJelMlcZK1AD/O NUvZn93L3Yl/jve6BtsP2U6NJ0wbB7or2ElQwcuv7zJgnnJMZUKcJIS49Rea3Pxq yikzoxwcdm6dKMTHkFj75YGGMDP4ELNfFPs3ygASjKIRiec4WlNfpFJ1JmL2DDIB yuCAHj3Da2CmMzaqy4aBbtOwvMoFCJgPssrwckgsvtiP8pSb4A+Yrp8HTGNm+y9X P0qqiM+L/MQ9LPtkLD5EJE0vNLhgtJuNi8CUM4CH =z81/ -----END PGP SIGNATURE----- --0hHDr/TIsw4o3iPK--