SlackwareThis Forum is for the discussion of Slackware 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.
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.
Distribution: Slackware 12.2 on Toshiba Satelite p105-s6187, kernel 2.6.27.7
Posts: 10
Rep:
I've searched high and low, but I'm not too experienced with configuring xorg by hand. But, I only have one issue with Slackware and that's the keyboard. I'm using a laptop of course, a Toshiba Satellite P105-S6187. The issue I have is that although the keymapping is correct, the functions on my numeric keypad only function as numbers regardless if NumLock is on or off. But, some of the numbers have double functions. 7 is supposed to double as HOME, 9 as PageUp, 3 as PageDown, 1 as END. So, when NumLock is off the 1 is supposed to function as END and 7 as HOME. Instead, they only function as numbers regardless. Here is my keyboard section from xorg.conf.
Quote:
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
if it was the num lock code then there was still a active file in the /tmp/ this has been a big issue with me running the gnome and kde together on 12.1. for some reason the start up scrpts were not removing the old session in tmp drove me nuts took me a while to figure this out. and as you know there was some bizarre things that were in my logs. radio the esd stuff if you really want some good trouble shooting put the gnome with the kde in slakware and have fun with a seahorse . I am glad you got it.
thats what it is all about.
Distribution: Slackware 12.2 on Toshiba Satelite p105-s6187, kernel 2.6.27.7
Posts: 10
Rep:
Solved! Here's the new code for my Xorg that fixes the numerical keypad issue, and apparently even my VT Switching now works too. I had a problem where, no matter what runlevel I booted into, the second I started X I lost VT Switching. But now, it works, and all I had to do was comment out THIS line.
Before:
Quote:
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
I ran across a blurb that using NumLockX in KDE was unnecessary because the KDE code essentially was the NumLockX code.
The NumLockX homepage says this on them main page.
Quote:
Originally Posted by http://ktown.kde.org/~seli/numlockx/
Note that KDE and many distributions already use NumLockX (or its older version), so you most probably don't need to care.
Quote:
Originally Posted by Woodsman
The only method that seems to eliminate the error messages was not using Num Lock in any manner.
[...]
There is no solution to eliminate the error messages if a user wants to use Num Lock in KDE.
Well, mystery solved although there is no cure.
How about just pushing the numlock button when you want to use it? I grep'd my logs and have never seen your errors, but my numlock is not on by default.
Either that, or you can just ignore the errors as I mentioned earlier since they are apparently just useless noise in this case.
How about just pushing the numlock button when you want to use it? I grep'd my logs and have never seen your errors, but my numlock is not on by default.
Yes, that would be one solution.
As I mentioned, the errors do not appear if in KDE Num Lock is set to Off or Leave unchanged. For people who do not use Num Lock they never will see the errors.
Quote:
Either that, or you can just ignore the errors as I mentioned earlier since they are apparently just useless noise in this case.
For what its worth, With 12.1 installed numlockx running from /.kde/autostart, worked quit well every time; Since installing 12.2, I thought it did not work, until I found and read this thread; Then I realized that even though the light was not on, numlock was enabled
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
