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
