Date: Fri, 27 Aug 2004 20:41:32 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: apeiron@comcast.net Cc: midian@ihme.org Subject: Re: USB keyboard problems Message-ID: <20040827.204132.36022184.imp@bsdimp.com> In-Reply-To: <20040826161900.GA31925@prophecy.dyndns.org> References: <20040820220601.G33344@midi.ihme.net> <20040826161900.GA31925@prophecy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040826161900.GA31925@prophecy.dyndns.org>
Christopher Nehren <apeiron@comcast.net> writes:
: On Fri, Aug 20, 2004 at 15:13:32 EDT, Markus H=E4stbacka scribbled th=
ese
: curious markings:
: > Ok, here comes the explanation of the problem, I recently upgraded =
to =
: > 5.2-CURRENT (Currently at 5.3-BETA1), and after the upgrade my USB =
: > keyboard didn't work. I could turn on/off the numlock/capslock/scro=
lllock =
: > lights but there was no response in other keys. Here's the informat=
ion I =
: > got from dmesg when the keyboard was connected at bootup:
: > ukbd0: Logitech Logitech USB Keyboard, rev 1.10/15.00, addr 3, icla=
ss 3/1
: > kbd1 at ukbd0
: > uhid0: Logitech Logitech USB Keyboard, rev 1.10/15.00, addr 3, icla=
ss 3/1
: =
: I find it very interesting that both you and I are having problems wi=
th
: a uhid device that used to work in 5.2.1 but that doesn't work any mo=
re
: in -CURRENT.
: =
: At least I'm not the only one with whom Warner Losh will take excepti=
on.
I guess it all depends on what you mean by recently. I'd thought that
some of my recent changes had broken it, but the breakage goes back
further than that. 5.2 release isn't 'recent', and I fully believe
that things may have changed since then... I see a major uhid upgrade
in that time frame, which may be the time of breakage...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040827.204132.36022184.imp>