From owner-freebsd-questions@FreeBSD.ORG Mon Apr 30 05:01:14 2012 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9D751065749 for ; Mon, 30 Apr 2012 05:01:14 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 9548A8FC0A for ; Mon, 30 Apr 2012 05:01:14 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q3U51DZO015510; Sun, 29 Apr 2012 23:01:13 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q3U51DG5015507; Sun, 29 Apr 2012 23:01:13 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 29 Apr 2012 23:01:13 -0600 (MDT) From: Warren Block To: Lars Eighner In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sun, 29 Apr 2012 23:01:13 -0600 (MDT) Cc: questions@freebsd.org Subject: Re: First character typed lost X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 05:01:14 -0000 On Sun, 29 Apr 2012, Lars Eighner wrote: > On Sun, 29 Apr 2012, Warren Block wrote: > >> On a Gateway ML6732 notebook, FreeBSD 9-stable is working great. Video >> works (i915), sound works, the only thing that isn't quite right is that >> the first character typed after the FreeBSD kernel loads is lost. After >> that, it works normally. This makes entering a passphrase more >> challenging. > > These are total shots in the dark: > > 1. It is entirely normal (and generally thought desirable) for the > screensaver to swallow the first character when it is running -- see if this > is worth further investigation by changing screensavers or disabling it > altogether. > > 2. check /etc/issue to see if there is a trailing ANSI sequence that might > eat a character. Interesting suggestions. Turning off legacy USB support in the BIOS as suggested by Adam seems to have fixed it.