From: Kevin A. <ke...@at...> - 2002-10-25 23:11:15
|
Sorry if this is not the best place to post, I didn't know where else to report the problem. It may be a bug but I am not sure. Cdrdao does not work on RedHat 8.0. I tried with RedHat binary and the official binaries for version 1.1.5 and 1.1.7 in the download area. (Driver generic-mmc, device 0,1,0) # /usr/bin/cdrdao write videocd.cue ... Turning BURN-Proof on Executing power calibration... Power calibration successful. Writing track 01 (mode MODE2_RAW/MODE2_RAW)... Writing track 02 (mode MODE2_RAW/MODE2_RAW)... ?: Input/output error. : scsi sendcmd: no error CDB: 2A 00 00 00 03 24 00 00 15 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.006s timeout 180s ERROR: Write data failed. ERROR: Writing failed - buffer under run? ERROR: Writing failed. ?: Input/output error. : scsi sendcmd: no error CDB: 1E 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 1.154s timeout 180s ERROR: Cannot prevent/allow medium removal. /proc/version: Linux version 2.4.18-17.8.0 (bhc...@da...) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Tue Oct 8 13:51:08 EDT 2002 /proc/scsi/scsi Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATAPI Model: CD-ROM DRIVE-50X Rev: G5BL Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: CDWRITER Model: IDE2410 Rev: A.23 Type: CD-ROM ANSI SCSI revision: 02 "cdrdao blank" works OK. I have tried to write to both a CD-RW after blanking and a new CD-R. Cdrdao works OK when the driver is set to generic-mmc-raw but it doesn't burn the disk correctly as I have problems reading it afterwards. This used to work when I hade Mandrake installed on the exact same system and binary (Cdrdao 1.1.5) using linux-2.4.19. Cdrdao also does not work when using linux-2.4.19 compiled with the exact same options I used to compile the kernel when I had Mandrake installed. I would really appreciate any help anyone can give me on getting cdrdao to work again. Thanks in advance. -- http://kevin.atkinson.dhs.org |
From: Kevin A. <ke...@at...> - 2002-10-27 12:22:15
|
Sorry if this is not the best place to post, I didn't know where else to report the problem. It may be a bug but I am not sure. Cdrdao does not work on RedHat 8.0. I tried with RedHat binary and the official binaries for version 1.1.5 and 1.1.7 in the download area. (Driver generic-mmc, device 0,1,0) # /usr/bin/cdrdao write videocd.cue ... Turning BURN-Proof on Executing power calibration... Power calibration successful. Writing track 01 (mode MODE2_RAW/MODE2_RAW)... Writing track 02 (mode MODE2_RAW/MODE2_RAW)... ?: Input/output error. : scsi sendcmd: no error CDB: 2A 00 00 00 03 24 00 00 15 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.006s timeout 180s ERROR: Write data failed. ERROR: Writing failed - buffer under run? ERROR: Writing failed. ?: Input/output error. : scsi sendcmd: no error CDB: 1E 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 1.154s timeout 180s ERROR: Cannot prevent/allow medium removal. /proc/version: Linux version 2.4.18-17.8.0 (bhc...@da...) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Tue Oct 8 13:51:08 EDT 2002 /proc/scsi/scsi Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATAPI Model: CD-ROM DRIVE-50X Rev: G5BL Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: CDWRITER Model: IDE2410 Rev: A.23 Type: CD-ROM ANSI SCSI revision: 02 "cdrdao blank" works OK. I have tried to write to both a CD-RW after blanking and a new CD-R. Cdrdao works OK when the driver is set to generic-mmc-raw but it doesn't burn the disk correctly as I have problems reading it afterwards. This used to work when I hade Mandrake installed on the exact same system and binary (Cdrdao 1.1.5) using linux-2.4.19. Cdrdao also does not work when using linux-2.4.19 compiled with the exact same options I used to compile the kernel when I had Mandrake installed. I would really appreciate any help anyone can give me on getting cdrdao to work again. Thanks in advance. -- http://kevin.atkinson.dhs.org |
From: Kevin A. <ke...@at...> - 2002-10-27 12:29:36
|
Sorry for the duplicate post. For some reason I didn't think the first post made it. -- http://kevin.atkinson.dhs.org |
From: Andreas M. <an...@da...> - 2002-10-27 16:42:14
|
Hi Kevin, > > Sorry if this is not the best place to post, I didn't know where else to > report the problem. It may be a bug but I am not sure. > > Cdrdao does not work on RedHat 8.0. I tried with RedHat binary and the > official binaries for version 1.1.5 and 1.1.7 in the download area. It very unlikely that this problem is directly related to a Linux distribution. It may depend on the kernel version though. > > (Driver generic-mmc, device 0,1,0) > > # /usr/bin/cdrdao write videocd.cue > ... > Turning BURN-Proof on > Executing power calibration... > Power calibration successful. > Writing track 01 (mode MODE2_RAW/MODE2_RAW)... > Writing track 02 (mode MODE2_RAW/MODE2_RAW)... > ?: Input/output error. : scsi sendcmd: no error > CDB: 2A 00 00 00 03 24 00 00 15 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00 > Sense Key: 0x2 Not Ready, Segment 0 > Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress) > Fru > 0x0 > Sense flags: Blk 0 (not valid) > cmd finished after 0.006s timeout 180s When does this error happen? At the beginning, the middle or the end of the recording process? > "cdrdao blank" works OK. I have tried to write to both a CD-RW after > blanking and a new CD-R. Cdrdao works OK when the driver is set to > generic-mmc-raw but it doesn't burn the disk correctly as I have problems > reading it afterwards. Did you try to recorder othe CD types, e.g. audio CDs? What type of problems did you have when reading the burned CD? Can you run a 'cat /dev/sr0 >/dev/null' without getting error messages from the kernel (check with 'dmesg')? > This used to work when I hade Mandrake installed on the exact same system > and binary (Cdrdao 1.1.5) using linux-2.4.19. Strange. > > Cdrdao also does not work when using linux-2.4.19 compiled with the > exact same options I used to compile the kernel when I had Mandrake > installed. In which sense does cdrdao not work. Doesn't it find the recorder device or does it fail in a different manor. Regards, Andreas -- Andreas Mueller Tel: +49 89 67808848 Ramsmeierstr. 1 Email: an...@da... 85579 Neubiberg, Germany |
From: Kevin A. <ke...@at...> - 2002-10-27 16:55:11
|
On 27 Oct 2002, Andreas Mueller wrote: > Hi Kevin, > > > > (Driver generic-mmc, device 0,1,0) > > > > # /usr/bin/cdrdao write videocd.cue > > ... > > Turning BURN-Proof on > > Executing power calibration... > > Power calibration successful. > > Writing track 01 (mode MODE2_RAW/MODE2_RAW)... > > Writing track 02 (mode MODE2_RAW/MODE2_RAW)... > > ?: Input/output error. : scsi sendcmd: no error > > CDB: 2A 00 00 00 03 24 00 00 15 00 > > status: 0x2 (CHECK CONDITION) > > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00 > > Sense Key: 0x2 Not Ready, Segment 0 > > Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress) > > Fru > > 0x0 > > Sense flags: Blk 0 (not valid) > > cmd finished after 0.006s timeout 180s > > When does this error happen? At the beginning, the middle or the end of > the recording process? The very beginning. > > "cdrdao blank" works OK. I have tried to write to both a CD-RW after > > blanking and a new CD-R. Cdrdao works OK when the driver is set to > > generic-mmc-raw but it doesn't burn the disk correctly as I have problems > > reading it afterwards. > > Did you try to recorder othe CD types, e.g. audio CDs? What type of > problems did you have when reading the burned CD? My DVD player doesn't like the VCD disk at all. It keeps on freezing. This happens with two different DVD players. It use to work find when with Mandrake 8.2 and the driver set to "generic-mmc". If it becomes necessary I can try burning another disk and perform more careful tests. However, my point is that "generic-mmc" fails while "generic-mmc-raw" does not. > Can you run a 'cat /dev/sr0 >/dev/null' without getting error messages > from the kernel (check with 'dmesg')? When should I do this? With a disk in the drive? > > This used to work when I hade Mandrake installed on the exact same system > > and binary (Cdrdao 1.1.5) using linux-2.4.19. > > Strange. > > > > > Cdrdao also does not work when using linux-2.4.19 compiled with the > > exact same options I used to compile the kernel when I had Mandrake > > installed. > > In which sense does cdrdao not work. Doesn't it find the recorder > device or does it fail in a different manor. Cdrdao fails in the same manor as it did with the Red Hat kernel binary. --- http://kevin.atkinson.dhs.org |
From: Andreas M. <an...@da...> - 2002-10-27 17:11:53
|
On Sun, 2002-10-27 at 17:55, Kevin Atkinson wrote: > On 27 Oct 2002, Andreas Mueller wrote: > > > Hi Kevin, > > > > > > (Driver generic-mmc, device 0,1,0) > > > > > > # /usr/bin/cdrdao write videocd.cue > > > ... > > > Turning BURN-Proof on > > > Executing power calibration... > > > Power calibration successful. > > > Writing track 01 (mode MODE2_RAW/MODE2_RAW)... > > > Writing track 02 (mode MODE2_RAW/MODE2_RAW)... > > > ?: Input/output error. : scsi sendcmd: no error > > > CDB: 2A 00 00 00 03 24 00 00 15 00 > > > status: 0x2 (CHECK CONDITION) > > > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00 > > > Sense Key: 0x2 Not Ready, Segment 0 > > > Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress) > > > Fru > > > 0x0 > > > Sense flags: Blk 0 (not valid) > > > cmd finished after 0.006s timeout 180s > > > > When does this error happen? At the beginning, the middle or the end of > > the recording process? > > The very beginning. Ok, then I have an idea. You will have to recompile cdrdao to try it out: Open the file "dao/GenericMMC.cc" in a text editor and look for function 'GenericMMC::writeData'. In its body you'll find following lines: // check if drive rejected the command because the internal buffer // is filled if(senseLen >= 14 && (sense[2] & 0x0f) == 0x2 && sense[7] >= 6 && sense[12] == 0x4 && sense[13] == 0x8) { Replace them by: // check if drive rejected the command because the internal buffer // is filled if(senseLen >= 14 && (sense[2] & 0x0f) == 0x2 && sense[7] >= 6 && sense[12] == 0x4 && (sense[13] == 0x7 || sense[13] == 0x8)) { Then compile cdrdao and try again (best with 'simulate' first). Looks like your model reports a slightly different error code if data is sent to drive while it is still writing the lead-in. > > > > "cdrdao blank" works OK. I have tried to write to both a CD-RW after > > > blanking and a new CD-R. Cdrdao works OK when the driver is set to > > > generic-mmc-raw but it doesn't burn the disk correctly as I have problems > > > reading it afterwards. > > > > Did you try to recorder othe CD types, e.g. audio CDs? What type of > > problems did you have when reading the burned CD? > > My DVD player doesn't like the VCD disk at all. It keeps on freezing. > This happens with two different DVD players. It use to work find when > with Mandrake 8.2 and the driver set to "generic-mmc". If it becomes > necessary I can try burning another disk and perform more careful tests. > However, my point is that "generic-mmc" fails while "generic-mmc-raw" does > not. Ok, but if the 'generic-mmc-raw' driver successfully writes the CD-R it should finally work. That's why I try to find out what is wrong with the resulting CD. The fact that the DVD player does not like it does not mean that the disk was not correctly written. The disk image might just contain incorrect VCD data. > > > Can you run a 'cat /dev/sr0 >/dev/null' without getting error messages > > from the kernel (check with 'dmesg')? > > When should I do this? With a disk in the drive? Yes, you could use the VCD that did not work in the DVD player. You can also just try to mount the CD and check if you can access its filesystem. If this works the CD writing was probably OK and the DVD player just does not like the data itself. > > > > This used to work when I hade Mandrake installed on the exact same system > > > and binary (Cdrdao 1.1.5) using linux-2.4.19. > > > > Strange. > > > > > > > > Cdrdao also does not work when using linux-2.4.19 compiled with the > > > exact same options I used to compile the kernel when I had Mandrake > > > installed. > > > > In which sense does cdrdao not work. Doesn't it find the recorder > > device or does it fail in a different manor. > > Cdrdao fails in the same manor as it did with the Red Hat kernel binary. Ok, but if the code change above fixes the problem it cannot be related to the kernel or the Linux distribution. Regards, Andreas -- Andreas Mueller Tel: +49 89 67808848 Ramsmeierstr. 1 Email: an...@da... 85579 Neubiberg, Germany |
From: Kevin A. <ke...@at...> - 2002-10-28 13:57:44
|
On 27 Oct 2002, Andreas Mueller wrote: > On Sun, 2002-10-27 at 17:55, Kevin Atkinson wrote: > > On 27 Oct 2002, Andreas Mueller wrote: > > > > > When does this error happen? At the beginning, the middle or the end of > > > the recording process? > > > > The very beginning. > > Ok, then I have an idea. You will have to recompile cdrdao to try it > out: .... I don't get it. It suddenly started working. Thus finding the problem I use to have will be rather difficult. > > > Did you try to recorder othe CD types, e.g. audio CDs? What type of > > > problems did you have when reading the burned CD? > > > > My DVD player doesn't like the VCD disk at all. It keeps on freezing. > > This happens with two different DVD players. It use to work find when > > with Mandrake 8.2 and the driver set to "generic-mmc". If it becomes > > necessary I can try burning another disk and perform more careful tests. > > However, my point is that "generic-mmc" fails while "generic-mmc-raw" does > > not. > > Ok, but if the 'generic-mmc-raw' driver successfully writes the CD-R it > should finally work. That's why I try to find out what is wrong with the > resulting CD. > > The fact that the DVD player does not like it does not mean that the > disk was not correctly written. The disk image might just contain > incorrect VCD data. The same videocd.cue/bin works fine when burned with generic-mmc. I know because I burned the exact same image using cdrdao on Windows 98 through VCDEazy. > > > Can you run a 'cat /dev/sr0 >/dev/null' without getting error messages > > > from the kernel (check with 'dmesg')? > > > > When should I do this? With a disk in the drive? > > Yes, you could use the VCD that did not work in the DVD player. You can > also just try to mount the CD and check if you can access its > filesystem. If this works the CD writing was probably OK and the DVD > player just does not like the data itself. OK. I will do when I get a chance. --- http://kevin.atkinson.dhs.org |
From: Kevin A. <ke...@at...> - 2002-11-11 15:43:41
|
On Fri, 25 Oct 2002, Kevin Atkinson wrote: > Cdrdao does not work on RedHat 8.0. I tried with RedHat binary and the > official binaries for version 1.1.5 and 1.1.7 in the download area. > > # /usr/bin/cdrdao write videocd.cue > ... > Turning BURN-Proof on > Executing power calibration... > Power calibration successful. > Writing track 01 (mode MODE2_RAW/MODE2_RAW)... > Writing track 02 (mode MODE2_RAW/MODE2_RAW)... > ... > ERROR: Write data failed. > ERROR: Writing failed - buffer under run? > ERROR: Writing failed. > ... I discovered what the problem was. It had nothing to do with cdrdao or the kernel version I was using. The problem was an overly aggressive autorun demean that gets launched with the KDE desktop. It was apparently trying to mount the cdrom in the middle of the burn! I solved the problem by killing the daemon and removing the file ~/.kde/Autostart/Autorun.desktop to keep it from starting up again. It took me an hour of google searching and some detective work to piece together the solution to this problem. --- http://kevin.atkinson.dhs.org |
From: Kevin A. <ke...@at...> - 2002-11-11 15:49:29
|
On Mon, 11 Nov 2002, Kevin Atkinson wrote: > On Fri, 25 Oct 2002, Kevin Atkinson wrote: > > > Cdrdao does not work on RedHat 8.0. I tried with RedHat binary and the > > official binaries for version 1.1.5 and 1.1.7 in the download area. > > > > # /usr/bin/cdrdao write videocd.cue > > ... > > Turning BURN-Proof on > > Executing power calibration... > > Power calibration successful. > > Writing track 01 (mode MODE2_RAW/MODE2_RAW)... > > Writing track 02 (mode MODE2_RAW/MODE2_RAW)... > > ... > > ERROR: Write data failed. > > ERROR: Writing failed - buffer under run? > > ERROR: Writing failed. > > ... > > I discovered what the problem was. It had nothing to do with cdrdao or > the kernel version I was using. The problem was an overly aggressive > autorun demean that gets launched with the KDE desktop. It was apparently > trying to mount the cdrom in the middle of the burn! I solved the problem > by killing the daemon and removing the file > ~/.kde/Autostart/Autorun.desktop to keep it from starting up again. It > took me an hour of google searching and some detective work to piece > together the solution to this problem. By "the solution to this problem" I mean "prevent the automount". I can't believe such a simple thing was so difficult to do. -- http://kevin.atkinson.dhs.org |