Assistance repairing NVIDIA GLX after failed driver install

**damien_d** · June 9th, 2009

Hello all,

I am attempting to repair my installation of Ubuntu 9.04 (x86-64) after attempting to install the NVIDIA 185 drivers manually (i.e. via the shell) to get CUDA 2.2 failed in a stinking pile of the proverbial.

I have since reinstalled nvidia-glx-180 via the usual Ubuntu repostories, and have restore by xorg.conf file back into its proper state.

However, I am having GLX problems - the visible symptoms are as follows:

Code:

damien@damien-desktop:~$ dmesg
[   58.392660] glxinfo[4649]: segfault at 0 ip 000000000040313a sp 00007fff7867ed70 error 4 in glxinfo[400000+5000]
[   58.402271] glxinfo[4652]: segfault at 0 ip 000000000040313a sp 00007fffd3ed05a0 error 4 in glxinfo[400000+5000]
[ 1354.325307] glxinfo[5924]: segfault at 0 ip 000000000040313a sp 00007fff1d0912b0 error 4 in glxinfo[400000+5000]
damien@damien-desktop:~$

And it looks like it failed to load the glx drivers for the xorg logs as well:

Code:

damien@damien-desktop:~$ cat /var/log/Xorg.0.log | grep EE
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "freetype" (module does not exist, 0)
(EE) Failed to load /usr/lib/xorg/modules/extensions//libglx.so
(EE) Failed to load module "glx" (loader failed, 7)
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
(EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
(EE) NVIDIA(0):     you continue to encounter problems, Please try
(EE) NVIDIA(0):     reinstalling the NVIDIA driver.

And basic utilities are failing:

Code:

damien@damien-desktop:~$ glxinfo | grep "OpenGL"
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib:  extension "GLX" missing on display ":0.0".
<snip>

I have tried a forced reinstall of the nvidia drivers:

Code:

sudo apt-get install --reinstall nvidia-glx-180

My xorg.conf file certainly asks to load GLX:

Code:

damien@damien-desktop:~$ cat /etc/X11/xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildd@crested)  Mon Nov  3 08:46:04 UTC 2008
# commented out by update-manager, HAL is now used
#Section "InputDevice"
#	Identifier     "Mouse0"
#	Driver         "mouse"
#	Option         "Protocol" "auto"
#	Option         "Device" "/dev/psaux"
#	Option         "Emulate3Buttons" "no"
#	Option         "ZAxisMapping" "4 5"
#EndSection
# commented out by update-manager, HAL is now used
#Section "InputDevice"
#	Identifier     "Keyboard0"
#	Driver         "kbd"
#EndSection

Section "Monitor"
	Identifier     "Monitor0"
	VendorName     "Unknown"
	ModelName      "Sony SDM-X73"
	HorizSync       28.0 - 65.0
	VertRefresh     57.0 - 63.0
	Option         "DPMS"
EndSection

Section "Monitor"
	Identifier     "Monitor1"
	VendorName     "Unknown"
	ModelName      "HP L1740"
	HorizSync       30.0 - 83.0
	VertRefresh     50.0 - 76.0
	Option         "DPMS"
EndSection

Section "Monitor"
	Identifier     "Monitor2"
	VendorName     "Unknown"
	ModelName      "LG L1753T"
	HorizSync       30.0 - 71.0
	VertRefresh     56.0 - 75.0
	Option         "DPMS"
EndSection

Section "Screen"
	Identifier     "Screen0"
	Device         "Device0"
	Monitor        "Monitor0"
	Option         "TwinView" "0"
	Option         "metamodes" "DFP: nvidia-auto-select +0+0"
	DefaultDepth	24
	SubSection "Display"
		Depth       24
	EndSubSection
EndSection

Section "Screen"
	Identifier     "Screen1"
	Device         "Device1"
	Monitor        "Monitor1"
	DefaultDepth    24
	Option         "TwinView" "0"
	Option         "metamodes" "CRT: nvidia-auto-select +0+0"
	SubSection "Display"
		Depth       24
	EndSubSection
EndSection

Section "Screen"
	Identifier     "Screen2"
	Device         "Device2"
	Monitor        "Monitor2"
	DefaultDepth    24
	Option         "TwinView" "0"
	Option         "metamodes" "nvidia-auto-select +0+0"
	SubSection "Display"
		Depth       24
	EndSubSection
EndSection

Section "Module"
	Load           "dbe"
	Load           "extmod"
	Load           "type1"
	Load           "freetype"
	Load		"glx"
	#       Disable 	"glx"
EndSection

Section "ServerLayout"
	Identifier     "Layout0"
	Screen      0  "Screen0" 1280 0
	Screen      1  "Screen1" LeftOf "Screen0"
	Screen      2  "Screen2" RightOf "Screen0"
	# commented out by update-manager, HAL is now used
	#	InputDevice    "Keyboard0" "CoreKeyboard"
	# commented out by update-manager, HAL is now used
	#	InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Device"
	Identifier     "Device0"
	VendorName     "NVIDIA Corporation"
	BoardName      "GeForce 8600 GT"
	BusID          "PCI:3:0:0"
	Screen          0
	Driver	"nvidia"
	Option	"NoLogo"	"True"
EndSection

Section "Device"
	Identifier     "Device1"
	VendorName     "NVIDIA Corporation"
	BoardName      "GeForce 8600 GT"
	BusID          "PCI:3:0:0"
	Screen          1
	Driver	"nvidia"
	Option	"NoLogo"	"True"
EndSection

Section "Device"
	Identifier     "Device2"
	VendorName     "NVIDIA Corporation"
	BoardName      "GeForce 8400 GS"
	BusID          "PCI:4:0:0"
	Driver	"nvidia"
	Option	"NoLogo"	"True"
EndSection

Section "ServerFlags"
	Option         "Xinerama" "1"
EndSection

damien@damien-desktop:~$

And various other fiddling around. Now I'm a bit lost

If anyone is able to help, it would be most appreciated.

-- Damien

**damien_d** · June 9th, 2009

Hmmm... this looks awfully like this bug: https://bugs.launchpad.net/ubuntu/+s...80/+bug/354484

I'll check it out and post the results.

-- Damien

**damien_d** · June 9th, 2009

Originally Posted by damien_d

Hmmm... this looks awfully like this bug: https://bugs.launchpad.net/ubuntu/+s...80/+bug/354484

I'll check it out and post the results.

Unfortunantly, no luck. The bug was fixed for some people by replacing some symlinks. On my system, I replaced:

Code:

damien@damien-desktop:~$ sudo rm /usr/lib/nvidia/libGL.so.1.xlibmesa 
damien@damien-desktop:~$ sudo ln -s /usr/lib/libGL.so.180.44 /usr/lib/nvidia/libGL.so.1.xlibmesa

And also linked:

Code:

sudo ln -s /usr/lib/xorg/modules/extensions/libglx.so.180.44 /usr/lib/xorg/modules/libglx.so

But GLX is still broken.

**damien_d** · June 9th, 2009

OK, taking a look at Xorg.0.log there is the following that looks interesting:

Code:

(II) Loading extension X-Resource
(II) LoadModule: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules//libglx.so
dlopen: /usr/lib/xorg/modules//libglx.so: undefined symbol: _nv000110gl
(EE) Failed to load /usr/lib/xorg/modules//libglx.so
(II) UnloadModule: "glx"
(EE) Failed to load module "glx" (loader failed, 7)
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
	compiled for 1.6.0, module version = 1.13.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0

Especially: "dlopen: /usr/lib/xorg/modules//libglx.so: undefined symbol: _nv000110gl"

Does that mean anything to anyone?

-- Damien

**damien_d** · June 14th, 2009

Solved my own thread. Well, sort of. I'm now running off the vanilla nvidia binary drivers (v185).

Note just removing the nvidia drivers from "System -> Administration -> Hardware Drivers" doesn't do it - there seems to be a lot of crud that doesn't get removed by it.

So here's how I did it:

1. Remove ALL TRACES of the packaged nvidia from your system:

Code:

sudo apt-get purge nvidia-180-kernel-source  nvidia-glx-173 nvidia-glx-new nvidia-180-libvdpau nvidia-glx-177 nvidia-settings nvidia-80-modaliases   nvidia-glx-180-dev nvidia-96-modaliases nvidia-glx-96

Yes, that prety much every package with the words nvidia-*

2. Reboot. X Will most likely crash. Fix using the options that Ubuntu throws at you.

3. Reboot again. There are still some remnants of the old vanilla install of the drivers remaining. Remove them by:

Code:

sudo nvidia-installer --remove

There's every chance it may throw errors at you again.

4. Reboot. Use "dmesg | grep nvidia" that there is no nvidia at all being loaded.

5. Install the vanilla nvidia drivers by the recommended method (i.e. ctrl-alt-F1; sudo /etc/init.d/gdm stop; sh <nvidia-package?.run)

6. Reboot, reconfigure x as desired. glxinfo should now run OK.

Be warned, you'll have to repeat the process of installing the vanilla nvidia drivers for every kernel Ubuntu installs (yuk!). Unless you specifically need the 185 driver (in this case, I need CUDA 2.2), you'll have to do extra work and use the official Ubuntu nvidia packages.

-- Damien

**unixcrab** · July 7th, 2009

I too made the mistake of trying to install this driver

. It is so easy and straight forward in opensuse...

To get GLX back I did this:

Code:

cd /usr/lib

then I saw the openGL libs (libGLcore.so.1 and libGL.so) linked to the new driver even after I had reinstalled the ubuntu driver:

Code:

ls -l libGL*

so I just deleted the new ones

Code:

sudo rm libGLcore.so.185.18.14

and

Code:

sudo rm libGL.so.185.18.14

Then run

Code:

sudo ldconfig

to relink back to the 180.44 libs.

Check it's all back by running:

Code:

ls -l libGL*

and you should see

Code:

libGLcore.so.1 -> libGLcore.so.180.44

and

Code:

libGL.so.1 -> libGL.so.180.44

Logout and back in again and GLX should be back

**damunzy** · July 13th, 2009

I had a similar issue. I followed the instructions on purging everything but after reboot I didn't have an invidia-installer. I was still having nvidia messages in dmesg but the system was using the generic driver not an nvidia driver. I figured I would try install 190.09 again and everything worked this time. Thanks for the through write up- it helped me learn where to look and led me to a fix for my system even though it wasn't exactly the same.

Originally Posted by damien_d

Solved my own thread. Well, sort of. I'm now running off the vanilla nvidia binary drivers (v185).

Note just removing the nvidia drivers from "System -> Administration -> Hardware Drivers" doesn't do it - there seems to be a lot of crud that doesn't get removed by it.

So here's how I did it:

1. Remove ALL TRACES of the packaged nvidia from your system:

Code:

sudo apt-get purge nvidia-180-kernel-source  nvidia-glx-173 nvidia-glx-new nvidia-180-libvdpau nvidia-glx-177 nvidia-settings nvidia-80-modaliases   nvidia-glx-180-dev nvidia-96-modaliases nvidia-glx-96

Yes, that prety much every package with the words nvidia-*

2. Reboot. X Will most likely crash. Fix using the options that Ubuntu throws at you.

3. Reboot again. There are still some remnants of the old vanilla install of the drivers remaining. Remove them by:

Code:

sudo nvidia-installer --remove

There's every chance it may throw errors at you again.

4. Reboot. Use "dmesg | grep nvidia" that there is no nvidia at all being loaded.

5. Install the vanilla nvidia drivers by the recommended method (i.e. ctrl-alt-F1; sudo /etc/init.d/gdm stop; sh <nvidia-package?.run)

6. Reboot, reconfigure x as desired. glxinfo should now run OK.

Be warned, you'll have to repeat the process of installing the vanilla nvidia drivers for every kernel Ubuntu installs (yuk!). Unless you specifically need the 185 driver (in this case, I need CUDA 2.2), you'll have to do extra work and use the official Ubuntu nvidia packages.

-- Damien

**haxwithaxe** · August 6th, 2009

hey just adding my 2 cents.
if x is still broken after reinstalling nvidiaglx-180 stuff then remember to run: "sudo nvidia-xconfig"
also when i ran nvidia-installer it wanted the "--uninstall" switch not the "--remove" switch

i'm really suprised the drivers will install and be used by nvidia config apps with non-compatible cards. : /