2005-01-31 19:09:34

by Paul Blazejowski

[permalink] [raw]
Subject: Re: Fw: Re: 2.6.11-rc2-mm2

On Sun, 30 Jan 2005 18:31:24 -0500, Dmitry Torokhov
<[email protected]> wrote:
> On Sunday 30 January 2005 16:01, Andrew Morton wrote:
> >
> > Did someone break usb input?
> >
> >
> > Begin forwarded message:
> >
> > Date: Sun, 30 Jan 2005 15:45:04 -0500
> > From: Paul Blazejowski <[email protected]>
> > To: Andrew Morton <[email protected]>
> > Cc: LKML <[email protected]>
> > Subject: Re: 2.6.11-rc2-mm2
> >
> >
> > Here's another one, my USB keyboard is not functioning properly, ie.
> > the caps lock,scrlk and num lock lights are not on when these keys are
> > pressed and dmesg gets tons of spam for each key presses:
> >
> > drivers/usb/input/hid-input.c: event field not found
> > drivers/usb/input/hid-input.c: event field not found
> > drivers/usb/input/hid-input.c: event field not found
> > drivers/usb/input/hid-input.c: event field not found
> > drivers/usb/input/hid-input.c: event field not found
> >
>
> I this it was fixed in Vojtech tree, probably with the following patch:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=110702712719062&q=raw
>
> --
> Dmitry
>

After applying the patch in above url, dmesg got quiet but the
keyboard LED lights are still non functional.

Paul

--
FreeBSD the Power to Serve!


2005-01-31 19:27:06

by Vojtech Pavlik

[permalink] [raw]
Subject: Re: Fw: Re: 2.6.11-rc2-mm2

On Mon, Jan 31, 2005 at 02:08:26PM -0500, Paul Blazejowski wrote:

> > > Begin forwarded message:
> > >
> > > Date: Sun, 30 Jan 2005 15:45:04 -0500
> > > From: Paul Blazejowski <[email protected]>
> > > To: Andrew Morton <[email protected]>
> > > Cc: LKML <[email protected]>
> > > Subject: Re: 2.6.11-rc2-mm2
> > >
> > >
> > > Here's another one, my USB keyboard is not functioning properly, ie.
> > > the caps lock,scrlk and num lock lights are not on when these keys are
> > > pressed and dmesg gets tons of spam for each key presses:
> > >
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > >
> >
> > I this it was fixed in Vojtech tree, probably with the following patch:
> >
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=110702712719062&q=raw
>
> After applying the patch in above url, dmesg got quiet but the
> keyboard LED lights are still non functional.

I didn't notice that, I'll try toggling the LED lights.

--
Vojtech Pavlik
SuSE Labs, SuSE CR

2005-02-04 14:56:59

by Vojtech Pavlik

[permalink] [raw]
Subject: Re: Fw: Re: 2.6.11-rc2-mm2

On Mon, Jan 31, 2005 at 02:08:26PM -0500, Paul Blazejowski wrote:
> On Sun, 30 Jan 2005 18:31:24 -0500, Dmitry Torokhov
> <[email protected]> wrote:
> > On Sunday 30 January 2005 16:01, Andrew Morton wrote:
> > >
> > > Did someone break usb input?
> > >
> > >
> > > Begin forwarded message:
> > >
> > > Date: Sun, 30 Jan 2005 15:45:04 -0500
> > > From: Paul Blazejowski <[email protected]>
> > > To: Andrew Morton <[email protected]>
> > > Cc: LKML <[email protected]>
> > > Subject: Re: 2.6.11-rc2-mm2
> > >
> > >
> > > Here's another one, my USB keyboard is not functioning properly, ie.
> > > the caps lock,scrlk and num lock lights are not on when these keys are
> > > pressed and dmesg gets tons of spam for each key presses:
> > >
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > > drivers/usb/input/hid-input.c: event field not found
> > >
> >
> > I this it was fixed in Vojtech tree, probably with the following patch:
> >
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=110702712719062&q=raw
> >
> > --
> > Dmitry
> >
>
> After applying the patch in above url, dmesg got quiet but the
> keyboard LED lights are still non functional.

Should be fixed in rc3. It was yet another bug.

--
Vojtech Pavlik
SuSE Labs, SuSE CR