CDRecord broken

[vidrep]

When trying to burn an image file to a CDRW, CDRecord counts down to start, but never begins burning disc. Attached is listdev and CDRecord log from last session.

[vidrep]

This is with hrev47877 x86_64. Blank CD command is working.

[vidrep]

CDRecord appears to be broken in the nightlies. I tried burning the hrev47877 anyboot image to a CD from within both the hybrid and 64 bit builds, using two different PC's. All attempts failed. However, when burning the CD using the alpha 4.1 partitions on the same PC's, the disc burned without a problem (using same command from the terminal for each attempt).

[korli]

For the record, could you please give the CDRecord version in alpha 4.1?

[vidrep]

Alpha4.1 - Cdrecord-ProDVD-ProBD-Clone 3.01a07 (i586-pc-haiku) Copyright (C) 1995-2012 Joerg Schilling

hrev47877 x86_gcc2 - Cdrecord-ProDVD-ProBD-Clone 3.01a18 (i586-pc-haiku) Copyright (C) 1995-2013 Joerg Schilling

[scottmc]

Related to #10099. cdrecord needs to be updated, and that will probably fix this issue.

[vidrep]

On my newest PC, CDRecord is only able to detect the DVD drive using Alpha 4.1 using the "cdrecord -scanbus" command. CDRecord is also not able to blank discs. The CDRecord version on nightly builds fail to detect the drive at all, yet Haiku will read audio or data disks that are inserted.

[vidrep]

I note that one of the completed GCI tasks was updating CDRecord to version 3.01a25. When can we expect it to appear in the nightlies?

[vidrep]

CDRecord still fails to blank CDRW disks in hrev48956 x86_gcc2. I have attached a copy of the terminal output from last session as well as a syslog.

[vidrep]

Attempting to write a file to a blank CD does not work either. Attached copy of terminal output from last session.

[vidrep]

Attached are reports from tonights testing using Alpha 4.1, hrev49020 x86_gcc2, and hrev49020 x86_64.

[vidrep]

I was finally able to successfully burn a CD-R using CDRTools 3.01a25 in hrev49020 x86_gcc2. The problem appears to be the FIFO buffer. Attempting to set any value greater than 128k in the command line argument (fs=)results in a "panic FIFO addr." error and no burn. Setting FIFO to a lower value causes CDRecord to disable FIFO for being "too small a value", but continues burning OK. Blanking a CDRW does not appear to work correctly, whether using "fast" or "all". Attached is a record of my last successful burn from the command line.

[vidrep]

On 64 bit, CDRecord will not detect my optical drive, even though it on the same hard drive, on another partition, and sharing the exact same hardware.

[pulkomandy]

I am discussing the issues with a cdrecord developer. This should be solved soon.

[pistooli]

I have just tried to burn from BurnitNow2 the alpha 4.1 iso on a recent nightly - hrev49031 cdrecord (CDRTools 3.01a25) was already present, BurnitNow2 was installed from HaikuDepot The CD drive is identified as TSSTcorpCDDVDW SH-224DB (9,0,0)

The burning starts, then it finally shows a message: Track 01: Total bytes read/written: 615106560/615106560 (300345 sectors).

The CD/DVD drive continues to spin and does not stop. Interestingly the image is still written, so manualy ejecting the CD stops the spinning of the drive.

[vidrep]

Did you have to manually configure the FIFO settings in the cdrecord.config file, or did it work "out of the box" with the default settings? What settings worked? What error messages, if any, did you see? Did blanking a CDRW work correctly?

[vidrep]

Replying to pulkomandy:

I am discussing the issues with a cdrecord developer. This should be solved soon.

Until CDRecord is fixed, any CD/DVD burning applications for Haiku (BurnItNow) are useless for testing purposes. I know the developer time is spread pretty thin, so I appreciate your taking the time to have a look at this.