nvidia-glx-new-envy 173.14 not working

Bug #239536 reported by Marco da Silva
14
Affects Status Importance Assigned to Milestone
linux-restricted-modules-envy-2.6.24 (Ubuntu)
Fix Released
Undecided
Alberto Milone

Bug Description

The latest update in the proposed-repository ( 2.6.24.501-501.30 ) isn't getting my X right.

01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)

It goes to VESA.

Had to revert to previous driver.

Revision history for this message
Marco da Silva (igama) wrote :

Forgot to say some things...

Ubuntu Hardy 32 bits

In the Log:

(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

Revision history for this message
Alberto Milone (albertomilone) wrote :

Please, try this:

type:
sudo apt-get install linux-headers-$(uname -r)

then upgrade to the latest driver and type:
sudo dkms add -m nvidia -v 173.14.05 -k $(uname -r)
sudo dkms build -m nvidia -v 173.14.05 -k $(uname -r)
sudo dkms install -m nvidia -v 173.14.05 -k $(uname -r)

Let me know how it goes. If there are problems, please post them here.

Changed in linux-restricted-modules-envy-2.6.24:
assignee: nobody → albertomilone
Revision history for this message
Christoph Lukas (christoph-lukas) wrote :

This happened to me too.

Had to uninstall linux-restricted-modules to make it work.

Revision history for this message
Marco da Silva (igama) wrote :

Alberto, after doing what you sugested it still didn't work.

I had to do what Christoph sugested and removed the package linux-restricted-modules-$(uname -r)

With this, in the Nvidia Settings shows Driver Version : 173.14.05

Revision history for this message
Alberto Milone (albertomilone) wrote :

Marco, Cristoph: did you put nv or nv_new in the blacklist in /etc/linux-restricted-modules-common ?

This is what people do when they install the driver from the installer from NVIDIA's website.

Revision history for this message
Christoph Lukas (christoph-lukas) wrote :

Neither nv nor nv_new.

After booting I found the following in syslog:

Jun 13 14:35:31 hardy kernel: [ 73.664800] NVRM: API mismatch: the client has the version 173.14.05, but
Jun 13 14:35:31 hardy kernel: [ 73.664805] NVRM: this kernel module has the version 169.12. Please
Jun 13 14:35:31 hardy kernel: [ 73.664807] NVRM: make sure that this kernel module and all NVIDIA driver
Jun 13 14:35:31 hardy kernel: [ 73.664810] NVRM: components have the same version.
Jun 13 14:35:36 hardy kernel: [ 78.761166] NVRM: API mismatch: the client has the version 173.14.05, but
Jun 13 14:35:36 hardy kernel: [ 78.761170] NVRM: this kernel module has the version 169.12. Please
Jun 13 14:35:36 hardy kernel: [ 78.761173] NVRM: make sure that this kernel module and all NVIDIA driver
Jun 13 14:35:36 hardy kernel: [ 78.761175] NVRM: components have the same version.

The old module seemed to be present in /lib/modules/$(uname -r)/volatile along with the new one in /lib/modules/$(uname -r)/updates/dkms and the old one seemed to be loaded.

Revision history for this message
Alberto Milone (albertomilone) wrote :

Cristoph: try this:

1) log out and press CTRL+ALT+F1 (so as to get to the command line).

2) Shut down the Xserver with either:
sudo /etc/init.d/gdm stop

or (if you use KDM):
sudo /etc/init.d/kdm stop

3) type:
sudo rmmod nvidia
sudo modprobe nvidia

4) Restart the Xserver:
sudo /etc/init.d/gdm start

or (if you use KDM):
sudo /etc/init.d/kdm start

Revision history for this message
Christoph Lukas (christoph-lukas) wrote :

Thanks for your suggestions but this did not solve it for me.

I already booted in rescue mode and tried to rmmod, modprobe, still loading the old version from the volatile dir.

But removing linux-restricted-modules works for me. Thanks again.

Revision history for this message
Carsten Schurig (cs42) wrote :

Doesn't work for me too. I'm using 2.6.24-19-server kernel. DKMS gives an error on build (see the attachment).

Unfortunately envyNG removes all the old packages first, but doesn't reinstall them even though installation of the new modules fails!

BTW install runs fine on this system if I use 2.6.24-19-generic as kernel.

Revision history for this message
Alberto Milone (albertomilone) wrote :

Carsten: I don't understand the errors since they are in German.

1) try typing:
sudo apt-get install linux-headers-$(uname -r)

2) I don't know whether the -server flavour is xen-enabled (and this could explain the failure)

Revision history for this message
Carsten Schurig (cs42) wrote :

1) the headers are installed
2) I think this flavour is Xen enabled, esp. as the compile error happens in some xen related part

Revision history for this message
Infinity_ (infinity-gm) wrote :

it doesn't work for me either, after installation and reboot, the nvidia logo doesn't show up, then gnome runs a low graphic mode.

Revision history for this message
Infinity_ (infinity-gm) wrote :

sorry forget to list my machine state:
nvidia 6600gt AGP,
ubuntu 8.04, 2.6.14.19-generic kernel
installed it with envyng.

Revision history for this message
The Punisher (melprinsi) wrote :

try this:

sudo apt-get install build-essentials

and install headers.

That's all folks, reboot and It will work!

Revision history for this message
getaceres (getaceres) wrote :

I had the same problem on a recently installed Hardy system. I tried to install the envy nvidia driver directly but I got this problem. I think that nvidia-glx-new-envy (or envy nvidia kernel source) should depend on build-essentials.
Also, it would be great if installing the driver packaged, it configured the xorg.conf file to start using it.

Revision history for this message
Alberto Milone (albertomilone) wrote :

all the ones who can get this driver to work:
I think the latest release of the NVIDIA driver should solve the problem:

getaceres:
1) can you open a bugreport about the dependency on the build-essentials, please?
2) for xorg.conf configuration it would be better if you used EnvyNG.

Revision history for this message
getaceres (getaceres) wrote :

Done in bug #243620

As for the configuration, I think that having Debian packages is a better way to install and uninstall things in Ubuntu since it's the "native" way (and also I didn't know about EnvyNG, I just saw that your version was newer than the nvidia-glx-new version) but anyway, thank you for your tools.

Revision history for this message
Alberto Milone (albertomilone) wrote :

getaceres: EnvyNG installs the Debian packages from Ubuntu's repositories and configures the xorg.conf as Jockey does.

Revision history for this message
Marco da Silva (igama) wrote :

Im using the latest driver in Proposed.

All working fine.

Revision history for this message
Odrodzona-Sarmacja (odrodzona-sarmacja) wrote :

I have just bough Asus En9600GT Nvidia and I was experiencing random gdm crashes on open source driver in my Xubuntu Hardy. So, I installed EnvyNG from ubuntu's repository and installed latest nvidia driver with its help. I still had gdm crashes, but nvidia driver was working okay. However after reboot I lost it. I was being dropped constantly to VESA driver instead of nvidia binary one and was not allowed to boot with any other driver but open source to get my gdm working normally. So in effect I had crashing gdm on open source and no way to play a 3d game on my Xubuntu Hardy. That is until I found this here thread. After reading it I installed manually latest nvidia driver from nvidia web site (NVIDIA-Linux-x86-173.14.05-pkg1.run) and... it works like miracle. No gdm crashes. No VESA on reboot and 100% working nvidia binary (until next kernel update I hear) :)

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Odrodzona: Please file a new bug for this problem. Thank you!

Changed in linux-restricted-modules-envy-2.6.24 (Ubuntu):
status: New → Fix Released
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.