Announcing cdrskin-0.7.2
Hi, be invited to try the new version 0.7.2 of my program cdrskin, a burn backend for CD, DVD and BD with a command line interface compatible to cdrecord. System requirements: Linux with kernel 2.4 or 2.6: libc, libpthread or FreeBSD : libc, libpthread, ATAPI/CAM enabled, see atapicam(4) Changes: * Bug fix: CD TAO sessions with multiple tracks did not work in -dummy mode. * Now emulating option -minfo and printing those info lines which can be provided by libburn. * New info lines with -atip and -minfo: Product Id: provides a uniform single word for determining identity of media products. Line Producer: gives a guess about the manufacturer of the media. For more info, see http://scdbackup.sourceforge.net/cdrskin_eng.html http://scdbackup.sourceforge.net/man_1_cdrskin.html Download: There is a cdrskin release tarball (containing libburn): http://scdbackup.sourceforge.net/cdrskin-0.7.2.pl00.tar.gz scdbackup.sourceforge.net is mirrored at scdbackup.webframe.org . cdrskin is also part of the libburn-0.7.2 SVN tag: http://svn.libburnia-project.org/libburn/tags/ZeroSevenTwo (needs autotools = 1.7 to apply command ./bootstrap) and of the libburn-0.7.2 release tarball: http://files.libburnia-project.org/releases/libburn-0.7.2.pl00.tar.gz (needs only vanilla tools for ./configure ; make) Post bug reports or requests either to one of these mailing lists: mailto:libburn-hack...@pykix.org mailto:cdwrite@other.debian.org or directly to me: mailto:scdbac...@gmx.net Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Announcing cdrskin-0.7.2
Thomas Schmitt scdbac...@gmx.net wrote: be invited to try the new version 0.7.2 of my program cdrskin, a burn backend for CD, DVD and BD with a command line interface compatible to cdrecord. When will you correct your wrong claim that states you did not copy any byte from cdrecord's sources? Note that we did already discuss this some time ago and it is obvious that you _did_ copy sources from an older version. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Announcing cdrskin-0.7.2
Mario ??ani?? mario.da...@gmail.com wrote: Note that we did already discuss this some time ago and it is obvious that you _did_ copy sources from an older version. You discussed it with yourself. That's way different, don't you think? :) No, the announced code contains (different from that the project itself claims) code parts from an older version of the cdrtools source. Claiming that there was no such code move is a missinformation. Whether this has been done directly or indirectly does not matter as there are enough identifyable parts that have been written by Heiko Eißfeldt for cdrecord. The Copyright law requires to mention the original authors which is not done.. OpenSource gives many permissions but it does not allow to hide things. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Announcing cdrskin-0.7.2
On Di, 13 Okt 2009, Joerg Schilling wrote: No, the announced code contains (different from that the project itself claims) code parts from an older version of the cdrtools source. Claiming that there was no such code move is a missinformation. Whether this has been done directly or indirectly does not matter as there are enough identifyable parts that have been written by Heiko Eißfeldt for cdrecord. The Copyright law requires to mention the original authors which is not done.. Shut up. We are all sick of that. Best wishes Norbert --- Dr. Norbert PreiningAssociate Professor JAIST Japan Advanced Institute of Science and Technology prein...@jaist.ac.jp Vienna University of Technology prein...@logic.at Debian Developer (Debian TeX Task Force)prein...@debian.org gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- POTT SHRIGLEY (n.) Dried remains of a week-old casserole, eaten when extremely drunk at two a.m. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Announcing cdrskin-0.7.2
Hi, When will you correct your wrong claim that states you did not copy any byte from cdrecord's sources? The claim is uphold. Note that we did already discuss this some time ago and it is obvious that you _did_ copy sources from an older version. I removed the code which was labeled as stemming from cdrdao and was not used by tested parts of libburn anyway. It obviously implemented the Reed-Solomon error correction as described in ECMA-130. One thing is to understand the math behind Reed-Solomon, quite a different thing is to understand the discretization math which leads to the tables in the cdrdao implementation. Lacking the latter math i decided to give up the inherited but never working CD raw modes of libburn. http://libburnia-project.org/changeset/2779/libburn You were informed about that decision in http://lists.debian.org/cdwrite/2009/08/msg00021.html See last topic near end of message. You read and replied. libburn still does CD Mode 1 (-data) and CD-DA (-audio). It also does DVD and BD where i deliberately deviated from cdrecord's doings and rather followed the much more appealing example of growisofs. If you find any other code parts which appear copied from your projects then please report them explicitely. Our code is public and can easily be referred to. Most suspect would be CD SAO which is the last remaining write strategy that was not implemented by myself. - Dr. Norbert Preining Associate Professor JAIST Japan Advanced Institute of Science and Technology I google among other things: Institut für Diskrete Mathematik und Geometrie, Technische Universität Wien Do you know by chance a smart student who can contribute an implementation or explanation of ECMA-130 Annex A ? The RSPC is a product code over GF(28) producing P- and Q-parity bytes. The GF(28) field is generated by the primitive polynomial P(x) = x8 + x4 + x3 + x2 + 1 The primitive element a of GF(28) is a = (0010) where the right-most bit is the least significant bit. [...] The words RSPC and P- and Q-parity bytes belong to the CD sector format specs. But the others must be established mathematic terms. (How is this connected to a Fourier transformation of the bit sequence on time domain ? Urgh ! Analysis ! On a finite set !) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: growisofs burns dvd successfully, but
Ingo Krabbe ingo.kra...@eoa.de wrote: On Mon, Oct 12, 2009 at 02:47:11PM +0200, Joerg Schilling wrote: Ingo Krabbe ingo.kra...@eoa.de wrote: As you recommended I changed my usage of growisofs/genisoimage into mkisofs/cdrecord. I see no crash and everything is OK, you may verify this by e.g. calling: Yes you are right. This disk was recorded with mkisofs -dvd-video and actually works. So maybe cdrecord isn't the problem after all, though reading the data from the dvd with readcd gives me an image I can mount with mount -oloop imgfile /mnt/image I would really like to fix this, as it seems to be possible to write dvd disks with cdrecord, but still it fails to write the toc without showing an error report. If you still believe to have problems, please describe your problems in a way that allows to understand them. -dvd-video seems to create a UDF Filesystem. It seems that the toc format of UDF is more stable, which leads me to the assumption that there might be a trick to get the iso9660 filesystem onto the dvd. Otherwise I would have quit this topic, but I just can't see where my drive or any other component fails here. There is no relation between the TOC and UDF. The TOC is something that is in the low level hidden meta data of the medium and related to accessing the media from a drive. UDF is a filesystem type that is required by DVD players and if the medium is readable by the drive, it is only a matter of the higher level code to deal with UDF. If there is really a failure that should be reported somewhere. Then, there is no problem in cdrtools. Your problem is located elsewhere, but without the apropriate information I cannot give you more help that I did already give you. Anyway I think it would be helpfull if you give me a short hint about debug=# and kdebug=# numbers. Sorry, why should I give hints on options that are intended to help me to debug low level problems that are not related to your problem? If there was any relation to your problem, you had been given the needed instructions. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov ap...@fy.chalmers.se wrote: When it comes to accuracy of information meant for general public, it's difference between implying things and spelling them in manner that can't be interpreted differently by different people. 1. According to 'man ata' DMA is enabled by default on Solaris 10. To my experience with Sun W1100z it holds true. Whis this is true for Solaris 10 x86 and hard disks, it is definitely not true for the other. Original statement was Solaris 10 in general does not by default enable DMA. Any sane person not intimately familiar with subject would interpret that Solaris 10 never uses DMA by default. Well, we are talking about CD/DVD/BluRay writing and it should be obvious for a scientist, that remarks are done here with thede constraints in mind. I cannot see statements of interest in the rest. If you like to prove that there are Sparc machines with Solaris that behave different from what all other users reported, please send the related information: - exactly describe the machine type, the OS release and the drive type. - send information from prtconf -pv - Send the kernel verbose information from /var/adm/messages that indicate that DMA was in fact enabled for the related drive - send the eeprom(1) output that indicates that the DMA is not disabled for CD-ROM type drive even though the low level kernel layers did set up DMA. - Send a cdrecord -v -checkdrive output for the drive that verifies that the drive is capable to do IO in a speed that requires DMA and thus indicates that DMA is really in effect. If you could verify this, you would be the first person to do so! Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Andy Polyakov ap...@fy.chalmers.se wrote: cdrecord: I/O error. read disk info: scsi sendcmd: no error CDB: 51 00 00 00 00 00 00 00 04 00 status: 0x0 (GOOD STATUS) resid: 4 on Fri, 9 Oct 2009 22:12:35 -0400: # dvd+rw-mediainfo /dev/rdsk/c3t0d0s0 ... READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 This time the same SCSI command worked. I also assume it worked in NeroLinux. This is not necessarily the same command.. Cdrecord is implemented in compliance to the SCSI standard. Without knowing whether dvd+rw-mediainfo is implemented compliant to the SCSI standard, It feels ridiculous that I have to say this, but what choice do I have facing FUD? I can assure general public that dvd+rw-media, as well as growisofs, is compliant with SCSI standard (modulo http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html). A. I am sorry to see that you obviously try to spread FUD. If this is rather caused by the fact that youn don't understand, please stay quiet or ask! Just to repease the important sentence: This is not necessarily the same command.. Cdrecord does implement things in a way that forgives problems in the drive and that is as SCSI compliant as possible. If growisofs does some _heuristics_ instead of asking the drive the way the SCSI standard suggests, this may result in different SCSI commands. As I already mentioned: the SCSI error message above was caused by a defective Solaris kernel module and is not a result from a problem in cdrecord. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
On Di, 13 Okt 2009, Joerg Schilling wrote: As I already mentioned: the SCSI error message above was caused by a defective Solaris kernel module and is not a result from a problem in cdrecord. No WHAT? Solaris has a defective kernel module? Incredible! Wow ... I have to post that on lkml, another of that pets of JS is fallable!!! Enjoy --- Dr. Norbert PreiningAssociate Professor JAIST Japan Advanced Institute of Science and Technology prein...@jaist.ac.jp Vienna University of Technology prein...@logic.at Debian Developer (Debian TeX Task Force)prein...@debian.org gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- WRITTLE (vb.) Of a steel ball, to settle into a hole. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Rob W wrob0...@gmail.com wrote: try to burn it via growisofs Seems to be working for growisofs. I started it tonight with a 15+ GB iso file. Will follow up with error messages, if any. Got to go now ... Please note: the fact that this works does not verfiy that it will always work. It seems that growisofs does some heuristiics where cdrecord just asks the drive and at this point becomes a victim of the kernel problems. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Announcing cdrskin-0.7.2
Thomas Schmitt scdbac...@gmx.net wrote: Hi, When will you correct your wrong claim that states you did not copy any byte from cdrecord's sources? The claim is uphold. Note that we did already discuss this some time ago and it is obvious that you _did_ copy sources from an older version. I removed the code which was labeled as stemming from cdrdao and was not used by tested parts of libburn anyway. It obviously implemented the Reed-Solomon error correction as described in ECMA-130. One thing is to understand the math behind Reed-Solomon, quite a different thing is to understand the discretization math which leads to the tables in the cdrdao implementation. Lacking the latter math i decided to give up the inherited but never working CD raw modes of Then please inform your users that you cannot grant correctly written CDs on Lite-ON drives and that you will not be able to write SVCDs on Pioneer drives. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Norbert Preining prein...@logic.at wrote: On Di, 13 Okt 2009, Joerg Schilling wrote: As I already mentioned: the SCSI error message above was caused by a defective Solaris kernel module and is not a result from a problem in cdrecord. No WHAT? Solaris has a defective kernel module? Incredible! Wow ... I have to post that on lkml, another of that pets of JS is fallable!!! We all know that you did never send anything besides trolling to this mailing list. Your mail has been counted, you do not need to confirm your attitude anymore in future - thank you for being quiet in future! Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Announcing cdrskin-0.7.2
Hi, Then please inform your users that you cannot grant correctly written CDs on Lite-ON drives and libburn works fine with my olde LITE-ON LTR-48125S CD-RW burner. that you will not be able to write SVCDs on Pioneer drives. (Harrumph) Users ! You might not be able to write SVCDs on Pioneer drives ! (Good so ?) Users, please also note: I have no idea how to write SVCD on any drive. libburn does Mode 1 (-data) and Audio tracks. To mix them on the same media will possibly not work in your old CD player in the living room. If the player is actually a little computer then this ban on mixing will not be an issue. There are rumors that one would need Mode 2 for multi-session CDs. The only real hint for this are statements in ECMA-168 which have no influence on CD or on ISO 9660 (ECMA-119). The rumored prescription cannot apply to Audio as this is mutually exclusive with Mode 2. The rumored prescription cannot be essential with computer attached CD-ROM drives as i have a lot of experience with multi-session Mode 1 CDs meanwhile. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
try to burn it via growisofs Seems to be working for growisofs started it tonight with a 15+ GB iso Checked it this morning, seems to have finished, and I have no idea how long it took. The iso file has size of 15635996672 bytes. 15577645056/15635996672 (99.6%) @0.3x, remaining 1:05 RBU 100.1% UBU 50.0% 15582494720/15635996672 (99.7%) @0.3x, remaining 0:59 RBU 100.0% UBU 50.0% 15587442688/15635996672 (99.7%) @0.3x, remaining 0:54 RBU 100.0% UBU 50.0% 15592718336/15635996672 (99.7%) @0.4x, remaining 0:48 RBU 100.0% UBU 50.0% 15597174784/15635996672 (99.8%) @0.3x, remaining 0:43 RBU 100.0% UBU 50.0% 15602384896/15635996672 (99.8%) @0.3x, remaining 0:37 RBU 100.0% UBU 50.0% 15607660544/15635996672 (99.8%) @0.4x, remaining 0:31 RBU 84.5% UBU 50.0% 15612379136/15635996672 (99.8%) @0.3x, remaining 0:26 RBU 70.4% UBU 50.0% 15617753088/15635996672 (99.9%) @0.4x, remaining 0:20 RBU 54.4% UBU 50.0% 15622340608/15635996672 (99.9%) @0.3x, remaining 0:15 RBU 40.7% UBU 50.0% 15627681792/15635996672 (99.9%) @0.4x, remaining 0:09 RBU 24.8% UBU 50.0% 15632826368/15635996672 (100.0%) @0.3x, remaining 0:03 RBU 9.5% UBU 50.0% builtin_dd: 7634768*2KB out @ average 0.2x4390KBps /dev/rdsk/c3t0d0s0: flushing cache /dev/rdsk/c3t0d0s0: closing track /dev/rdsk/c3t0d0s0: closing session :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Rob W: Checked it this morning, seems to have finished, and I have no idea how long it took. builtin_dd: 7634768*2KB out @ average 0.2x4390KBps Not faster than 7634768*2/(0.3*4390) seconds. 3 hours 13 minutes at least. Probably rather 4 to 5 hours. Very slow. But at the end a bit too fast for USB 1. So that theory seems invalid, too. :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error Uh oh. It is still ill. Can you read all 7634768 blocks from the BD-R ? dd if=/dev/...block.device... \ of=/dev/null \ bs=2048 count=7634768 Does it mount ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Checked it this morning, seems to have finished, and I have no idea how long it took. builtin_dd: 7634768*2KB out @ average 0.2x4390KBps Not faster than 7634768*2/(0.3*4390) seconds. 3 hours 13 minutes at least. Probably rather 4 to 5 hours. Very slow. But at the end a bit too fast for USB 1. So that theory seems invalid, too. USB1 full-speed is 12Mbps or 1.5MBps, right? 0.2x4390KBps is around half the speed... Also keep in mind that if wire speed is not sufficient to sustain media speed, unit will be forced to make idle revolutions and performance can drop to *portion* of wire speed. :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error Uh oh. It is still ill. It's harmless bug. It was discussed earlier. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
Thank you Thomas for suggesting things to try. ... spoil your joy of success Let us not digress too much - remember my definition of success: # cdrecord dev=3,0,0 speed=2 driveropts=burnfree image.iso try to burn it via growisofs I have no idea how long it took Probably rather 4 to 5 hours I agree, but should only take 30 minutes, with no errors. Does it mount? Yes, I can see all of my files on the Windows machine too. Can you read all 7634768 blocks? Wow, dd is really slow. I am still waiting for results.
Re: Announcing cdrskin-0.7.2
Hi, Bill Davidsen wrote: The usual programs to generate the info create multiple files and a cuefile (see the cdrecord man page). Real cdrecord uses this cuefile to write the SVCD media, It would be interesting to see the cuefile and a ls -l of the track source files. I will probably not be able to perform the necessary CD sector preparations by the current libburn. But it could give me an idea what sector formats are used. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: cdrtools-2.01.01a66 ready
Joerg Schilling wrote: NEW features of cdrtools-2.01.01a66: *** NOTE: cdrtools is currently in a state just before a new major release. You have been saying this for several years, it has less meaning than have a nice day, so either release a new beta or release candidate, or stop promising things you can't deliver. You nit-pick other's posts, so don't complain if you get called on this. Libsiconv: - Fixed a problem in libsiconv in case that the the locale is specified as iconv:name. Cdrecord: - Better man page with repect to dev= - The cdrecord man page has been restructured. - Fixed a bug in the workaround code for a firmware bug for DVD+R media in HL-DT-ST drives. Cdda2wav (Maintained/enhanced by Jörg Schilling, originated by Heiko Eißfeldt he...@hexco.de): - Better man page with repect to dev= - The cdda2wav man page has been restructured. Readcd: - readcd now only send the Plextor specific SCSI commands for the -cxscan option in case that the drive identifies as Plextor. - Better man page with repect to dev= I will read the new man pages before commenting, but I'm happy to see work on this. TODO: - Support correct inode numbers for UDF hardlinks - Support sockets, pipes, char/blk-dev specials with UDF Another thing I will try before I comment. -- Bill Davidsen david...@tmr.com Unintended results are the well-earned reward for incompetence. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: Announcing cdrskin-0.7.2
Thomas Schmitt wrote: Hi, Then please inform your users that you cannot grant correctly written CDs on Lite-ON drives and libburn works fine with my olde LITE-ON LTR-48125S CD-RW burner. that you will not be able to write SVCDs on Pioneer drives. (Harrumph) Users ! You might not be able to write SVCDs on Pioneer drives ! (Good so ?) Users, please also note: I have no idea how to write SVCD on any drive. The usual programs to generate the info create multiple files and a cuefile (see the cdrecord man page). Real cdrecord uses this cuefile to write the SVCD media, the last (years ago) time I tried to do that with wodim it seemed to work but the media wouldn't play. This format is still (marginally) useful for small video where the quality of VCD is unacceptable and the cost between CD and DVD blanks matters. libburn does Mode 1 (-data) and Audio tracks. To mix them on the same media will possibly not work in your old CD player in the living room. If the player is actually a little computer then this ban on mixing will not be an issue. There are rumors that one would need Mode 2 for multi-session CDs. The only real hint for this are statements in ECMA-168 which have no influence on CD or on ISO 9660 (ECMA-119). The rumored prescription cannot apply to Audio as this is mutually exclusive with Mode 2. The rumored prescription cannot be essential with computer attached CD-ROM drives as i have a lot of experience with multi-session Mode 1 CDs meanwhile. Have a nice day :) Thomas -- Bill Davidsen david...@tmr.com Unintended results are the well-earned reward for incompetence. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
USB1 full-speed is 12Mbps or 1.5MBps, right? I am using USB 2.0 ports - 480 Mbps or 60 MBps. Burning DVDs on the Plextor PX-716UF drive using cdrecord from my Solaris10 (sparc) machine is pretty fast.
Re: solaris cdrecord BH08LS20 drive BD-R problems
When it comes to accuracy of information meant for general public, it's
difference between implying things and spelling them in manner that
can't be interpreted differently by different people.
1. According to 'man ata' DMA is enabled by default on Solaris 10. To my
experience with Sun W1100z it holds true.
Whis this is true for Solaris 10 x86 and hard disks, it is definitely not
true
for the other.
Original statement was Solaris 10 in general does not by default enable
DMA. Any sane person not intimately familiar with subject would
interpret that Solaris 10 never uses DMA by default.
Well, we are talking about CD/DVD/BluRay writing and it should be obvious for
a
scientist, that remarks are done here with thede constraints in mind.
General public is far from scientific. But even if it was, it would be
even more incentive to stick to most accurate formulations.
I cannot see statements of interest in the rest. If you like to prove that
there
are Sparc machines with Solaris that behave different from what all other
users
reported, please send the related information:
- exactly describe the machine type, the OS release and the drive type.
Information can be found in attachments.
- send information from prtconf -pv
Attached.
- Send the kernel verbose information from /var/adm/messages that
indicate that DMA was in fact enabled for the related drive
Boot log from /var/adm/messages is attached.
- send the eeprom(1) output that indicates that the DMA is not disabled
for CD-ROM type drive even though the low level kernel layers did
set up DMA.
eeprom output can be found in attached 'prtconf -pv' output in Node
0xf002d22c section.
- Send a cdrecord -v -checkdrive output for the drive that verifies
that the drive is capable to do IO in a speed that requires DMA and thus
indicates that DMA is really in effect.
Attached.
-
Now for the rest of subscribers. None of attached information tells DMA
story. As already mentioned on SPARC Solaris (at least up to 10)
negotiated ATA mode can be found in 'prtconf -v' output. Here is
relevant portion from system in question:
ide, instance #0
Driver properties:
name target1-dcd-options length 4
value 0x00a2.
name target0-dcd-options length 4
value 0x00a4.
name dcd_options length 4
value 0x00a4.
Here target0 is system disk and target1 - optical unit. As already
mentioned 0xa2 stands for UDMA-2. This can be confirmed experimentally
by running for example perl -e '$sz=32*1024;
while(1){syscall(173,0,?x$sz,$sz,0)}' /vol/rdsk/noname' against
recorded media and monitoring system with iostat. syscall(173) is
pread(2) and idea is to make unit deliver 1st 32KB from buffer over and
over again. Here is snippet from 'iostat 5' output:
ttydad0 sd0 nfs1 nfs2 cpu
tin tout kps tps serv kps tps serv kps tps serv kps tps serv us sy
wt id
0 16 0 00 19840 62010 000 00 10
11 79 0
0 48 2 12 19847 62010 000 009
11 80 0
0 16 0 00 19885 62110 000 006
11 83 0
0 16 0 00 19834 62010 000 009
12 79 0
sd0 is the optical unit and as per above it delivers almost 20MBps at
~11% system time. Writing naturally can't be performed at 20MBps, but 2x
DVD recording [with growisofs] consumes ~8% system time:
ttydad0 sd0 nfs1 nfs2 cpu
tin tout kps tps serv kps tps serv kps tps serv kps tps serv us sy
wt id
0 78 0 00 2752 9200 000 001
8 26 65
0 78 0 00 2900 9700 000 001
9 27 62
0 78 4 14 2694 9000 000 001
5 28 66
0 47 0 00 2854 9500 000 001
8 28 64
A.
System Configuration: Sun Microsystems sun4u
Memory size: 512 Megabytes
System Peripherals (PROM Nodes):
Node 0xf0029e64
boot-retained-page:
energystar-v3:
idprom:
.......
scsi-initiator-id: 0007
reset-reason: 'POR'
breakpoint-trap: 007f
#size-cells: 0002
model: 'SUNW,375-0096'
name: 'SUNW,Sun-Blade-100'
clock-frequency: 04fca6ea
banner-name: 'Sun Blade 100 (UltraSPARC-IIe)'
device_type: 'upa'
stick-frequency: 0054c563
Node 0xf002cff8
name: 'packages'
Node 0xf0047a58
name: 'SUNW,builtin-drivers'
Node 0xf0051a18
disk-write-fix:
name: 'deblocker'
Node 0xf0051efc
name: 'disk-label'
Node 0xf0052850
iso6429-1983-colors:
Re: solaris cdrecord BH08LS20 drive BD-R problems
Hi, Andy Polyakov wrote: USB1 full-speed is 12Mbps or 1.5MBps, right? 0.2x4390KBps is around half the speed... Yes. But 0.2x was the average. At the end the run was around 0.35x. Given a certain overhead in the USB bit stream this is slightly too much. But i just read from Rob, 5 Oct 2009: Note that my blu-ray drive is connected to my system via USB 2.0 and Rob freshly: Burning DVDs on the Plextor PX-716UF drive using cdrecord from my Solaris10 (sparc) machine is pretty fast. For USB 2 this would be truly awful performance. Does it mount? Yes, I can see all of my files on the Windows machine too. This means the first few MB of the image are readable. The bulk of file content is not tested by showing a sound directory tree. Readable file content should be unaltered. If you find content deviations without seeing i/o errors then the data was altered after leaving the realm of the burn program and before being burned to media. Wow, dd is really slow. I am still waiting for results. That's really a riddle. What USB SATA bridge would be that slow ? should only take 30 minutes, with no errors. On unformatted BD-R i achieve 9 MB/s = 28 minutes for 7634768 blocks. Plus preparations and post production. Yep. 30 minutes is realistic. With growisofs that would need option -use-the-force-luke=spare:none which Andy does mention but not recommend in http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/ With formatted BD-R you have to live with half speed. That's still about 4 times faster than what you experience now. :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: I/O error It's harmless bug. It was discussed earlier. A. Sorry for not paying attention. We are getting quite multithreaded from time to time. :)) Well, i am curious whether the media delivers all recorded blocks. A CentOS experiment with growisofs-7.1 would be interesting too. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
USB1 full-speed is 12Mbps or 1.5MBps, right? I am using USB 2.0 ports - 480 Mbps or 60 MBps. I unfortunately have no personal experience with USB storage on SPARC Solaris and can't advice on how to verify if system actually negotiated USB2 Hi-speed for unit in question. My comment was merely about Thomas' calculations. Burning DVDs on the Plextor PX-716UF drive using cdrecord from my Solaris10 (sparc) machine is pretty fast. Yes, but it doesn't exclude possibility that system failed to negotiate anticipated rate for the other unit. Though as just mentioned, I can only speculate on the matter of USB under SPARC Solaris and you should take it as such. A. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: cdrtools-2.01.01a66 ready
Bill Davidsen david...@tmr.com wrote: Joerg Schilling wrote: NEW features of cdrtools-2.01.01a66: *** NOTE: cdrtools is currently in a state just before a new major release. You have been saying this for several years, it has less meaning than have a nice day, so either release a new beta or release candidate, or stop promising things you can't deliver. You nit-pick other's posts, so don't complain if you get called on this. You are not currect: I am saying this since three releases as we are currently getting _very_ close to the mext major release. There is not much to do except reworking for the man pages. BTW: since the last major release, more than 30% of the code has been rewritten or replaced and many new funtions have been added so more than 50% of the code is new since the last final release from september 2004. There have been 7100 single file edits in 2900 edit groups, resulting in an average of aprox. 4 file edits per day during this period. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: solaris cdrecord BH08LS20 drive BD-R problems
The iso file has size of 15635996672 bytes Can you read all 7634768 blocks? Wow, dd is really slow # date Tue Oct 13 16:18:12 EDT 2009 # dd bs=2048 if=/dev/dsk/c3t0d0s0 of=/dev/null 11826176+0 records in 11826176+0 records out # date # Tue Oct 13 17:43:11 EDT 2009 That would be 24220008448 bytes (~24.2GB) growisofs pre-formatted the disc for 24.8GB It took approximately 85 minutes for the dd read, so dd read the disc at a rate around 4.75 MBps. Maybe not really really slow, but still slow. What USB SATA bridge would be that slow? The same one that is fast on the windows machine. whether the media delivers all recorded blocks The only way to verify this is to traverse through all of the files in the iso image (mounted loopback) and diff them with files on the blu-ray disc. No thanks. I trust that growisofs recorded properly. CentOS experiment with growisofs Yes, but now I need to focus on cdrecord on solaris10. How will the CentOS experiment help me with that?
