nvidia-173 kernel module failed to build in Precise (Unable to determine the target kernel version - like bug 576648)

[jokrebel]

(This is an instance of bug #576648. Please do not dupe these two bugs (yet), the old one has so many dupes it is timing out, and this report has useful logs on it.)

This problem comes about due to bug #897681 in jockey, where it selects to install -173 when it should be installing -current. This report focuses only on the build troubles for 173.

[Original Report]
I only run a "sudo apt-get upgrade"

DKMS make.log for nvidia-173-173.14.30 for kernel 3.2.0-2-generic (i686)
Fr 2. Dez 10:51:49 CET 2011
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Fehler 1

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: nvidia-173 173.14.30-0ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module 285.05.09 Fri Sep 23 18:53:08 PDT 2011
 GCC version: gcc-Version 4.6.2 (Ubuntu/Linaro 4.6.2-5ubuntu1)
.tmp.unity.support.test.0:

ApportVersion: 1.90-0ubuntu1
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
DKMSKernelVersion: 3.2.0-2-generic
Date: Fri Dec 2 10:51:53 2011
DistUpgraded: Log time: 2011-12-01 20:20:12.327370
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus:
 nvidia-173, 173.14.30, 3.0.0-13-generic, i686: installed
 nvidia-current, 285.05.09, 3.0.0-13-generic, i686: installed
 nvidia-current, 285.05.09, 3.2.0-2-generic, i686: installed
GraphicsCard:
 nVidia Corporation NV41 [Quadro FX Go1400] [10de:00cc] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:019b]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Dell Inc. Precision M70
PackageVersion: 173.14.30-0ubuntu8
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-generic root=UUID=e7f673a0-58ca-4377-b749-85f1122b8cff ro quiet splash vt.handoff=7
SourcePackage: nvidia-graphics-drivers-173
Title: nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build
UpgradeStatus: Upgraded to precise on 2011-12-01 (0 days ago)
XorgConf:
 Section "Device"
  Identifier "Default Device"
  Option "NoLogo" "True"
 EndSection
dmi.bios.date: 09/30/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0D8006
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/30/2005:svnDellInc.:pnPrecisionM70:pvr:rvnDellInc.:rn0D8006:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M70
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu7
version.libdrm2: libdrm2 2.4.27-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.10.4-1ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Bryce Harrington (bryce)]

This is basically a dupe of bug #576648. However, since that bug has a large number of dupes and is relatively old, we can leave this bug report open for investigating this in precise for now.

[Daniel van Vugt (vanvugt)]

I don't think a bug being old makes it any less important. But hopefully that's not what you meant. :)

So long as bug 576648 gets updated with all fixes and status updates then it's probably OK to keep this duplicate separate... (?)

I strongly suggest fixing lucid as soon as precise is fixed. Because lucid is where the vast majority of duplicates are coming from.

[Bryce Harrington (bryce)]

Oh I certainly do think that new bugs are more important than old ones, but no that's not what I meant.

What I meant is that it looks like the instance of this build failure in precise may be due to something different than what's causing it in lucid. Because these build failures apparently weren't happening in oneiric (even though jockey bug #897681 was), I have a suspicion it's a recent regression, possibly kernel-version-specific.

[Daniel van Vugt (vanvugt)]

FYI, most of the precise instances of this bug are attached to bug 576648 as duplicates still. And I'm not seeing any timeouts since adding a few more, so strongly suggest that this one should be marked as a duplicate of bug 576648 too.

It probably doesn't matter if the fix for precise is a little different. I still think it should be fixed under the heading of 576648 where more users of 12.04/kernel-3.2 are subscribed.

[jokrebel (jokrebel)]

Sorry for that. Now its been marked as dublicate of 576648. I have no
practice in doing bug-reports. I only followed the instructions on my
screen. After that error Ubunutu braught me direktly to this (old)
bug-report-page.

Am 08.12.2011 04:23, schrieb Daniel van Vugt:
> FYI, most of the precise instances of this bug are attached to bug
> 576648 as duplicates still. And I'm not seeing any timeouts since adding
> a few more, so strongly suggest that this one should be marked as a
> duplicate of bug 576648 too.
>
> It probably doesn't matter if the fix for precise is a little different.
> I still think it should be fixed under the heading of 576648 where more
> users of 12.04/kernel-3.2 are subscribed.
>

[Bryce Harrington (bryce)]

On Thu, Dec 08, 2011 at 03:23:23AM -0000, Daniel van Vugt wrote:
> FYI, most of the precise instances of this bug are attached to bug
> 576648 as duplicates still. And I'm not seeing any timeouts since adding
> a few more, so strongly suggest that this one should be marked as a
> duplicate of bug 576648 too.

See https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/507062 which
is timing out due to too many dupes (reported to Launchpad as #864843).

576648 has timed out for me one time so far. I had tried to post a
comment to the bug at the time I set the status and priority and the
comment got lost, which is why I am not enthused about doing further
work on that bug report.