[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cd0 problems
On Thu, 6 Jun 2002 14:01:08 GMT
"Sky McKinley" <email@example.com> wrote:
> Hello. I've looked through the archives and seen reference to my
> problem, but never an explanation or a fix. When using utilities like
> cdio and cdrecord, I get messages like:
Those messages are pretty normal. If you search the list archives, you
will find a better explaination of what they mean.
> and the drive stops responding, refusing to eject discs, etc. When
> using cdrecord, the probe detected the drive to be at scsibus -2
> target -2 lun -2, which seems a bit odd. The drive is a Toshiba CDROM
> drive in a Toshiba Satellite 3000 laptop. It's one of those drives
> where you can put in either a floppy drive or a CDROM. My full dmesg
> is as follows:
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: <MATSHITA, UJDA720 DVD/CDRW, 1.00> SCSI0 5/cdrom removable
Under OpenBSD, you need to specify the bus, target, and lun. You can
find these in the output from dmesg. In your case:
cdrecord dev=/dev/cd0c:0,0,0 ...
I believe I have the exact same drive in an IBM Thinkpad T21 (only
labeled as an IBM drive). When writing or copying CD's with cdrdao or
cdrecord, the drive does stop responding, and requires the respective
unlock commands from cdrecord or cdrdao in order to be usable again.
The only way I've been able to write to CD-R(W) media is to use the
force option to each command (cdrdao --force ..., cdrecord -force ...).
With this option set, the drive seems to work as expected.