UbuntuThis forum is for the discussion of Ubuntu 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.
Hi there
The nvidia drivers from nvidia.com do work in ubuntu, and are quite an improvement over the stock ones.
I took this to mean the ones in Ubuntu, maybe I was wrong.
After the reboot, the desktop looked better, but the video is still choppy when I move windows around or scroll down a webpage. I don't think this worked 100% of what I was trying to accomplish.
Well in any event, you did get the driver installed successfully, yes?
Is the display excessively choppy. or just a little bit?
Code:
glxinfo | grep direct
Type that into a console, and see what it returns. It should say Yes, Direct Rendering Enabled.
If it is, perhaps we should look at the xorg.conf file next, and see if there's anything obvious in there misconfigured?.
Last edited by GrapefruiTgirl; 04-07-2007 at 06:44 PM.
Ugx..OK, make sure the Modules Section (of /etc/X11/xorg.conf) looks like this (note the GLX item; v4l is optional, only if you use any Video 4 Linux devices):
For one, the nvidia drivers do their own DRI, so you shouldn't need DRI in there.
When you edit the file, you should know you must restart X for any changes to take effect, in case you didn't know..
OK, if it is still all choppy and stuff, post the xorg.conf file. Let's have a look. Also, post the output of 'lspci' from a root console.
Last edited by GrapefruiTgirl; 04-07-2007 at 07:04 PM.
Well, the whole file shouldn't be humungous, provided it isn't like 90% comments and depending on how it's laid out, it's usually best to see the whole thing.
BTW, when you now do 'glxinfo | grep direct' what does it say?
So yes, post the file in {code} tags.
Sure a newer driver may well work with an older card but I question if it will make a noticeable difference in performance. The GPU itself and associated hardware determine the performance. What I can say with certainty that the safest most trouble free driver will be provided by the the distribution developers. If you were to review all the Nvidia driver trouble posts you will see that the bulk of these users went to the command line and didn't use the nvidia-glx provided by Ubuntu. There have been issues on occasion when the kernel gets updated but those problems are solved in a day or to. If you roll your own, every kernel upgrade will be a problem and require special handling by the user. I'm certain that all help offered on the forums is well meaning but that hardly means well informed and thought out.
To attampt to correct the '...RGB GLX...' error in the above glxinfo output, try the following in the Screen section:
Code:
Option "AddARGBGLXVisuals" "True"
Now, your Device section says 'vesa' for a driver. The driver should be "nvidia".
And finally, as Mentioned before, you should not have the DRI section at the bottom. The rest looks well enough to work, even if it may benefit from some fine tuning or other options; these changes should make it work.
And, in case you or anyone is wondering, I have the entire nvidia proprietary drivers tutorial here, which is what I reference when trying to help people with nvidia driver issues. Many people do not seem to have it handy, and it has been invaluable on many occasions. It covers a wide variety of cards and motherboards.
Auto config tools are great, when they work, but in my experience, nvidia's auto-config tool did/does not make my card work, nor many others very well, and ATI's auto-config-tool is much much worse..
EDIT: This post assumes you have at least gotten the driver built and installed..
EDIT2 - this link http://www.linuxquestions.org/questi...d.php?t=299456 indicates that /etc/init.d/gdm stop is how to exit X in Ubuntu. It likely has to be entered as root.
Last edited by GrapefruiTgirl; 04-07-2007 at 10:42 PM.
Just add the "Option" line anywhere in here? Incidentally, this monitor is a Dell P1110 21" and when I setup an older box with Ubuntu as a test box, using this same monitor, about a month ago, it recognized it. This new system with the Abit mobo and the GeForece 6100 isn't recognizing it. Shouldn't I change the "Generic Video Card" and the "Generic Montitor" options here as well?
Code:
Section "DRI"
Mode 0666
Remove this section completely? I missed you saying that before.
And I change the "vesa" part to read "nvidia" now.
Yup, the 'Option' entries, I usually have them right under the 'DefaultDepth' entry.
And yes, the Section "DRI", Mode 0666, and EndSection, are not needed for nvidia.
And yes, the vesa driver will give you no pleasure so it gets changed to 'nvidia'
As for the names of the monitor and device, it isn't too important. Just make sure you type it & spell it exactly the same way, in each reference to it.
Last edited by GrapefruiTgirl; 04-08-2007 at 02:49 PM.
I changed the "vesa" to "nvidia" and I removed the last section about "DRI" and I placed that Option line where you told me to. I don't know which one hosed it, but now it won't even boot into X. I am typing this post from one of my XP boxes. I tried rebooting and choosing "recovery mode" from the GRUB menu, and still nothing. When it tries to load X, the whole screen goes black and nothing happens.
How can I find and edit the xorg.conf file from a cmd prompt?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
