Subject: Re: Re: Re: CVS commit: pkgsrc/sysutils/nvnet
To: Quentin Garnier <cube@cubidou.net>
From: Joel CARNAT <joel@carnat.net>
List: pkgsrc-changes
Date: 01/13/2006 11:35:36
Dans l'épisode précédent (Fri, Jan 13 2006 - 11:30), Quentin Garnier nous apprenait que :
> On Fri, Jan 13, 2006 at 11:06:09AM +0100, Joel CARNAT wrote:
> [...]
> > > > Note that I had GENERIC.MPACPI (to have ACPI configured) and the module
> > > > didn't load because it said it was incompatible with MP mode. So I
> > > > switched to GENERIC and it went up OK. Maybe there's should be a note in
> > > > MESSAGE ?
> > > 
> > > Or maybe there should be a fix. What does it says exactly?
> > > 
> > 
> > I can't test it on my home machine right now.
> > But I did try to have it run on my DELL workstation (which don't have
> > any nVIDIA card ;) and it seems it got the same message :
> > 
> > /netbsd: NetBSD 3.99.15 (GENERIC.MPACPI) #0: Wed Jan 11 10:16:16 UTC 2006
> > ...
> > /netbsd: LKM 'nv': environment compile options mismatch - LKM '', kernel 'MULTIPROCESSOR'
> 
> This means compilation environment is not the same;  you need
> -DMULTIPROCESSOR when building the LKM.
> 
> > /netbsd: LKM 'nv': kernel version mismatch - LKM 399001500, kernel 300000000
> 
> This obviously means you built the LKM with -current sources and tried
> loading it on a 3.0 kernel.  Ouch.
> 

As I said, I can't test it with the right machine, so I tested it here
and the configuration is indeed not clean :) The LKM was compiled with a
running 3.0_STABLE kernel using -current sources. Then the -current
kernel was booted. Indeed I don't get the second message at home when I
had GENERIC.MPACPI ; only the first one.