dvdrtools-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dvdrtools-users] Re: Weird "scsibus" assignment -- WAS: Sony DRU-500A:


From: Dominique Alessandri
Subject: [Dvdrtools-users] Re: Weird "scsibus" assignment -- WAS: Sony DRU-500A: Cannot even burn DVD+/-Rs
Date: Sat, 25 Jan 2003 16:28:53 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021203

Bryan,

> Er, the "3" in "3,0,0" is not the "device" but the "bus/controller."

Sorry for having confused 'device' and 'bus'.

> That means you must have 3 other "bus/controllers" in your system
> labeled 0, 1 and 2.  Plus, IDE-SCSI actually "lumps" all ATA devices
> into the same "bus," even if they are on different cards.

Exactly. I did a cdrecord -scanbus, and I am clearly using the correct device (3,0,0). The box has an on-board scsi controller which is not used (bus 0 and 1) that causes the 'cdrecord-prodvd: Warning Linux Bus mapping botch.' messages. In addition the box has a RAID controller that is seen as bus 2 by the OS. The IDE-SCSI devices are 'mapped' onto bus 3:

# cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
Linux sg driver version: 3.1.24
cdrecord: Warning Linux Bus mapping botch.
cdrecord: Warning Linux Bus mapping botch.
Using libscg version 'schily-0.5'
scsibus2:
        2,0,0   200) 'IBM     ' 'SERVERAID       ' '1.00' Disk
[SNIP]
scsibus3:
        3,0,0   300) 'SONY    ' 'DVD RW DRU-500A ' '1.0f' Removable CD-ROM
        3,1,0   301) *
[SNIP]

So, I am sure that I am using the correct device. Actually also cdrecord-prodvd tells me this:

Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'SONY    '
Identifikation : 'DVD RW DRU-500A '
Revision       : '1.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Drive current speed: 2
Drive default speed: 2
Drive max speed    : 2
Selected speed     : 2

The problems only start later. There must be something else going wrong:

Executing 'log sense' command on Bus 3 Target 0, Lun 0 timeout 100s
CDB:  4D 00 43 00 00 00 00 00 FF 00
/usr/local/bin/cdrecord-prodvd: Input/output error. log sense: scsi
sendcmd: no error
CDB:  4D 00 43 00 00 00 00 00 FF 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 20 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x20 Qual 0x00 (invalid command operation code) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.009s timeout 100s

[SNIP]

/usr/local/bin/cdrecord-prodvd: Input/output error. reserve_rzone: scsi
sendcmd: no error
CDB:  53 00 00 00 00 00 22 C2 C0 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.010s timeout 100s
input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Writing  time:   41.798s
Average write speed 999.0x.
Fixating...
Fixating time:    0.000s
/usr/local/bin/cdrecord-prodvd: fifo had 64 puts and 0 gets.
/usr/local/bin/cdrecord-prodvd: fifo was 0 times empty and 0 times full,
min fill was 100%.

The question is why the 'log sense' and all the other commands are
considered to be 'Illegal Request(s)'.

BTW, using stock RedHat cdrecord the drive burns CDs just fine.

If I find the time I might just try to use the drive on a IDE-only PC and see how it behaves. However, I suspect that it is merely the problem of some driver missmatch.

Dominique





reply via email to

[Prev in Thread] Current Thread [Next in Thread]