nvidia: Multiple versions in DKMS

Thanks for reporting. I'll work on it.

Please motu-sru team upload this fix to Hardy (SRU):

http://albertomilone.com/ubuntu/newlrm/pitti/linux-restricted-modules-envy-2.6.24_2.6.24.503-503.31.diff.gz
http://albertomilone.com/ubuntu/newlrm/pitti/linux-restricted-modules-envy-2.6.24_2.6.24.503-503.31.dsc
http://albertomilone.com/ubuntu/newlrm/pitti/linux-restricted-modules-envy-2.6.24_2.6.24.503-503.31_source.changes

This bug was fixed in the package nvidia-graphics-drivers-177 - 177.70-0ubuntu1

---------------
nvidia-graphics-drivers-177 (177.70-0ubuntu1) intrepid; urgency=low

  * Add driver 178.70:
     * Added support for the following new GPUs:
       o GeForce 9800 GTX+
       o GeForce 9800 GT
       o GeForce 8100P
       o nForce 780a SLI
       o nForce 750a SLI
       o Quadro FX 770M
       o Quadro NVS 160M
       o Quadro NVS 150M
     * Improved support for RENDER operations with the same source
       and destination; this should enhance performance in
       some situations, e.g. when dragging Plasma applets in KDE4.
     * Fixed a text rendering performance regression that affected
       GeForce 6 and 7 series GPUs.
     * Fixed a regression that caused text to be missing or
       corrupt on GeForce 6 and 7 series GPUs.
     * Fixed a regression responsible for false negatives during
       SLI video bridge detection attempts after X server
       restarts.
     * Fixed a bug that resulted in AGP FW/SBA settings and overrides
       being applied incorrectly when using the Linux kernel's
       AGP GART driver.
     * Fixed a bug that caused initialization of the builtin AGP
       GART driver (NvAGP) to fail.
  * Fix (LP: #261816) Replace "remove" with "remove|upgrade" in the
    case loop in nvidia-177-kernel-source.prerm so that older versions
    of the drivers are removed in case of upgrade

 -- Alberto Milone (tseliot) <email address hidden> Thu, 28 Aug 2008 22:22:50 +0200

Earlier today I received both the Nvidia update from 177.68 to 177.70 and the kernel update from 2.6.26-5 to 2.6.27-2. Upon restarting the system I found that the Nvidia driver 177.70 had been built for kernel 2.6.26-5 not 2.6.27-2. Reinstalling nvidia-graphics-drivers-177 solved the problem.

Graham: that happened because the .prerm file of 177.68 was still there and was affected by the problem. The upgrade from 177.70 to newer releases should no longer cause this bug.

Since updating to intrepid I NEVER succeded installing the nvidia drivers for my Geforce 6 Series through the jockey tool. Activating one of the four proposed drivers (173, 177, 71, 96) always seems to install it - but never to activate it!! Restarting the gdm or the system always led to the anoying X reconfiguring screen. And even there, selecting the nvidia driver - installed only seconds before with jockey - disables gdm from starting up correctly. Hmmmm, so the nvidia driver has not been installed and activated, even though the jockey tool told me so before??? Very anoying! Another strange thing is that newer versions of the x-server don't seem to need a xorg.conf file anymore - but the nvidia does for its option, card, and monitor settings!? Very strange!! Mabe there lies the big trouble of the x-server and nvdia playing smoothly together ...

Luckily, downloading and installing the nvidia driver manually always succeded!! Hopefully, the jockey version in the final intrepid release will work a 100 percent. Here are my steps to install the nvidia driver, which of course you have to repeat every time you install a new kernel:

1. Download, save an make executable NVIDIA-Linux-x86-177.67-pkg1.run.
2. Go to console with CTRL+ALT+F1, login, and kill gdm with "sudo killall gdm".
3. Uninstall the old nvidia driver with "sudo sh NVIDIA-Linux-x86-177.67-pkg1.run --uninstall".
4. IMPORTANT: Delete ALL xorg.config files with "sudo rm /etc/X11/xorg*".
5. Install the nvidia driver with "sudo sh NVIDIA-Linux-x86-177.67-pkg1.run".
(6. Remove everything of nvidia and jockey in synaptic - exept maybe nvidia-settings.)

Hope this helps a little! André

André:
1) the method which you suggested will break some symlinks created by the packages in Ubuntu. Be careful.
2) proprietary drivers are not loaded by default unless specified in the xorg.conf
3) without a log or further information on your system (you will have to reproduce the problem) I'm afraid I can't help you.
4) this is not the right place to report your problem. Feel free to file a new bugreport.

Thanks for your work Alberto !

It broke for me....

----------------------------------------

Preparing to replace nvidia-glx-177 177.68-0ubuntu1 (using .../nvidia-glx-177_177.70-0ubuntu1_i386.deb) ...
Unpacking replacement nvidia-glx-177 ...
dpkg: error processing /var/cache/apt/archives/nvidia-glx-177_177.70-0ubuntu1_i386.deb (--unpack):
 trying to overwrite `/usr/lib/xorg/modules/extensions/libglx.so', which is also in package xserver-xorg-core

--------------------------------------
sudo apt-get install -f

Setting up nvidia-177-kernel-source (177.70-0ubuntu1) ...
Removing all DKMS Modules
Done.
Adding Module to DKMS build system
driver version= 177.70
Doing initial module build
Installing initial module
Done.

;)

----------------------------------

I also noticed on Friday that mesa is also using libglx.so, so it seems to be a trublemaker...

I have NOT uninstalled 177.70 from nVidia if that maybe disturbs this !

Thanks !

Followup > a force overwrite gave me correct glx

sudo dpkg --force-overwrite -i /var/cache/apt/archives/nvidia-glx-177_177.70-0ubuntu1_i386.deb

glxinfo OK

plun: the error was caused by the NVIDIA installer.

Ciao Albert

Thanks for your quick answer, and sorry that I did actually oversee the bug title. Meanwhile I have succeeded installing the nvidia 177 beta driver with jockey, but it took me a while to figure out which version of the driver supports which graphic card, and which driver is alpha, beta or stable. Maybe there should be more text in synaptics describing in depth a more detailed status of the driver (the card coverage on the other hand is very well explained). Well, ok, I admit that I could spend some time searching the internet about that ...

One major lowdown at the moment is, that if I try to change the screen settings either with displayconfig-gtk or gnome-display-properties my display gets corrupted again and cannot be set back. I have to uninstall the nvidia driver, reboot and reinstall the nvdia driver. Fortunately, using nvidia-settings for changing the display setting works like a charm! But this I should report somewhere else :-)

Thanks again, Alberto! Keep up the good work! Greetings from André

Hello again Alberto...

This is for sure a new bug but I take it here...

Clean install this weekend and something breaks glx

----------------------------------------------------------
Broken
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Device"
 Identifier "Configured Video Device"
 Driver "nvidia"
 Option "NoLogo" "True"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 Defaultdepth 24
EndSection
Section "ServerLayout"
 Identifier "Default Layout"
  screen 0 "Default Screen" 0 0
 Inputdevice "Generic Keyboard"
 Inputdevice "Configured Mouse"

 #Uncomment if you have a wacom tablet
 #InputDevice "stylus" "SendCoreEvents"
 # InputDevice "cursor" "SendCoreEvents"
 # InputDevice "eraser" "SendCoreEvents"
 Inputdevice "Synaptics Touchpad"
EndSection
Section "Module"
 Load "glx"
EndSection

---------------------------------------------

Works

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Device"
 Identifier "Configured Video Device"
 Driver "nvidia"
EndSection

-----------------------------------------------------

Load glx after driver..... ??? I have no logfiles beacuse I was in hurry... ;)

The 1st xorg.conf is broken.

In the ServerLayout section there are references to InputDevice sections which don't exist.

Section "ServerLayout"
    Identifier "Default Layout"
    screen 0 "Default Screen" 0 0
    Inputdevice "Generic Keyboard"
    Inputdevice "Configured Mouse"

    #Uncomment if you have a wacom tablet
    #InputDevice "stylus" "SendCoreEvents"
    # InputDevice "cursor" "SendCoreEvents"
    # InputDevice "eraser" "SendCoreEvents"
    Inputdevice "Synaptics Touchpad"
EndSection

Did use use nvidia-settings, nvidia-xconfig or Jockey or some other program to set up the xorg.conf?

No this is a "default" install which I directly enabled the driver with Menu System > Administration >Hardware drivers

I then first tried a normal Ctrl-Alt-Backspace > X broken > failsafe driver

Reboot > failsafe driver again

Jockey reports the driver as installed and "In use"

Cleaned up xorg.conf according to nVidias recomendations for unstable Xorg 7.4 and GLX works again.

http://www.nvnews.net/vbulletin/showpost.php?p=1666354&postcount=4

I have then seen several issues within forums and IRC with the same problem...

can you attach all the files in /etc/X11/ whose names begin with "xorg"?

Done, I also noticed this change

 * control: drop Recommends again, it would otherwise pull nvidia-glx-173
     in and break 3D for many.

https://lists.ubuntu.com/archives/intrepid-changes/2008-September/006600.html

that change doesn't affect your problem.

Can you attach this file (if it exists)?
/var/cache/jockey/nvidia.oldconf

Yup... You have a ongoing case within the forum

http://ubuntuforums.org/showthread.php?t=913896

Oldconf
--------------------------------------------------------
Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

---------------------------------------------------------------------------

I had the same kind of issue this morning with nvidia module (kernel 2.6.27-3-generic and nvidia 177.70 update), with this message during the kernel update :

        nvidia (177.68): Unable to locate /var/lib/dkms/nvidia/177.68/source/dkms.conf
        DKMS tree must be manually fixed

(this is because /usr/src/nvidia-177.68 no longer exists)

nivdia-177.70 module was built but not installed.

I've fixed this with dkms, from the command line :

sudo dkms install -m nvidia -v 177.70 -k 2.6.27-3-generic

Confirm this

2008/9/12 Bruno Patri <email address hidden>

> I had the same kind of issue this morning with nvidia module (kernel
> 2.6.27-3-generic and nvidia 177.70 update), with this message during the
> kernel update :
>
> nvidia (177.68): Unable to locate
> /var/lib/dkms/nvidia/177.68/source/dkms.conf
> DKMS tree must be manually fixed
>
> (this is because /usr/src/nvidia-177.68 no longer exists)
>
> nivdia-177.70 module was built but not installed.
>
> I've fixed this with dkms, from the command line :
>
> sudo dkms install -m nvidia -v 177.70 -k 2.6.27-3-generic
>
> --
> nvidia: Multiple versions in DKMS
> https://bugs.launchpad.net/bugs/261816
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

I am not sure if this is my issue or not, I installed 27-3 and the update for 177 nvidia in the same updates and now gdm won't start at all.

I have dual 8800GT's in SLI was working fine with 177.68 and 27-2 kernel.

I tried:

sudo dkms install -m nvidia -v 177.70 -k 2.6.27-3-generic

and I got : Error! This module/version combo is already installed
for kernel: 2.6.27-3-generic (x86_64)

I have attached Xorg.0.log

I have added back my original xorg.conf and now this is what I have:
http://pastebin.ca/1203102

any help would be appreciated

combread: I think the xserver doesn't know which card it should initialise first.

Try replacing your old xorg.conf with the attached one and restart the xserver.

Let me know how it goes.

You are a genius Alberto Milone!

That worked perfectly!!!

THANK YOU

lol
sudo nvidia-xconfig ;)

2008/9/15 cornbread <email address hidden>

> You are a genius Alberto Milone!
>
> That worked perfectly!!!
>
> THANK YOU
>
> --
> nvidia: Multiple versions in DKMS
> https://bugs.launchpad.net/bugs/261816
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

I tried nvidia-xconfig several times in the process of trying to fix this issue and it never worked.

Followup:

Clean Alpha 6 install and everything works... :)

Filed this bug about Jockey and minor changes.

https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/272238

Thanks for your work !

As regards Hardy, I will backport the fix from Intrepid soon.

Ok, here's the debdiff.

# ls -l /var/log/apt/
total 88
-rw------- 1 root root 18423 2008-10-16 07:19 term.log
-rw------- 1 root root 3378 2008-09-26 07:23 term.log.1.gz
-rw------- 1 root root 8903 2008-08-28 07:34 term.log.2.gz
-rw------- 1 root root 8860 2008-08-01 16:42 term.log.3.gz
-rw------- 1 root root 25370 2008-07-04 02:46 term.log.4.gz
-rw------- 1 root root 11143 2008-05-30 05:40 term.log.5.gz

WTF?
Ban him.

2008/10/16 keepitsimpleengr <email address hidden>

>
> ** Attachment added: "term.log"
> http://launchpadlibrarian.net/18611749/term.log
>
> --
> nvidia: Multiple versions in DKMS
> https://bugs.launchpad.net/bugs/261816
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

It's ok. I asked him to attach those files.

Bugaga lol :)

2008/10/16 Alberto Milone <email address hidden>

> It's ok. I asked him to attach those files.
>
> --
> nvidia: Multiple versions in DKMS
> https://bugs.launchpad.net/bugs/261816
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Patch reviewed by ~motu-sru. Looks reasonable -- proceed with upload and verification please.

Accepted into hardy-proposed, please test and give feedback here.

Works in Hardy with both 2.6.24-21-generic and server. Right now I'm using nvidia 173.14.12

Thanks a lot :)

This bug was fixed in the package linux-restricted-modules-envy-2.6.24 - 2.6.24.503-503.31

---------------
linux-restricted-modules-envy-2.6.24 (2.6.24.503-503.31) hardy-proposed; urgency=low

  * Fix (LP: #261816) Backport fix from Intrepid for
    nvidia-FLAVOUR-kernel-source.postinst so as to clean up /var/lib/dkms/nvidia
    and replace "remove" with "remove|upgrade" in the case loop in
    nvidia-FLAVOUR-kernel-source.prerm so that older versions of the drivers are
    removed from the dkms tree in case of upgrade.

 -- Alberto Milone (tseliot) <email address hidden> Thu, 16 Oct 2008 12:30:48 +0200

Copied to hardy-updates.

I still get similar messages after 10.04 kernel upgrade to 2.6.32-24-generic on x86_64 amdx4:-

Sep 1 11:39:04 infinity dkms_autoinstaller: nvidia (185.18.36): Unable to locate /var/lib/dkms/nvidia/185.18.36/source/dkms.conf
Sep 1 11:39:04 infinity dkms_autoinstaller: DKMS tree must be manually fixed
Sep 1 11:39:04 infinity dkms_autoinstaller: vboxnetflt (3.0.8): Unable to locate /var/lib/dkms/vboxnetflt/3.0.8/source/dkms.conf
Sep 1 11:39:04 infinity dkms_autoinstaller: DKMS tree must be manually fixed
Sep 1 11:39:07 infinity dkms_autoinstaller: vboxdrv (3.0.8): Unable to locate /var/lib/dkms/vboxdrv/3.0.8/source/dkms.conf
Sep 1 11:39:07 infinity dkms_autoinstaller: DKMS tree must be manually fixed
Sep 1 11:39:08 infinity dkms_autoinstaller: virtualbox-ose-guest: Multiple versions in DKMS. Unsure what to do. Resolve manually.
Sep 1 11:39:08 infinity dkms_autoinstaller: vboxnetadp (3.0.8): Unable to locate /var/lib/dkms/vboxnetadp/3.0.8/source/dkms.conf
Sep 1 11:39:08 infinity dkms_autoinstaller: DKMS tree must be manually fixed
Sep 1 11:39:09 infinity dkms_autoinstaller: nvidia (185.18.36): Unable to locate /var/lib/dkms/nvidia/185.18.36/source/dkms.conf
Sep 1 11:39:09 infinity dkms_autoinstaller: DKMS tree must be manually fixed
Sep 1 11:39:09 infinity dkms_autoinstaller: vboxnetflt (3.0.8): Unable to locate /var/lib/dkms/vboxnetflt/3.0.8/source/dkms.conf
Sep 1 11:39:09 infinity dkms_autoinstaller: DKMS tree must be manually fixed
Sep 1 11:39:10 infinity dkms_autoinstaller: vboxdrv (3.0.8): Unable to locate /var/lib/dkms/vboxdrv/3.0.8/source/dkms.conf
Sep 1 11:39:10 infinity dkms_autoinstaller: DKMS tree must be manually fixed
Sep 1 11:39:10 infinity dkms_autoinstaller: virtualbox-ose-guest: Multiple versions in DKMS. Unsure what to do. Resolve manually.
Sep 1 11:39:10 infinity dkms_autoinstaller: vboxnetadp (3.0.8): Unable to locate /var/lib/dkms/vboxnetadp/3.0.8/source/dkms.conf
Sep 1 11:39:10 infinity dkms_autoinstaller: DKMS tree must be manually fixed