From owner-freebsd-current@FreeBSD.ORG Sat Feb 14 17:50:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FB0F1065673 for ; Sat, 14 Feb 2009 17:50:49 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 35CD78FC15 for ; Sat, 14 Feb 2009 17:50:48 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=kw03RjmKpLm8ql5X2xOdcA==:17 a=8kQB0OdkAAAA:8 a=1CN9iF9E7jFLt1ORQR8A:9 a=Z08txhc5j48nq8zA9SIA:7 a=D9iRuhEhXyyI2eL7C2f7UJ5huzkA:4 a=LY0hPdMaydYA:10 a=9aOQ2cSd83gA:10 a=ZwLf6ompmDNpQzrU:21 a=GL7I8PeG4CA-SF5D:21 Received: from [85.19.218.115] (account mc467741@c2i.net HELO laptop) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 145404997; Sat, 14 Feb 2009 18:50:47 +0100 From: Hans Petter Selasky To: Yoshihiro Ota Date: Sat, 14 Feb 2009 18:53:13 +0100 User-Agent: KMail/1.9.7 References: <20090213204112.7b982402.ota@j.email.ne.jp> <200902141759.27816.hselasky@c2i.net> <20090214124727.82638653.ota@j.email.ne.jp> In-Reply-To: <20090214124727.82638653.ota@j.email.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902141853.14366.hselasky@c2i.net> Cc: freebsd-current@freebsd.org Subject: Re: USB2 - keyboard error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2009 17:50:49 -0000 On Saturday 14 February 2009, Yoshihiro Ota wrote: > On Sat, 14 Feb 2009 17:59:26 +0100 > > Hans Petter Selasky wrote: > > Hi, > > > > I've looked at the USB code and I cannot find anything wrong. To get more > > debugging: > > > > sysctl hw.usb2.ukbd.debug=15 > > > > If you press num-lock, does the num-lock led turn on/off ? > > > > Is the behaviour the same for other USB keyboards ? > > > > --HPS > Hi, What I can offer is to add a USB quirk that disables the setting of the leds. Then you can add this by usbconfig for example. Try adding a return before the switch() in "ukbd_set_leds_callback()" and see if the keyboard works like expected. BTW: Do leds work with USB1 ? --HPS