Package: nvidia-kernel-source
Version: 1.0.8776-4
Followup-For: Bug #416594

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello all,

I can confirm that I've also experienced this problem with
nvidia-kernel-source package version 1.0.8776-4. I've got a slightly
different configuration to the previous bug reports - I'm running on
AMD64, and I'm using a stock 2.6.20.7 kernel source.

I first experienced this problem with 2.6.20.1, but never with 2.6.19
and earlier. For 2.6.20.1, I came up with a very messy workaround that
wasn't satisfactory. This time, with 2.6.20.7,I tried Bastian
Kleineidam's suggested patch, which worked fine.

I noticed that the ROOT_CMD variable is used in a variety of other
places in the makefile, though, and wondered if these might need
changing, too. Not being an expert on the way packages are built, I
can't really comment on this, but thought it was worth raising the
issue.

All the best,
- -Dave.

- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.20.1
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages nvidia-kernel-source depends on:
ii  debhelper                     5.0.45     helper programs for debian/rules
ii  dpatch                        2.0.21     patch maintenance system for Debia
ii  make                          3.81-3     The GNU version of the "make" util
ii  sed                           4.1.5-1    The GNU sed stream editor

Versions of packages nvidia-kernel-source recommends:
ii  devscripts                    2.10.2     Scripts to make the life of a Debi
ii  kernel-package                10.068     A utility for building Linux kerne
ii  nvidia-glx                    1.0.8776-4 NVIDIA binary XFree86 4.x driver

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQIVAwUBRiEZBBIA1yCB7VsRAQqwFBAAhSJXaOFKPGST/ULa0Qj4MOyxLoa318aM
YicEA6gSOtrEGqObVzMm7t31cvlUCgcKjWJ2Fn8aNKNQxV2E8SDfcwC1bFzn1ZbH
jnfdN8QUhOXNGrr3md1v+Niotv1FBM/V1qseo4DHQNH3idrGo+9fAnStkhBjItXV
s85+JqMCjv61E+gEnTfN2hN5efTM0ZTGfYJXif4TJEg9RaCpTxj5Vnz/wvfT5Yl4
XqCmk0zDEaKAC8rXghI+JDAcPW840nGsH7+6ZWm7uyOaHRPC6AMgaI+mHQznXrrm
Y6Yp/0pZwa1KutHz9rUS0CKwuoZyl8ZhEJHuBZsR6RDsbmRQDCYnLdwQ+gpg6GCA
2D+oAOsAlOCGpnSuB+sRtCup+kmKViTx1kktjANIKYSKDEfFWAo+r3ROndBBnbM1
XWhnhtk3J91L5K1P72Hh/thxbzzOU/kgKlx27TN1oQGoq+Y3Kf7HtpIvPK3bUEKt
JaoOpZK+bSlIQ1C6pTljt5nSHkkQt3Nk0BNCa4xi9UXVG1sDY7fRA8lVxY2GG9YZ
absH5uvP9A7XNA4Axuqn02M06VjR+GU08sovywQHGbw8F1o7Bm9s/3MTCzrrRiun
Obu3vrCxIoM7dPAZf13QtjV5cEqYNospDbePjBqRpa9ODVbMJR4H3c7V2IVs2zed
QTe4OLS1KqU=
=nS/p
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to