From owner-freebsd-questions@FreeBSD.ORG Sun Feb 1 11:06:24 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A37616A4CE for ; Sun, 1 Feb 2004 11:06:24 -0800 (PST) Received: from sarevok.webteckies.org (node123e0.a2000.nl [24.132.35.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2E0E43D3F for ; Sun, 1 Feb 2004 11:06:18 -0800 (PST) (envelope-from mdev@sarevok.webteckies.org) Received: by sarevok.webteckies.org (Postfix, from userid 100) id A82C1B82A; Sun, 1 Feb 2004 20:06:17 +0100 (CET) From: Melvyn Sopacua Organization: WebTeckies.org To: freebsd-questions@FreeBSD.org Date: Sun, 1 Feb 2004 20:06:13 +0100 User-Agent: KMail/1.5.94 References: <200401302148.28075.bsd@elkins.org> <200402010035.22746.freebsd-questions@webteckies.org> <200401311854.07542.jeffelkins@earthlink.net> In-Reply-To: <200401311854.07542.jeffelkins@earthlink.net> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_o4UHAcxaQYIlvm/"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402012006.16987.freebsd-questions@webteckies.org> Subject: Re: Using the ATAPI/CAM Driver X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 19:06:24 -0000 --Boundary-02=_o4UHAcxaQYIlvm/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 01 February 2004 00:54, Jeff Elkins wrote: > On Saturday 31 January 2004 6:35 pm, Melvyn Sopacua wrote: > >On Saturday 31 January 2004 18:54, Jeff Elkins wrote: > >> > > I _can_ mount cds using the /dev/acd* devices, while using the > >> > > /dev/cd* devices for writing. Is this the way atapi cdrws are > >> > > supposed to work under freebsd? > >> > > >> > So, is cam compiled into the kernel? Do you have the xpt SCSI driver? > >> > If cam is configured correctly, there should be mentioning of cd0 > >> > in /var/run/dmesg.boot and the cd's should be listed via: > >> > > >> > camcontrol devlist > >> > >> kathix# camcontrol devlist > >> at scbus0 target 0 lun 0 (pass0,da0) > >> at scbus0 target 0 lun 1 (pass1,da1) > >> at scbus0 target 0 lun 2 (pass2,da2) > >> at scbus0 target 0 lun 3 (pass3,da3) > >> at scbus1 target 0 lun 0 (pass4,da4) > >> at scbus3 target 0 lun 0 (pass5,cd0) > >> at scbus3 target 1 lun 0 (pass6,cd1) > >> > >> > >> cd0 at ata1 bus 0 target 0 lun 0 > >> cd0: Removable CD-ROM SCSI-0 device > >> cd0: 16.000MB/s transfers > >> > >> cd1 at ata1 bus 0 target 1 lun 0 > >> cd1: Removable CD-ROM SCSI-0 device > >> cd1: 16.000MB/s transfers > > > >Try getting rid of the DMI devices. As you can see above, the cd's claim > > bus0, while cam puts them on bus 3. Still a chance that the seagate > > overrides them though. > > > >If: > >cdrecord dev=3D3,0,0 yourfiles.iso > > > >works correctly, you might want to follow this up to -current or > > -hardware. > > Thanks. > > All recording functions work, both with cdrecord and growisofs. The only > issue is being unable to mount with /dev/cd0, /dev/cd1. I realise that I'm > in uncharted waters with 5.2, and I appreciate the reply. Does cdrecord work with dev=3D/dev/cd0 also? You did fixate those cd's (shouldn't give a "device not configured", but I/= O=20 error if you didn't, but just to make sure). =2D-=20 Melvyn =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =46reeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Ja= n 28=20 18:01:18 CET 2004 =20 root@sarevok.lan.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG = =20 i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --Boundary-02=_o4UHAcxaQYIlvm/ Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAHU4oOv9JNmfFN5URAmbcAJ0btwSejl9LOm46yLLRrR3DpvsQUgCfZupn ZEV5JoDS9CPVL2CDjscIbko= =KDJ+ -----END PGP SIGNATURE----- --Boundary-02=_o4UHAcxaQYIlvm/--