Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
I made a xorg.conf file, and set it up the way I would think it would work, but still only the primary monitor is working. I am using a single video card (Nvidia GeForce 9800GT) with 2 DVI ports on the back.
When I change driver to "nv", X immediately gives a fatal error and returns to the command line.
I had to append .txt to the filename because the forum software wold not let it through.
This are the lines I would change, in case you have never seen a diff, the lines starting with '-' are the ones I would delete, and the ones starting with '+' are the ones I'd add (most times it's just a trivial change from one to another).
However as said my experience with nv is quite limited. I am not sure if that's the right way to disable xrandr with nv. I don't even know if nv has a working support for xrandr. In any case randr only gave me problems in the past. Maybe it's my brain from the paleolithic the real problem, who knows.
The resolutions are of course mine, you should set yours instead.
I don't know how to do that because it happens in command-line mode (so I can't copy/paste), and using tee woundn't work because it goes to stderr. Is there a way to use tee to capture stderr along with stdout?
Yes, there are ways, you can redirect file descriptors at your wish, for example:
startx >$HOME/mylogfile.txt 2>&1
This works for bash, it might be slightly different for each shell. However, the file descriptor 1 is always stdout, and the second is stderr. That sentence redirects stdout to a file, and then stderr to stdout. You can read more about that here. Note that the order in which you redirect the streams matters.
Also, if you have gpm running you can just select the text with the mouse (yes, even in the console), then open an editor and paste it with middle click. This way is a pain and it won't work for anything bigger than the scroll buffer of your console, so I advice the other method.
The easiest way would probably be to just attach the log file: /var/log/Xorg.0.log, that file will likely contain more detail about the real problem than the startx output, most times.
The driver is failing to load in a nasty way. This kind of thing happens sometimes when the server and the driver are not in sync (different versions, or from different repositories, or compiled against different header versions). So check that everything is sane in that regard, if you used any external (as in non-official) repository try reinstalling the xorg server and all the drivers using the official packages.
If that doesn't work, then please attach the full log file so we can see if there's anything else that I can see. However this kind of error is not usually due to a bogus xorg.conf file, but, as said, I am no master when it comes to "nv".