From owner-freebsd-scsi Mon Aug 10 22:40:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11512 for freebsd-scsi-outgoing; Mon, 10 Aug 1998 22:40:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11505 for ; Mon, 10 Aug 1998 22:40:45 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id XAA00192; Mon, 10 Aug 1998 23:34:36 -0600 (MDT) Date: Mon, 10 Aug 1998 23:34:36 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808110534.XAA00192@narnia.plutotech.com> To: The Hermit Hacker cc: scsi@FreeBSD.ORG Subject: Re: CAM support for NCR controller... Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Actually, I'm going to leave the system "as is" for the next couple of > days, while I await some new hardware to arrive. If someone out there > working on the NCR drivers has suggestions on what I can try towards > providing more debug information on the problem, towards the betterment of > the CAM drivers, please speak up...I provide my system as a test bed. A "boot -v" dmesg from the CAM system would be a place to start. It would also help if you related the errors that are reported during your failed CD-R burn sessions. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message