Date: Thu, 31 Jul 1997 22:18:30 +0200 From: Stefan Esser <se@FreeBSD.ORG> To: Mike Burgett <mburgett@cmnsens.zoom.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@FreeBSD.ORG>, Stefan Esser <se@FreeBSD.ORG> Subject: Re: -stable and /usr/sbin/ncrcontrol Message-ID: <19970731221830.00759@mi.uni-koeln.de> In-Reply-To: <199707311941.MAA00453@dragon.cmnsens.zoom.com>; from Mike Burgett on Thu, Jul 31, 1997 at 12:41:56PM -0700 References: <199707311941.MAA00453@dragon.cmnsens.zoom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 31, Mike Burgett <mburgett@cmnsens.zoom.com> wrote: > I've been on a schedule of CVSup'ing 2.2-stable daily, and doing a 'make world > install' every week or so. So far so good. This morning, I did my weekly > build, and built a new kernel, and rebooted, so everything should be in sync. > > However, when I tried running '/usr/sbin/ncrcontrol -i', I get 'incompatible > with kernel. Rebuild!' The problem is that "ncrcontrol" accesses some data structure in the kernel, and whenever a kernel is built with a different definition of that structure, ncrcontrol has to be rebuilt, too. > Is there something I'm missing here, or should this work? I've not tried > using it before, so I have no idea if/when it ever worked here. Could you send me your kernel config file ? Kernel config options may effect the size of the above mentioned data structure, and the compilation of ncrcontrol can't guess the build directory of your kernel, and thus doesn't know which options you use in your kernel ... > (And yes, my system does include an NCR controller, an ASUS SC200, which has > sd0, sd1, cd0, and st0 hung off of it...) I had no doubt you really had a NCR SCSI controller ... :) Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970731221830.00759>