The patch is 0019-BKL-That-s-all-folks.patch which is purging all bkl-related headers, which are useless now, since the kernel is build without bkl. The problem now is, nvidia noes not need bkl itself, but the module are including some headers, which are not exist after applying this patch.

Yep. My problem is that I really need a recent driver in order to profit from CUDA. Therefore my only option is installing the proprietary driver downloaded from the NVIDIA website. If the Aptosid kernel is not going to work, I will try to install the vanilla kernel (again).

Yep. My problem is that I really need a recent driver in order to profit from CUDA. Therefore my only option is installing the proprietary driver downloaded from the NVIDIA website. If the Aptosid kernel is not going to work, I will try to install the vanilla kernel (again).

I'm not using nvidia driver now.
But if it does not actually use BKL, but just the module does not build without some kernel option,
then isn't it easier to fix the source of module than building a private kernel for that?

(assuming that the source for module, to be locally compiled is open source and downloadable...
and the closed source driver itself does not deends on the kernel option..)

My suggestion is to stick with 2.6.37 and to opt out of automatic kernel upgrades. I'm sure that slh will issue a new kernel momentarily that fixes the problem... if not perhaps we can encourage towo to do some kernel magic.