linux-kernel - Re: Bug#594089: keyboard-configuration: caps lock keycode problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Oct 2010 12:25:08 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Tom Vier <tom@...adsys.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 Wed, Oct 27, 2010 at 02:34:35PM -0400, Tom Vier wrote:
> 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=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
> 


Hmm, this keyboard registers 2 input devices... I wonder, if you press
CapsLock/Favories and RightShift/Previous and monitor both event devices
with evtest - will it report events on both devices at once?

-- 
Dmitry
--
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/