You are not logged in.
Pages: 1
Topic closed
Hi,
I am trying to use a cheap bluetooth keyboard.
So far, it's connected fine but everything beyond is a problem.
Only a few keys are responding and they respond wrong.
For example, pressing the "p" key writes a "*" on the console. Pressing "o" result in a "6" and so on. Most of the other keys doesn't respond at all.
I never had any issues with keyboards so actually I don't know how to debug such issues, maybe you can help me.
Here is my hwinfo output:
PS/2 00.0: 10800 Keyboard
[Created at input.226]
Unique ID: v4Uw.qNkKwQl2yOC
Hardware Class: keyboard
Model: "Bluetooth Keyboard"
Vendor: 0x05ac
Device: 0x022c "Bluetooth Keyboard"
Compatible to: int 0x0211 0x0001
Device File: /dev/input/event15
Device Number: char 13:79
Driver Info #0:
XkbRules: xfree86
XkbModel: pc104
Config Status: cfg=new, avail=yes, need=no, active=unknownI tried to set the keys with:
setxkbmap -device 15 -model pc104 -layout de -variant nodeadkeysbut it didn't change anything.
I can't give you any info on the keyboard itself because it hasn't got any. I bought it from amazon because it was the cheapest - no I regret that descision ![]()
Here the link: http://www.amazon.de/SellerFun-Wireless … B00QTT8JI6
It hadn't got any info-papers or driver cd's with it...
Have you got any suggestions where to start looking or what to try to get this working?
Greetz
0x30
Offline
I've got a similar one (bought in Poland for about €10), mine is called Omega and I also used to have some problems with it. Actually I was unable to enter Polish characters on it, but I believe that my solution might be helpful in some way.
What I did was to create a file /etc/X11/xorg.conf.d/60-keyboard.conf and paste something like this into it:
Section "InputClass"
Identifier "Keyboard0"
#MatchProduct "AT Translated Set 2 keyboard"
MatchIsKeyboard "on"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "pl(intl)"The above is from my PC, where I use that keyboard. In your case, the last line should contain "de" instead of "pl".
I'm not sure that it would solve the problem, but it might. And it should not do any harm ![]()
Last edited by Hwiparam (2015-07-11 07:41:28)
Offline
Have you ever solved this problem?
I also have a cheap bluetooth keybaord
, and I have the exact same problem. What I figured out is that keyboard is behaving this way because it thinks numlock is turned on (although my keboard doesnt even have a num lock button). I managed to fix it by turning numlock off programmatically (using numlockx package), however it happens sometimes that keyboard disconnects for a super short moment then it again thinks that numlock is on, so that is not a solution.
Emacs, Arch Linux. Haskell, web dev
Offline
Please refrain from bumping 2 year old topics, if you have an issue and feel that what's being discussed is still relevant, open a new topic with an up to date description of your problem and link back to this one.
https://wiki.archlinux.org/index.php/Co … bumping.22
Closing this old thread.
Offline
Pages: 1
Topic closed