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.
I'm starting to get annoyed with the fact that numlock is always turned off, I'm always greeted with the system bell whenever I start typing numbers. So I stumbled upon Xleds in the xorg.conf file.
Option "Xleds" "1 2 3"
Apparently this will let me use the command `xset led 1` to turn on numlock, but nothing happens. The led mask after running `xset -q` is set at all 0's. The same thing happens with capslock. I can use the numlock and capslock keys, but nothing happens with xset. How can I fix this?
Now scroll lock: The scroll lock button does nothing, but `xset led 3` and `xset -led 3` will turn the status light on/off.
After fidgeting with /etc/X11/xinit/.Xmodmap and setting Scroll_Lock to Mod3, the scroll lock button will turn the led on/off, but I haven't yet tried using xset with Scroll_Lock bound to Mod3.
Also, I heard something about a setting in xorg.conf called ServerNumlock. What exactly does this do, and will that help my situation?
Well, first the Xmodmad file is really only there for one reason......
Quote:
# In versions of XFree86 prior to 4.3.0, a .Xmodmap file was required in
# this directory in order to make the backspace key function correctly.
# This does not seem to be needed any longer, but if you notice problems
# with the backspace key, you might want to try it.
# Old .Xmodmap follows:
keycode 22 = BackSpace
Now, you dont mention what WM you are using........if its KDE.........open up the KDE control center and click on peripherals>keyboard
there will be a check box to turn on/off the numlock when KDE starts up...........
I created my own .Xmodmap file using the output from `xmodmap -pke` then adding and modifying it for the modifier keys. I'll edit it some more, then paste it if necessary.
I'm using fluxbox 0.9.9 so KDE's options don't help, but thanks anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.