Keyboard issue

damico · 2016-12-18 14:43:37

Hi,

I'm using Arch Linux more than one year, and recently, I had to change my microsoft wireless keyboard, and bought Multilaser TC200 Mechanical keyboard. The problem is, this keyboard has an issue that the keys left control, windows key (or super L), left alt, alt gr, right control and right shift, always works like left shift. I realize that looking in Region and Language, and looking in keyboard configuration (map).

I tried to change the keyboard, but nothing happened. I've searched a lot, but was no lucky.

I also tried in Windows 10, and works fine.

Please help me fix this error.

Thanks in advance.

Last edited by damico (2016-12-18 15:29:26)

Texbrew · 2016-12-18 15:09:49

always works like left shit.

Oh man, we gotta watch our typos, but you can blame that one on your keyboard. Have you tried a wired keyboard? Apologies, I can't help you with keyboard mapping, I have never had to change any of mine. But then, I don't use wireless keyboards, either.

I feel your pain, though. I had to muddle through getting an ancient ps/2 keyboard to work on an ancient PC when I did my first bare metal Arch install.

I don't have the answer you seek, but I bet there is an answer out there looking for you.

damico · 2016-12-18 15:28:54

Texbrew wrote:

always works like left shit.
Oh man, we gotta watch our typos, but you can blame that one on your keyboard. Have you tried a wired keyboard? Apologies, I can't help you with keyboard mapping, I have never had to change any of mine. But then, I don't use wireless keyboards, either.
I feel your pain, though. I had to muddle through getting an ancient ps/2 keyboard to work on an ancient PC when I did my first bare metal Arch install.
I don't have the answer you seek, but I bet there is an answer out there looking for you.

I think that was not clear. I changed my wireless keyboard to a new one, that is a Multilaser TC200 mechanical.

I hope to find an answer.

Edit: Fixed the typo.

Last edited by damico (2016-12-18 15:29:56)

Texbrew · 2016-12-18 15:43:49

No, the apologizing ball is in my court. I missed the word mechanical in your post. And I couldn't resist the temptation to tease you for the typo. I'll try to be serious at least for the rest of today.

And I sincerely hope you find your answer, no shift. Oh shift, there I go again. I'm sorry.

seth · 2016-12-18 16:23:21

Is this on X11 or gnome on wayland?
In case of xorg, dump "setxkbmap -query -print" and in case of wayland, try X11 first.

damico · 2016-12-18 16:39:55

seth wrote:

Is this on X11 or gnome on wayland?
In case of xorg, dump "setxkbmap -query -print" and in case of wayland, try X11 first.

Hi,

these are the output:

[rodrigo@archdesk ~]$ loginctl show-session c3  -p Type
Type=x11
[rodrigo@archdesk ~]$ setxkbmap -query -print
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+br+us:2+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
rules:      evdev
model:      pc105
layout:     br,us
variant:    ,
[rodrigo@archdesk ~]$

seth · 2016-12-18 17:44:08

Try "setxkbmap -model evdev" but the most likely reason is the double layout. Also the "dead" comma in the variants strikes me odd.
How do you configure the keyboard? xorg configlet, ie. /etc/X11/xorg.conf.d/11-keyboard.conf ?

damico · 2016-12-18 20:05:16

seth wrote:

Try "setxkbmap -model evdev"

I tried that but nothing happened (apparently).

seth wrote:

Also the "dead" comma in the variants strikes me odd.
How do you configure the keyboard? xorg configlet, ie. /etc/X11/xorg.conf.d/11-keyboard.conf ?

Should I quit that comma?
Well, My configuration was automatically. I also tried some things a couple of days ago, so the things can be differently from the "automatic configuration".
I found the file above:

[rodrigo@archdesk xorg.conf.d]$ cat 00-keyboard.conf 
# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "br"
EndSection
[rodrigo@archdesk xorg.conf.d]$

seth · 2016-12-18 20:12:41

The keyboard is probably reconfigured by some runtime tool (of your session).
Try to log into a failsafe X11 (eg. startx) and see whether the behavior is similar there (or the keyboard behaves as expected)

"Automatically" implies you're not applying some overly weird xmodmap's, are you?

damico · 2016-12-18 21:12:20

seth wrote:

The keyboard is probably reconfigured by some runtime tool (of your session).
Try to log into a failsafe X11 (eg. startx) and see whether the behavior is similar there (or the keyboard behaves as expected)
"Automatically" implies you're not applying some overly weird xmodmap's, are you?

No lucky. And no weird xmodmap.

I also tried live versions of Ubuntu, Linux Mint (Cinnamon), Fedora. All have same behavior.

seth · 2016-12-18 21:20:38

Kernel level issue? Do the keys behave the same on VT1 and/or produce wrong codes with "showkey"?

damico · 2016-12-18 21:33:42

seth wrote:

Kernel level issue? Do the keys behave the same on VT1 and/or produce wrong codes with "showkey"?

About the kernel, I don't know. I don't know that much in linux.

In showkey, the "problem" keys produce no codes. Other keys are shown below.

[rodrigo@archdesk ~]$ showkey -a --ascii

Press any keys - Ctrl-D will terminate this program

\ 	 92 0134 0x5c
z 	122 0172 0x7a
	 	  9 0011 0x09

seth · 2016-12-18 21:36:41

Just log into a virtual terminal (Ctrl+Alt+F1) and try there.
The specific showkey command won't expectably show anything since SHIFT etc ain't printable. Omit all switches and only check the keycodes.

damico · 2016-12-18 21:41:57

seth wrote:

Just log into a virtual terminal (Ctrl+Alt+F1) and try there.
The specific showkey command won't expectably show anything since SHIFT etc ain't printable. Omit all switches and only check the keycodes.

All "problem" keys results in keycode 42

seth · 2016-12-18 21:55:09

Looks bad, check "showkey --scancodes" (the output is weird, you'll get numbers for presses and releases and also printable chars print text - just check whether some problematic keys produce the very same output)

damico · 2016-12-18 22:02:41

seth wrote:

Looks bad, check "showkey --scancodes" (the output is weird, you'll get numbers for presses and releases and also printable chars print text - just check whether some problematic keys produce the very same output)

The scancode of problematic keys produce the same codes (0x2a and 0xaa)

seth · 2016-12-18 22:12:39

Is that thing programmable? (ie. can you upload specialized keymaps into probably cost-efficient volatile storage of the keyboard)?

otto_simpson · 2017-05-11 19:47:17

I spent all my day in this, unbelievable but I found a solution:

You need to download this driver here https://bitbucket.org/Swoogan/aziokbd/src

Open the aziokbd.c file and edit the following

Line 43: #define ML_PRODUCT_ID 0x760a
Line 69: /* 72-79 */ KEY_RIGHTBRACE, KEY_BACKSLASH, KEY_BACKSLASH, KEY_SEMICOLON, KEY_APOSTROPHE, KEY_GRAVE, KEY_COMMA, KEY_DOT,
Line 94: /* 224-231 */ KEY_RESERVED, KEY_RESERVED, KEY_RESERVED, KEY_RESERVED, KEY_RESERVED, KEY_RESERVED, KEY_RESERVED, KEY_RO,

Install in the dkms option

$ sudo ./install.sh dkms #inside project folder

do not forget you need the base-devel, linux-headers and dkms packages to do this, besides the mercurial package to download in the Swoogan repository

After that it is necessary to add a parameter in the kernel, in my case with grub I edited the /etc/default/grub file by entering the parameter usbhid.quirks=0x0c45:0x760a:0x4 in GRUB_CMDLINE_LINUX_DEFAULT, getting

GRUB_CMDLINE_LINUX_DEFAULT = "quiet usbhid.quirks=0x0c45:0x760a:0x4"

And then automatically re-generate the grub.cfg file with:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

Restart and test it, if it does not work switch usbhid.quirks =0x0c45:0x760a:0x4 by usbhid.quirks=0x0c45:0x760a:0x7 in GRUB_CMDLINE_LINUX_DEFAULT, re-generate the grub.cfg and restart again.

Credits:
https://bitbucket.org/Swoogan/
https://bitbucket.org/Swoogan/aziokbd/i … t-22264835
http://adrenaline.uol.com.br/forum/thre … 1072836541

Arch Linux

#1 2016-12-18 14:43:37

Keyboard issue

#2 2016-12-18 15:09:49

Re: Keyboard issue

#3 2016-12-18 15:28:54

Re: Keyboard issue

#4 2016-12-18 15:43:49

Re: Keyboard issue

#5 2016-12-18 16:23:21

Re: Keyboard issue

#6 2016-12-18 16:39:55

Re: Keyboard issue

#7 2016-12-18 17:44:08

Re: Keyboard issue

#8 2016-12-18 20:05:16

Re: Keyboard issue

#9 2016-12-18 20:12:41

Re: Keyboard issue

#10 2016-12-18 21:12:20

Re: Keyboard issue

#11 2016-12-18 21:20:38

Re: Keyboard issue

#12 2016-12-18 21:33:42

Re: Keyboard issue

#13 2016-12-18 21:36:41

Re: Keyboard issue

#14 2016-12-18 21:41:57

Re: Keyboard issue

#15 2016-12-18 21:55:09

Re: Keyboard issue

#16 2016-12-18 22:02:41

Re: Keyboard issue

#17 2016-12-18 22:12:39

Re: Keyboard issue

#18 2017-05-11 19:47:17

Re: Keyboard issue

Board footer