[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CC870BB.2050000@triadsys.com>
Date: Wed, 27 Oct 2010 14:34:35 -0400
From: Tom Vier <tom@...adsys.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
CC: Samuel Thibault <sthibault@...ian.org>,
"594089@...s.debian.org" <594089@...s.debian.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jiri Kosina <jkosina@...e.cz>
Subject: Re: Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/27/2010 12:08 PM, Dmitry Torokhov wrote:
> On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote:
>> Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit :
>> Sure, but dumpkeys shows the table from scancodes to keycodes, not from
>> input events to scancodes.
>
> I am just wondering if some of the translation is leaking even though
> the keyboard is in raw mode...
>
> OK, scratch that... Are there any other input devices? Anything
> connected via uinput and listening? What does /proc/bus/input/devices
> show? Maybe if Tom could compile and load evbug module it would show us
> where the additional events are coming form, becaus ethey surely are not
> generated by the keyboard itself (otherwise we'd have seen them in
> evtest output for that device).
Minor correction to what I wrote earlier about the scroll wheel. That is
actually my mouse. It says Dell but it's really made by Logitech.
I just tried the console and what's funny is Favorites actually works as
Capslock and Previous works as right-shift. X has the opposite problem.
In case anyone missed it, Debian Stable works fine with this keyboard.
The keyboard on the working Stable machine is exactly the same (same usb
id's). I'm not familiar with the input stack, but in case it is a kernel
problem, the difference is:
Stable dist, working:
Linux zero 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64
GNU/Linux
Testing dist, not working:
Linux tom 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64
GNU/Linux
/proc/bus/input/devices on the problem machine:
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3
I: Bus=0003 Vendor=046d Product=c016 Version=0110
N: Name="Logitech Optical USB Mouse"
P: Phys=usb-0000:00:13.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/input/input1
U: Uniq=
H: Handlers=mouse1 event1
B: EV=17
B: KEY=70000 0 0 0 0
B: REL=103
B: MSC=10
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/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=10000000000000 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/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=3
B: KEY=10000000000000 0
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=40001
B: SND=6
I: Bus=0003 Vendor=046d Product=c30a Version=0110
N: Name="Logitech Logitech USB Keyboard"
P: Phys=usb-0000:00:13.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.0/input/input9
U: Uniq=
H: Handlers=kbd event2
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f
I: Bus=0003 Vendor=046d Product=c30a Version=0110
N: Name="Logitech Logitech USB Keyboard"
P: Phys=usb-0000:00:13.0-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.1/input/input10
U: Uniq=
H: Handlers=kbd mouse2 event3
B: EV=17
B: KEY=fffffffffffff f8403340000 60d8fafd01d008 1f000000000000 0
B: REL=103
B: MSC=10
--
Tom Vier <tom@...adsys.com>
Senior Net/Sys Admin
Triad Systems Engineering, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists