So near and yet so far...
I'm trying to hang a Panasonic DVD-RAM disk on to my DU4.0D system.
The system sees it OK, and read-access works. (dd if=/dev/DVDdev of=/dev/null)
but writing is a problem, in that the device seems to default to read-only,
and I cant permanently change that.
Using scu:
scu> sh inq
Inquiry Information:
Peripheral Device Type: 0x5 (Read-Only Direct Access)
Peripheral Qualifier: 0 (Peripheral Device Connected)
Device Type Modifier: 0
Removable Media: Yes
ANSI Version: 2 (Complies to ANSI X3.131-1994, SCSI-2)
ECMA Version: 0
ISO Version: 0
Response Data Format: 2 (SCSI-2)
Terminate I/O Process: No
Additional Length: 91
Soft Reset Support: No
Command Queuing Support: No
Target Transfer Disable: No
Linked Command Support: No
Synchronous Data Transfers: Yes
Support for 16 Bit Transfers: No
Support for 32 Bit Transfers: No
Relative Addressing Support: No
Vendor Identification: MATSHITA
Product Identification: PD-2 LF-D100
Firmware Revision Level: A110
Vendor Specific Data: 31 31 2f 30 36 2f 39 38 50 "11/06/98P"
44 2d 32 20 4c 46 2d 44 31 "D-2 LF-D1"
30 30 01 00 00 00 00 00 00 "00 "
00 00 00 00 00 00 00 00 00 " "
00 00 00 00 00 00 00 00 00 " "
00 00 00 00 00 00 00 00 00 " "
00 00 00 00 00 00 " "
scu> sh dev
Inquiry Information:
SCSI Bus ID: 0
SCSI Target ID: 1
SCSI Target LUN: 0
Peripheral Device Type: 0x5 (Read-Only Direct Access)
Peripheral Qualifier: 0 (Peripheral Device Connected)
Device Type Modifier: 0
Removable Media: Yes
ANSI Version: 2 (Complies to ANSI X3.131-1994, SCSI-2)
ECMA Version: 0
ISO Version: 0
Response Data Format: 2 (SCSI-2)
Terminate I/O Process: No
Additional Length: 91
Soft Reset Support: No
Command Queuing Support: No
Target Transfer Disable: No
Linked Command Support: No
Synchronous Data Transfers: Yes
Support for 16 Bit Transfers: No
Support for 32 Bit Transfers: No
Relative Addressing Support: No
Vendor Identification: MATSHITA
Product Identification: PD-2 LF-D100
Firmware Revision Level: A110
By using scu, I can do a
scu> set cam dev direct-access
whereupon:
scu> sh inq shows no change, but
scu> sh dev shows me a writeable device
scu> sh inq
Inquiry Information:
Peripheral Device Type: 0x5 (Read-Only Direct Access)
Peripheral Qualifier: 0 (Peripheral Device Connected)
Device Type Modifier: 0
Removable Media: Yes
ANSI Version: 2 (Complies to ANSI X3.131-1994, SCSI-2)
ECMA Version: 0
ISO Version: 0
Response Data Format: 2 (SCSI-2)
Terminate I/O Process: No
Additional Length: 91
Soft Reset Support: No
Command Queuing Support: No
Target Transfer Disable: No
Linked Command Support: No
Synchronous Data Transfers: Yes
Support for 16 Bit Transfers: No
Support for 32 Bit Transfers: No
Relative Addressing Support: No
Vendor Identification: MATSHITA
Product Identification: PD-2 LF-D100
Firmware Revision Level: A110
Vendor Specific Data: 31 31 2f 30 36 2f 39 38 50 "11/06/98P"
44 2d 32 20 4c 46 2d 44 31 "D-2 LF-D1"
30 30 01 00 00 00 00 00 00 "00 "
00 00 00 00 00 00 00 00 00 " "
00 00 00 00 00 00 00 00 00 " "
00 00 00 00 00 00 00 00 00 " "
00 00 00 00 00 00 " "
scu> sh dev
Inquiry Information:
SCSI Bus ID: 0
SCSI Target ID: 1
SCSI Target LUN: 0
Peripheral Device Type: 0 (Direct Access)
Peripheral Qualifier: 0 (Peripheral Device Connected)
Device Type Modifier: 0
Removable Media: No
ANSI Version: 0 (May or maynot comply to ANSI-approved sta
ndard)
ECMA Version: 0
ISO Version: 0
Response Data Format: 0 (SCSI-1)
Additional Length: 0
and indeed I can then do a
scu> write media lba 1000 and write to the device.
However this new ability to write seems to be only possible within scu.
If I try to dd to the device, it still complains 'read-only'.
If I exit and re-enter scu and try the 'write media' without first
doing a 'set cam dev direct-access' it fails in the same way.
Is there some way I can globally and permanently (at least for the duration of
one boot) change the mode on a device?
I've attempted to make an entry in /etc/ddr.dbase for this device,
with a TypeSubClass = floppy_3.5 but the system seems to take no
notice of it. In fact all the above is without a ddr entry. (Never
did understand the reason for all those SCSIDEVICE entries when the
system seems to be able to find out all it wants to know by asking
the device - I've got Seagate, Fujitsu and IBM 3rd-party hard disks
all happily labelled and singing without any ddr entries...)
TIA,
Terry
Terry Horsnell (tsh_at_mrc-lmb.cam.ac.uk)
Computer Manager
Medical Research Council
Lab of Molecular Biology
Hills Road
CAMBRIDGE CB2 2QH
U.K.
Received on Mon Feb 22 1999 - 17:11:20 NZDT