From owner-freebsd-hackers Wed Dec 15 17: 2:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 65D2115414 for ; Wed, 15 Dec 1999 17:02:14 -0800 (PST) (envelope-from whs@xs4all.nl) Received: from localhost (dc2-isdn2218.dial.xs4all.nl [194.109.156.170]) by smtp1.xs4all.nl (8.9.3/8.9.3) with SMTP id CAA21971 for ; Thu, 16 Dec 1999 02:02:11 +0100 (CET) Message-ID: <3858485E.167EB0E7@xs4all.nl> Date: Thu, 16 Dec 1999 02:03:10 +0000 From: "W.H.Scholten" Organization: Robots anonymous X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: ncr scsi timeout References: <199912152234.RAA69777@lakes.dignus.com> <3858372B.D5BBFAF@xs4all.nl> <19991215165550.A8672@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry wrote: > In general, the stock NCR driver isn't being actively maintained, and your > problem could be the result of a bug in the driver, or some problem with > your MO drive. It's hard to say for sure. Gerard's driver is actively > maintained, though, so if you still have problems with his driver, it'll be > easier to get the problems fixed. I'm using a Tekram DC 390U (ncr 875 ultra, not wide) controller which the readme said was supported, so I just compiled a new kernel with the new driver and everything works hunky dory now :-) Thanks. Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message