From owner-freebsd-usb@FreeBSD.ORG  Wed Jan 30 09:24:17 2013
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 041ACE78
 for <freebsd-usb@freebsd.org>; Wed, 30 Jan 2013 09:24:17 +0000 (UTC)
 (envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe06.c2i.net [212.247.154.162])
 by mx1.freebsd.org (Postfix) with ESMTP id 8DC799C5
 for <freebsd-usb@freebsd.org>; Wed, 30 Jan 2013 09:24:15 +0000 (UTC)
X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED,
	BAYES_50
Received: from [176.74.213.204] (account mc467741@c2i.net HELO
 laptop015.hselasky.homeunix.org)
 by mailfe06.swip.net (CommuniGate Pro SMTP 5.4.4)
 with ESMTPA id 371750980; Wed, 30 Jan 2013 10:24:08 +0100
From: Hans Petter Selasky <hselasky@c2i.net>
To: Yuri <yuri@rawbw.com>
Subject: Re: Why my USB keyboard doesn't generate scancodes?
Date: Wed, 30 Jan 2013 10:25:20 +0100
User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; )
References: <5104974C.803@rawbw.com> <201301301010.10490.hselasky@c2i.net>
 <5108E521.5000503@rawbw.com>
In-Reply-To: <5108E521.5000503@rawbw.com>
X-Face: ?p&W)c<w+fb'sd#*]i!s!UQ[!|W8%I(I+\}LQ-Z1nB*t(u_>(+80hU; '{.$5K+zq{oC6y|
 /D'an*6mw>j'f:eBsex\Gi, <a&s"J*gPjz0nO,
 Sucb&N84|zkA2YlM?`/Vp=@Bh}pyW=TQ WtqwY'_Sy0aa~(jJCeFpDW
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201301301025.20211.hselasky@c2i.net>
Cc: freebsd-usb@freebsd.org
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 09:24:17 -0000

On Wednesday 30 January 2013 10:17:21 Yuri wrote:
> On 01/30/2013 01:10, Hans Petter Selasky wrote:
> > On Wednesday 30 January 2013 09:56:21 Yuri wrote:
> >> On 01/30/2013 00:33, Hans Petter Selasky wrote:
> >>> What is printed in dmesg with ukbd.debug enabled when you press a key
> >>> or two. And also try NumLock.
> >> 
> >> I have hw.usb.ukbd.debug=15 and nothing is printed in dmesg. Based on my
> >> previous dtrace log, no key click messages reach ukbd driver at all.
> >> This is the reason nothing gets logged.
> >> This keyboard only has 2 buttons, and NumLock isn't among them.
> >> I think the buttons are supposed to be PgUp/PgDown.
> > 
> > Hi,
> > 
> > I see what is going on now. Your keyboard is endpoint 0x81 and no events
> > are reported here. Instead those key events are part of the mouse
> > protocol, 0x82, and it is currently not supported that a mouse can
> > generate key-events. However, it might be that those keys are mapped
> > into some axis. Try to enable hw.usb.ums.debug=15 instead.
> > 
> > Can you also try to dump the other HID descriptors:
> > 
> > usbconfig -d X.Y do_request 0x81 0x06 0x2200 0 0x100
> > usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x100
> > usbconfig -d X.Y do_request 0x81 0x06 0x2200 2 0x100
> 
> Here is what is printed from the keyboard click:
> ums_intr_callback: sc=0xfffffe02f497d000 actlen=5
> ums_intr_callback: data = 16 00 00 27 00 00 00 00
> ums_intr_callback: sc=0xfffffe02f497d000 actlen=5
> ums_intr_callback: data = 16 00 00 00 00 00 00 00
> 

The length was a bit too short. Can you re-run?

usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x300

--HPS