SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Some times ago its appeared I have a couple of problems related X
1. Only, and only KDE reacts on magic keystroke Alt+Ctrl+Backspace. Neither xfce, fluxbox, blackbox, wmaker, fvwm2 or twm reacts. I'm personally using xfce and sometimes fluxbox, and never kde. Other my desktop PC with the same Slackware have not such problems.
2. Only, and only root user can use keyboard in X. Other users can use mouse only. Even Alt+Ctrl+Backspace unusable. And I cannot understand what wrong.
I'm quite newbie in configuring X-related stuff, and cannot remember what I could do to cause such behaviour. Shall be thankful for any help.
2. are you using a custom xorg.conf? what keyboard do you have there?
What do you mean "custom"?
It always custom, because it was generated by xorgsetup. And I did not found any installed packages which provides own xorg.conf as out-of-box configuration.
Keyboard model is Mitsumi KFK-EA4XT.
w1k0, I do not have any problems with localisation or keyboard layout. My problem is with keyboard as input device itself.
I would suggest hashing the keyboard entries in xorg.conf and let hal config it (using evdev instead of kbd) but since you tried without xorg.conf, you have already done it. Have you read /var/log/Xorg.0.log to see if there is any error opening the device or something ?
I am a bit confused. According to your log, hal configured the devices. If you have set them in xorg.conf, it should get first priority and not hal.
Also, unless you have added an fdi file in /etc/hal, hal shouldn't set your layouts and options.
This "Keyboard0" you have configured in xorg.conf, is it set in the "ServerLayout" section ? Is there a line InputDevice "Keyboard0" "CoreKeyboard" ?
Something definitely wrong with my slackware installation!
I have new weird log message, when starting X as root(without any xorg.conf). Do not have it now, but it says that "AllowEmptyInput is true and so all input devices will be blocked". And they actually got blocked, until I set in xorg.conf AllowEmptyInput to false. What is this was? What stupid script creates those setting?
And again, problem of keyboard absence for non-root users is still actual.
II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AutoAddDevices.
From CHANGES_AND_HINTS.TXT for Slackware 13.1
Speaking of Xorg, the version of Xorg shipped with Slackware 13.1 will not
(in most cases) require an /etc/X11/xorg.conf file at all. Configuration of
input devices and such is handled by HAL, and the X server autoconfigures
everything else. You can still create an xorg.conf file if you wish, or you
can create a minimal xorg.conf with only the specific contents that you wish
to override (as an example, to use a binary-only video driver).
Due to removed drivers and other such changes, it's quite possible that your
old xorg.conf will not work correctly with this version of Xorg.
If you need to use a non-US keyboard layout, then copy the file located at
/usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi to /etc/hal/fdi/policy
and edit it to suit your needs. Have a look at the contents of that file
for an example and more information. If you prefer to do this the "old" way
using /etc/X11/xorg.conf, then you can use "X -configure" or "xorgsetup" to
generate an xorg.conf, then add the following lines to the "ServerFlags"
section to disable input device hotplugging via HAL:
Option "AllowEmptyInput" "false"
Option "AutoAddDevices" "false"
Option "AutoEnableDevices" "false"
This is also relevant if you prefer to disable HAL completely for whatever
There seems to be problem with your HAL setup. Check your configuration files in /etc/hal/fdi/policy (or just delete them to use the defaults). Also check that the HAL daemon is being started at boot. Make sure that /etc/rc.d/rc.messagebus and /etc/rc.d/rc.hald are executable.