Xorg will not use restricted Nvidia driver in Gusty

Bug #116254 reported by Dean Loros
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xorg

Gutsy current release. Closed source Nvidia driver no longer works with current updates as of 5-21-07. Only workaround at this time is to use the nv driver & in my case, xinerama. Affects all kernels that Gutsy uses. reinstalling the nvidia driver, resetting xorg.conf or running without a xorg.conf all result on the nv driver and a non-accelerated desktop.

Revision history for this message
Dean Loros (autocrosser) wrote :

See forum posting for more information---
http://ubuntuforums.org/showthread.php?p=2701620#post2701620

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

If xorg has been updated to 7.3 in Gusty then it might be the NVIDIA binary driver is no longer compatible...

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi Dean, thanks for reporting this bug.

The nvidia driver works okay on my gutsy test system (xserver 1.3, NVS 285), however we did run into an fglrx issue (see bug 115188), so perhaps there is an incompatibility.

Can you describe in more detail what is causing the nvidia driver to not work for you? Please attach your xorg.conf and Xorg.0.log files when trying to load nvidia.

Changed in xorg:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Dean Loros (autocrosser) wrote :

Hi--I'll get info to you in about 6hrs (at work right now). I fussed with my xorg.conf & got the nvidia driver to work in my 22-1 kernel--still no go in anything newer. I'll reboot this evening & get the log to you....

Revision history for this message
Dean Loros (autocrosser) wrote :

Ok--I did four runs--two with the 2.6.22-4 kernel & two with the 2.6.22-1 kernel. Last night I was able to get the nvidia driver & twinview working again in the 22-1 kernel, but it will not finish loading with the 22-4 kernel. I have applied all current (as of 6pm Pacific time--05/23/07) updates with no change in the 22-4 kernel. I see that in the 22-4 kernel the nvidia module loads & then Xorg seems to be looking for the FB module--Why would a framebuffer need to be loaded after the nvidia driver? And why is the 22-1 kernel "seem" not as picky about it? In any case--I have included single & dual .conf files with a info file for reference. If you need more infl, just ask.

Dean Loros

Revision history for this message
Dean Loros (autocrosser) wrote :

Thanks guys!!!

I just got the 22-5 kernel, the nvidia-glx-new & the updated nvidia-kernel-common installed & I can use the nvidia driver with my dual-monitor xorg.conf. The Xorg.0.log looks normal--anything you want me to try or do to see if or how it breaks?

Changed in xorg:
status: Needs Info → Unconfirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Great to hear it's working!

Offhand, the things worth testing are Xinerama+OpenGL, and Compiz. Oh, you could also see if displayconfig-gtk runs with your configuration.

Also, if you happen to continue trying newer kernels, please let us know if you spot regressions with this behavior with any of them.

Thanks,
Bryce

Revision history for this message
Bryce Harrington (bryce) wrote :

Closing as resolved, as per user comment.
Thanks for the bug report!

Changed in xorg:
status: Unconfirmed → Fix Released
Revision history for this message
Dean Loros (autocrosser) wrote :

Hi Bryce--

I'll change over to Compiz as soon as the Compiz/Beryl remerge is thru--If you want, I'll build a couple of xorg .conf's to play with Xinerama--haven't done much with it for a few years...I'll take a look at displayconfig too. I try to be on the bleeding edge all the time, so I'll keep you informed

Thanks for the note!!!
Dean

Revision history for this message
Dean Loros (autocrosser) wrote :

Hi Bryce--

I got displayconfig-gtk---it opens, but I can't change any settings. Where is the preference folder for it?

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi Dean,

There isn't a preference folder for it yet. Also, one reason you may not be able to change settings is that you must run it as superuser: `sudo displayconfig-gtk`.

Bryce

Revision history for this message
Dean Loros (autocrosser) wrote :

Thanks Bryce--

I tend to post first--explore later :( I found that out about 15/20 min after I posted--I see that it is not using the restricted drivers yet--I do have several failures saved--it would configure & crash during the test. Where should I post the fails?

Revision history for this message
Bryce Harrington (bryce) wrote :

You can post the fails to the displayconfig-gtk package in launchpad. It would help if you could doublecheck whether we already have a bug against the given crash (chances are we do).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.