From owner-freebsd-current Mon Nov 4 18:48:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22918 for current-outgoing; Mon, 4 Nov 1996 18:48:51 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA22784 for ; Mon, 4 Nov 1996 18:47:10 -0800 (PST) From: sthaug@nethelp.no Received: from verdi.nethelp.no by mail.crl.com with SMTP id AA04301 (5.65c/IDA-1.5 for ); Mon, 4 Nov 1996 19:48:13 -0700 Received: (qmail 2733 invoked by uid 1001); 5 Nov 1996 02:43:43 +0000 (GMT) To: richardc@CSUA.Berkeley.EDU Cc: se@zpr.uni-koeln.de, joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: ncrcontrol in -current In-Reply-To: Your message of "Mon, 4 Nov 1996 16:18:37 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 05 Nov 1996 03:43:43 +0100 Message-Id: <2731.847161823@verdi.nethelp.no> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The reason for a mismatch (if both ncrcontrol and the kernel > > were in fact built from corresponding sources) is that you > > specified some kernel config option (i.e. the maximum number > > of LUNs or TAGs) that have not become visible to the build > > process for ncrcontrol. > > Hmmm, okay... > > > So, please add those kernel options to the ncrcontrol Makefile > > and rebuilt ncrcontrol, if that might be the cause of your > > problem. > > Oh okay but I know I don't have any kernel options relating to the > ncr since the other machines use Adaptec 2940W controllers and not the > NCR-810. Do you have FAILSAFE? That one bit me. It *does* influence max # of LUNs/tags. Steinar Haug, Nethelp consulting, sthaug@nethelp.no