[SOLVED] Xorg 1.6.5: can't find the xorg.conf file to configure keyboard.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Xorg 1.6.5: can't find the xorg.conf file to configure keyboard.
I would like help to configure xorg to change keyboard layout.
I just did a fresh install of Debian Squeeze (testing) and X 11.0, xorg 1.6.5 is installed. I need to be able to switch keyboard layout and up to now (in my Lenny/Sid I had previously and all previous versions of Debian I've used), I was able to do it by tweaking the /etc/X11/xorg.conf :
My problem is that there is no xorg.conf file in any of the usual locations. I created a new one by X -configure, which I copied to /etc/X11/xorg.conf and edited the keyboard section. But xorg doesn't seem to read it and I still can't switch my keyboard layout.
I'm sure I'm missing the obvious here, I would appreciate any help.
Last edited by dreamwalking; 12-18-2009 at 06:02 PM.
I don't know the answer to your question exactly, but at least in the new Slackware with the new xorg, you CAN create an xorg.conf file and it will be used. It's required for my NVIDIA proprietary driver. On my slack, at least, there is xorgsetup I believe will allow for a remap of the keyboard and set up an xorg.conf file for you. I'm not sure how well it will work, but it's worth a try. You can always just "rm xorg.conf" if it fails to work properly with no ill effects. Of course this has been my experience with slackware_current while trying to sort out a driver issue the last few weeks.
If you do not have an /etc/X11/xorg.conf file, then your X server needs HAL to run.
Which I assume must be my case? That could be why X does not read the xorg.conf I wrote myself but it does read the hal policy file.
Originally Posted by damgar
From a console you can't type
and bring up a curses based program to modify the xserver?
No, this does not work in Debian (I think). I believe in Etch (not sure) there was the equivalent xorgcfg, but now this doesn't work anymore. It's either you manually edit the xorg.conf file, or you reconfigure the package (dpkg-reconfigure xserver-xorg).
But after reading the thread you linked, it seems I should try and modify hal policies instead of xorg.conf.
My machine doesn't require xorg.conf and doesn't have one if I don't create one, it's actually been very handy for me to troubleshoot issues with the nvidia proprietary driver and kernels from 2.6.31 up locking my machine. After the required hard reset I just rename xorg.conf so I startx with an open source driver. Debian (or actually ubuntu) always confuses me
If xorg.conf is missing for some reason, Xorg will probe your hardware on every startup. Though this works fine in most cases, some settings remain inaccessible. To create a starting point for customization, do the following:
Switch to a console as root (not a terminal emulator in X), then run:
Alternatively, reboot the machine in single user mode, then run:
Follow the on-screen instructions. This should give you something to work with.
With Debian these days it is best, IMNSHO, to use the "console-setup" package. Yes, I know that sounds strange since you are asking about X, but if you use this package to set your keyboard on the console, X will automatically use the same settings. So just install the package and answer the config questions it asks you.
I think this has been the situation is sid for about 6 months now.
Yeah, I've heard Slackware is more straight-forward than Debian. I wouldn't mind to have to create my own xorg.conf file (I did already, actually), but I'm puzzled as to why xorg doesn't read it.
I have configured the xdm to iniciate at startup, so I log in directly in X, but even if I go with startx, xorg.conf still doesn't get read.
Thanks for your answer!
gives me only 3 options: "Encoding for the console", "Character set to support" and "Font for the console".
As for the Debian wiki entry, I saw it before posting this thread. My problem is, actually, that X seems to ignore my xorg.conf. However, editing the hald seemed to fix the problem (though ctrl+alt+bksp still doesn't kill X).
And now I have Greek on the console, too! Thanks!
(I was initially hesitant to change the default encoding, but it works fine, I can switch easily between Latin and Greek characters)
Last edited by dreamwalking; 12-19-2009 at 06:11 AM.
Yes, it did give me the option and I did restart X. It just doesn't work.
Googling a bit more about this, it seems to be a feature of X.org > 1.5, supposedly to prevent new users from accidentally killing X and lose their work? I still don't get why users that do want this functionality are not given an easy and obvious option to get it.