Re: 2.6.28 + nvidia closed source
When can we expect either a proper kernel kbuild, or a decoupling of
dependencies that will allow building out-of-tree kernel modules without
This was posted not long ago in a similar thread :
Gilles Mocellin wrote :
Le Wednesday 04 February 2009 00:26:41 Alex Samad, wrote :
I have been using the kernel snapshot repo to grab a 2.6.28 kernel, >>but
I notice they are not building a kbuild package and thus I can't >>build
modules against the kernel.
How are other people building their 2.6.28 kernel and/or kbuild
I've just rebuilt it for me (I use the nvidia driver).
It's not really hard :
You must have the deb-src line in /etc/apt/sources.list :
deb http://kernel-archive.buildserver.net/debian-kernel trunk main
deb-src http://kernel-archive.buildserver.net/debian-kernel trunk main
To be able to compile, instal build-essentials.
$ apt-get source linux-kbuild-2.6-2.6.28
$ cd linux-kbuild-2.6-2.6.28
$ cd ..
$ dpkg -i linux-kbuild-2.6.28_2.6.28-1~snapshot.12595_amd64.deb
After that, you can install linux-headers-2.6.28-1-amd64,
and m-a a-i nvidia ...
Thank you very much. I missed that thread.
It still begs some questions. Why don't they build/package a normal
kbuild that matches the dependency that the kernel header package has?
I suppose that it will enter mainstream, instead of being in
kernel-archive, and then there will be a kbuild infrastructure. Maybe
it is too much work for the relatively few people who roll their own
custom kernel. But a lot of people use that NVidia blob. And other
hardware drivers that need compiling.