lots of syslog error messages when writing to UDF DVDs
I'm running on an 650MHz Athlon, and the CD-RW drive in question is a generically rebranded Lite-On Combo LTC-48161H (16x DVD/48x read/48x CD-R/24x CD-RW combo drive.) I just compiled kernel 2.6.0, with the packet-writing patch (packet-2.6.1-rc1-2.patch.bz2) on a Debian unstable system. I followed the instructions in the hint file (http://cvs.linuxfromscratch.org/index.cgi/hints/Attic/cdrw-hint.txt?rev=1.3) to get it working, and it's working to an extent. The problem is that when I copy medium-large sized files (a few megabytes, such as an mp3,) the drive just keeps running & running, with the LED lit in amber (meaning it's writing). Running sync to get the drive to finish the job doesn't seem to do anything, and if I umount and remount the CD-RW, some of the files I tried to copy to it are missing. When I run dmesg, I get thousands of these error messages. ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5736 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5744 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 as well as UDF-fs DEBUG fs/udf/super.c:1005:udf_load_partdesc: Partition (0:0 type 1522) starts at physical 1408, block length 273920 UDF-fs DEBUG fs/udf/super.c:1338:udf_load_partition: Using anchor in block 256 UDF-fs DEBUG fs/udf/super.c:1571:udf_fill_super: Lastblock=0 UDF-fs DEBUG fs/udf/super.c:847:udf_find_fileset: Fileset at block=32, partition=0 UDF-fs DEBUG fs/udf/super.c:909:udf_load_fileset: Rootdir at block=64, partition=0 UDF-fs INFO UDF 0.9.7 (2002/11/15) Mounting volume 'LinuxUDF', timestamp 2004/01/13 02:33 (1e5c) UDF-fs DEBUG fs/udf/misc.c:286:udf_read_tagged: location mismatch block 4751, tag 0 != 3343 udf: udf_read_inode(ino 4751) failed !bh UDF-fs DEBUG fs/udf/misc.c:286:udf_read_tagged: location mismatch block 4751, tag 0 != 3343 udf: udf_read_inode(ino 4751) failed !bh UDF-fs DEBUG fs/udf/misc.c:286:udf_read_tagged: location mismatch block 4751, tag 0 != 3343 and Buffer I/O error on device pktcdvd0, logical block 31194 lost page write due to I/O error on pktcdvd0 Buffer I/O error on device pktcdvd0, logical block 31195 lost page write due to I/O error on pktcdvd0 Buffer I/O error on device pktcdvd0, logical block 31196 lost page write due to I/O error on pktcdvd0 Buffer I/O error on device pktcdvd0, logical block 31197 lost page write due to I/O error on pktcdvd0 Buffer I/O error on device pktcdvd0, logical block 31198 lost page write due to I/O error on pktcdvd0 Does anybody here have any ideas on how to get rid of these errors? Doug
On Tue, 13 Jan 2004, Doug Holland wrote:
I'm running on an 650MHz Athlon, and the CD-RW drive in question is a generically rebranded Lite-On Combo LTC-48161H (16x DVD/48x read/48x CD-R/24x CD-RW combo drive.)
I just compiled kernel 2.6.0, with the packet-writing patch (packet-2.6.1-rc1-2.patch.bz2) on a Debian unstable system. I followed the instructions in the hint file (http://cvs.linuxfromscratch.org/index.cgi/hints/Attic/cdrw-hint.txt?rev=1.3) to get it working, and it's working to an extent.
The problem is that when I copy medium-large sized files (a few megabytes, such as an mp3,) the drive just keeps running & running, with the LED lit in amber (meaning it's writing). Running sync to get the drive to finish the job doesn't seem to do anything, and if I umount and remount the CD-RW, some of the files I tried to copy to it are missing.
When I run dmesg, I get thousands of these error messages.
ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5736 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5744 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 ... Does anybody here have any ideas on how to get rid of these errors?
I don't know yet, but I have the same problem on one of my IDE drives (Sony CRX175A). I only have a problem when using native ide support in a 2.6 kernel. In 2.4 the drive works with both native ide and scsi emulation, and it also works with scsi emulation in 2.6. I have another IDE drive (HP 8100) on the same ide channel which works perfectly with native ide in 2.6, so it can't be that packet writing using native ide is completely broken in 2.6. It looks like I/O requests sent from the packet driver to the ide driver get shifted 4 sectors. In the log file below, the requested sectors (the numbers within parenthesis on the pkt_gather_data lines) exactly match the reported read sectors (in pkt_end_io_read), except for the 4 sector offset. I also get an "access beyond end of device" if I try to access the last sector on the disc, so it seems like the offset is added before the actual I/O operation starts. run_state_machine: pkt 5 pkt_gather_data: Adding frame 0 (120500), page:c1098f80 offs:0 pkt_gather_data: Adding frame 1 (120504), page:c1098f80 offs:2048 pkt_gather_data: Adding frame 2 (120508), page:c10940c0 offs:0 pkt_gather_data: Adding frame 3 (12050c), page:c10940c0 offs:2048 pkt_gather_data: Adding frame 4 (120510), page:c1095498 offs:0 pkt_gather_data: Adding frame 5 (120514), page:c1095498 offs:2048 pkt_gather_data: Adding frame 6 (120518), page:c10933c8 offs:0 pkt_gather_data: Adding frame 7 (12051c), page:c10933c8 offs:2048 pkt_gather_data: Adding frame 8 (120520), page:c1095b28 offs:0 pkt_gather_data: Adding frame 9 (120524), page:c1095b28 offs:2048 pkt_gather_data: Adding frame 10 (120528), page:c1095b00 offs:0 pkt_gather_data: Adding frame 11 (12052c), page:c1095b00 offs:2048 pkt_gather_data: Adding frame 12 (120530), page:c1093148 offs:0 pkt_gather_data: Adding frame 13 (120534), page:c1093148 offs:2048 pkt_gather_data: Adding frame 20 (120550), page:c10941d8 offs:0 pkt_gather_data: Adding frame 21 (120554), page:c10941d8 offs:2048 pkt_gather_data: Adding frame 22 (120558), page:c10941b0 offs:0 pkt_gather_data: Adding frame 23 (12055c), page:c10941b0 offs:2048 pkt_gather_data: Adding frame 24 (120560), page:c108e328 offs:0 pkt_gather_data: Adding frame 25 (120564), page:c108e328 offs:2048 pkt_gather_data: Adding frame 26 (120568), page:c108e300 offs:0 pkt_gather_data: Adding frame 27 (12056c), page:c108e300 offs:2048 pkt_gather_data: Adding frame 28 (120570), page:c10958a8 offs:0 pkt_gather_data: Adding frame 29 (120574), page:c10958a8 offs:2048 pkt_gather_data: Adding frame 31 (12057c), page:c1095880 offs:2048 pkt_gather_data: need 25 frames for zone 120500 pkt 5 : s=120500 WAITING -> READ_WAIT ... pkt_gather_data: Adding frame 31 (7c), page:c10929c8 offs:2048 pkt_gather_data: need 29 frames for zone 0 pkt 1 : s= 0 WAITING -> READ_WAIT pkt_end_io_read: bio=c3acd908 sec0=120500 sec=120580 err=-5 kcdrwd: i:0 ow:0 rw:5 ww:0 rec:0 fin:0 kcdrwd: sleeping pkt_end_io_read: bio=c3acdc4c sec0=120500 sec=120554 err=0 pkt_end_io_read: bio=c3acdc00 sec0=120500 sec=120558 err=0 pkt_end_io_read: bio=c3acdbb4 sec0=120500 sec=12055c err=0 pkt_end_io_read: bio=c3acd234 sec0=120500 sec=120560 err=0 pkt_end_io_read: bio=c3acdb1c sec0=120500 sec=120564 err=0 pkt_end_io_read: bio=c3acdad0 sec0=120500 sec=120568 err=0 pkt_end_io_read: bio=c3acda84 sec0=120500 sec=12056c err=0 pkt_end_io_read: bio=c3acdf90 sec0=120500 sec=120570 err=0 pkt_end_io_read: bio=c3acdf44 sec0=120500 sec=120574 err=0 pkt_end_io_read: bio=c3acd9a0 sec0=120500 sec=120578 err=0 pkt_end_io_read: bio=c3acd4e0 sec0=120500 sec=120504 err=0 pkt_end_io_read: bio=c3acd494 sec0=120500 sec=120508 err=0 pkt_end_io_read: bio=c3acd448 sec0=120500 sec=12050c err=0 pkt_end_io_read: bio=c3acd3fc sec0=120500 sec=120510 err=0 pkt_end_io_read: bio=c3acd3b0 sec0=120500 sec=120514 err=0 pkt_end_io_read: bio=c3acd364 sec0=120500 sec=120518 err=0 pkt_end_io_read: bio=c3acd318 sec0=120500 sec=12051c err=0 pkt_end_io_read: bio=c3a9778c sec0=120500 sec=120520 err=0 pkt_end_io_read: bio=c3a97150 sec0=120500 sec=120524 err=0 pkt_end_io_read: bio=c3a97104 sec0=120500 sec=120528 err=0 pkt_end_io_read: bio=c3a97a38 sec0=120500 sec=12052c err=0 pkt_end_io_read: bio=c3a979ec sec0=120500 sec=120530 err=0 pkt_end_io_read: bio=c3a979a0 sec0=120500 sec=120534 err=0 pkt_end_io_read: bio=c3acde60 sec0=120500 sec=120538 err=0 kcdrwd: wake up handle_queue -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
On Tue 13 Jan 2004 11:35 am, Peter Osterlund wrote:
On Tue, 13 Jan 2004, Doug Holland wrote:
I'm running on an 650MHz Athlon, and the CD-RW drive in question is a generically rebranded Lite-On Combo LTC-48161H (16x DVD/48x read/48x CD-R/24x CD-RW combo drive.)
I just compiled kernel 2.6.0, with the packet-writing patch (packet-2.6.1-rc1-2.patch.bz2) on a Debian unstable system. I followed the instructions in the hint file (http://cvs.linuxfromscratch.org/index.cgi/hints/Attic/cdrw-hint.txt?rev= 1.3) to get it working, and it's working to an extent.
The problem is that when I copy medium-large sized files (a few megabytes, such as an mp3,) the drive just keeps running & running, with the LED lit in amber (meaning it's writing). Running sync to get the drive to finish the job doesn't seem to do anything, and if I umount and remount the CD-RW, some of the files I tried to copy to it are missing.
When I run dmesg, I get thousands of these error messages.
ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5736 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5744 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54
....
Does anybody here have any ideas on how to get rid of these errors?
I don't know yet, but I have the same problem on one of my IDE drives (Sony CRX175A). I only have a problem when using native ide support in a 2.6 kernel. In 2.4 the drive works with both native ide and scsi emulation, and it also works with scsi emulation in 2.6.
I have another IDE drive (HP 8100) on the same ide channel which works perfectly with native ide in 2.6, so it can't be that packet writing using native ide is completely broken in 2.6.
It looks like I/O requests sent from the packet driver to the ide driver get shifted 4 sectors. In the log file below, the requested sectors (the numbers within parenthesis on the pkt_gather_data lines) exactly match the reported read sectors (in pkt_end_io_read), except for the 4 sector offset.
I also get an "access beyond end of device" if I try to access the last sector on the disc, so it seems like the offset is added before the actual I/O operation starts.
run_state_machine: pkt 5 pkt_gather_data: Adding frame 0 (120500), page:c1098f80 offs:0 pkt_gather_data: Adding frame 1 (120504), page:c1098f80 offs:2048 ... -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
Weird. I'm gonna try again using my older HP 9100, see if it behaves a little better. I would really like to avoid turning on SCSI emulation - it's always been a pain for me to set up, and my drives otherwise work fine without it. Thanks for the help, Doug
On Tue 13 Jan 2004 1:31 pm, Doug Holland wrote:
On Tue 13 Jan 2004 11:35 am, Peter Osterlund wrote:
I don't know yet, but I have the same problem on one of my IDE drives (Sony CRX175A). I only have a problem when using native ide support in a 2.6 kernel. In 2.4 the drive works with both native ide and scsi emulation, and it also works with scsi emulation in 2.6.
I have another IDE drive (HP 8100) on the same ide channel which works perfectly with native ide in 2.6, so it can't be that packet writing using native ide is completely broken in 2.6.
It looks like I/O requests sent from the packet driver to the ide driver get shifted 4 sectors. In the log file below, the requested sectors (the numbers within parenthesis on the pkt_gather_data lines) exactly match the reported read sectors (in pkt_end_io_read), except for the 4 sector offset.
I also get an "access beyond end of device" if I try to access the last sector on the disc, so it seems like the offset is added before the actual I/O operation starts.
run_state_machine: pkt 5 pkt_gather_data: Adding frame 0 (120500), page:c1098f80 offs:0 pkt_gather_data: Adding frame 1 (120504), page:c1098f80 offs:2048
...
-- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
Weird. I'm gonna try again using my older HP 9100, see if it behaves a little better.
I would really like to avoid turning on SCSI emulation - it's always been a pain for me to set up, and my drives otherwise work fine without it.
Thanks for the help,
Doug
I just tried again with the HP 9100, got the same errors. Another strange behavior... After I copy some files to the disk, after I umount and remount it, and do an ls -al, I get the following: $ ls -l /cdrw ls: /cdrw/climbatize.mp3: Permission denied ls: /cdrw/smack_my_bitch_up.mp3: Permission denied total 51710 -rw------- 1 root root 6706539 Jan 13 13:50 breathe.mp3 -rw------- 1 root root 5144939 Jan 13 13:50 diesel_power.mp3 -rw------- 1 root root 5617755 Jan 13 13:50 firestarter.mp3 -rw------- 1 root root 5182033 Jan 13 13:50 fuel_my_fire.mp3 -rw------- 1 root root 6330898 Jan 13 13:50 funky_shit.mp3 drwxr-xr-x 2 root root 40 Jan 13 12:28 lost+found -rw------- 1 root root 6808416 Jan 13 13:50 mindfields.mp3 -rw------- 1 root root 10921135 Jan 13 13:50 narayan.mp3 -rw------- 1 root root 6228498 Jan 13 13:50 serial_thrilla.mp3 I guess those two files got mangled.
On Tue, 13 Jan 2004, Doug Holland wrote:
On Tue 13 Jan 2004 1:31 pm, Doug Holland wrote:
On Tue 13 Jan 2004 11:35 am, Peter Osterlund wrote:
I don't know yet, but I have the same problem on one of my IDE drives (Sony CRX175A). I only have a problem when using native ide support in a 2.6 kernel. In 2.4 the drive works with both native ide and scsi emulation, and it also works with scsi emulation in 2.6.
I have another IDE drive (HP 8100) on the same ide channel which works perfectly with native ide in 2.6, so it can't be that packet writing using native ide is completely broken in 2.6.
It looks like I/O requests sent from the packet driver to the ide driver get shifted 4 sectors. In the log file below, the requested sectors (the numbers within parenthesis on the pkt_gather_data lines) exactly match the reported read sectors (in pkt_end_io_read), except for the 4 sector offset.
This was probably a false alarm. I get the same shift also for cases that work.
I also get an "access beyond end of device" if I try to access the last sector on the disc, so it seems like the offset is added before the actual I/O operation starts.
Or maybe not. The Sony drive reports: pktcdvd: 65534kB available on disc and the HP drive reports (for the same disc): pktcdvd: 65536kB available on disc They report the same values whether I use scsi emulation or native ide, but only in the ide case do I get the "access beyond end of device" errors. However, this is not the only problem, because if I try to create a smaller filesystem that doesn't go anywhere near the last sector, I still get the reported IDE errors.
I would really like to avoid turning on SCSI emulation - it's always been a pain for me to set up, and my drives otherwise work fine without it.
Agreed, it should work without scsi emulation. I'm working on it...
Another strange behavior... After I copy some files to the disk, after I umount and remount it, and do an ls -al, I get the following:
$ ls -l /cdrw ls: /cdrw/climbatize.mp3: Permission denied ls: /cdrw/smack_my_bitch_up.mp3: Permission denied ...
Not that strange. If the block device driver doesn't work correctly, any filesystem you try to put on top of it can develop all sorts of funny filesystem errors. -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
On Tue, 13 Jan 2004, Peter Osterlund wrote:
On Tue, 13 Jan 2004, Doug Holland wrote:
When I run dmesg, I get thousands of these error messages.
ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5736 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5744 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 ... Does anybody here have any ideas on how to get rid of these errors?
I don't know yet, but I have the same problem on one of my IDE drives (Sony CRX175A). I only have a problem when using native ide support in a 2.6 kernel. In 2.4 the drive works with both native ide and scsi emulation, and it also works with scsi emulation in 2.6.
I have another IDE drive (HP 8100) on the same ide channel which works perfectly with native ide in 2.6, so it can't be that packet writing using native ide is completely broken in 2.6.
I've found that the errors are caused by the seek commands generated by ide-cd. Increasing IDECD_SEEK_THRESHOLD to a very large value works for me (see patch below). With the standard threshold I get: ... cdrom_transfer_packet_command: 28 00 00 04 33 80 00 00 1e 00 00 00 cdrom_transfer_packet_command: 2b 00 00 00 01 27 00 00 00 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 01 27 00 00 19 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 01 07 00 00 0a 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 00 13 00 00 0d 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 00 00 00 00 10 00 00 00 cdrom_transfer_packet_command: 2a 00 00 00 00 00 00 00 20 00 00 00 cdrom_transfer_packet_command: 2b 00 00 00 01 00 00 00 00 00 00 00 ide-cd: media marked write protected hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 1024 cdrom_transfer_packet_command: 03 00 00 00 12 00 00 00 00 00 00 00 end_request: I/O error, dev hdc, sector 1032 ... With a bigger threshold, I could successfully write >100MB to a CDRW. Does anyone know what the seek commands are good for? --- linux/drivers/ide/ide-cd.c.old 2004-03-23 00:08:39.000000000 +0100 +++ linux/drivers/ide/ide-cd.c 2004-03-23 00:03:20.000000000 +0100 @@ -915,6 +915,7 @@ int cmd_len; struct cdrom_info *info = drive->driver_data; ide_startstop_t startstop; + int i; if (CDROM_CONFIG_FLAGS(drive)->drq_interrupt) { /* Here we should have been called after receiving an interrupt @@ -939,6 +940,10 @@ cmd_len = ATAPI_MIN_CDB_BYTES; /* Send the command to the device. */ + printk("cdrom_transfer_packet_command:"); + for (i = 0; i < cmd_len; i++) + printk(" %02x", rq->cmd[i]); + printk("\n"); HWIF(drive)->atapi_output_bytes(drive, rq->cmd, cmd_len); /* Start the DMA if need be */ @@ -1267,7 +1272,7 @@ } -#define IDECD_SEEK_THRESHOLD (1000) /* 1000 blocks */ +#define IDECD_SEEK_THRESHOLD (10000000) /* 1000 blocks */ #define IDECD_SEEK_TIMER (5 * WAIT_MIN_SLEEP) /* 100 ms */ #define IDECD_SEEK_TIMEOUT (2 * WAIT_CMD) /* 20 sec */ -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
Dear Peter,
I has almost the same problem, when try to format a disk:
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54
but my kernel version is 2.4.23, and with a CD writer: CD-W224EA, ATAPI CD/DVD-ROM drive.
Could you please see my previous post: Packet writing: cdrwtool -d /dev/hdc -q failed? Although some warm-hearted person give me some hints, I still can not work it out.
I have been tortured by it these days and really hope to get help from you.
Thank you in advance.
Best Regards,
kurt
Peter Osterlund
On Tue, 13 Jan 2004, Doug Holland wrote:
When I run dmesg, I get thousands of these error messages.
ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5736 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 5744 ide-cd: write_intr decode_status bad hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 ... Does anybody here have any ideas on how to get rid of these errors?
I don't know yet, but I have the same problem on one of my IDE drives (Sony CRX175A). I only have a problem when using native ide support in a 2.6 kernel. In 2.4 the drive works with both native ide and scsi emulation, and it also works with scsi emulation in 2.6.
I have another IDE drive (HP 8100) on the same ide channel which works perfectly with native ide in 2.6, so it can't be that packet writing using native ide is completely broken in 2.6.
I've found that the errors are caused by the seek commands generated by ide-cd. Increasing IDECD_SEEK_THRESHOLD to a very large value works for me (see patch below). With the standard threshold I get: ... cdrom_transfer_packet_command: 28 00 00 04 33 80 00 00 1e 00 00 00 cdrom_transfer_packet_command: 2b 00 00 00 01 27 00 00 00 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 01 27 00 00 19 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 01 07 00 00 0a 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 00 13 00 00 0d 00 00 00 cdrom_transfer_packet_command: 28 00 00 00 00 00 00 00 10 00 00 00 cdrom_transfer_packet_command: 2a 00 00 00 00 00 00 00 20 00 00 00 cdrom_transfer_packet_command: 2b 00 00 00 01 00 00 00 00 00 00 00 ide-cd: media marked write protected hdc: command error: status=0x51 { DriveReady SeekComplete Error } hdc: command error: error=0x54 end_request: I/O error, dev hdc, sector 1024 cdrom_transfer_packet_command: 03 00 00 00 12 00 00 00 00 00 00 00 end_request: I/O error, dev hdc, sector 1032 ... With a bigger threshold, I could successfully write >100MB to a CDRW. Does anyone know what the seek commands are good for? --- linux/drivers/ide/ide-cd.c.old 2004-03-23 00:08:39.000000000 +0100 +++ linux/drivers/ide/ide-cd.c 2004-03-23 00:03:20.000000000 +0100 @@ -915,6 +915,7 @@ int cmd_len; struct cdrom_info *info = drive->driver_data; ide_startstop_t startstop; + int i; if (CDROM_CONFIG_FLAGS(drive)->drq_interrupt) { /* Here we should have been called after receiving an interrupt @@ -939,6 +940,10 @@ cmd_len = ATAPI_MIN_CDB_BYTES; /* Send the command to the device. */ + printk("cdrom_transfer_packet_command:"); + for (i = 0; i < cmd_len; i++) + printk(" %02x", rq->cmd[i]); + printk("\n"); HWIF(drive)->atapi_output_bytes(drive, rq->cmd, cmd_len); /* Start the DMA if need be */ @@ -1267,7 +1272,7 @@ } -#define IDECD_SEEK_THRESHOLD (1000) /* 1000 blocks */ +#define IDECD_SEEK_THRESHOLD (10000000) /* 1000 blocks */ #define IDECD_SEEK_TIMER (5 * WAIT_MIN_SLEEP) /* 100 ms */ #define IDECD_SEEK_TIMEOUT (2 * WAIT_CMD) /* 20 sec */ -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340 -- To unsubscribe, e-mail: packet-writing-unsubscribe@suse.com For additional commands, e-mail: packet-writing-help@suse.com Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time.
On Wed, 24 Mar 2004, ke chen wrote:
Dear Peter,
I has almost the same problem, when try to format a disk: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } hdc: packet command error: error=0x54
but my kernel version is 2.4.23, and with a CD writer: CD-W224EA, ATAPI CD/DVD-ROM drive.
Could you please see my previous post: Packet writing: cdrwtool -d /dev/hdc -q failed?
Maybe disabling the seek commands fixes this problem too. Please test this patch. --- linux/drivers/ide/ide-cd.c.orig 2004-03-24 23:48:47.000000000 +0100 +++ linux/drivers/ide/ide-cd.c 2004-03-24 23:47:58.000000000 +0100 @@ -913,6 +913,7 @@ unsigned int timeout = pc->timeout; struct cdrom_info *info = drive->driver_data; ide_startstop_t startstop; + int i; if (CDROM_CONFIG_FLAGS(drive)->drq_interrupt) { /* Here we should have been called after receiving an interrupt @@ -933,6 +934,10 @@ ide_set_handler(drive, handler, timeout, cdrom_timer_expiry); /* Send the command to the device. */ + printk("cdrom_transfer_packet_command:"); + for (i = 0; i < cmd_len; i++) + printk(" %02x", cmd_buf[i]); + printk("\n"); HWIF(drive)->atapi_output_bytes(drive, cmd_buf, cmd_len); /* Start the DMA if need be */ @@ -1283,7 +1288,7 @@ } -#define IDECD_SEEK_THRESHOLD (1000) /* 1000 blocks */ +#define IDECD_SEEK_THRESHOLD (10000000) /* 1000 blocks */ #define IDECD_SEEK_TIMER (5 * WAIT_MIN_SLEEP) /* 100 ms */ #define IDECD_SEEK_TIMEOUT WAIT_CMD /* 10 sec */ -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
hi Peter,
There is still some problems. Error messages are listed as followllings:
cdrwtool -d /dev/hdc -q -t 4
using device /dev/hdc
setting speed to 4
1458KB internal buffer
setting write speed to 4x
Settings for /dev/hdc:
Fixed packets, size 32
Mode-2 disc
I'm going to do a quick setup of /dev/hdc. 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
wait_cmd: Input/output error
Command failed: 04 17 00 00 00 00 00 00 00 00 00 00 - sense 05.26.00
format disc: Input/output error
tail -f /var/log/messages
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 25 08:35:06 localhost last message repeated 2 times
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 1e 00 00 00 01 00 00 00 00 00 00 00
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 5c 00 00 00 00 00 00 00 0c 00 00 00
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 5a 00 05 00 00 00 00 00 10 00 00 00
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 5a 00 05 00 00 00 00 00 3c 00 00 00
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: bb 00 ff ff 02 c0 00 00 00 00 00 00
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 5a 00 85 00 00 00 00 00 10 00 00 00
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 5a 00 85 00 00 00 00 00 3c 00 00 00
Mar 25 08:35:06 localhost kernel: cdrom_transfer_packet_command: 55 10 00 00 00 00 00 00 3c 00 00 00
Mar 25 08:35:30 localhost kernel: cdrom_transfer_packet_command: a1 01 00 00 00 00 00 00 00 00 00 00
Mar 25 08:35:30 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 02 00 00 00
Mar 25 08:35:30 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 22 00 00 00
Mar 25 08:35:30 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 1c 00 00 00
Mar 25 08:35:30 localhost kernel: cdrom_transfer_packet_command: 04 17 00 00 00 00 00 00 00 00 00 00
Mar 25 08:35:30 localhost kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
Mar 25 08:35:30 localhost kernel: hdc: packet command error: error=0x54
Mar 25 08:35:30 localhost kernel: cdrom_transfer_packet_command: 03 00 00 00 12 00 00 00 00 00 00 00
Mar 25 08:35:30 localhost kernel: ATAPI device hdc:
Mar 25 08:35:30 localhost kernel: Error: Illegal request -- (Sense key=0x05)
Mar 25 08:35:30 localhost kernel: Invalid field in parameter list -- (asc=0x26, ascq=0x00)
Mar 25 08:35:30 localhost kernel: The failed "Format Unit" packet command was:
Mar 25 08:35:30 localhost kernel: "04 17 00 00 00 00 00 00 00 00 00 00 "
Mar 25 08:35:30 localhost kernel: cdrom_transfer_packet_command: 1e 00 00 00 00 00 00 00 00 00 00 00
Thank you very much
BR,
kurt
Peter Osterlund
Dear Peter,
I has almost the same problem, when try to format a disk: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } hdc: packet command error: error=0x54
but my kernel version is 2.4.23, and with a CD writer: CD-W224EA, ATAPI CD/DVD-ROM drive.
Could you please see my previous post: Packet writing: cdrwtool -d /dev/hdc -q failed?
Maybe disabling the seek commands fixes this problem too. Please test this patch. --- linux/drivers/ide/ide-cd.c.orig 2004-03-24 23:48:47.000000000 +0100 +++ linux/drivers/ide/ide-cd.c 2004-03-24 23:47:58.000000000 +0100 @@ -913,6 +913,7 @@ unsigned int timeout = pc->timeout; struct cdrom_info *info = drive->driver_data; ide_startstop_t startstop; + int i; if (CDROM_CONFIG_FLAGS(drive)->drq_interrupt) { /* Here we should have been called after receiving an interrupt @@ -933,6 +934,10 @@ ide_set_handler(drive, handler, timeout, cdrom_timer_expiry); /* Send the command to the device. */ + printk("cdrom_transfer_packet_command:"); + for (i = 0; i < cmd_len; i++) + printk(" %02x", cmd_buf[i]); + printk("\n"); HWIF(drive)->atapi_output_bytes(drive, cmd_buf, cmd_len); /* Start the DMA if need be */ @@ -1283,7 +1288,7 @@ } -#define IDECD_SEEK_THRESHOLD (1000) /* 1000 blocks */ +#define IDECD_SEEK_THRESHOLD (10000000) /* 1000 blocks */ #define IDECD_SEEK_TIMER (5 * WAIT_MIN_SLEEP) /* 100 ms */ #define IDECD_SEEK_TIMEOUT WAIT_CMD /* 10 sec */ -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340 -- To unsubscribe, e-mail: packet-writing-unsubscribe@suse.com For additional commands, e-mail: packet-writing-help@suse.com --------------------------------- Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time.
On Thu, 25 Mar 2004, ke chen wrote:
There is still some problems. Error messages are listed as followllings:
cdrwtool -d /dev/hdc -q -t 4 using device /dev/hdc setting speed to 4 1458KB internal buffer setting write speed to 4x Settings for /dev/hdc: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/hdc. 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 wait_cmd: Input/output error Command failed: 04 17 00 00 00 00 00 00 00 00 00 00 - sense 05.26.00 format disc: Input/output error
The problem is that the drive complains that the format command contains invalid parameters. My patch is unrelated to this problem so it will not make any difference. I don't know why it fails. Does it work if you try to format a smaller part of the disc? (cdrwtool -d /dev/hdc -m 1024). Does packet writing work if you use a disc that has been formatted in another OS? -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
Hi Peter,
I think you offered patch is working somehow. If you see my previous posts, Joao has already suggested me to format it with less space. But at that time, it still produced the same errors. After gettting your patch, i can got through "/usr/bin/cdrwtool -d /dev/hdc -m 295232", but "cdrwtool -d /dev/hdc -q" still doesn't work.
Now there exsists other problems, when I tried to mount the packet device "mount /dev/pktcdvd0 /mnt/cdrom -t udf -o rw", it says "mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd0 or too many mounted file systems"
In /var/log/messages, it says
"UDF-fs: No partition found (1)"
Please see the detailed messages on /var/log/messages:
Mar 29 08:03:13 localhost kernel: pktcdvd: writer hdc sucessfully registered
Mar 29 08:03:13 localhost kernel: cdrom_transfer_packet_command: 1e 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:03:13 localhost kernel: cdrom_transfer_packet_command: 35 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:03:13 localhost kernel: cdrom_transfer_packet_command: bb 00 ff ff ff ff 00 00 00 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 1e 00 00 00 01 00 00 00 00 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 02 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 22 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 08 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 1c 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 02 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 22 00 00 00
Mar 29 08:03:56 localhost kernel: pktcdvd: inserted media is CD-RW
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 08 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 1c 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 5a 00 05 00 00 00 00 00 34 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 5a 00 05 00 00 00 00 00 3c 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 55 10 00 00 00 00 00 00 3c 00 00 00
Mar 29 08:03:56 localhost kernel: pktcdvd: Fixed packets, 32 blocks, Mode-2 disc
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 5a 00 08 00 00 00 00 00 0c 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 55 10 00 00 00 00 00 00 14 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 5a 00 2a 00 00 00 00 01 12 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 5a 00 2a 00 00 00 00 00 22 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 43 02 04 00 00 00 00 00 02 00 00 00
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 43 02 04 00 00 00 00 00 1c 00 00 00
Mar 29 08:03:56 localhost kernel: pktcdvd: Max. media speed: 10
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: bb 00 0a 5f 06 ea 00 00 00 00 00 00
Mar 29 08:03:56 localhost kernel: pktcdvd: speed (R/W) 15/10
Mar 29 08:03:56 localhost kernel: cdrom_transfer_packet_command: 54 01 00 00 00 00 00 00 00 00 00 00
Mar 29 08:04:32 localhost kernel: pktcdvd: 590464kB available on disc
Mar 29 08:04:32 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:04:32 localhost kernel: cdrom_transfer_packet_command: 28 00 00 00 00 10 00 00 01 00 00 00
Mar 29 08:04:32 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 02 00 00 00
Mar 29 08:04:32 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 22 00 00 00
Mar 29 08:04:32 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 08 00 00 00
Mar 29 08:04:32 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 1c 00 00 00
Mar 29 08:04:32 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 81 3f 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 80 3f 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 80 07 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 81 3d 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 80 3d 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 80 05 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 80 a9 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 7f a9 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 7f 71 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 80 a7 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 7f a7 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 04 7f 6f 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b2 41 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b1 41 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b1 09 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b2 3f 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b1 3f 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b1 07 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b1 ab 00 00 01 00 00 00
Mar 29 08:04:33 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b0 ab 00 00 01 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b0 73 00 00 01 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b1 a9 00 00 01 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b0 a9 00 00 01 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 28 00 00 03 b0 71 00 00 01 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 28 00 00 00 01 38 00 00 01 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 28 00 00 00 01 00 00 00 01 00 00 00
Mar 29 08:04:34 localhost kernel: UDF-fs: No partition found (1)
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 35 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: bb 00 ff ff ff ff 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 1e 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 1e 00 00 00 01 00 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 00 00 00 00 00 00 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 02 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 51 00 00 00 00 00 00 00 22 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 08 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 52 01 00 00 00 01 00 00 1c 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: bb 00 ff ff ff ff 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: bb 00 ff ff ff ff 00 00 00 00 00 00
Mar 29 08:04:34 localhost kernel: cdrom_transfer_packet_command: 1e 00 00 00 00 00 00 00 00 00 00 00
Thank you very much.
BR,
kurt
Peter Osterlund
There is still some problems. Error messages are listed as followllings:
cdrwtool -d /dev/hdc -q -t 4 using device /dev/hdc setting speed to 4 1458KB internal buffer setting write speed to 4x Settings for /dev/hdc: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/hdc. 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 wait_cmd: Input/output error Command failed: 04 17 00 00 00 00 00 00 00 00 00 00 - sense 05.26.00 format disc: Input/output error
The problem is that the drive complains that the format command contains invalid parameters. My patch is unrelated to this problem so it will not make any difference. I don't know why it fails. Does it work if you try to format a smaller part of the disc? (cdrwtool -d /dev/hdc -m 1024). Does packet writing work if you use a disc that has been formatted in another OS? -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340 -- To unsubscribe, e-mail: packet-writing-unsubscribe@suse.com For additional commands, e-mail: packet-writing-help@suse.com --------------------------------- Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time.
On Mon, 29 Mar 2004, ke chen wrote:
I think you offered patch is working somehow. If you see my previous posts, Joao has already suggested me to format it with less space. But at that time, it still produced the same errors. After gettting your patch, i can got through "/usr/bin/cdrwtool -d /dev/hdc -m 295232", but "cdrwtool -d /dev/hdc -q" still doesn't work.
I don't see how my patch can make any difference, except for changing timing because of the excessive amount of debug messages.
Now there exsists other problems, when I tried to mount the packet device "mount /dev/pktcdvd0 /mnt/cdrom -t udf -o rw", it says "mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd0 or too many mounted file systems"
cdrwtool -m only formats the disc, which is not the same as putting a filesystem on the disc. If you run mkudffs /dev/pktcdvd0 can you then mount the disc? -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340
hi, Peter,
it works! thank you very much.
"cdrwtool -d /dev/hdc -m 295232"
"pktsetup /dev/pktcdvd0 /dev/hdc"
"mkudffs /dev/pktcdvd0"
"mount /dev/pktcdvd0 /mnt/cdrom -t udf"
But i must format the disc with a big amount, if i just specified "cdrwtool -d /dev/hdc -m 1024", it still failed when mounting the disc. One more question is that why I need to run mkusffs command in my case, and it is not a must for other cases.
Thank you again.
BR,
kurt
Peter Osterlund
I think you offered patch is working somehow. If you see my previous posts, Joao has already suggested me to format it with less space. But at that time, it still produced the same errors. After gettting your patch, i can got through "/usr/bin/cdrwtool -d /dev/hdc -m 295232", but "cdrwtool -d /dev/hdc -q" still doesn't work.
I don't see how my patch can make any difference, except for changing timing because of the excessive amount of debug messages.
Now there exsists other problems, when I tried to mount the packet device "mount /dev/pktcdvd0 /mnt/cdrom -t udf -o rw", it says "mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd0 or too many mounted file systems"
cdrwtool -m only formats the disc, which is not the same as putting a filesystem on the disc. If you run mkudffs /dev/pktcdvd0 can you then mount the disc? -- Peter Osterlund - petero2@telia.com http://w1.894.telia.com/~u89404340 --------------------------------- Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time.
participants (3)
-
Doug Holland -
ke chen -
Peter Osterlund