Re: m-a auto install failed with new kernel.....
On Tue, May 27, 2008 at 08:43:06PM +0000, Michael Fothergill wrote:
> OK, I did it. Here is the output:
>
> debian:/var/log# m-a a-i -t nvidia-kernel
> .
> Updated infos about 1 packages
> Getting source for kernel version: 2.6.25-2-amd64
> Kernel headers available in /lib/modules/2.6.25-2-amd64/build
> apt-get install build-essential
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> build-essential is already the newest version.
> The following packages were automatically installed and are no longer required:
> libavutil1d libavcodec1d libpostproc1d libdc1394-13 libavformat1d
> Use 'apt-get autoremove' to remove them.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> Done!
> unpack
> Extracting the package tarball, /usr/src/nvidia-kernel.tar.bz2, please wait...
> "/usr/share/modass/packages/nvidia-kernel-source" build KVERS=2.6.25-2-amd64 KSRC=/lib/modules/2.6.25-2-amd64/build KDREV=2.6.25-3 kdist_image
> /usr/bin/make -f debian/rules clean
> make[1]: Entering directory `/usr/src/modules/nvidia-kernel'
> # select which makefile to use.
> rm -f /usr/src/modules/nvidia-kernel/nv/Makefile || true
> if [ 6 = 6 ]; then \
> cd /usr/src/modules/nvidia-kernel/nv ; \
> ln -s Makefile.kbuild Makefile ; \
> cd .. ; \
> fi
> if [ 6 = 4 ]; then \
> cd /usr/src/modules/nvidia-kernel/nv ; \
> ln -s Makefile.nvidia Makefile ; \
> cd .. ; \
> fi
> if [ -e patch-stamp ]; then \
> dpatch deapply-all ; \
> rm -rf patch-stamp debian/patched ; \
> fi
> if [ -f /usr/src/modules/nvidia-kernel/debian/control.template ]; then \
> cp /usr/src/modules/nvidia-kernel/debian/control.template /usr/src/modules/nvidia-kernel/debian/control; \
> fi
> dh_testroot
> rm -f build-stamp configure-stamp
> /usr/bin/make clean SYSSRC=/lib/modules/2.6.25-2-amd64/build -C /usr/src/modules/nvidia-kernel/nv -f Makefile
> make[2]: Entering directory `/usr/src/modules/nvidia-kernel/nv'
> make[2]: Leaving directory `/usr/src/modules/nvidia-kernel/nv'
There is no 'nv' subdir in the current version. Only 169.12-1 had the
nv subdir and it doens't work with 2.6.25. Get the current version of
the packages first. 169.12-3 or 169.12-4 (whichever we are now at).
--
Len Sorensen
Reply to: