Date: Tue, 07 Jan 2003 13:06:55 From: R P <rpsbsd@cox.net> To: "Justin T. Gibbs" <gibbs@scsiguy.com> Cc: freebsd-scsi@freebsd.org Subject: Re: scsi parity errors Message-ID: <3.0.5.32.20030107130655.00946c20@pop.west.cox.net> In-Reply-To: <448790000.1041967888@aslan.btc.adaptec.com> References: <3.0.5.32.20030107115902.009423f0@pop.west.cox.net> <3.0.5.32.20030107063959.00916c40@pop.west.cox.net> <3.0.5.32.20030107063959.00916c40@pop.west.cox.net> <3.0.5.32.20030107115902.009423f0@pop.west.cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:31 PM 1/7/03 -0700, you wrote: >All cables must be terminated at their ends. What I'm saying is that >you may need to disable some of the termination on the controller depending >on your cable configuration. The auto setting should work, but I will >only know if the controller got this correct once I've seen the verbose >boot messages along with a description of what cables were connected >during that boot. Well, I can't read as fast as it scrolls up and there's no way to capture it. The controller is definitely falling back to 40. I'm outa time for today and may not get back to this for a week or two. I'll look for a new cable in the mean time. Thanks for your help. Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20030107130655.00946c20>