nvidia driver issues

[Onur Gumus]

Hello,
I am trying to use nvidia drivers. It was working with fiesty and gutsy. But with the recent updates of gutsy. IT does not work anymore. When I enable the nvidia driver from restricted drivers managers , after rebooting , it falls to fail safe X and the only way I could boot on to gnome was to select nv (not nvidia)

I tried purging and removing my current nvidia-glx-new driver and re installing. IT did not work. IT seems it still uses 100.14.11 still although the so called installed version is 100.14.19

Here's the output of my command line :

onur@onur-laptop:~$ sudo apt-get install nvidia-glx-new=100.14.19+2.6.22.4-13.6
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  menu libpth20 libflac++5c2 fftw3 kdelibs-data guile-g-wrap libgtk-cil
  koffice-data libglib-cil libffi4 python-qt3 libgmp3c2 perl-suid libept0
  libxapian15 libtunepimp5 libifp4 debtags guile-library libdbus-qt-1-1c2
  libfakekey0 rdiff-backup g-wrap libpurple-bin libgpgme11 libpqxx-2.6.9
  libntfs-3g5 librsync1 libnjb5 libofa0 libgwrap-runtime0
Use 'apt-get autoremove' to remove them.
Suggested packages:
  nvidia-settings
The following NEW packages will be installed:
  nvidia-glx-new
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 0B/5014kB of archives.
After unpacking 15.2MB of additional disk space will be used.
Selecting previously deselected package nvidia-glx-new.
(Reading database ... 254337 files and directories currently installed.)
Unpacking nvidia-glx-new (from .../nvidia-glx-new_100.14.19+2.6.22.4-13.6_i386.deb) ...
Setting up nvidia-glx-new (100.14.19+2.6.22.4-13.6) ...

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
/sbin/ldconfig.real: /usr/lib/libGLcore.so.100.14.11 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig.real: /usr/lib/libGL.so.100.14.11 is not an ELF file - it has the wrong magic bytes at the start.

[John Vivirito (gnomefreak)]

Can you please give us the ouput of dpkg -S /usr/lib/libGL.so.100.14.11
I went to ask you on IRC but you left already. If you come back please ping me.

[Ian Jackson (ijackson)]

Also, the output of the following commands please:
  md5sum /usr/lib/libGL.so.100.14.11
  ls -ald /usr/lib/libGL.so.1
  ldconfig

Thanks.

[Ian Jackson (ijackson)]

Oh, and while we're here I suppose:
  md5sum /slash/ubuntu/var/cache/apt/archives/nvidia-glx-new_100.14.19+2.6.22.4-13.6_i386.deb
not that I think that that will tell us anything very significant.

[Ian Jackson (ijackson)]

And you could attach your /usr/lib/libGL.so.100.14.11 to this bug report. Sorry for the endless serious of afterthoughts.

[Onur Gumus (ogumus)]

nur@onur-laptop:~$ dpkg -S /usr/lib/libGL.so.100.14.11
dpkg: /usr/lib/libGL.so.100.14.11 not found.
onur@onur-laptop:~$ md5sum /usr/lib/libGL.so.100.14.11
464fe723449d60ddfb7c5979235a6788 /usr/lib/libGL.so.100.14.11
onur@onur-laptop:~$ ls -ald /usr/lib/libGL.so.1
lrwxrwxrwx 1 root root 18 2007-10-09 18:57 /usr/lib/libGL.so.1 -> libGL.so.100.14.19
onur@onur-laptop:~$ ldconfig
/sbin/ldconfig.real: /usr/lib/libGLcore.so.100.14.11 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig.real: /usr/lib/libGL.so.100.14.11 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig.real: Can't create temporary cache file /etc/ld.so.cache~: Permission denied

onur@onur-laptop:~$ md5sum /var/cache/apt/archives/nvidia-glx-new_100.14.19+2.6.22.4-13.6_i386.deb
bbba582dcf2c6767f8113a211c00e675 /var/cache/apt/archives/nvidia-glx-new_100.14.19+2.6.22.4-13.6_i386.deb

onur@onur-laptop:~$ ls /usr/lib/libGL.so.100*.*
/usr/lib/libGL.so.100.14.03 /usr/lib/libGL.so.100.14.19
/usr/lib/libGL.so.100.14.11

That file doesn't exist

[Onur Gumus (ogumus)]

sorry it exists and attached

[Ian Jackson (ijackson)]

Hmm. Well, it looks that the file /usr/lib/libGL.so.100.14.11 on your system wasn't installed by dpkg. The Ubuntu archive has contained such a file in the nvidia-glx-new package at one time, but that file had md5sum 5ab7b642bbf08fce3255de574ca15836.

Your file is indeed mangled in some way. It starts with a bunch of zeroes. ldconfig is correct to complain.

I assume it must have come from envy. I don't think there's evidence of a dpkg bug here.

[Alberto Milone (albertomilone)]

1) Did you also install the driver through NVIDIA's installer?

2) can you post the output of this command?
ls -l /usr/lib/libGL.so

3) Which version of Envy did you use?

[Onur Gumus (ogumus)]

1) Did you also install the driver through NVIDIA's installer?

Yes I did. No joy.

2) can you post the output of this command?
ls -l /usr/lib/libGL.so

onur@onur-laptop:~$ ls -l /usr/lib/libGL.so
lrwxrwxrwx 1 root root 10 2007-10-09 17:38 /usr/lib/libGL.so -> libGL.so.1

3) Which version of Envy did you use?
0.9.4-0ubuntu4

I have tried envy a long time ago. And I could still use beryl at that time.
Can you offer me any fix ?

[Alberto Milone (albertomilone)]

Type:
sudo apt-get --purge remove envy
sudo rm -R /usr/share/envy

then follow point B of the instructions:
http://albertomilone.com/pmwiki/pmwiki.php?n=Main.Envy-InstructionsForUbuntu

Mixing Envy with the Nvidia installer might have caused the mess.

[Onur Gumus (ogumus)]

Well after step 6 of B I got an error of your OS is not supported by Envy. So I cannot proceed any more.

[Alberto Milone (albertomilone)]

have a look at this post:
http://albertomilone.com/wordpress/?p=107

[Onur Gumus (ogumus)]

Thanks I fixed the issue, by cleaning the driver from envy and re installing from envy.

AFAIK envy was not the problem. It was I forced 100.14.11 at sometime recently. Ironically, the only solution came from envy. It fixed my driver issues. Thanks

Note : I also had to run dpkg-reconfigure xserver-xorg since my monitor resolution was not set correctly.