Hey folks,

  I recently got an USB Gyration Media Center Universal Remote, and it
works fine except for 5 buttons.  In short, 4 of the keys are not
recognized by HID, and one of them repeats endlessly, even under
2.6.24-rc6.  I gathered this info running evbug and
CONFIG_HID_DEBUG=yes.

  This is what the remote looks like from /proc/bus/input/devices:

I: Bus=0003 Vendor=0c16 Product=0002 Version=0110
N: Name="Gyration Gyration RF Technology Receiver"
P: Phys=usb-0000:00:02.0-9/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.0/input/input7
U: Uniq=
H: Handlers=kbd event7
B: EV=10001f
B: KEY=37fff ac3027 bf004444 0 0 1 c04 a37c000 267bfa d941dfed
e09effdf 1cfffff ffffffff fffffffe
B: REL=40
B: ABS=1 0
B: MSC=10

I: Bus=0003 Vendor=0c16 Product=0002 Version=0120
N: Name="Gyration Gyration RF Technology Receiver"
P: Phys=usb-0000:00:02.0-9/input1
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.1/input/input8
U: Uniq=
H: Handlers=kbd mouse2 event8
B: EV=10001f
B: KEY=37fff 4aff3b7 bf0d4444 0 0 1f0001 c04 a37c007 ffa67bfa d941dfff
80beffcd 1cfffff febffbff dffffffe
B: REL=143
B: ABS=1 0
B: MSC=10

The specific problems:

1) The power button, which is actually a Sleep or Suspend button, when
pressed repeats endlessly.  One must disconnect the receiver for it to
stop.  I suspect this is because the key press event registers
correctly, but not the key release.  From the logs, upon pressing the key:

Dec 28 13:32:12 adolfo kernel: [ 3419.782830] drivers/hid/hid-core.c:
report (size 2) (numbered)
Dec 28 13:32:12 adolfo kernel: [ 3419.782836] drivers/hid/hid-core.c:
report 3 (size 1) =  82
Dec 28 13:32:12 adolfo kernel: [ 3419.782842] hid-debug: input
GenericDesktop.SystemPowerDown = 0
Dec 28 13:32:12 adolfo kernel: [ 3419.782847] hid-debug: input
GenericDesktop.SystemSleep = 1
Dec 28 13:32:12 adolfo kernel: [ 3419.782856] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 4, Code: 4, Value: 65666
Dec 28 13:32:12 adolfo kernel: [ 3419.782864] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 1, Code: 142, Value: 1
Dec 28 13:32:12 adolfo kernel: [ 3419.782866] hid-debug: input
GenericDesktop.SystemWakeUp = 0
Dec 28 13:32:12 adolfo kernel: [ 3419.782872] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 0, Code: 0, Value: 0
Dec 28 13:32:12 adolfo kernel: [ 3420.032899] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 1, Code: 142, Value: 2
Dec 28 13:32:12 adolfo kernel: [ 3420.032906] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 0, Code: 0, Value: 1
Dec 28 13:32:12 adolfo kernel: [ 3420.068869] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 1, Code: 142, Value: 2
Dec 28 13:32:12 adolfo kernel: [ 3420.068876] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 0, Code: 0, Value: 1
Dec 28 13:32:12 adolfo kernel: [ 3420.104839] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 1, Code: 142, Value: 2
Dec 28 13:32:12 adolfo kernel: [ 3420.104846] evbug.c: Event. Dev:
usb-0000:00:02.0-9/input1, Type: 0, Code: 0, Value: 1

2) Four of the buttons ("TV", "SETUP MENU", "LAST", and "INPUT") are
not recognized and do not register any events; only "TV" generates a
short debug message, but nothing else:

Dec 28 13:31:50 adolfo kernel: [ 3398.582532] drivers/hid/hid-core.c:
report (size 3) (numbered)
Dec 28 13:31:50 adolfo kernel: [ 3398.582538] drivers/hid/hid-core.c:
report 6 (size 2) =  00 00

  In my next post I'll attach the full log from the time the RF
receiver is connected to the time it is disconnected.

  If I can fix the endlessly repeating key I'll be 90% happy, because
then I can use it to Suspend/Resume my HTPC.  The missing keys would
be a bonus.  The problem is I'm a kernel newbie, as as of yet do not
know where to begin.  For starters, what is the most low-level USB
interface in kernel where I could start debugging this, just to see if
ANYTHING is getting through?

Thanks for your help,
Adolfo
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to