August 2003 - Packet Writing - openSUSE Mailing Lists

SUMMARY: 2.4.21 packet-mode UDF CDRW via USB from external ATAPI burner
by Frantisek Rysanek 28 Aug '03

28 Aug '03

Dear everyone, this message is a summary/result of a private e-mail exchange with a few Linux kernel developers. The two active participants were Peter Osterlund and Matthew Dharm. I was trying to get packet-written UDF to work with the following hardware setup: [Linux PC]->[USB]->[USB/IDE converter]->[ATAPI CDRW drive] USB/IDE converter was one of 1) Cypress Semiconductor CY7C68300 (USB2) 2) ScanLogic SL11R-IDE (USB 1.1) ATAPI CDRW drive was one of 1) NEC DVD_RW ND-1300A 2) RICOH CD-R/RW MP7240A The Linux kernel version was 2.4.21. As posted earlier and documented elsewhere, for packet writing to CD-ROM drives, you need the packet-writing kernel patch and you need to set up /dev/pktcdvd* device nodes. You also need to download the udf-tools package, containing some user-space utils, most importantly pktsetup and cdrwtool. As documented elsewhere, IDE/ATAPI devices attached via a USB converter appear in Linux as dynamically added SCSI devices - the CD drives appear as /dev/scd*. The emulation magic is done by the usb-storage module. My symptoms were the following: 1) UDF formatting using cdrwtool and CD burning using cdrecord was possible at least with the Cypress chip (USB2). The ScanLogic chip tended to corrupt such long track-at-once writes for some reason, either due to an individual hardware failure or due to a design flaw, or maybe due to USB1.1 - I don't know. 2) it was possible to run pktsetup and to mount the media RW 3) write attempts generated heaps of I/O errors and nothing got actually written. 4) which could be checked by unmounting the CD and remounting it read-only from the base device scd* (which worked flawless) 5) with native ATAPI/IDE attachment (no USB), the software setup worked flawless. An additional symptom is that, when attached via the USB converter, the ATAPI CDRW drive is detected as a scsi1 cdrom, rather than a scsi3-mmc cdrw. The reason is the following: In Linux 2.4, the usb-storage module does a SCSI emulation. My limited knowledge suggests that SCSI and ATAPI share a common subset of the command sets. There are two standard formats of the SCSI commands: 6byte and 10byte. There's a special MODE_SENSE command, that allows the host computer to learn about the capabilities of a particular SCSI (cdrom?) device - read-only, read-write, CD/DVD etc. My ATAPI devices only accept the 10byte MODE_SENSE. I don't know if this is an inherent ATAPI feature or practical implementation flaw that goes unnoticed under Microsoft and Apple OS'es (as suggested by others). The pktcdvd.o module (for UDF packet writing on CDRW) uses the standard SCSI CDrom interface (the sr.o module) to access the SCSI drives, and hence also USB-storage / ATAPI devices. The sr.o module uses 6byte MODE_SENSE to get the device capabilities. The usb-storage module is able to translate the 6byte MODE_SENSE to 10byte, if inited properly. However, it does not act accordingly on the basis of just detecting an ATAPI CDROM. The particular init parameters have to be configured in drivers/usb/storage/unusual_devs.h, for a particular *USB/IDE converter*. The defaults for my converters do not include 6byte-to-10byte translation. Why cdrecord and cdrwtool do work: they're using the SCSI-generic interface, rather than the SCSI-cdrom interface. And they're doing their own detection (MODE_SENSE). And, CDrecord has been used to dealing with ATAPI CDRW drives via a SCSI emulation for quite some time now. The cdrwtool seems to be inspired by cdrecord in this respect. Solution: Compile-time configuration change is required, in a header file (not accessible via config/menuconfig). I had to modify one section and add one section to the unusual_devs.h. See the patch attached below my signature. There are two possible modifications to unusual_devs.h: either you can stick to the default US_SC_SCSI protocol and just add the US_FL_MODE_XLATE flag (can be OR'ed with other flags), or you can replace the US_SC_SCSI protocol by one of US_SC_8020 or US_SC_8070. Deeper in the usb-storage guts, this is essentially equivalent to adding the US_FL_MODE_XLATE flag to the transparent SCSI handler. Matthew Dharm says that this is _not_quite_ equivalent - I'm not sure. Thanks to Peter Osterlund for suggesting the US_SC_8020 tag and thanks to Matthew Dharm for spending his time discussing the usb-storage guts with me. Thanks to both for the debugging hints. Matthew Dharm went on to suggest that this should really be solved in sr.o, in the get_capabilites() function, that should try 10byte MODE_SENSE and fall back to 6byte. Which is a point for further improvements in sr.c and has already been suggested by Matthew Dharm at the relevant addresses... Meanwhile, the 2.6.x is knocking on the door, coming with a ton of reworks and improvements in USB/SCSI/IDE, a new runtime hot-swappable device inventory model etc. Other implications: Due to the way usb-storage is implemented in kernel 2.4.21, there is no way in terms of compile-time configuration to enable 6-to-10byte command translation for all ATAPI CDRW drives in general. The default is "no translation" and everyone needs to turn this on for their particular converter USB/IDE converter chip (rather than for a particular ATAPI drive). Which involves modifying or adding a section in unusual_devs.h. Debugging hints: Turn on USB debugging, verbose USB storage debugging, verbose SCSI debugging and kernel debugging in 'make menuconfig'. Set PACKET_DEBUG to 2 in include/linux/pktcdvd.h . Don't forget to turn on kernel debug logging in syslog.conf && /etc/init.d/syslog restart The messages from usb-storage come out as kern.=debug . I myself have set up logging of all kernel messages into a dedicated file: # add this line to /etc/systlog.conf kern.* /var/log/kerndebug Thanks to everyone involved for their time and effort. Frank Rysanek ############## now for the patch ############ Please note another patch that had to be applied in order to make the ScanLogic SL11R chip work (merged in my patch below). The patch was originally applied by Gunther Meyer a long time ago, disapproved of by Leif Sawyer shortly afterwards, but seems to be necessary even now - without it, usb-storage.o hangs upon insmod. One other unnecessary modification is the additional debugging stub in drivers/usb/storage/transport.c that shows whether the translation works. If you're only interested in 6-to-10byte translation, focus on unusual_devs.h and the flag US_FL_MODE_XLATE. Please note that this patch is hardware-specific to my USB/IDE converters - but you shouldn't have a problem to roll your own section in unusual_devs.h if you have a different converter chip with the same symptoms. ############### file 2.4.21-USB_packet_UDF_CDRW.patch ################ diff -Naur linux-2.4.21-pkt/drivers/usb/storage/transport.c linux/drivers/usb/storage/transport.c --- linux-2.4.21-pkt/drivers/usb/storage/transport.c 2003-06-13 16:51:37.000000000 +0200 +++ linux/drivers/usb/storage/transport.c 2003-08-27 14:14:47.000000000 +0200 @@ -627,6 +627,10 @@ int need_auto_sense; int result; + US_DEBUGP("usb_stor_invoke_transport():\n"); + US_DEBUGP(" obtained this from the protocol handler:\n"); + US_DEBUG(usb_stor_show_command(us->srb)); + /* send the command to the transport layer */ result = us->transport(srb, us); @@ -1251,7 +1255,8 @@ le32_to_cpu(bcs->Signature), bcs->Tag, bcs->Residue, bcs->Status); if (bcs->Signature != cpu_to_le32(US_BULK_CS_SIGN) || - bcs->Tag != bcb->Tag || +/* bcs->Tag != bcb->Tag || */ + ((bcs->Tag != bcb->Tag) && !(us->flags & US_FL_QUIRKS_TAG)) || bcs->Status > US_BULK_STAT_PHASE || partial != 13) { US_DEBUGP("Bulk logical error\n"); ret = USB_STOR_TRANSPORT_ERROR; diff -Naur linux-2.4.21-pkt/drivers/usb/storage/unusual_devs.h linux/drivers/usb/storage/unusual_devs.h --- linux-2.4.21-pkt/drivers/usb/storage/unusual_devs.h 2003-08-20 09:33:08.000000000 +0200 +++ linux/drivers/usb/storage/unusual_devs.h 2003-08-27 14:07:18.000000000 +0200 @@ -120,13 +120,40 @@ /* Reported by Peter Wächtler <pwaechtler(a)loewe-komp.de> * The device needs the flags only. + * + * Update by Gunther Meyer <gunther.mayer(a)gmx.net>: + * Firmware 2.60 needs US_FL_QUIRKS_TAG here! Bugger device. + * + * Update by Frank Rysanek <Frantisek.Rysanek(a)post.cz>: + * For proper detection of ATAPI MMC CD-RW drives, so that + * they're any use for packet-written UDF, this device also + * needs the US_FL_MODE_XLATE flag. + * In combination with the US_SC_SCSI protocol, this flag + * causes translation of the 6byte MODE_SENSE commands to + * the corresponding 10byte format. */ -UNUSUAL_DEV( 0x04ce, 0x0002, 0x0074, 0x0074, +UNUSUAL_DEV( 0x04ce, 0x0002, 0x0000, 0x9999, "ScanLogic", "SL11R-IDE", US_SC_SCSI, US_PR_BULK, NULL, - US_FL_FIX_INQUIRY), + US_FL_QUIRKS_TAG | US_FL_MODE_XLATE), +/* Reported by Frank Rysanek <Frantisek.Rysanek(a)post.cz>. + * For proper detection of ATAPI MMC CD-RW drives, so that + * they're any use for packet-written UDF, this device also + * needs the US_FL_MODE_XLATE flag. + * In combination with the US_SC_SCSI protocol, this flag + * causes translation of the 6byte MODE_SENSE commands to + * the corresponding 10byte format. + * Otherwise the device is perfectly generic, + * For read-only CDRom access this entry is not needed. + */ +UNUSUAL_DEV( 0x04b4, 0x6830, 0x0000, 0x9999, + "Cypress Semiconductor", + "CY7C68300 USB2/IDE converter", + US_SC_SCSI, US_PR_BULK, NULL, + US_FL_MODE_XLATE), + /* Reported by Kriston Fincher <kriston(a)airmail.net> * Patch submitted by Sean Millichamp <sean(a)bruenor.org> * This is to support the Panasonic PalmCam PV-SD4090 diff -Naur linux-2.4.21-pkt/drivers/usb/storage/usb.h linux/drivers/usb/storage/usb.h --- linux-2.4.21-pkt/drivers/usb/storage/usb.h 2003-08-20 09:33:06.000000000 +0200 +++ linux/drivers/usb/storage/usb.h 2003-08-20 09:50:08.000000000 +0200 @@ -103,6 +103,9 @@ #define US_FL_IGNORE_SER 0x00000010 /* Ignore the serial number given */ #define US_FL_SCM_MULT_TARG 0x00000020 /* supports multiple targets */ #define US_FL_FIX_INQUIRY 0x00000040 /* INQUIRY response needs fixing */ +#define US_FL_QUIRKS_TAG 0x00000080 /* the buggy device doesn't echo the tag + in the status response !*/ + #define USB_STOR_STRING_LEN 32

1 0

cdrwtool : no medium found on SuSE 8.2 with philips DVDRW228
by Peter Van Biesen 26 Aug '03

26 Aug '03

Hi, I'm trying to setup an udf disk but I get following error : --------------------------------------------------------------------- pcvlf936:/bigvol # cdrwtool -d /dev/cdrecorder -q -t 2 using device /dev/cdrecorder setting speed to 2 1280KB internal buffer setting write speed to 2x Settings for /dev/cdrecorder: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/cdrecorder. The disc is going to be blanked and formatted with one big track. All data on the device will be lost!! Press CTRL-C to cancel now. ENTER to continue. Initiating quick disc blank wait_cmd: No medium found Command failed: a1 01 00 00 00 00 00 00 00 00 00 00 - sense 02.04.07 blank disc: Illegal seek ------------------------------------------------------------------------ The drive is blanking the disk, but the error occurs before the drive is done writing. Any help would be welcome. Thanks ! PEter. -- Peter Van Biesen Adj. Sysadmin V.F.S.I.P.H. tel: +32 (0) 2 225 85 70 fax: +32 (0) 2 225 85 88 e-mail: peter.vanbiesen(a)vlafo.be

1 0

Patch for 2.4.22
by Peter Osterlund 25 Aug '03

25 Aug '03

I have uploaded a patch for kernel 2.4.22: http://w1.894.telia.com/~u89404340/patches/packet/2.4/packet-2.4.22.patch.b… Changes since last version: - Fixed pktcdvd driver to work nicely with the loop driver, so that you can create encrypted CDs for example. (The loop driver doesn't bother to mark buffers uptodate before sending them to the block device driver.) - Made it impossible to kill the kcdrwd kernel thread from user space. - Don't give up if the OPC command fails. A drive that does not implement the OPC command will probably do OPC internally before starting to write, so ignoring the error seems sensible. -- Peter Osterlund - petero2(a)telia.com http://w1.894.telia.com/~u89404340

1 0

Re: 2.4.21 (and 2.4.18): packet-mode UDF CDRW via USB from external ATAPI burner
by Peter Osterlund 20 Aug '03

20 Aug '03

On Wed, 20 Aug 2003, Frantisek Rysánek wrote: > Okay, here's a more chatty log, as per your recommendation > (the attached text file). > I had usb-storage verbose debug turned on the last time already > - but that module doesn't seem to complain about anything. Then I don't think it is activated. It will generate lots of debug information even when nothing is wrong. Maybe you need to modify /etc/syslog.conf to include debug messages. -- Peter Osterlund - petero2(a)telia.com http://w1.894.telia.com/~u89404340

1 0

Re: 2.4.21 (and 2.4.18): packet-mode UDF CDRW via USB from external ATAPI burner
by Peter Osterlund 18 Aug '03

18 Aug '03

On Mon, 18 Aug 2003, [iso-8859-2] Franti¹ek Ry¹ánek wrote: > If you happen to have any ideas, please let me know. > Ask me if you want me to test something. It would probably help if you enable verbose usb storage debugging messages and set PACKET_DEBUG to 2 in include/linux/pktcdvd.h. > pktcdvd: pktcdvd0: WRITE error sector 1280 > pktcdvd: pktcdvd0: WRITE error sector 1284 > pktcdvd: pktcdvd0: WRITE error sector 1288 > ... etc, about 30 lines -- Peter Osterlund - petero2(a)telia.com http://w1.894.telia.com/~u89404340

1 0

Disc format problems
by Ljubomir Bozic Jr. 10 Aug '03

10 Aug '03

I have 2.4.21 kernel with con kolivas patches Drive is LG GCE-8480B 48x/16x48x I can't format disc. # cdrwtool -t 10 -b full -d /dev/scd0 setting speed to 10 full blank using device /dev/scd0 1432KB internal buffer setting write speed to 10x wait_cmd: No medium found Command failed: a1 00 00 00 00 00 00 00 00 00 00 00 - sense 06.29.00 blank disc: Illegal seek I will appreciate any help. Thanks, Ljubo -- Registered Linux User #277235 Registered Machine #205191

1 0

Re: ? help: cdrwtool fails
by Jim Sweet 07 Aug '03

07 Aug '03

Sorry about the last post...mysterious browser problems. Anyway, returning to the thread, I am able to run the command cdrwtool -t 4 -b full -d /dev/hdd without any apparent problems. Subsequently, I find that pktsetup /dev/pktcdvd0 /dev/hdd completes as well, although the following entries appear in /var/log/messages: Aug 7 16:53:40 <hostname> kernel: cdrom: This disc doesn't have any tracks I recognize! Aug 7 16:53:40 <hostname> kernel: pktcdvd: writer hdd sucessfully registered As mentioned before, the command mkudffs /dev/pktcdvd0 fails with the error trying to change type of multiple extents. If I supply a number of blocks, e.g. 295264, then 'mkudffs' /appears/ to work, e.g. # strace -o /tmp/strace.mkudffs mkudffs /dev/pktcdvd0 295264 start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=16, type=PVDS start=273, blocks=1, type=LVID start=274, blocks=294733, type=PSPACE start=295007, blocks=1, type=ANCHOR start=295008, blocks=239, type=USPACE start=295247, blocks=16, type=RVDS start=295263, blocks=1, type=ANCHOR # However, the 'strace' output shows the following: open("/dev/pktcdvd0", O_RDWR|O_CREAT|O_LARGEFILE, 0660) = -1 EIO (Input/output error) which appears to be the following code from udftools-1.0.0b2/mkudffs/main.c : 158 #ifdef HAVE_OPEN64 159 fd = open64(filename, O_RDWR | O_CREAT, 0660); 160 #else 161 fd = open(filename, O_RDWR | O_CREAT | O_LARGEFILE, 0660); 162 #endif Can anyone suggest a reason why the open() should fail? Regards, and thanks for any help, Jim >Although I am still stuck, I have a bit more information. > >>>Try to use mkudffs to write the file system instead: >>> >>> pktsetup /dev/pktcdvd0 /dev/hdd >>> mkudffs /dev/pktcdvd0 >>> >>>I've had problems using cdrwtool to create the file system with some >>>drives, and using mkudffs instead solved those problems. >> >>mkudffs fails with >> >> trying to change type of multiple extents > >I am able to run the command > >cdrwtool -t 4 -b full -d /dev/hdd > > > > >> >>What does that mean? >> >>Thanks again for your time. >> >>Jim >> >>_________________________________________________________________ >>On the move? Get Hotmail on your mobile phone >>http://www.msn.co.uk/msnmobile >> >> >>-- >>To unsubscribe, e-mail: packet-writing-unsubscribe(a)suse.com >>For additional commands, e-mail: packet-writing-help(a)suse.com >> > >_________________________________________________________________ >On the move? Get Hotmail on your mobile phone >http://www.msn.co.uk/msnmobile > > >-- >To unsubscribe, e-mail: packet-writing-unsubscribe(a)suse.com >For additional commands, e-mail: packet-writing-help(a)suse.com > _________________________________________________________________ Use MSN Messenger to send music and pics to your friends http://www.msn.co.uk/messenger

1 0

Re: ? help: cdrwtool fails
by Jim Sweet 07 Aug '03

07 Aug '03

Hi again, Although I am still stuck, I have a bit more information. >>Try to use mkudffs to write the file system instead: >> >> pktsetup /dev/pktcdvd0 /dev/hdd >> mkudffs /dev/pktcdvd0 >> >>I've had problems using cdrwtool to create the file system with some >>drives, and using mkudffs instead solved those problems. > >mkudffs fails with > > trying to change type of multiple extents I am able to run the command cdrwtool -t 4 -b full -d /dev/hdd > >What does that mean? > >Thanks again for your time. > >Jim > >_________________________________________________________________ >On the move? Get Hotmail on your mobile phone >http://www.msn.co.uk/msnmobile > > >-- >To unsubscribe, e-mail: packet-writing-unsubscribe(a)suse.com >For additional commands, e-mail: packet-writing-help(a)suse.com > _________________________________________________________________ On the move? Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile

1 0

Re: ? help: cdrwtool fails
by Jim Sweet 06 Aug '03

06 Aug '03

Thanks for your mail. >It looks like the blanking succeeds, but writing the file system fails. >Try to use mkudffs to write the file system instead: > > pktsetup /dev/pktcdvd0 /dev/hdd > mkudffs /dev/pktcdvd0 > >I've had problems using cdrwtool to create the file system with some >drives, and using mkudffs instead solved those problems. mkudffs fails with trying to change type of multiple extents What does that mean? Thanks again for your time. Jim _________________________________________________________________ On the move? Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile

1 0

? help: cdrwtool fails
by Jim Sweet 06 Aug '03

06 Aug '03

Hi, I have been following Richard Downing's "CD-RW UDF (Packet-CD) filesystem" but I'm stuck: cdrwtool bombs out with the following errors: # strace -o /tmp/trace.cdrwtool ./cdrwtool -d /dev/hdd -q using device /dev/hdd 1328KB internal buffer setting write speed to 12x Settings for /dev/hdd: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/hdd. The disc is going to be blanked and formatted with one big track. All data on the device will be lost!! Press CTRL-C to cancel now. ENTER to continue. Initiating quick disc blank Disc capacity is 295264 blocks (590528KB/576MB) Formatting track start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=31, type=USPACE start=288, blocks=32, type=PVDS start=320, blocks=32, type=LVID start=352, blocks=32, type=STABLE start=384, blocks=1024, type=SSPACE start=1408, blocks=293568, type=PSPACE start=294976, blocks=31, type=USPACE start=295007, blocks=1, type=ANCHOR start=295008, blocks=160, type=USPACE start=295168, blocks=32, type=STABLE start=295200, blocks=32, type=RVDS start=295232, blocks=31, type=USPACE start=295263, blocks=1, type=ANCHOR Writing UDF structures to disc wait_cmd: Input/output error Command failed: 2a 00 00 00 00 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 01 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 01 20 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 01 40 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 01 60 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 05 80 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 05 a0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 05 c0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 05 e0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 00 06 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 04 80 40 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 04 81 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 04 81 20 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 2a 00 00 04 81 40 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: Input/output error Command failed: 35 02 00 00 00 00 00 00 00 00 00 00 - sense 02.04.07 Quick setup complete! can't unlock door I am using RedHat 9 (2.4.20-18) which I patched using pktcd-rh9-2.4.20-18.patch. The burner is an Artec WRR-52Z, which I am using the standard IDE driver --- NOT the fake scsi one. Any comments or advice would be gratefully received. Regards, Jim _________________________________________________________________ Express yourself with cool emoticons - download MSN Messenger today! http://www.msn.co.uk/messenger

3 2