From owner-freebsd-questions@FreeBSD.ORG Mon Oct 6 20:54:00 2014 Return-Path: Delivered-To: freebsd-questions@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 DC6D7994 for ; Mon, 6 Oct 2014 20:53:59 +0000 (UTC) Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC7C3918 for ; Mon, 6 Oct 2014 20:53:59 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id hz1so5862516pad.22 for ; Mon, 06 Oct 2014 13:53:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:references:mail-followup-to:date :in-reply-to:message-id:user-agent:mime-version:content-type; bh=yFCZhy7vvtpNW6CC4lbWr6St8K1OP1YwuL6XFNmd6Rw=; b=GfnqMknglCDBn4MyoT6AJC9KHRID4Rc+FRm2PI8LgxvK/mZT8lP4dxhWOVSIpaMLxO HpdUrx/nJqmMAtimrwJ5nIoi0H354fQbI6FUUEFcfOUaNh/X5El7y0byx4LoSBTqj5C1 8gUHDhExC0A17aZDFgfAiv5/pX1lAZyGZHNQdVb3XjEth73+gpCMe20N7G2gRVv6LJOV ys0Ld+1IJdTr+wxTOt+wKNtubH4no5pSTOY3QGfZLB8j3RbUUaTIXP/j6Yw+Hsa83ZiZ CHqZVM8xaruC7sdMxsrmfwQ9WA6znPJDv5JHzJ3XObOyW1qSevAZ+PHtPRYE54zjaoJE v0Jg== X-Gm-Message-State: ALoCoQmzi61/bI8GtEQeNlz3cHRTYzi3MshR+449huWOR0F1XOfdvC/6e/i5mV9qEyLHLqcIY65X X-Received: by 10.66.235.8 with SMTP id ui8mr26463627pac.63.1412628833488; Mon, 06 Oct 2014 13:53:53 -0700 (PDT) Received: from elk.localnet ([2604:8800:100:82aa:6ef0:49ff:fe05:658b]) by mx.google.com with ESMTPSA id ca2sm14113963pbc.26.2014.10.06.13.53.52 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 06 Oct 2014 13:53:52 -0700 (PDT) Received: from carlj by elk.localnet with local (Exim 4.80) (envelope-from ) id 1XbFHx-0003w6-TD for freebsd-questions@freebsd.org; Mon, 06 Oct 2014 13:53:49 -0700 From: Carl Johnson To: freebsd-questions@freebsd.org Subject: Re: freebsd-questions Digest, Vol 540, Issue 1 References: Mail-Followup-To: freebsd-questions@freebsd.org Date: Mon, 06 Oct 2014 13:53:49 -0700 In-Reply-To: (Daniel's message of "Mon, 6 Oct 2014 09:14:30 -0700") Message-ID: <87k34cex7m.fsf@elk.localnet> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2014 20:54:00 -0000 Daniel writes: >> >> > The keyboard i have is a USB keyboard. The keyboard works fine in all >> > scenarios except for when prompted with the geli password. >> > >> > http://i.minus.com/ibbw2T5C7Oppp5.jpg >> > >> > > >> I just realized that I am seeing something similar that might be >> related. I don't use geli, but my usb keyboard isn't recognized until >> about halfway through the boot process. It works for BIOS setup and >> after boot, but it doesn't work during the boot menu stage. I don't >> know enough to know what the problem is, but that might help someone >> else limit where the problem is. You might want to try a minimal >> installation without geli and see if that is also true for you. If it >> is the same problem, then it has been around for a while since mine is >> running 9.1-RELEASE. My keyboard is actually a wireless usb one, but >> that is probably no different than regular usb. >> > > It works fine without geli, but I'm not sure what stage in the boot process > to check for it to start working. Do you just hit keys constantly to see? > I looked in the forums yesterday and people reporting the same issue I have > saying things worked fine until 9.1-RELEASE. So it could very well be. In my case I can't use the keyboard during the boot menu, so I can't select single user mode or verbose boot. Instead I have to wait through the timeout to get a normal boot. If that works properly on yours, then this must be an independent problem. I was thinking about it more and the boot menu is probably controlled by the loader, but I don't know if geli password is also handled by the loader. -- Carl Johnson carlj@peak.org