From owner-freebsd-scsi Tue Feb 12 12:25: 4 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id C59C137B41C for ; Tue, 12 Feb 2002 12:24:44 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id VAA14166; Tue, 12 Feb 2002 21:20:12 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1CKGbF88226; Tue, 12 Feb 2002 21:16:37 +0100 (MET) (envelope-from j) Date: Tue, 12 Feb 2002 21:16:37 +0100 From: Joerg Wunsch To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG, Frank Altpeter Subject: Re: SCSI parity error detected Message-ID: <20020212211637.L74623@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG, Frank Altpeter References: <20020211235534.G57760@uriah.heep.sax.de> <20020211213743.N1867-100000@gerard> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20020211213743.N1867-100000@gerard>; from groudier@free.fr on Mon, Feb 11, 2002 at 09:53:55PM +0100 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Gérard Roudier wrote: > Dawicontrol uses proprietary BIOS and setup area not supported by > the driver. Their BIOS very probably knows that the upper lines of > the 53c875 that is _wide_ are not connected to the SCSI BUS. That would be my guess, too. > But the sym driver does not detect this. This could be achieved, for > example, by providing a specific sub-vendor id. But for now, I > donnot know if their controller provides such information. Hmm, maybe Frank still has the output of a verbose boot that includes the PCI registers... > In order to check the possible Wide nego. issue, the driver source can be > hacked, for example, as follows: > > --- sym_conf.h.orig Sun Dec 2 16:21:07 2001 > +++ sym_conf.h Mon Feb 11 21:49:46 2002 > @@ -146,7 +146,7 @@ > /* > * Max wide order. > */ > -#define SYM_SETUP_MAX_WIDE (1) > +#define SYM_SETUP_MAX_WIDE (0) Ah, so see my other mail, that would be the required tunable e. g. for the device hints... -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message