From owner-freebsd-questions Wed Aug 11 21:51: 1 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ginger.kf7nn.com (mti-r1-aptis-4-p2007.cybertrails.com [162.42.15.214]) by hub.freebsd.org (Postfix) with ESMTP id 345B715684 for ; Wed, 11 Aug 1999 21:50:56 -0700 (PDT) (envelope-from root@ginger.kf7nn.com) Received: (from root@localhost) by ginger.kf7nn.com (8.9.3/8.9.3) id VAA01798; Wed, 11 Aug 1999 21:33:36 -0700 (MST) (envelope-from root) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 11 Aug 1999 21:33:36 -0700 (MST) From: kf7nn1@cybertrails.com To: kf7nn1@cybertrails.com Subject: Re: cdrecord help Cc: vagner@www.timandpatrick.com, questions@FreeBSD.ORG, cjclark@home.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I added the posix scheduler stuff to my kernel and rebuilt and it got rid of those errors about RR-scheduler not available as the website suggested. Funny thing is this is a 6X write 4X rewrite and i originally tried the 6x write as shown below, for S and G i tried it at 4X this time and its going on about 10 minutes of doing the dummy write without errors. Next i will try it without the -dummy and see if it makes it at 4X although its supposed to do 6X. OH one more thing, I see a warning for track size so how do i know the track size to tell it.?? On 12-Aug-99 kf7nn1@cybertrails.com wrote: > well here is my output although i dont know if > the errors are due to the dummy write or not. > > This is with a blank cd-r in the drive that i have done nothing > with, and was wondering do i need to put a filesystem on it > or something first or can i just write it raw from another > cd-rom? > > > mutsgo# cdrecord -dummy -data -speed=6 dev=0,3,0 /dev/rwdc0c > cdrecord: No such file or directory. No read access for '/dev/rwdc0c'. > > mutsgo# cdrecord -dummy -data -speed=6 dev=0,3,0 /dev/rwcd0c > Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling > cdrecord: No such file or directory. WARNING: RR-scheduler not available, > disab > ing. > scsidev: '0,3,0' > scsibus: 0 target: 3 lun: 0 > Device type : Removable CD-ROM > Version : 2 > Response Format: 2 > Capabilities : SYNC > Vendor_info : 'YAMAHA ' > Identifikation : 'CRW6416S ' > Revision : '1.0b' > Device seems to be: Generic mmc CD-RW. > Using generic SCSI-3/mmc CD-R driver (mmc_cdr). > Driver flags : SWABAUDIO > cdrecord: WARNING: Track size unknown. Data may not fit on disk. > cdrecord: Undefined error: 0. WARNING: RR-scheduler not available, disabling. > Starting to write CD/DVD at speed 6 in dummy mode for single session. > Last chance to quit, starting dummy write in 1 seconds. > cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error > CDB: 2A 00 00 00 10 B6 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 21 00 00 00 00 00 00 00 00 > 00 > 0 08 00 00 00 00 00 00 08 00 > Sense Key: 0x5 Illegal Request, Segment 0 > Sense Code: 0x21 Qual 0x00 (logical block address out of range) Fru 0x0 > Sense flags: Blk 0 (not valid) > resid: 63488 > cmd finished after 2.263s timeout 40s > write track data: error after 8761344 bytes > Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 > mutsgo# > > On 12-Aug-99 Crist J. Clark wrote: >> vagner@WWW.TIMANDPATRICK.COM wrote, >>> I just installed a Yamaha 6416S on my 3.2-stable system >>> and need some help with the commands to write a cd-r. >>> >>> The reason I ask is because the man page for cdrecord >>> reads like I know all about these cd recorders when I dont >>> cause i just got it. >>> >>> I have an atapi cd-rom at wdc1 (secondary slave) >>> and the scsi cd-rw at ID3 scsibus 0. >>> >>> Installed is cdrecord, mkisofs and cd-write. >>> >>> What would I type in to make a duplicate of the >>> cdrom in the wdc1 drive on the scsi cd0 drive (yamaha)? >>> >>> I dont want to waste a bunch of cd-r's trying to >>> figure out the commands! this is another reason I ask first... >> >> See the -dummy flag for how to test a command line without actually >> burning the CD. >> >>> I am almost brave enough to try >>> cdrecord dev= /dev/wcd0c:0,cd0,0 >> >> To copy straight from one CD to another, I would try, >> >># cdrecord -data -speed= dev=0,3,0 /dev/rwdc0c >> >> As mentioned above, to test this, >> >># cdrecord -dummy -data -speed= dev=0,3,0 /dev/rwdc0c >> >> HTH. >> -- >> Crist J. Clark cjclark@home.com > > ---------------------------------- > E-Mail: kf7nn1@cybertrails.com or kf7nn@kf7nn.com > Date: 11-Aug-99 > Time: 20:45:18 > > Great minds run in great circles. > > This message was sent using FreeBSD Unix. > ---------------------------------- ---------------------------------- E-Mail: kf7nn1@cybertrails.com or kf7nn@kf7nn.com Date: 11-Aug-99 Time: 21:27:14 One seldom sees a monument to a committee. This message was sent using FreeBSD Unix. ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message