Comment 36 for bug 576648

Revision history for this message
n0PxN0p (n0pxn0p) wrote :

I confirm it is present on natty with packages from oneiric listed below:
linux-image-3.0.0-17-generic linux-headers-3.0.0-17-generic module-init-tools procps

And: nvidia-current 270.41.06-0ubuntu1.1 (which is the latest for natty at the moment, as well as those listed above)

Result of building nvidia module according to /var/lib/dkms/nvidia-current/270.41.06/build/make.log:
-----------------------------------------------------------------------------------------------------------------
DKMS make.log for nvidia-current-270.41.06 for kernel 3.0.0-17-generic (x86_64)
Вт. апр. 24 13:38:56 VOLT 2012
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] Ошибка 1

--------------------------------------------------EOF--------------------------------------------------------

Workaround that supposes switching back to kernel version Natty shipped with is not an option for me, due to several bugs i'm catching on my laptop, including this one for example: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/924905 (which makes it impossible to use the laptop at all in my case).
Building module from source in not a best option for me also due to several reasons that also hardly refer to current bug.

Should i provide some additional info?