Bug#419181: nvidia-kernel-source: Ubuntu must have solved this in some way
did you look how Ubuntu worked around this bug? They are running Linux 2.6.20 in feisty and therefore they must have found a solution. They simply don't enable CONFIG_PARAVIRT in their -generic kernel images; presumably it is enabled for the -server flavours. Given that the kernel team's suggestion is tell $company to fix their proprietary crap I don't think we can expect any help there. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
Bug#419181: nvidia-kernel-source: Ubuntu must have solved this in some way
On Tue, May 01, 2007 at 09:11:16AM +0100, Sam Morris wrote: did you look how Ubuntu worked around this bug? They are running Linux 2.6.20 in feisty and therefore they must have found a solution. They simply don't enable CONFIG_PARAVIRT in their -generic kernel images 2.6.20-15-generic in 7.04 has CONFIG_PARAVIRT enabled. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419181: nvidia-kernel-source: Ubuntu must have solved this in some way
On Tue, 2007-05-01 at 10:14 +0100, Matt Zimmerman wrote: On Tue, May 01, 2007 at 09:11:16AM +0100, Sam Morris wrote: did you look how Ubuntu worked around this bug? They are running Linux 2.6.20 in feisty and therefore they must have found a solution. They simply don't enable CONFIG_PARAVIRT in their -generic kernel images 2.6.20-15-generic in 7.04 has CONFIG_PARAVIRT enabled. Why, so it is... I guess I shouldn't run grep so early in the morning. :) So, I tried building an nvidia-kernel-KVERS package on my Debian system with the sources extracted from from Ubuntu's nvidia-kernel-source binary package, and got the same error from modpost. Since the same source builds fine on my Ubuntu system, I guess Ubuntu modified kbuild or some other part of the kernel to work around the error. I wonder what the chances are that the same workaround could be applied to the Debian kernel? -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
Bug#419181: nvidia-kernel-source: Ubuntu must have solved this in some way
Package: nvidia-kernel-source Version: 1.0.9755-1 Followup-For: Bug #419181 Hi there, did you look how Ubuntu worked around this bug? They are running Linux 2.6.20 in feisty and therefore they must have found a solution. Thanks, Johannes -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nvidia-kernel-source depends on: ii debhelper 5.0.49 helper programs for debian/rules ii dpatch2.0.21 patch maintenance system for Debia ii make 3.81-3 The GNU version of the make util ii sed 4.1.5-1The GNU sed stream editor Versions of packages nvidia-kernel-source recommends: ii devscripts2.10.4 Scripts to make the life of a Debi pn kernel-packagenone (no description available) ii nvidia-glx1.0.9755-1 NVIDIA binary Xorg driver -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
