From owner-freebsd-bugs Tue Nov 23 5:20: 4 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BF45714E14 for ; Tue, 23 Nov 1999 05:20:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA30226; Tue, 23 Nov 1999 05:20:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 23 Nov 1999 05:20:01 -0800 (PST) Message-Id: <199911231320.FAA30226@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jan Riedinger Subject: Re: kern/15054: system with ncr controller fails to boot if plextor cdrom connected Reply-To: Jan Riedinger Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/15054; it has been noted by GNATS. From: Jan Riedinger To: ken@kdm.org (Kenneth D. Merry) Cc: jan@physik.tu-berlin.de, freebsd-gnats-submit@FreeBSD.ORG, se@FreeBSD.ORG, groudier@club-internet.fr Subject: Re: kern/15054: system with ncr controller fails to boot if plextor cdrom connected Date: Tue, 23 Nov 1999 14:11:00 +0100 (CET) > > Gerard Roudier and Stefan Esser are the only ones who know how to decipher > the NCR driver's error message. Perhaps one of you could decipher Jan's > error messages below? > > Sorry for including the whole text of your problem report, but it may be > necessary for one of them to make sense of what is going on. > > Gerard Roudier has ported his SYM driver from Linux to FreeBSD. It fixes > many bugs with the existing NCR driver, and supports most NCR 53c8xx chips, > including the 53c860. > > You may want to try out Gerard's driver, since you'll probably have a > better chance of getting your CDROM drive working with it. Here's a > snippet from his latest release (November 13th): > > > I have made available SYM driver 0.10.0. The driver should compile fine > > under FreeBSD 3.2, 3.3 and -CURRENT. > > > > Installation requires the following files: > > > > ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/SYM-0.9.0-19991024.tar.gz > > ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/PATCH-SYM-0.10.0-19991111.gz > > ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/README.sym > > Since the SYM driver supports 3.3, you should be able to install 3.3 > without your CDROM drive, patch his driver into the sources, recompile your > kernel and try it out. > Thank you very much for your hint. With the sym driver I was able to boot even with a connected CDROM and I got parity error messages. I examined my jumper settings and saw, that I had set a jumper at the CDROM to enable termination instead of parity checking. But this solved only the parity error messages and nothing else. At the next step I had the idea to make the CDROM responsible for the termination of the SCSI bus and not my TANDBERG streamer, because this one has only a passiv termination. Now I can boot my system with and without the sym driver. Now someone has to close the pr-report. Thank you very much Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message