You are not logged in.

#1 2015-08-23 05:52:53

umaxtu
Member
Registered: 2010-11-21
Posts: 31

[Solved]Inspiron 14z stopped recognizing volume-,volume+ and mute key

I get the following from xev when I press any of those keys :

KeymapNotify event, serial 32, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

Running "xmodmap -pke | grep XF86Audio" gives me

keycode 122 = XF86AudioLowerVolume NoSymbol XF86AudioLowerVolume
keycode 123 = XF86AudioRaiseVolume NoSymbol XF86AudioRaiseVolume
keycode 171 = XF86AudioNext NoSymbol XF86AudioNext
keycode 172 = XF86AudioPlay XF86AudioPause XF86AudioPlay XF86AudioPause
keycode 173 = XF86AudioPrev NoSymbol XF86AudioPrev
keycode 174 = XF86AudioStop XF86Eject XF86AudioStop XF86Eject
keycode 175 = XF86AudioRecord NoSymbol XF86AudioRecord
keycode 176 = XF86AudioRewind NoSymbol XF86AudioRewindhttps://demo.yubico.com/u2f
keycode 198 = XF86AudioMicMute NoSymbol XF86AudioMicMute
keycode 208 = XF86AudioPlay NoSymbol XF86AudioPlay
keycode 209 = XF86AudioPause NoSymbol XF86AudioPause
keycode 215 = XF86AudioPlay NoSymbol XF86AudioPlay
keycode 216 = XF86AudioForward NoSymbol XF86AudioForward
keycode 234 = XF86AudioMedia NoSymbol XF86AudioMedia

/var/log/Xorg.0.log shows that Xorg detects the dell wmi hotkeys

[     5.116] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[     5.116] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
[     5.116] (**) Dell WMI hotkeys: always reports core events
[     5.116] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event6"
[     5.116] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
[     5.116] (--) evdev: Dell WMI hotkeys: Found keys
[     5.116] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
[     5.116] (**) Option "config_info" "udev:/sys/devices/virtual/input/input11/event6"
[     5.116] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 13)

And evtest detects them:

Event: time 1440308449.847534, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1440308449.847534, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1
Event: time 1440308449.847534, -------------- SYN_REPORT ------------
Event: time 1440308449.855428, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1440308449.855428, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0
Event: time 1440308449.855428, -------------- SYN_REPORT ------------
Event: time 1440308451.406557, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0
Event: time 1440308451.406557, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1440308451.406557, -------------- SYN_REPORT ------------
Event: time 1440308451.414437, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0
Event: time 1440308451.414437, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
Event: time 1440308451.414437, -------------- SYN_REPORT ------------
Event: time 1440308452.387485, type 4 (EV_MSC), code 4 (MSC_SCAN), value a0
Event: time 1440308452.387485, type 1 (EV_KEY), code 113 (KEY_MUTE), value 1
Event: time 1440308452.387485, -------------- SYN_REPORT ------------
Event: time 1440308452.395381, type 4 (EV_MSC), code 4 (MSC_SCAN), value a0
Event: time 1440308452.395381, type 1 (EV_KEY), code 113 (KEY_MUTE), value 0
Event: time 1440308452.395381, -------------- SYN_REPORT ------------

I swear they were working a few hours ago, the one thing that I changed since then was creating /etc/X11/xorg.conf.d/90-dpifix.conf:

Section "Monitor"
    Identifier             "LVDS1"
    DisplaySize             310 174    # In millimeters
EndSection

But I don't see why that would break them.
Does anybody have any ideas on how to fix this and how it got broken in the first place?

Edit: The output of "udevadm info /dev/input/by-path/platform-i8042-serio-0-event-kbd" makes me seem like something was changed in the udev hardware db

P: /devices/platform/i8042/serio0/input/input0/event0
N: input/event0
S: input/by-path/platform-i8042-serio-0-event-kbd
E: DEVLINKS=/dev/input/by-path/platform-i8042-serio-0-event-kbd
E: DEVNAME=/dev/input/event0
E: DEVPATH=/devices/platform/i8042/serio0/input/input0/event0
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_PATH=platform-i8042-serio-0
E: ID_PATH_TAG=platform-i8042-serio-0
E: ID_SERIAL=noserial
E: KEYBOARD_KEY_81=playpause
E: KEYBOARD_KEY_82=stopcd
E: KEYBOARD_KEY_83=previoussong
E: KEYBOARD_KEY_84=nextsong
E: KEYBOARD_KEY_85=brightnessdown
E: KEYBOARD_KEY_86=brightnessup
E: KEYBOARD_KEY_87=battery
E: KEYBOARD_KEY_88=unknown
E: KEYBOARD_KEY_89=ejectclosecd
E: KEYBOARD_KEY_8F=switchvideomode
E: KEYBOARD_KEY_8a=suspend
E: KEYBOARD_KEY_8b=switchvideomode
E: KEYBOARD_KEY_8c=unknown
E: KEYBOARD_KEY_90=previoussong
E: KEYBOARD_KEY_91=prog1
E: KEYBOARD_KEY_92=media
E: KEYBOARD_KEY_93=unknown
E: KEYBOARD_KEY_95=camera
E: KEYBOARD_KEY_97=email
E: KEYBOARD_KEY_98=f21
E: KEYBOARD_KEY_99=nextsong
E: KEYBOARD_KEY_9a=setup
E: KEYBOARD_KEY_9b=switchvideomode
E: KEYBOARD_KEY_9e=f21
E: KEYBOARD_KEY_a2=playpause
E: KEYBOARD_KEY_a4=stopcd
E: KEYBOARD_KEY_d8=screenlock
E: KEYBOARD_KEY_d9=f21
E: KEYBOARD_KEY_ed=media
E: MAJOR=13
E: MINOR=64
E: SUBSYSTEM=input
E: USEC_INITIALIZED=1654882

but how did it get screwed up?
Edit2: It was the udev rules that I had to add to get my Yubikey to work in U2F mode:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="1050", TAG+="uaccess", TAG+="udev-acl"

Cause identified but the problem hasn't been fixed yet in case I didn't make that clear.
Edit3: renaming my yubikey rules file from 50-yubikey.rules to 70-yubikey-rules seems to have fixed it

Last edited by umaxtu (2015-08-23 07:11:18)

Offline

Board footer

Powered by FluxBB