Date: Wed, 15 Dec 1999 18:36:35 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: "W.H.Scholten" <whs@xs4all.nl> Cc: hackers@FreeBSD.ORG Subject: Re: ncr scsi timeout Message-ID: <19991215183635.A9876@panzer.kdm.org> In-Reply-To: <3858485E.167EB0E7@xs4all.nl>; from whs@xs4all.nl on Thu, Dec 16, 1999 at 02:03:10AM %2B0000 References: <199912152234.RAA69777@lakes.dignus.com> <3858372B.D5BBFAF@xs4all.nl> <19991215165550.A8672@panzer.kdm.org> <3858485E.167EB0E7@xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 16, 1999 at 02:03:10 +0000, W.H.Scholten wrote: > 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 :-) Good, glad to hear it! Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991215183635.A9876>