Date: Thu, 10 Dec 1998 10:50:14 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: freebsd@magnet.geophysik.tu-freiberg.de Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM, cdrecord and PLASMON RF4100 anyone ? Message-ID: <199812101750.KAA11062@panzer.plutotech.com> In-Reply-To: <199812100753.IAA01592@magnet.geophysik.tu-freiberg.de> from Holm Tiffe at "Dec 10, 98 08:53:24 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Holm Tiffe wrote... > Hi, > > yesterday I have for the first time tried cdrecord from the ports > to burn an CDR on my oldish PLASMON RF4100. The machine I use > was previously non-CAM an I've used FreeBSD's own worm driver to > write my CDR's. > > First, it seems that my PLASMON doesn't like the write_track() cmd > in the file drv_philips.c around the line 504. > After removing that, I was able to burn my first CDR. > But wat the hell ist this ? > > 00000000 b3 b3 b3 f7 f7 f7 f7 a2 a2 a2 a2 c2 c2 c2 c2 8c |................| > 00000010 8c 8c 8c 9b 9b 9b 9b 1f 1f 1f 1f f6 f6 f6 f6 42 |...............B| > 00000020 42 42 42 24 24 24 24 3b 3b 3b 3b 9d 9d 9d 9d be |BBB$$$$;;;;.....| [ ... ] Looks kinda like garbage. > this is a dump from the first bytes of my CDR, the entire CDR contains now this > sort of junk. > > The ISO-fs I was trying to burn is totally intact, an I can mount it using > the vn devices. > > here are the first bytes from it: > > 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 00008000 01 43 44 30 30 31 01 00 46 72 65 65 42 53 44 20 |.CD001..FreeBSD | > 00008010 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | [ ... ] And that looks okay. > > Has anyone seen this before ? Any suggestions ? > > The cmd to write the CDR was cdrecord -data dev=0,4,0 usr8.cd I doubt this is the problem, but what happens if you reverse the arguments: cdrecord dev=0,4,0 -data usr8.cd You don't have to try it, since it's unlikely that that's the problem. The cdrecord usage information kinda indicates that things subsequent to the "-data" are tracks to burn. > Cdrecord has successfully detected the burner's model and the > firmware version: > > Cdrecord release 1.6.1 Copyright (C) 1995-1998 J<F6>rg Schilling > scsidev: '0,4,0' > scsibus: 0 target: 4 lun: 0 > Device type : Removable WORM > Version : 2 > Response Format: 2 > Capabilities : SYNC > Vendor_info : 'PLASMON ' > Identifikation : 'RF4100 ' > Revision : '1.26' > Device seems to be: Plasmon RF-4100. > Using driver for Plasmon RF 4100 (plasmon_rf4100). > Driver flags : > Starting to write CD/DVD at speed 1 in write mode for single session. Well, it appears that cdrecord is able to talk to the drive, since it gets back the correct inquiry information. So, I doubt this is a CAM problem. I would suggest contacting Joerg Schilling <schilling@fokus.gmd.de>, the author of cdrecord. He may know of issues with that particular drive, or cdrecord, that would cause the above problem. Sorry I can't help more, Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812101750.KAA11062>