Re: mkisofs error
Be _very_ careful, genisoimage is full of bugs and creates defective filesystems. Do not use it, genisoimage is unmaintained and does not even support files 4 GB! Other well known bugs in genisoimage create defective directory entries for . and ... This is because genisoimage is based on a 5 year old version of mkisofs with additional bugs added that never have been in the original software. Mkisofs has no known bugs and is well maintained. I see no reason why mkisofs should be the cause for your problem... Well you did not describe the problem in a way that could allow to analyse the background. Possible reasons for your problem could be read errors on the medium, check using: readcd f=/dev/null whether the medium is fully readable. Another possible reason could be a problem in the filesystem driver of the kernel. If a file gives a read error, there should be a kernel message related to the problem. If you are able to extract the file using isoinfo using the ISO-9660 name of the file (be careful not to use the defective isoinfo that comes with cdrkit), the problem is definitely not in mkisofs. BTW: do you use a recent or an outdated mkisofs? The latest version of mkisofs is 2.01.01a66 and FreeBSD by default unfortunately distributes extremely outdated versions. 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CD writing fails on P6T motherboard with Pioneer cdwriter
Hi, you are using an _extremely_ outdated version of cdrtools. Upgrade to a recent cdrtools version ftp://ftp.berlios.de/pub/cdrecord/alpha/ If you still have problems with writing this audio CD, try to write in -raw96r mode. The pioneer drives have some strange firmware limitations and cannot write some Cds due to a broken memory layout in the firmware of the writer. 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CD writing fails on P6T motherboard with Pioneer cdwriter
Yuri y...@rawbw.com wrote: Yes, I used cdrtools 2.01 from FreeBSD ports which is from ~2004. For some reason all more recent version all labeled as 'alphas'. Upgrading to Cdrecord-ProDVD-ProBD-Clone 2.01.01a62 didn't help. Adding -raw96r option causes this error message: cdrecord: SAO RAW writing only makes sense in clone mode. And adding -clone on top of that causes this error message: cdrecord: SAO RAW writing not yet implemented. I have no idea what you misstyped to create this error message. Did you use -sao together with -raw96r? 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CD writing fails on P6T motherboard with Pioneer cdwriter
Yuri y...@rawbw.com wrote: I used -dao. Removing -dao. Removing -dao made my command line like this: cdrecord dev=5,0,0 speed=4 -raw96r -v -pad -useinfo -text *.wav And now it fails with this log: Cdrecord-ProDVD-ProBD-Clone 2.01.01a62 (i386-unknown-freebsd7.2) Copyright (C) 1995-2009 J???rg Schilling TOC Type: 0 = CD-DA scsidev: '5,0,0' scsibus: 5 target: 0 lun: 0 Using libscg version 'schily-0.9'. SCSI buffer size: 65536 atapi: 0 Device type : Removable CD-ROM Version : 0 Response Format: 2 Capabilities : Vendor_info : 'PIONEER ' Identifikation : 'DVD-RW DVR-112D' Revision : '1.21' ... Track 10: audio 95 MB (09:27.22) no preemp pregapsize: 305 Track 11: audio 27 MB (02:41.44) no preemp pregapsize: 332 Total size: 586 MB (58:05.80) = 261435 sectors Lout start: 586 MB (58:07/60) = 261435 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Disk Is not unrestricted Disk Is not erasable Disk sub type: Medium Type B, low Beta category (B-) (4) ATIP start of lead in: -11834 (97:24/16) ATIP start of lead out: 359849 (79:59/74) Disk type: Short strategy type (Phthalocyanine or similar) Manuf. index: 24 Manufacturer: SONY Corporation Capacity Blklen/Sparesz. Format-type Type 0 2048 0x00 Unformated or Blank Media Blocks total: 359849 Blocks current: 359849 Blocks remaining: 98414 Starting to write CD/DVD/BD at speed 4 in real RAW/RAW96R mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is OFF. Performing OPC... cdrecord: WARNING: Drive returns wrong startsec (-150) using -11834 from ATIP Writing lead-in at sector -11834 cdrecord: Input/output error. write_g1: scsi sendcmd: cmd timeout after 41.429 (40) s CDB: 2A 00 FF FF D4 02 00 00 1A 00 cmd finished after 41.429s timeout 40s write leadin data: error after 1400256 bytes cdrecord: Could not write Lead-in. Writing time: 56.827s cdrecord: fifo had 64 puts and 0 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. What error message did cdrecord print? 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CD writing fails on P6T motherboard with Pioneer cdwriter
Yuri y...@rawbw.com wrote: I've sent you the entire output. This line: cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. was the last. And it returned exit code 255. You did not send the SCSI error message 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CD writing fails on P6T motherboard with Pioneer cdwriter
Yuri y...@rawbw.com wrote: Joerg Schilling wrote: You did not send the SCSI error message Jörg I've sent the entire output printed to stdout/stderr. This line in there talks about timeout: cdrecord: Input/output error. write_g1: scsi sendcmd: cmd timeout after 41.429 (40) s OK, if this is a timeout, then you would need to find why this timeout happens. There are two probabilities: 1) A cabling problem 2) This is PATA and you have a hard disk at the same cable. In case of 1), check or replace the cables, make sure that the OS is set up for UDMA to the drive (this requires a 80 wire cable - unfortunately the drive manufacturers deliver only 40 wire cable). In case of 2) use the -immed option. 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [perl] sysopen(CD, /dev/cd0, O_RDONLY | O_NONBLOCK) fails
Bruce Cran br...@cran.org.uk wrote: cd0 is also what you get if you use atapicam (ATAPI is SCSI over ATA from what I remember) - for example cdrecord has traditionally used it No, with CAM on FreeBSD /dev/xpt is opened and then the route to the device is extablished via the SCSI address. when writing CDs. Apparently the OP has the issue both when using atapicam (/dev/cd0) and the normal ata node /dev/acd0. Cdrecord did this in 1998 and before - a long time ago. 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Copying audio CD with dd/cdrecord produces unplayable CD
I am trying to copy an audio CD. First I've ran: dd if=/dev/acd0tN of=track-N.cdr bs=2352 for every track. This gets raw track files. Secondly I run: cdrecord -v -dao -audio $* dev=2,0,0 speed=4 This is supposed to recreate the original CD. But when I try to play it I can hear only noise. Well, you should not expect to get a usable read result from dd. It is much better to use cdda2wav -vall to read the original and if you later use cdrecord -useinfo you will get a correct copy. BTW: cdrecord of course works in a platform independent way and thus expects raw audio data in standard network byte order Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wrong times written by mkisofs?
Bob Johnson [EMAIL PROTECTED] wrote: Let me asume you use a _recent_ mkisofs and set up a correct timezone... [...] What do you get from mkisofs -version? mkisofs 2.01 (i386-unknown-freebsd6.2) This is nearly 4 years old, why don't you use a recent version? recent is 2.01.01a37 What timezone do you have (how many hours from GMT and which location)? U.S. Eastern Standard Time (EST = GMT-5) What do you have in the TZ= variable? It seems to be empty. So you run your system in GMT? What do you see with TZ=GMT ls -l ToJoe? # TZ=GMT ls -l /mnt total 62113 -rw--- 1 bobj bobj 2246671 Jan 19 12:22 IMG_0660_080115_2348.JPG -rw--- 1 bobj bobj 3346787 Jan 19 12:22 IMG_0661_080116_0524.JPG You see, it did not change These times are the correct LOCAL time, not GMT. The following are five hours off: # TZ=EST ls -l /mnt total 62113 -rw--- 1 bobj bobj 2246671 Jan 19 07:22 IMG_0660_080115_2348.JPG -rw--- 1 bobj bobj 3346787 Jan 19 07:22 IMG_0661_080116_0524.JPG You know these times already? Something is wrong anyway, but I cannot help from remote Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wrong times written by mkisofs?
Giorgos Keramidas [EMAIL PROTECTED] wrote: mkisofs 2.01 (i386-unknown-freebsd6.2) This is nearly 4 years old, why don't you use a recent version? recent is 2.01.01a37 FWIW, 2.01 is the version available in the Ports tree as `sysutils/cdrtools'. The 2.01.01a37 version is available too, as `cdrtools-devel'. But stable versions are dead versions because they don't change. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wrong times written by mkisofs?
Irecently built a CD of images to give to a friend. I noticed the timestamps displayed when I list the CD contents are five hours earlier than they should be. Five hours matches my GMT offset. This is a dual-boot system with Win XP, so the hardware clock is set to local time. E.g. a file on my hard drive has a correct timestamp -rw--- 1 bobo bobo 2246671 Jan 19 12:22 IMG_0660_080115_2348.JPG while the same file on the resulting CD looks like -rw--- 1 bobo bobo 2246671 Jan 19 07:22 IMG_0660_080115_2348.JPG The date command returns the correct local time. Did I do something incorrectly, or is this a bug in mkisofs? It appears to me that mkisofs decided to correct for GMT offset when it shouldn't have. The sequence of operations I followed is below. Let me asume you use a _recent_ mkisofs and set up a correct timezone... Then you found a FreeBSD kernel bug in your filesystem code. BTW: The first bug I found in mkisofs (this was in 1995) was a TZ bug and mkisofs did use the wrong sign for the timezone offset. Since this has been fixed, the only reported problems where in effect +- 24 hours from New-year. What do you get from mkisofs -version? What timezone do you have (how many hours from GMT and which location)? What do you have in the TZ= variable? What do you see with TZ=GMT ls -l ToJoe? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cdrtools versions and hal
I recently removed sysutils/cdrtools and installed cdrtools-devel instead because cdrecord in cdrtools doesn't have prodvd included and cdrtools-devel does (helped by a recent post from the author pointing out that cdrecord from cdrtools is quite old). FreeBSD uses an extremely outdated cdrtools vertsion for unknown reasons. Anyway, I just csupped my ports and ran portmanager -s which told me that cdrtools-2.01_6 is missing and hal-0.5.8.20070909 is built with OLD dependency: cdrtools-2.01_6. Can I make cdrtools-devel to be the dependency of hal so that it will get rebuilt with it and make the cdrtools missing message disappear? Will I break things if I do? Is hald on FreeBSD working or has it the same conceptional bugs as on Linux? Hald on Solaris is based on the old vold support code in the disk driver sd.c Hald on Linux does it's own test unit ready and seems to do incorrect conclusions from state transitions. Linux in addition offers more than one driver entry for the devices that are able to send conflicting simultaneous commands. Hal in general is missing a concept for dealing with multi session writes. On Solaris, it wait until the tray is opened again after an empty CD/DVD has been inserted. What is the state on FreeBSD? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CD/DVD writer no longer works
Cdrecord-Clone 2.01 (i386-unknown-freebsd6.0) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,1,0' scsibus: 1 target: 1 lun: 0 Using libscg version 'schily-0.8'. SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'TSSTcorp' Identifikation : 'CD-RW TS-H292B' Revision : 'DE03' Device seems to be: Generic mmc CD-RW. Current: 0x Profile: 0x000A Profile: 0x0009 Profile: 0x0008 1) you are using an extremely outdated cdrecord version. A recent version is here: ftp://ftp.berlios.de/pub/cdrecord/alpha/ Use 2.01.01a36 2) your drive seems to have problems with the medium or is defective as it reports medium not present and no current profile is selected. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
