CD Writer Trouble
Hi All, I am having trouble with a CD writer, a Yamaha CRW2100S SCSI. Trying to write with this CD writer using cdrdao always aborts with an error at what appears to be the same location on the disk each time (07:52, somewhere in track 6 IIRC) . It does this whether in real write mode or in simulate mode. Trying to write with this CD writer using cdrecord always aborts with an error between track 1 and track 2. I have only tried this in simulate mode. So, the first thing I'd like to know is if people think this is hardware problem, or a compatibility problem between the drivers and the CDR unit? The only driver for cdrdao that seems to do anything useful with this CDR is the mmc-raw driver. When the problem occurs the following output is produced; Starting: cdrdao simulate --remote 7 -v0 --device 1,0,0 --driver generic-mmc-raw:0x0 --buffers 30 /tmp/tocvmhD6b ?: Input/output error. : scsi sendcmd: no error CDB: 2A 00 00 00 8A BC 00 00 1A 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 06 00 00 00 00 0A 00 00 00 00 29 00 00 00 Sense Key: 0x6 Unit Attention, Segment 0 Sense Code: 0x29 Qual 0x00 (power on, reset, or bus device reset occurred) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 2.879s timeout 20s ERROR: Write data failed. ERROR: Writing failed - buffer under run? ERROR: Simulation failed. And dmesg reports: sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray VFS: Disk change detected on device sr(11,0) ncr53c810-0:0: ERROR (20:0) (8-28-0) (7/13) @ (script e7c:180008a0). ncr53c810-0: script cmd = 88080000 ncr53c810-0: regdump: da 10 80 13 47 07 00 1f 80 08 80 28 00 00 00 00. ncr53c810-0: have to clear fifos. ncr53c810-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 7) For cdrecord, cdrecord seems to pick the mmc driver. The error message I get know from it is: cdrecord: Input/output error. read track info: scsi sendcmd: no error CDB: 52 01 00 00 00 FF 00 00 1C 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 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.000s timeout 240s Steve.
On Wed, 21 Nov 2001, Steve Fosdick wrote:
Hi All,
I am having trouble with a CD writer, a Yamaha CRW2100S SCSI.
Hi Steve, I have an identical Yamaha CRW2100S writer connected to a Tekram DC390U SCSI card which works perfectly.
So, the first thing I'd like to know is if people think this is hardware problem, or a compatibility problem between the drivers and the CDR unit?
And dmesg reports:
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray VFS: Disk change detected on device sr(11,0) ncr53c810-0:0: ERROR (20:0) (8-28-0) (7/13) @ (script e7c:180008a0). ncr53c810-0: script cmd = 88080000 ncr53c810-0: regdump: da 10 80 13 47 07 00 1f 80 08 80 28 00 00 00 00. ncr53c810-0: have to clear fifos. ncr53c810-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 7)
For cdrecord, cdrecord seems to pick the mmc driver. The error message I get know from it is:
cdrecord: Input/output error. read track info: scsi sendcmd: no error CDB: 52 01 00 00 00 FF 00 00 1C 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 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.000s timeout 240s
Have you tryed using the sym53c8xx kernel module instead of the ncr53c8xx. This is an updated driver, your old one may be having problems controling your new writer. Here is my DMESG output sym53c8xx: at PCI bus 0, device 9, function 0 sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up) sym53c8xx: 53c1010-33 detected with Symbios NVRAM PCI: Found IRQ 11 for device 00:09.1 PCI: Sharing IRQ 11 with 00:09.0 PCI: Sharing IRQ 11 with 00:0d.0 sym53c8xx: at PCI bus 0, device 9, function 1 sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up) sym53c8xx: 53c1010-33 detected with Symbios NVRAM sym53c1010-33-0: rev 0x1 on pci bus 0 device 9 function 0 irq 11 sym53c1010-33-0: Symbios format NVRAM, ID 7, Fast-80, Parity Checking sym53c1010-33-0: on-chip RAM at 0xd8000000 sym53c1010-33-0: restart (scsi reset). sym53c1010-33-0: handling phase mismatch from SCRIPTS. sym53c1010-33-0: Downloading SCSI SCRIPTS. sym53c1010-33-1: rev 0x1 on pci bus 0 device 9 function 1 irq 11 sym53c1010-33-1: Symbios format NVRAM, ID 7, Fast-80, Parity Checking sym53c1010-33-1: on-chip RAM at 0xd8002000 sym53c1010-33-1: restart (scsi reset). sym53c1010-33-1: handling phase mismatch from SCRIPTS. sym53c1010-33-1: Downloading SCSI SCRIPTS. scsi0 : sym53c8xx-1.7.3c-20010512 scsi1 : sym53c8xx-1.7.3c-20010512 Vendor: SEAGATE Model: ST19171W Rev: 6004 Type: Direct-Access ANSI SCSI revision: 02 Vendor: SEAGATE Model: ST19171W Rev: 6004 Type: Direct-Access ANSI SCSI revision: 02 sym53c1010-33-0-<0,0>: tagged command queue depth set to 4 sym53c1010-33-0-<1,0>: tagged command queue depth set to 4 Vendor: YAMAHA Model: CRW2100S Rev: 1.0H Type: CD-ROM ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 sym53c1010-33-0-<0,*>: FAST-20 WIDE SCSI 40.0 MB/s (50.0 ns, offset 15) SCSI device sda: 17854230 512-byte hdwr sectors (9141 MB) sda: sda1 sym53c1010-33-0-<1,*>: FAST-20 WIDE SCSI 40.0 MB/s (50.0 ns, offset 15) SCSI device sdb: 17854230 512-byte hdwr sectors (9141 MB) sdb: sdb1 Attached scsi CD-ROM sr0 at scsi1, channel 0, id 3, lun 0 sym53c1010-33-1-<3,*>: FAST-20 SCSI 20.0 MB/s (50.0 ns, offset 7) sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray As you can see, my SCSI card reports the writer as a FAST-20 SCSI 20.0MB/s device, whereas you'rs is reporting it as a 10Mb device. Cdrecord uses the MMC driver with no problems. Hope that helps Chris -- Chris *************************************************************************** E Mail Chris@glovercc.clara.co.uk WWW http://www.glovercc.clara.co.uk ICQ 18054759 Someday, we'll look back on this, laugh nervously and change the subject. -Anon
I don't know how old your CDR is but some older drives have problems with the newer media. A firmware upgrade normaly fixes this. Mike On Wed, 2001-11-21 at 10:20, Chris Glover wrote:
On Wed, 21 Nov 2001, Steve Fosdick wrote:
Hi All,
I am having trouble with a CD writer, a Yamaha CRW2100S SCSI.
Hi Steve,
I have an identical Yamaha CRW2100S writer connected to a Tekram DC390U SCSI card which works perfectly.
So, the first thing I'd like to know is if people think this is hardware problem, or a compatibility problem between the drivers and the CDR unit?
And dmesg reports:
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray VFS: Disk change detected on device sr(11,0) ncr53c810-0:0: ERROR (20:0) (8-28-0) (7/13) @ (script e7c:180008a0). ncr53c810-0: script cmd = 88080000 ncr53c810-0: regdump: da 10 80 13 47 07 00 1f 80 08 80 28 00 00 00 00. ncr53c810-0: have to clear fifos. ncr53c810-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 7)
For cdrecord, cdrecord seems to pick the mmc driver. The error message I get know from it is:
cdrecord: Input/output error. read track info: scsi sendcmd: no error CDB: 52 01 00 00 00 FF 00 00 1C 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 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.000s timeout 240s
Have you tryed using the sym53c8xx kernel module instead of the ncr53c8xx. This is an updated driver, your old one may be having problems controling your new writer.
Here is my DMESG output
sym53c8xx: at PCI bus 0, device 9, function 0 sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up) sym53c8xx: 53c1010-33 detected with Symbios NVRAM PCI: Found IRQ 11 for device 00:09.1 PCI: Sharing IRQ 11 with 00:09.0 PCI: Sharing IRQ 11 with 00:0d.0 sym53c8xx: at PCI bus 0, device 9, function 1 sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up) sym53c8xx: 53c1010-33 detected with Symbios NVRAM sym53c1010-33-0: rev 0x1 on pci bus 0 device 9 function 0 irq 11 sym53c1010-33-0: Symbios format NVRAM, ID 7, Fast-80, Parity Checking sym53c1010-33-0: on-chip RAM at 0xd8000000 sym53c1010-33-0: restart (scsi reset). sym53c1010-33-0: handling phase mismatch from SCRIPTS. sym53c1010-33-0: Downloading SCSI SCRIPTS. sym53c1010-33-1: rev 0x1 on pci bus 0 device 9 function 1 irq 11 sym53c1010-33-1: Symbios format NVRAM, ID 7, Fast-80, Parity Checking sym53c1010-33-1: on-chip RAM at 0xd8002000 sym53c1010-33-1: restart (scsi reset). sym53c1010-33-1: handling phase mismatch from SCRIPTS. sym53c1010-33-1: Downloading SCSI SCRIPTS. scsi0 : sym53c8xx-1.7.3c-20010512 scsi1 : sym53c8xx-1.7.3c-20010512 Vendor: SEAGATE Model: ST19171W Rev: 6004 Type: Direct-Access ANSI SCSI revision: 02 Vendor: SEAGATE Model: ST19171W Rev: 6004 Type: Direct-Access ANSI SCSI revision: 02 sym53c1010-33-0-<0,0>: tagged command queue depth set to 4 sym53c1010-33-0-<1,0>: tagged command queue depth set to 4 Vendor: YAMAHA Model: CRW2100S Rev: 1.0H Type: CD-ROM ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 sym53c1010-33-0-<0,*>: FAST-20 WIDE SCSI 40.0 MB/s (50.0 ns, offset 15) SCSI device sda: 17854230 512-byte hdwr sectors (9141 MB) sda: sda1 sym53c1010-33-0-<1,*>: FAST-20 WIDE SCSI 40.0 MB/s (50.0 ns, offset 15) SCSI device sdb: 17854230 512-byte hdwr sectors (9141 MB) sdb: sdb1 Attached scsi CD-ROM sr0 at scsi1, channel 0, id 3, lun 0 sym53c1010-33-1-<3,*>: FAST-20 SCSI 20.0 MB/s (50.0 ns, offset 7) sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
As you can see, my SCSI card reports the writer as a FAST-20 SCSI 20.0MB/s device, whereas you'rs is reporting it as a 10Mb device.
Cdrecord uses the MMC driver with no problems.
Hope that helps
Chris
-- Chris *************************************************************************** E Mail Chris@glovercc.clara.co.uk WWW http://www.glovercc.clara.co.uk ICQ 18054759 Someday, we'll look back on this, laugh nervously and change the subject. -Anon
_______________________________________________ main@lists.alug.org.uk http://www.anglian.lug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Wed, 21 Nov 2001 10:20:40 Chris Glover wrote:
Have you tryed using the sym53c8xx kernel module instead of the ncr53c8xx. This is an updated driver, your old one may be having problems controling your new writer.
Thanks Chris. I seem to remember using the sym53c8xx driver in the past, but when I try to load it now I get: /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: init_module: No such deviceHint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: insmod /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o failed /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: insmod sym53c8xx failed From 'cat /proc/pci' I get: Bus 0, device 11, function 0: Non-VGA unclassified device: LSI Logic / Symbios Logic (formerly NCR) 53c810 (rev 1). IRQ 10. Master Capable. Latency=64. I/O at 0xd800 [0xd8ff]. Non-prefetchable 32 bit memory at 0xefffff00 [0xefffffff]. It is quite an old SCSI card and I don't think the card does more than 10Mb/s but I though SCSI devices were supposed to negotiate all these things. I wonder if the sym53c8xx driver has changed significantly between kernel 2.2 and the 2.4.13 I am running now. Steve.
Hi Steve, Looks like you still have the ncr module loaded when you try to load the sym one. If it's compiled into your kernel, you'll need to rebuild it. ...and in next weeks egg sucking lesson... hard boiled or scrambled? :-) Hope that helps Chris Chris *************************************************************************** E Mail Chris@glovercc.clara.co.uk WWW http://www.glovercc.clara.co.uk ICQ 18054759 Someday, we'll look back on this, laugh nervously and change the subject. -Anon
-----Original Message----- From: Steve Fosdick [mailto:fozzy@pelvoux.demon.co.uk] Sent: 22 November 2001 00:47 To: Chris Glover Cc: Steve Fosdick; main@lists.alug.org.uk Subject: Re: [Alug] CD Writer Trouble
On Wed, 21 Nov 2001 10:20:40 Chris Glover wrote:
Have you tryed using the sym53c8xx kernel module instead of the ncr53c8xx. This is an updated driver, your old one may be having problems controling your new writer.
Thanks Chris.
I seem to remember using the sym53c8xx driver in the past, but when I try to load it now I get:
/lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: init_module: No such deviceHint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: insmod /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o failed /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: insmod sym53c8xx failed
From 'cat /proc/pci' I get:
Bus 0, device 11, function 0: Non-VGA unclassified device: LSI Logic / Symbios Logic (formerly NCR) 53c810 (rev 1). IRQ 10. Master Capable. Latency=64. I/O at 0xd800 [0xd8ff]. Non-prefetchable 32 bit memory at 0xefffff00 [0xefffffff].
It is quite an old SCSI card and I don't think the card does more than 10Mb/s but I though SCSI devices were supposed to negotiate all these things.
I wonder if the sym53c8xx driver has changed significantly between kernel 2.2 and the 2.4.13 I am running now.
Steve.
On Thu, 22 Nov 2001 09:46:18 Chris Glover wrote:
Looks like you still have the ncr module loaded when you try to load the sym one. If it's compiled into your kernel, you'll need to rebuild it.
I wish it were that simple. All the SCSI drivers are built as modules, so I tried loading the sym driver again just after the machine had booted and got exactly the same error message, and lsmod confirms no other SCSI drivers installed. I did find one new error message though. From 'dmesg' I get: PCI: Found IRQ 10 for device 00:0b.0 sym53c8xx: at PCI bus 0, device 11, function 0 sym53c8xx: not initializing, device not supported As I said, I think the sym driver has supported by card in the past so I'm not sure if that support has been removed or if the driver is just not recognising the device properly. Steve.
On Thu, 22 Nov 2001 23:10:50 Steve Fosdick wrote:
As I said, I think the sym driver has supported by card in the past so I'm not sure if that support has been removed or if the driver is just not recognising the device properly.
I checked the source code for the sym driver and it recognises the chip on my SCSI card as a plain 53C810 rather than a 53C810A and the driver did support in the past but not now. I did however remember that I had a similar SCSI card in another PC so I tried swapping them to see if the other card has the 53C810A on it - maybe it was this other machine on which I remembered having the sym driver work. The other card didn't have an 53C810A, still just the plain one and so the sym driver still wouldn't work with it but the other card was a genuine NCR one which the first one was not so I thought I'd give things a go with the ncr kernel driver. I have now managed to get it to write a CD without any SCSI errors (I haven't tested the CD yet) and with the generic-mmc cdrdao driver. Fingers crossed that the disk actually works. Steve.
If this is of any use, this is what I get when I cat /proc/pci. My Tekram DC390U is two SCSI controllers on the one card, hence it appearing twice. SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c1010 Ultra3 SCSI Adapter (rev 1). IRQ 11. Master Capable. Latency=72. Min Gnt=17.Max Lat=18. I/O at 0xac00 [0xacff]. Non-prefetchable 64 bit memory at 0xd8005000 [0xd80053ff]. Non-prefetchable 64 bit memory at 0xd8000000 [0xd8001fff]. Bus 0, device 9, function 1: SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c1010 Ultra3 SCSI Adapter (#2) (rev 1). IRQ 11. Master Capable. Latency=72. Min Gnt=17.Max Lat=18. I/O at 0xb000 [0xb0ff]. Non-prefetchable 64 bit memory at 0xd8004000 [0xd80043ff]. Non-prefetchable 64 bit memory at 0xd8002000 [0xd8003fff]. Bus 0, device 11, function 0: I'm running Kernel 2.4.10 on a Duron 600 if that helps Chris Chris *************************************************************************** E Mail Chris@glovercc.clara.co.uk WWW http://www.glovercc.clara.co.uk ICQ 18054759 Someday, we'll look back on this, laugh nervously and change the subject. -Anon
-----Original Message----- From: Steve Fosdick [mailto:fozzy@pelvoux.demon.co.uk] Sent: 22 November 2001 00:47 To: Chris Glover Cc: Steve Fosdick; main@lists.alug.org.uk Subject: Re: [Alug] CD Writer Trouble
On Wed, 21 Nov 2001 10:20:40 Chris Glover wrote:
Have you tryed using the sym53c8xx kernel module instead of the ncr53c8xx. This is an updated driver, your old one may be having problems controling your new writer.
Thanks Chris.
I seem to remember using the sym53c8xx driver in the past, but when I try to load it now I get:
/lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: init_module: No such deviceHint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: insmod /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o failed /lib/modules/2.4.13/kernel/drivers/scsi/sym53c8xx.o: insmod sym53c8xx failed
From 'cat /proc/pci' I get:
Bus 0, device 11, function 0: Non-VGA unclassified device: LSI Logic / Symbios Logic (formerly NCR) 53c810 (rev 1). IRQ 10. Master Capable. Latency=64. I/O at 0xd800 [0xd8ff]. Non-prefetchable 32 bit memory at 0xefffff00 [0xefffffff].
It is quite an old SCSI card and I don't think the card does more than 10Mb/s but I though SCSI devices were supposed to negotiate all these things.
I wonder if the sym53c8xx driver has changed significantly between kernel 2.2 and the 2.4.13 I am running now.
Steve.
participants (3)
-
Chris Glover -
Lincoln, Michael C -
Steve Fosdick