Update nvidia-glx-new package to latest 100 series driver

Bug #120943 reported by Chris Halse Rogers
108
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Please update the nvidia-glx-new package to the new nvidia.com 100.14.11 driver release. Release notes:
http://www.nvidia.com/object/linux_display_amd64_100.14.11.html

The highlight for us would be support for a bunch of new Geforce 8 series cards.
(Bug description updated; there's been a new stable driver release - 100.14.11 rather than 100.14.9. Release notes suggest that this one might also fix VT switching)

Daniel T Chen (crimsun)
Changed in linux-restricted-modules-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Wishlist
status: Unconfirmed → Confirmed
Revision history for this message
Yann Klis (strass) wrote :

This chipset is usually present on all recent laptops through the Nvidia Quadro * NVS denomination. For example, my Thinkpad T61 doesn't work with the nv driver (system freeze), vesa is quite ugly and the only solution ATM to have a usable desktop is to use the Nvidia proprietary driver starting at version 100.14.09

description: updated
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote : Re: Update nvidia-glx-new pacakge to 100.14.11

Perhaps this bug should be retitled "Update nvidia-glx-new package to 100 series driver"?

Revision history for this message
sophizzle (launchpad-phun) wrote :

the old driver is not only breaking my X-System, but also my balls...... :-(
please update it..

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

This bug is for 7.10 (Gutsy). See Bug #121096 for 7.04 (Feisty).

Revision history for this message
VF (vfiend) wrote :

I'm running the new nvidia drivers and they do seem to fix vt switching, that's a huge reason to get them in.

Revision history for this message
Christian Schürer-Waldheim (quincunx) wrote :

that's great news - do you know anything about the "black windows" bug, which occurred with compiz/beryl? It would be great if this one is fixed too.

Revision history for this message
VF (vfiend) wrote :

Nope, I've actually never experienced that bug so I can't help you there.

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

Christian:
Please see Bug #96473 for the "NVIDIA black windows" bug.

Revision history for this message
Travis Watkins (amaranth) wrote :

Please don't do this upgrade, it makes my system lock up when compiz is running and you try to kill/restart X (like, say, when you're rebooting).

Revision history for this message
stivani (stivani-deactivatedaccount) wrote :

I can confirm that the Nvidia Quadro NVS 140M needs the updated driver from the 100 series. I hope this driver will find its way into Gutsty.

Revision history for this message
mangar (mycrapaccount-deactivatedaccount) wrote :

Using 8800gts, with the nv driver, there's no support for dual screens.
with the nvidia-glx driver installed with restricted manager, there's a "no screens found" error.
with Alberto's Envy (slightly modified to recognize gutsy), 3d acceleration, twinview works.

Since not using this driver removes several, popular use cases, I think that the driver should be upgraded.
Thanks in advance!

Revision history for this message
Instabin (jcampbell-z3wave) wrote :

Why does ubuntu have to update nvidia-glx-new.
Can we just make a nvidia-glx-100.14.11, that would solve everyones problems.

Revision history for this message
Instabin (jcampbell-z3wave) wrote :

Also this driver also supports the Geforce FX through 8xxx series cards.
If its implement it would be great if the restricted drivers manager selected it by default for the supported cards.

Revision history for this message
Alvin (alvind) wrote :

I can confirm that the Nvidia Quadro FX 570M needs the updated driver.

Revision history for this message
Jasey (jason-rivers) wrote :

I can confirm that all my games require this driver as i'm on an 8600GTS It would be nice to have this setup by default so my system works OTB.

Revision history for this message
Michael R. Head (burner) wrote :

Confirmed that my new T61P is not supported by any of nv, nvidia-glx, or nvidia-glx-new. It's a Quadro FX 570M that is only supported by vesa or the 100-series of nvidia drivers.

Revision history for this message
slamdunk (antongiulio05) wrote :

I need of this driver for my Dell XPS M1330 with Nvidia 8400GS.

I tried to install manually driver, but there are many problems:

1) metacity disappared (and so windows borders are not showed)
2) freeze after few seconds
3) auto-launch of compiz (I don't know why)

If you use "nv" or "vesa" in your xorg.conf you get very slow performances (glxgears returns less of 200 FPS) and for example, a DVD playing is jerky.

Does anybody know what a kind of problems there are to include it in gutsy-repositories?

Thanks,
Julio

Revision history for this message
Yagisan (yagisan) wrote :

This bug has 5 duplicates

Can someone from canonical state whether or not they will include this driver. Yes - I know its not opensource, but a great many of us need it as nv or vesa don't work well. I have a dual core 64bit 2.3Ghz gutsy system hear, and just reading pdf's in the ubuntu default view pegs 1 core at 100% and it lags worse then my pentium 2 system does. We have 3 nvidia drivers, I don't see how we can regress much further by updating this package.

02:00.0 VGA compatible controller: nVidia Corporation GeForce 8500 GT (rev a1)

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

OK I've noticed an update hitting the mirrors for Gutsy (but it looks like the linux-image update is still propagating and has some dependency issue). It would be useful to hear whether the update "resolves" this issue for the original reporter (Chris) and for most of the other people posting to this bug.

Travis:
I guess you can't please all of the people all of the time...

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

Yagsian:
Issues appear to have been introduced when three packages for the NVIDIA drivers were formed in Feisty. See https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/121096/comments/3 for some details. Whether its possible to regress further is not clear cut - I guess it depends on the testing/reporting upon release...

Revision history for this message
Yagisan (yagisan) wrote :

Sitsofe Wheeler :
It's the nvidia binary driver - they always break something new on each upgrade - its what they do - But we don't ship the experimental nouveau drivers (even if we did - I'd still need this binary driver so I can run renouveau and submit my new card). I'll wait for the updates to appear on the mirror I'm using, and will post back after trying it out.

Revision history for this message
Michael R. Head (burner) wrote :

So 2.6.22-10-generic and the most recent nvidia-glx-new are at 100 series now. When I booted after the latest kernel update, restricted manager asked if I'd like to install the nvidia binary drivers, and did so, installing the new hotness.

Cheers!

Since I didn't report this, I won't close it, but someone else may want to.

Revision history for this message
Michael R. Head (burner) wrote :

By the by, bug 98641 is still in effect, which sorta mitigates the usefulness of this fix for me...

Revision history for this message
slamdunk (antongiulio05) wrote :

Yes there is that bug, and follow last message by "Michael R. Head" and :

modprobe nvidia_new

it works:)

Julio

Revision history for this message
slamdunk (antongiulio05) wrote :

Suddenly it doesn't work :(

After restarting system I got from Xorg.log:

(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure
(EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and
(EE) NVIDIA(0): that the NVIDIA device files have been created properly.
(EE) NVIDIA(0): Please consult the NVIDIA README for details.
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Julio

Revision history for this message
Chris Halse Rogers (raof) wrote :

nvidia-glx-new is now the latest 100 series driver, so this bug is closed. Works for me, although I note that the libwfb module is still missing.

Changed in linux-restricted-modules-2.6.22:
status: Confirmed → Fix Released
Revision history for this message
Christian Schürer-Waldheim (quincunx) wrote :

@slamdunk: do you have the linux-restricted-drivers (ABI version 10) package installed too?

Revision history for this message
Yagisan (yagisan) wrote :

Well, the good news is, the driver detects my new card - the bad news - as others have mentioned https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/98641 and https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/103050 still exist - effectivly making this bug not fixed. No point having an updated driver that doesn't actually work.

Revision history for this message
slamdunk (antongiulio05) wrote :

@Christian Schuerer

that's my packages installed list:

# apt-show-versions | grep linux
linux-headers-2.6.22-10/gutsy uptodate 2.6.22-10.30
linux-restricted-modules-2.6.22-9-generic/gutsy uptodate 2.6.22.2-9.8
util-linux-locales/gutsy uptodate 2.13~rc3-5
linux-headers-2.6.22-9-generic/gutsy uptodate 2.6.22-9.25
linux-image-2.6.22-9-generic/gutsy uptodate 2.6.22-9.25
linux-image-generic/gutsy uptodate 2.6.22.10.11
linux-libc-dev/gutsy uptodate 2.6.22-10.30
linux-ubuntu-modules-2.6.22-9-generic/gutsy uptodate 2.6.22-9.22
linux-restricted-modules-common/gutsy uptodate 2.6.22.3-10.1
linux-headers-2.6.22-10-generic/gutsy uptodate 2.6.22-10.30
linux-sound-base/gutsy uptodate 1.0.14-1ubuntu1
linux-image-2.6.22-10-generic/gutsy uptodate 2.6.22-10.30
linux-headers-generic/gutsy uptodate 2.6.22.10.11
linux-headers-2.6.22-9/gutsy uptodate 2.6.22-9.25
linux-ubuntu-modules-2.6.22-10-generic/gutsy uptodate 2.6.22-10.23
libselinux1/gutsy uptodate 2.0.15-2ubuntu1
util-linux/gutsy uptodate 2.13~rc3-5
linux-restricted-modules-2.6.22-10-generic/gutsy uptodate 2.6.22.3-10.1

I suppose you refer to "linux-restricted-modules-2.6.22-10-generic/gutsy uptodate 2.6.22.3-10.1"

Revision history for this message
slamdunk (antongiulio05) wrote :

I don't know why, but I need to do everytime I restart my system:

# modprobe -r nvidia
# modprobe nvidia_new

put nvidia_new in /etc/modules doesn't work

Revision history for this message
slamdunk (antongiulio05) wrote :

Ok solved with:

DISABLED_MODULES=”nvidia nv”

in /etc/default/linux-restricted-modules-common

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

slamdunk:
Sounds like the reverse form of the hidden file problem (i.e. the dotfile that indicates the use of the new driver is missing...). Be careful with DISABLED_MODULES=”nv" - at the moment it is broken and doesn't disable the nvidia-glx-new driver as it should (see Bug #105756 )

Revision history for this message
reliable-robin-22 (nicolasdiogo) wrote :

hi,

i am using a Nvidia Geforce 8600gts on a desktop.
and using Gutsy:
Linux buda 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 GNU/Linux

i am having problems with this card, and i found this page while searching for a solution.
after installing the nvidia-glx-new i only had a black screen with no option of using a different screen to fix the problem (tty0, tty1..), which will be a problem for new users.
but i have fixed the problem by connecting throuhg ssh and following advice of slamdunk:

# modprobe -r nvidia
# modprobe nvidia_new

but i have only used once so far. and everything seems fine for the moment.

i suppose one could alter the section of modules in the xorg.conf file to load nvidia module by adding ( Load nvidia ).

additionally, i have two monitors connected to this card and the new Screen and Graphics did not detect them. so i have used nvidia-settings tool to configure my xorg.conf file. should i open a bug report for that?

system:
amd64 5200+
motherboard: GA-M57SLI-S4
ram: 2gb ddr2 667
monitors: samsung syncmaster 226bw and 913n

Revision history for this message
zeddock (zeddock) wrote :

I have changed the status to confirmed from Fix released as the last comments here do not sound like the fix has worked. If I shouldn't do this, please let me know and I am sorry.

zeddock

Changed in linux-restricted-modules-2.6.22:
status: Fix Released → Confirmed
Revision history for this message
Reed Lipman (rmlipman) wrote :

I can confirm the missing libwfb is the same bug as https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/98641 . Applying the fix described for the 9755 driver but using the 100-series libraries worked for me.

Revision history for this message
slamdunk (antongiulio05) wrote :

Since last updates suddenly performances are halved.

glxgears returns now 2500 fps (before 4800) and 3d animations are jerky

attached my /var/log/Xorg.0.log

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

slamdunk:
Probably a separate issue to this one - check whether it's been filed already and if not please open a new bug report. If you're worried about speed though then I ensure you're not using a compositing manager (e.g. desktop effects are completely off) before running tests.

Revision history for this message
slamdunk (antongiulio05) wrote :

@Sitsofe:

I'm using gnome without effects for my tests (no compiz etc.)
open here new bug-report: https://bugs.launchpad.net/ubuntu/+bug/136650

Revision history for this message
Travis Watkins (amaranth) wrote :

The initial reporter was asking for the driver to be updated to 100.14.11, now it is. If you have other issues please take them to their respective bug reports or file new ones.

Changed in linux-restricted-modules-2.6.22:
status: Confirmed → Fix Released
Changed in dell:
status: New → Fix Released
Revision history for this message
Michael R. Head (burner) wrote :

And now we're up to 100.14.19! w00t!

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Changed in somerville:
status: New → Fix Released
no longer affects: dell
Revision history for this message
Timothy R. Chavez (timrchavez) wrote :

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305638

no longer affects: somerville
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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