http://bugzilla.novell.com/show_bug.cgi?id=567336 http://bugzilla.novell.com/show_bug.cgi?id=567336#c1 Jörg Schiling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joerg.schilling@fokus.fraun | |hofer.de --- Comment #1 from Jörg Schiling 2010-01-05 12:40:12 UTC --- Wodim does not support to write DVDs, it is unmaintained and it cannot be legally distributed. I recommmend you to upgrade to recent original software: http://cdrecord.berlios.de/ http://cdrecord.berlios.de/private/linux-dist.html Note tast SuSe even has binary packages for the original software. If cdrecord does not write as fast was you might expect, then your drive is not able to write the related medium at higher speed. Original Verbatim media (check with "cdrecord -atip") should however be supported at the speed that is pronted on the medium. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567336 http://bugzilla.novell.com/show_bug.cgi?id=567336#c3 --- Comment #3 from Rod Schaffter 2010-01-05 19:48:28 UTC --- Created an attachment (id=335043) --> (http://bugzilla.novell.com/attachment.cgi?id=335043) console output of cdrecord -prcap dev=/dev/sr0 This is the console output of cdrecord -prcap dev=/dev/sr0 using cdrecord from the Factory:Base repository. instead of the wodim included with openSUSE 10.2.. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567336 http://bugzilla.novell.com/show_bug.cgi?id=567336#c4 --- Comment #4 from Jörg Schiling 2010-01-05 22:31:43 UTC --- (In reply to comment #2)

I of course used wodim because that is what was included in the 11.2 distribution. I removed wodim, and the cdrkit-cdrtools compatibility package, and installed cdrecord and mkisofs from the Factory:Base repository.

The console output of cdrecord -prcap dev=/dev/sr0 incorrectly indicates that the top DVD write speed of this drive is 6x, as did wodim. However, K3b WOULD write a disk at 16x, averaging 12.6x for the test disk I burned, so in that regard, the substitution of cdrecord/mkisofs for wodim was a success.

It seems that you are missinterpreting the output from cdrecord. Cdrecord typically just outputs the information provided by the drive. Cdrecord just knows a lot about bugs in the drive's firmware and how to circumvent related problems. If you like to get information for a specific medium, you of course need to _insert_ this medium first _before_ you call cdrecord. You did not do this, but rather did run cdrecord with an empty tray, so you cannot expect information that is related to a medium..... Didn't you wonder why the drive reported you a max. speed of 8467x when looking at the output? Now back to your drive: it is well known that this drive has firmware bugs and always returns CD related values in the MMC-2 part of the reply although with MMC-2, the DVD media type was introduced into the standard. If you like to discuss the problem, you of course first need to insert _exactly_ the medium, you are interested in. Then have a close look at the get performance values...... Some drives (e.g. Pioneer still will not return useful values here. Now back to k3b: I recommend you to make a bug report against k3b as k3b does not use cdrecord to ask for the possible write speed. Instead, k3b tries to send SCSI commands itself (which is introducing a security problem as k3b is a GUI that cannot be audited for security). The important problem with k3b however is that it does not have the needed knowledge about the drives and it's firmware bugs, so k3b is expected to give wrong results as long as it is not converted to rather ask cdrecord for the needed parameters. I recommend you to run: cdrecord -vv -checkdrive to get the max. write speed for a specific medium, as the related output is not what the drive tells you directly but instead a firmware bug workaround is used in this case. BTW: From reading my statements, you may understand why it is of course a bad idea to use old versions of cdrecord (older than the drive) or completely unmaintained software like wodim. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567336 http://bugzilla.novell.com/show_bug.cgi?id=567336#c6 --- Comment #6 from Jörg Schiling 2010-01-20 22:03:31 UTC --- You don't need to use closed source software in order to get decent behavior..... The original cdrtools (even available as binary packet via SuSE) also has no problem to write at the maximum supported speed because cdrtools is well maintained software. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567336 http://bugzilla.novell.com/show_bug.cgi?id=567336#c8 --- Comment #8 from Jörg Schiling 2010-01-21 00:36:16 UTC --- Please stop your trolling. You reported a bug against an illegal and unmaintained fork on my software. I am trying to help you. The only way to get rid of the > 100 well known bugs in the fork is to upgrade to recent original software. SuSE does even provide you with binary packages for the original softwarem so there would be no problem for you if you did just follow my advise. If you however like to stay with the broken and illegal fork wodim, you should stop sending bugs reports as the fork is unmaintained. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567336 http://bugzilla.novell.com/show_bug.cgi?id=567336#c10 --- Comment #10 from Jörg Schiling 2010-01-21 08:05:09 UTC --- I am sorry to see that you made your bug report not in hope for a fix but rather in order to play political games against OpenSource software. Have a nice day and have fun with your bugs. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567336 http://bugzilla.novell.com/show_bug.cgi?id=567336#c12 --- Comment #12 from Rod Schaffter 2010-01-21 15:24:42 UTC --- All Politics aside, the version of cdrecord available in the Factory Base repository solved my problem with drive speeds, as I noted above. The version of wodim and cdrkit-cdrtools-compat included with 11.2 and Factory, 1.1.9, is not the current version, which is 1.1.10. Whether it solves the speed issues is unknown-I'm personally quite happy with cdrecord, myself. The source is available here as CDRkit if anyone wants to play with it... http://cdrkit.org/releases/ Cheers,Rod -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.