search

scap1784 / logkeys

Automatically exported from code.google.com/p/logkeys
Other
0 stars 0 forks source link

Couldn't determine keyboard device. #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Error:
logkeys: Couldn't determine keyboard device. :/
logkeys: Please post contents of your /proc/bus/input/devices file as a new bug 
report. Thanks!

see devices file attach

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse0 event2 
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=045e Product=00f9 Version=0111
N: Name="Microsft Microsoft Wireless Desktop Receiver 3.1"
P: Phys=usb-0000:00:06.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3 
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=107

I: Bus=0003 Vendor=045e Product=00f9 Version=0111
N: Name="Microsft Microsoft Wireless Desktop Receiver 3.1"
P: Phys=usb-0000:00:06.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.1/input/input4
U: Uniq=
H: Handlers=kbd mouse1 event4 
B: EV=10001f
B: KEY=837fff 2c3027 bf004444 0 0 1f0001 10f84 8b27c007 ff7f7bfa d9415fff 
febeffdf ffefffff ffffffff fffffffe
B: REL=fc3
B: ABS=1 0
B: MSC=10

I: Bus=0003 Vendor=0413 Product=6f00 Version=0002
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:00:04.1-2/ir0
S: Sysfs=/devices/pci0000:00/0000:00:04.1/usb1/1-2/input/input5
U: Uniq=
H: Handlers=kbd event5 
B: EV=3
B: KEY=14afc336 284284d 0 0 0 4 80058000 2190 40000801 9e96c0 0 900200 ffd

I: Bus=0001 Vendor=10ec Product=0662 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:08.0/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: EV=40001
B: SND=6

Original issue reported on code.google.com by indika.l...@gmail.com on 12 Jun 2010 at 11:04

GoogleCodeExporter commented 9 years ago 
Hello. :-)

Thanks for this bug report.

Can you please follow the procedure described here
http://code.google.com/p/logkeys/wiki/Documentation#Empty_log_file_or_%27Couldn%
27t_determine_keyboard_device&
and determine which device interfaces your keyboard.

It will likely be /dev/input/event3 or /dev/input/event4. 

Whichever it is, please add a comment here.
Then, until the next version of logkeys, run it with -d switch, e.g.
$ logkeys --start --device /dev/input/event3

:-)

Original comment by kernc...@gmail.com on 13 Jun 2010 at 2:52

GoogleCodeExporter commented 9 years ago 
Issue 35 has been merged into this issue.

Original comment by kernc...@gmail.com on 15 Jul 2010 at 3:05

GoogleCodeExporter commented 9 years ago 
Hopefully fixed in r72.

Original comment by kernc...@gmail.com on 19 Aug 2010 at 3:57