With Haiku PM, cdrecord is no longer able to see my device. Need to update cdrecord to 3.01a18 for all builds

[Giova84]

hrev46198 cdrtools-3.01~a07 on Haiku without PM, was able to see and use my burner device. But now on Haiku PM, is no longer able to see my device.

cdrecord --scanbus

will result in:

Cdrecord-ProDVD-ProBD-Clone 3.01a07 (i586-pc-haiku) Copyright (C) 1995-2012 Joerg Schilling
Using libscg version 'schily-0.9'.
cdrecord: No target found.

Unfortunately the syslog doesn't show anything about this issue.

[Giova84]

I have built cdrtools-3.01~a08 and this new compiled version is able to see my burner device.

[scottmc]

Can you try using this .hpkg on a Haiku hrev46203 or newer? ​http://ports-space.haiku-files.org/packages-to-test/cdrtools-3.01%7Ea17-1-x86_gcc2.hpkg

[Giova84]

Hi Scott, This revision ​http://ports-space.haiku-files.org/packages-to-test/cdrtools-3.01%7Ea17-1-x86_gcc2.hpkg works as expected.

Thank you.

[Giova84]

But.. There is a typo in the package name? Is reported as 3.01a17 but in terminal i read, instead, "3.01a16".

[scottmc]

try using haikuporter to build the a18 version and see if that works and reports the correct version on the command line.

[Giova84]

All fine with a18 version. So can you officially replace, on Haiku, the current a07 with a18?

[scottmc]

Thanks for the feedback. If no one else beats me to it, I'll try to get it added within the next week. I need to put together a fresh partition to use for making Haiku builds, I've been working in a VM lately.

[Giova84]

Hi, I see that the newer revision (a18) of cdrecord is applied in hrev46403, when the this nightly build will be available (i don't see new nightlies since days) i will send you a feedback.

[scottmc]

ok. let's keep the ticket open until I get the gcc4 and x86_64 hpkg files added as well.

[scottmc]

Is this working for you now?

[Giova84]

Hi, as I've said on comment:7 and in comment:9 with a18 version (which is now present by default) all is fine.

[scottmc]

​http://sourceforge.net/projects/cdrtools/files/alpha/

[vidrep]

See ticket #11257 for related issue.

[scottmc]

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

[pulkomandy]

The gcc2 image is fine now, so moving out of R1 milestone.

[vidrep]

hrev49020 x86_64 nightly fails to see the optical device. Alpha 4.1 and 32 bit nightly share the same hard drive on different partitions, and both detect it OK.

[anevilyak]

That's pretty much to be expected, as cdrecord on x86_64 is still the old version (3.01a07).

[vidrep]

Replying to anevilyak:

That's pretty much to be expected, as cdrecord on x86_64 is still the old version (3.01a07).

Alpha 4.1 is also using 3.01a07 and it detects the drive no problem. Do you recall which hrev immediately preceded PM? I'd like to be sure that the 64 bit CDRecord wasn't broken before PM.

[pulkomandy]

I think this is solved now?

[vidrep]

Replying to scottmc:

ok. let's keep the ticket open until I get the gcc4 and x86_64 hpkg files added as well.

Replying to pulkomandy:

I think this is solved now?

hrev49286 x86_64 is still using old 3.01a07 revision, and still cannot detect the optical drives in either of my PC's. So, not solved yet.

[vidrep]

All optical devices are now being detected on 64 bit builds with hrev49287. Problem solved. Thanks!

Will the 3.01a29 version of CDRTools be made available for 32 bit builds as well? Currently it is still using 3.01a25, which had some issues.

[vidrep]

Tested CD disk burning with hrev49292 x86_gcc2 and x86_64.

x86_gcc2 (cdrecord version 3.01a25) - fail due to FIFO error (see attached cdrecord_session1)

x86_64 (cdrecord version 3.01a29) - successful!

32 bit Haiku needs to be updated to working cdrtools revision 3.01a29.

[vidrep]

Just a question: Is there any reason why 32 bit Haiku builds are still using the broken cdrtools (3.01a25), while 64 bit has already been updated to a working version (3.01a29)?

[pulkomandy]

Probably because no one bothered to update the package. doing so is a very boring task, which is why we have waddlesplash working in a paid contract to automate it. Once that is done, submitting a pull request to haikuports will be the only thing needed to get an updated package, and the developers won't have to worry about rebuilding packages for all 3 architectures and upload them, each time a bug pops in.

[vidrep]

CDRTools in 32 bit versions has been broken for nearly 2 years now. Trying to test any of the CD recording apps such as BurnItNow is pointless until this is fixed first. If it is too boring for the developers to upgrade this package and others like it, then imagine the frustration of the end user who has no working apps.

[waddlesplash]

If it is too boring for the developers to upgrade this package and others like it, then imagine the frustration of the end user who has no working apps.

See #10893 -- this is the whole point of the contract I'm currently on. :p

[humdinger]

I updated the cdrtools package for gcc2 with hrev49443. gcc4 fails to build. 64bit complains that the declared files "settings/cdrecord" and "settings/rscsi" aren't included in the package. When building for gcc2 there is no such policy error...

[vidrep]

Humdinger, 64 bit builds already had the updated (working) 3.01a29 Cdrtools, so the 3.01a30 package is not really necessary now. Only the 32 bit package was broken in current nightlies. Thanks for the update.

[pulkomandy]

Can we close this then?

[vidrep]

I won't be able to test this until I get home from work later tonight. I'll let you know as soon as I have finished testing.

[vidrep]

CDrecord appears to be working again. This ticket can be closed. Blanking CDRW brings up an error message which indicates a possible hardware compatability issue. Where are these kind of non-Haiku related reports to be sent?

[anevilyak]

Assuming that behavior can be duplicated on Linux, i.e. can definitely be shown to not be a quirk of the Haiku port, that would entail filing a bug with the cdrtools project, which is maintained at ​http://sourceforge.net/projects/cdrtools/ as far as I'm aware.

[vidrep]

Ok. Maybe keep the ticket open until I can determine whether it is a hardware issue or not. I have 3 additional DVD burners and 2 more PC's I can test with.

[vidrep]

This ticket can be closed for the error described in the ticket. Blanking of RW media still is an issue. I'll open another ticket for that.