From owner-freebsd-questions Sun Jul 18 10: 3:27 1999 Delivered-To: freebsd-questions@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 9A2B314BD8 for ; Sun, 18 Jul 1999 10:03:13 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id TAA25645 for ; Sun, 18 Jul 1999 19:01:37 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id TAA07633 for ; Sun, 18 Jul 1999 19:01:28 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id TAA65068 for ; Sun, 18 Jul 1999 19:01:37 +0200 (CEST) Date: Sun, 18 Jul 1999 19:01:34 +0200 From: Andre Albsmeier To: Udo Schweigert Cc: tyl , freebsd-questions@FreeBSD.ORG Subject: Re: How to make cdrecord work Message-ID: <19990718190134.A26406@internal> References: <19990718175430.A9850@alaska.cert.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <19990718175430.A9850@alaska.cert.siemens.de>; from Udo Schweigert on Sun, Jul 18, 1999 at 05:54:30PM +0200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18-Jul-1999 at 17:54:30 +0200, Udo Schweigert wrote: > On Sun, Jul 18, 1999 at 09:22:14PM +0800, tyl wrote: > > > > my OS : FreeBSD 4.0-19990503 > > kernel : with "device pass0" > > > > when I run "cdrecord -scanbus", It appears the following lines > > cdrecord: Inappropriate ioctl for device. CAMIOCOMMAND ioctl failed. > > cdrecord: Inappropriate ioctl for device. Cannot open SCSI driver. > > > > I know I must miss MANY things, but I cannot find suggestions from FAQ > > or somethings like that. Is there any web site or documents for my > > situation? I am very appreciated for your help !!! > > > > Hace you created your pass devices /dev/pass? I think I also had these error > messages because there weren't enough of them. So something like: > > # cd /dev > # sh MAKEDEV pass8 > > will do it. I think the error messgae for a missing /dev/pass device is different. Also, if the cdrom device is not one of the first 8 devices, 8 pass devices is not enough. IMHO, a good idea is to wire the devices down in the kernel config together with the pass entry. My part of the kernel config looks like the following (ok, it's a bigger machine, but that's what I have got hand at the moment): controller ahc0 controller scbus0 at ahc0 device pass0 at scbus0 target 0 device da0 at scbus0 target 0 device pass1 at scbus0 target 1 device da1 at scbus0 target 1 device pass2 at scbus0 target 2 device da2 at scbus0 target 2 device pass3 at scbus0 target 3 device da3 at scbus0 target 3 device pass4 at scbus0 target 4 unit 0 device sa0 at scbus0 target 4 unit 0 device ch0 at scbus0 target 4 unit 1 device pass5 at scbus0 target 5 device cd1 at scbus0 target 5 device pass6 at scbus0 target 6 device cd0 at scbus0 target 6 controller ahc1 controller scbus1 at ahc1 device pass10 at scbus1 target 0 device da10 at scbus1 target 0 device pass11 at scbus1 target 1 device da11 at scbus1 target 1 device pass12 at scbus1 target 2 device da12 at scbus1 target 2 device pass13 at scbus1 target 3 device da13 at scbus1 target 3 device pass14 at scbus1 target 4 device da14 at scbus1 target 4 device pass15 at scbus1 target 5 device da15 at scbus1 target 5 device pass16 at scbus1 target 6 device da16 at scbus1 target 6 controller ahc2 controller scbus2 at ahc2 device pass20 at scbus2 target 0 device da20 at scbus2 target 0 device pass21 at scbus2 target 1 device da21 at scbus2 target 1 device pass22 at scbus2 target 2 device da22 at scbus2 target 2 device pass23 at scbus2 target 3 device da23 at scbus2 target 3 device pass24 at scbus2 target 4 device da24 at scbus2 target 4 device pass25 at scbus2 target 5 device da25 at scbus2 target 5 device pass26 at scbus2 target 6 device da26 at scbus2 target 6 The resulting "cdrecord -scanbus" command: scsibus0: 0) 'IBM ' 'DPES-31080 ' 'S31Q' Disk 1) 'SEAGATE ' 'ST423451N ' '0011' Disk 2) * 3) * 4) 'Quantum ' 'DLT4700 ' 'D98C' Removable Tape 5) 'YAMAHA ' 'CRW4260 ' '1.0q' Removable CD-ROM 6) 'PIONEER ' 'CD-ROM DR-766 ' '1.00' Removable CD-ROM 7) * scsibus1: 100) 'IBM ' 'DDRS-34560 ' 'S97B' Disk 101) 'IBM ' 'DDRS-39130 ' 'S97B' Disk 102) 'SEAGATE ' 'ST15230N ' '0298' Disk 103) 'Quantum ' 'XP34300 ' 'L915' Disk 104) 'IBM ' 'DDRS-39130W ' 'S97B' Disk 105) 'QUANTUM ' 'XP39100W ' 'LYK8' Disk 106) * 107) * scsibus2: 200) 'IBM ' 'DDRS-34560 ' 'S97B' Disk 201) 'IBM ' 'DDRS-39130 ' 'S97B' Disk 202) 'SEAGATE ' 'ST15230N ' '0298' Disk 203) 'Quantum ' 'XP34300 ' 'L915' Disk 204) 'IBM ' 'DDRS-39130W ' 'S97B' Disk 205) 'QUANTUM ' 'XP39100W ' 'LYK8' Disk 206) * 207) * You can boot -v and see which pass device corresponds to the cdwriter. Don't forget that you also must have the /dev/xpt0 device. Hope that helps, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message