From owner-freebsd-questions Mon Jun 21 14:16: 1 1999 Delivered-To: freebsd-questions@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 7857214E32 for ; Mon, 21 Jun 1999 14:15:55 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id OAA38472; Mon, 21 Jun 1999 14:15:53 -0700 (PDT) (envelope-from mph) Date: Mon, 21 Jun 1999 14:15:53 -0700 From: Matthew Hunt To: cjclark@home.com Cc: FreeBSD Questions Subject: Re: cdrecord Problems After Upgrade Message-ID: <19990621141553.A38327@wopr.caltech.edu> References: <199906211935.PAA04495@cc942873-a.ewndsr1.nj.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906211935.PAA04495@cc942873-a.ewndsr1.nj.home.com>; from Crist J. Clark on Mon, Jun 21, 1999 at 03:35:33PM -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 21, 1999 at 03:35:33PM -0400, Crist J. Clark wrote: > We just upgraded a 3.1-STABLE system to 3.2-STABLE, and now it seems > that 'cdrecord' is broken. The CDD is found fine during startup, I don't know anything specific, as I don't use cdrecord on FreeBSD, but I do know that there were CAM (SCSI subsystem) changes between 3.1 and 3.2. These changes require recompiling most software that interacts with SCSI devices directly, such as xmcd and probably cdrecord. You should try re-building cdrecord or installing the package that comes with 3.2. I suspect that will solve your problem. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message