Cyril, I had similar errors to what you posted in #25, which I thought
was strange, because I'd already succesfully built the module from
nvidia-kernel-source 180.29-1 using make-kpkg on a vanilla upstream
2.6.29 kernel. 

To build against the stock kernel I installed
linux-headers-2.6.26-1-amd64, linux-headers-2.6.26-1-common,
linux-kbuild-2.6.29 and linux-source-2.6.29. I merged the contents of
linux-headers-2.6.29-1-amd64, linux-headers-2.6.29-1-common,
linux-kbuild-2.6.29 and linux-source-2.6.29 and used options
--revision=1 --append-to-version=-1-amd64 to make-kpkg. The module then
builds, installs and loads successfully.

Why make-kpkg works but m-a doesn't is a mystery to me, but I hope
pointing out that it does helps you more knowledgeable people to track
down the problem.

-- 
TH * http://www.realh.co.uk



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to