linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: linux-hotplug@vger.kernel.org
Subject: Re: keyboard problem with UP & PrintScrn
Date: Sat, 03 Apr 2010 13:51:01 +0000	[thread overview]
Message-ID: <201004030951.01669.edt@aei.ca> (raw)
In-Reply-To: <201004030932.34838.edt@aei.ca>

Hi,

Just realized that udev is just showing a single entry for a key press.  Unless the constant stream events
is not normal please ignore this.

Thanks
Ed

On Saturday 03 April 2010 09:32:34 Ed Tomlinson wrote:
> Hi,
> 
> I reciently switched to xorg 1.8 which uses udev for keyboard setup when using evdev.  My UP and Printscrn 
> keys  did not work (all other keys work as expected).  xev does not show the keypress events for either of these 
> keys.  Googling lead me to /lib/udev/keymap.  Running this with the -i option also fails to show the keypress events.  
> There is also a constant stream of null events from keymap -i with the keypress / keyrelease events  coming out in 
> this stream when a key is pressed.
> 
> In xorg.conf I have:
> 
> Section "InputDevice"
>         Identifier  "Keyboard0"
>         Driver      "evdev"
>         option      "Device" "/dev/input/event0"
>         option      "CoreKeyboard"
>         option      "XkbModel" "pc105"
>         option      "XkbLayout" "ca"
>         option      "XkbVariant" "fr"
>         Option      "XkbOptions" "terminate:ctrl_alt_bksp"
> EndSection
> 
> and extracting from: udevadm info --export-db > /tmp/udev-db.txt"
> I get:
> 
> P: /devices/platform/i8042
> E: UDEV_LOG=3
> E: DEVPATH=/devices/platform/i8042
> E: DRIVER=i8042
> E: MODALIAS=platform:i8042
> E: SUBSYSTEM=platform
> 
> P: /devices/platform/i8042/serio0
> E: UDEV_LOG=3
> E: DEVPATH=/devices/platform/i8042/serio0
> E: DRIVER=atkbd
> E: SERIO_TYPE\x06
> E: SERIO_PROTO\0
> E: SERIO_ID\0
> E: SERIO_EXTRA\0
> E: MODALIAS=serio:ty06pr00id00ex00
> E: SUBSYSTEM=serio
> E: DMI_VENDOR=System manufacturer
> 
> P: /devices/platform/i8042/serio0/input/input0
> E: UDEV_LOG=3
> E: DEVPATH=/devices/platform/i8042/serio0/input/input0
> E: PRODUCT\x11/1/1/ab41
> E: NAME="AT Translated Set 2 keyboard"
> E: PHYS="isa0060/serio0/input0"
> E: EV=120013
> E: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
> E: MSC=10
> E: LED=7
> E: MODALIAS=input:b0011v0001p0001eAB41-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D,7E,7F,80,8C,8E,8F,9B,9C,9D,9E,9F,A3,A4,A5,A6,AC,AD,B7,B8,B9,D9,E2,ram4,l0,1,2,sfw
> E: SUBSYSTEM=input
> 
> P: /devices/platform/i8042/serio0/input/input0/event0
> N: input/event0
> S: char/13:64
> S: input/by-path/platform-i8042-serio-0-event-kbd
> E: UDEV_LOG=3
> E: DEVPATH=/devices/platform/i8042/serio0/input/input0/event0
> E: MAJOR\x13
> E: MINORd
> E: DEVNAME=/dev/input/event0
> E: SUBSYSTEM=input
> E: ID_INPUT=1
> E: ID_INPUT_KEY=1
> E: ID_INPUT_KEYBOARD=1
> E: ID_SERIAL=noserial
> E: ID_PATH=platform-i8042-serio-0
> E: DMI_VENDOR=System manufacturer
> E: DEVLINKS=/dev/char/13:64 /dev/input/by-path/platform-i8042-serio-0-event-kbd
> 
> The kernel is 2.6.33.2 and udev is 151-r1 (gentoo)
> 
> How do we go about debugging this one?
> 
> Thanks
> Ed Tomlinson
> 

      reply	other threads:[~2010-04-03 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 13:32 keyboard problem with UP & PrintScrn Ed Tomlinson
2010-04-03 13:51 ` Ed Tomlinson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201004030951.01669.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).