Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-09-2006, 03:08 PM
|
#1
|
Member
Registered: Feb 2005
Posts: 57
Rep:
|
Keyboard trouble
Hi,
I run Gentoo with KDE and I have a german keyboard (Cherry RS 6000 M). However only the "basic" keys work, i.e. no "@", no "|", no umlauts like "ü", no backslash. And the KDE Keyboard Tool (the little flag in the panel that indicates which keyboard layout you are using) shows "ERR: Error changing keyboard layout to 'de(nodeadkeys)'" (or "... to 'en(basic)'"). In the KDE Control Center I set - Keyboard model: Generic 104-key PC (tried several other)
- Active layouts: "us basic" and "de nodeadkeys" (tried also "de basic")
Here is my /etc/X11/xorg.conf:
Code:
Section "ServerLayout"
Identifier "X.Org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "AlwaysCore"
...
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbOptions" "grp:toggle,grp_led:scroll"
Option "XkbVariant" ",winkeys"
EndSection
...
Any idea anyone?
Thanks a lot guys!
Max
|
|
|
11-09-2006, 03:10 PM
|
#2
|
Senior Member
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507
Rep:
|
try "pc105" instead of "pc104".
|
|
|
11-10-2006, 05:22 AM
|
#3
|
Member
Registered: Feb 2005
Posts: 57
Original Poster
Rep:
|
Hi uselpa,
thx for your post. I changed Option "XkbModel" "pc104" to Option "XkbModel" "pc105" in the xorg.conf and set the keyboard model to "Generic 105-key (Intl) PC" in the KDE Control Center. Didn't work though.
What else could I try?
Max
|
|
|
11-10-2006, 02:22 PM
|
#4
|
Senior Member
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507
Rep:
|
Try something minimalistic, without CoreKeyboard, Options and Variant. Here's mine, for example (for a swiss-french keyboard):
Code:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "ch"
Option "XkbVariant" "fr"
EndSection
so yours should be
Code:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
EndSection
|
|
|
11-11-2006, 09:01 AM
|
#5
|
Member
Registered: Feb 2005
Posts: 57
Original Poster
Rep:
|
Sweet! It works!
You cannot imagine how good it feels to just press the button for "@" and see it appearing on the screen
Thx again!
|
|
|
11-12-2006, 05:09 AM
|
#6
|
Member
Registered: Feb 2005
Posts: 57
Original Poster
Rep:
|
Arg!! I just realized something weired: When I do a console login and then startx, they keyboard works. When I do a graphical login to KDE, the keyboard doesn't work (e.g. behaves as described above)!
What could the problem be?
Thanks again,
Max
|
|
|
11-12-2006, 06:43 AM
|
#7
|
Senior Member
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507
Rep:
|
One possible reason I see is that you have more than one xorg.conf (or any of its other possible names) and that, when X is started from the initscripts, it uses another conf file or another combination of conf files than the one used by a manual startx command.
If you start it manually, you're probably not root, but your init scripts are run by root. So your root user might have a personal .xserverrc that changes the keyboard settings. Try to log in as root and type "startx", does the keyboard work? What if you are another user?
If that doesn't clarify the issue, look for local configuration files, analyse your initscripts and see how X is started in your 'graphical' runlevel, or the brute-force method: as root, type "cd / && grep -R Keyboard * | less". The latter will take some time, though.
|
|
|
All times are GMT -5. The time now is 03:40 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|