CrunchBang Linux

tknomanzr

#! Die Hard

From: Heavener, OK

Registered: 2014-12-09

Posts: 777

Keyboard Maping Issues.

I am wondering if anyone has run into this sort of thing before. The function keys on my laptop are all buggered up.
Here is the output from xev when I press <F2>:

tknomanzr@UEFI-test:~$ xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'
36 Return
33 p
33 p
33 p
33 p
33 p
33 p
33 p
33 p
33 p
33 p
33 p

This is all wrong, because, as you can see, <F2> is mapped over <p>, creatinf a race condition. The above will keep running until I break it. I know I can remap the XF86 mappings but that wont do me any good until I can resolve the above issue. Also, <F5> is not mapped at all, IE no output from Xev. There are other oddities as well so question is:

Is this a driver issue?
A Bios Issue?

This same issue exists in both 3.16.04 kernel and 3.19.1 kernel.

Hardware: HP Pavilion g7 notebook w/ Amd-A6 dual core.

sudo hwinfo
58: PS/2 00.0: 10800 Keyboard
  [Created at input.226]
  Unique ID: nLyy.+49ps10DtUF
  Hardware Class: keyboard
  Model: "AT Translated Set 2 keyboard"
  Vendor: 0x0001 
  Device: 0x0001 "AT Translated Set 2 keyboard"
  Compatible to: int 0x0211 0x0001
  Device File: /dev/input/event0
  Device Files: /dev/input/event0, /dev/input/by-path/platform-i8042-serio-0-event-kbd
  Device Number: char 13:64
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=new, avail=yes, need=no, active=unknown

is the relevant output for my keyboard.

---

My Deviant Art Page

Head_on_a_Stick

CatMod

From: A world of pure imagination

Registered: 2014-01-21

Posts: 4,797

Re: Keyboard Maping Issues.

A Bios Issue?

This.

Check your firmware (BIOS) options.

---

Using Debian ~ Debian Reference ~ CrunchBang FAQ
Advice For New Users On Not Breaking Their Debian System

Forum Moderator