Bug 99311 - Keyboard: Multiples keys, same keycode/keysym/scancode
Summary: Keyboard: Multiples keys, same keycode/keysym/scancode
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Alan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-02 05:07 UTC by Facundo Curti
Modified: 2015-07-18 07:50 UTC (History)
0 users

See Also:
Kernel Version: 4.0.4-2-ARCH and 3.12 ubuntu
Tree: Mainline
Regression: No


Attachments

Description Facundo Curti 2015-06-02 05:07:33 UTC
I have a new keyboard, it works FINE in winbugs, but in linux, the keys shift, windows, ctrl and alt have the same keycode.

Using xev, it says keycode 50.

Using showkey on tty, it says code 42

Finally, using showkey --scancodes , it says 0x2a when pressing, 0xaa when release.


It happens on any of the four keys above montioned.

The keyboard is a noga NKB-710.

dmesg no shows any error:

[32243.886168] usb 3-9: new low-speed USB device number 8 using xhci_hcd
[32244.064732] usb 3-9: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[32244.064745] usb 3-9: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[32244.068497] input: SONiX USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/0003:0C45:7603.0007/input/input20
[32244.119603] hid-generic 0003:0C45:7603.0007: input,hidraw1: USB HID v1.11 Keyboard [SONiX USB Keyboard] on usb-0000:00:14.0-9/input0
[32244.137041] input: SONiX USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.1/0003:0C45:7603.0008/input/input21
[32244.189479] hid-generic 0003:0C45:7603.0008: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [SONiX USB Keyboard] on usb-0000:00:14.0-9/input1

I dont know what more info I can sahre. Ask anything. Bye!
Comment 1 Facundo Curti 2015-06-03 05:56:22 UTC
Fixed with this: (A custom driver)
http://swoogan.blogspot.com.ar/2014/09/azio-l70-keyboard-linux-driver.html

Using these, the special keys like "home", "calc", "next song", "play", etc... Does not works. xev even not receive any signal... (on my keyboard, a nkb-710)
Anyway, it fix the bigger problem... Now I can use it :P (mostly jaja).

I think someone could make a official driver for this, unfortunately, exceeds my knowledge (I just stole someon else's work).

Thank you! Bye!
Comment 2 Facundo Curti 2015-07-18 07:50:29 UTC
Is wrote down this bug? The status didn't change since it was published.
Or maybe it was repeated? (Even when I searched before publishing)

Bye! ;)

Note You need to log in before you can comment on or make changes to this bug.