From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 16:13:07 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2385A1065672 for ; Wed, 25 Nov 2009 16:13:07 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mailv1.ecc.u-tokyo.ac.jp (mailv1.ecc.u-tokyo.ac.jp [133.11.225.59]) by mx1.freebsd.org (Postfix) with ESMTP id C2FF48FC1E for ; Wed, 25 Nov 2009 16:13:06 +0000 (UTC) Received: from mhs001.ecc.u-tokyo.ac.jp (mhs001.ecc.u-tokyo.ac.jp [133.11.70.161]) by mailv1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id C57326C0043 for ; Thu, 26 Nov 2009 01:13:05 +0900 (JST) Received: from amulet.amuletic.net (124.155.55.252 [124.155.55.252]) by mhs001.ecc.u-tokyo.ac.jp (SpamBlock.pstn.b 3.4.102) with ESMTP id for ; Thu, 26 Nov 2009 01:12:59 +0900 Date: Thu, 26 Nov 2009 01:13:00 +0900 Message-ID: From: Hiroharu Tamaru To: Travelling Particle <166162@gmail.com> In-Reply-To: References: <200911201224.08313.hselasky@c2i.net> <200911212300.20154.hselasky@c2i.net> User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 124.155.55.252 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Cc: freebsd-usb@freebsd.org Subject: Re: [keyboard] ukbd stops working after filesystems mount at boot time X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2009 16:13:07 -0000 Hi At Wed, 25 Nov 2009 15:14:01 +0300, Travelling Particle wrote: > > Does this let you work around your problem too? > > > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+0+/usr/local/www/db/text/2008/freebsd-mobile/20080309.freebsd-mobile > > Haven't tried the patch, but I see what you mean. I had tested with > atkbd and kbdmux both disabled and having geli passphrase visible. > It appears that in 8.0-PRERELEASE (cvsuped Nov 23 2009, I think) the > original problem I had reported is gone: if I can get thru the > passphrase, the late stage continues fine and keyboard works at login > prompt without any problem. However, the keyboard works unreliably(*) > just before the late boot stage, at the moment when the geli > passphrase is expected. 8.0-RC3 behaved the opposite way: no problem > at the passphrase, but unusable console right after that. > > (*) By working unreliably I mean that key presses are randomly > skipped. Sometimes you see keys pressed right after the first press, > sometimes it takes 3-4 times to repeat the press before the symbol > gets entered. > > I have googled up that skipping key presses at the passphrase prompt > was reported since a long time ago. I see that it was somewhat fixed > in 8.0-RC3 with undesired side-effects. This leaves me wonder if the > keyboard can be fixed without breaking the console. I am willing to > help: if anyone needs debugging output or anything, just tell me what > I should do. USB keyboard is the only input device this computer has > (no PS/2 or serial port), so I' somewhat desperate. > > > Chances are that unreliable key inputs at boot stage is not that > > usb specific, but I couldn't dig any deeper then... > > I think it's usb-specific. What else would be responsible for dropping > input from the usb device? BIOS or something alike, or some non-interrupt driven method, or some interrupt mechanism itself? Back then, I wondered if the kernel used BIOS or any of the above, that probably is different from how the device is driven after the boot stage is finalized, but I never reached the actual code to know it myself. I'd appreciate if someone can confirm it either way. Anyway, in my case, I was using atkbd, and not ukbd, and it was just that I thought if it were really the BIOS, the same work around may help. Anyway, reading your description above, more than one thing is probably involved, so just take what I wrote as my wild guess at best. I wish I knew the kernel better not to guess a lot like this, of course... So, the ball is back on the side of the experts here ;-p > Thanks.