Installation looks for non-existant path

Bug #325274 reported by jstarek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx-180

The installation of the nvidia-glx-180 package did not work as expected on an Intrepid machine I was setting up.

Software environment:

Ubuntu 8.10 (Intrepid Ibex) Server, AMD64
Kernel 2.6.27-11-server
nvidia-glx-180 Version 180.11-0ubuntu1~intrepid1_amd64

Problem description:

When installing the package, the following error message appears and the kernel module is not installed:

Error! Your kernel source for kernel 2.6.24-23-generic cannot be found at
/lib/modules/2.6.24-23-generic/build or /lib/modules/2.6.24-23-generic/source.
Installing initial module

Error! Could not locate nvidia.ko for module nvidia in the DKMS tree.
You must run a dkms build for kernel 2.6.24-23-generic (x86_64) first.

Steps to reproduce:

1. Install an Ubuntu 8.10 Server system.
2. Add the ubuntu-desktop metapackage (not necessary, but that was the way my installation went)
3. Install kernel source and headers
4. Install nvidia-glx-180
5. The error message will appear in the output of aptitude.

Diagnosis:

The directories mentioned in the error message do not exist at the time of installation. There should be a symlink /lib/modules/`uname -r`/build/ that points to /usr/src/linux-headers-`uname -r`.

Workaround:

The module may be installed using module-assistant. I did not examine this in detail, but installing module-assistant and sudo module-assistant auto-install nvidia worked in an environment that also had the following, *possibly* related packages installed (yes, I sort of lost track which were strictly necessary):
nvidia-kernel-common
nvidia-180-kernel-source
nvidia-glx-180-dev
linux-restricted-modules-`uname -r`
linux-restricted-modules-common
linux-headers-`uname -r`
linux-headers-generic
linux-source

[lspci]
00:00.0 RAM memory [0500]: nVidia Corporation MCP78S [GeForce 8200] Memory Controller [10de:0754] (rev a2)
            Subsystem: ASUSTeK Computer Inc. Device [1043:82f2]
02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8200 [10de:0849] (rev a2)
            Subsystem: ASUSTeK Computer Inc. Device [1043:82f2]

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi juergen-starek,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in nvidia-graphics-drivers-180:
status: New → Incomplete
Revision history for this message
jstarek (juergen-starek) wrote :

Sorry for the long delay. I'm adding the output of lspci here...

Revision history for this message
jstarek (juergen-starek) wrote :

...and just checked the Xorg logfiles. As this is an installation issue, I don't think there's valuable info in there, but if anyone needs this, please ask and I'll try to provide it quickly.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

Revision history for this message
jstarek (juergen-starek) wrote :

I can't test the Jaunty update (lack of test machines), and there seems to be no new package for Intrepid's AMD64 architecture. So, I'd say this is still open. Bryce, is there any more info I can provide? If not, can we move away from "incomplete" status?

Bryce Harrington (bryce)
description: updated
Revision history for this message
jstarek (juergen-starek) wrote :

When upgrading to the 2.6.27-14-server kernel yesterday, I could verify that this bug is still there. Bryce, I asked you before: Can we move this away from "incomplete"? I'm certain that this has nothing to do with the xorg.conf, so I removed the corresponding tag, but just in case, I attached it. I'm really not sure what more information you want...

Or should I re-file this bug against DKMS?

tags: removed: needs-lspci-vvnn needs-xorglog
Revision history for this message
Bryce Harrington (bryce) wrote :

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
jstarek (juergen-starek) wrote :

Sorry, the workstation in question needs to remain on Intrepid for the time being, and as I said, I lack other machines where I could test this. I asked around our CS department at the university, but found no one who can test on Jaunty / Karmic.

Revision history for this message
Bryce Harrington (bryce) wrote :

Since the hardware is no longer available for doing troubleshooting with, we'll have to close the bug for now. However please feel free to reopen if you or anyone else has the same HW and can reproduce this issue using the latest development version of Ubuntu and is willing to do some troubleshooting with it.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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