Re: cdrtools /devel and wodim broken
Ready to start test for failing command? Enter CR to continue: ** Testing for failed SCSI command. scgcheck: Input/output error. inquiry: scsi sendcmd: retryable error CDB: 12 00 00 FF 24 00 status: 0x0 (GOOD STATUS) cmd finished after 0.013s timeout 40s -- SCSI Transport return != SCG_NO_ERROR (1) -- SCSI status byte set to 0 (0x0) -- SCSI failed command test FAILED You seem to have a general problem with correct error reporting in SCSI with your kernel SCSI transport. Please try to contact the maintainer of this driver. 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Joerg Schilling-3 wrote: You seem to have a general problem with correct error reporting in SCSI with your kernel SCSI transport. Please try to contact the maintainer of this driver. Thanks for support, I have pinged him already. ragards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p30086322.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
on 28/10/2010 00:08 Jakub Lach said the following: Sean C. Farley-2 wrote: For me, the solution appeared to be setting the grace time to three seconds to avoid the slowdown of the drive: gracetime=3 At least, the disc worked on subsequent burns this way. Jakub, you may try to see if this setting helps. No, gracetime doesn't help. Maybe Alexander Motin could shed some light on (ahci?) problem? So maybe it's worth while getting in contact with him? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Hi, your problem: Track 01:0 of 2858 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 20 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid)=20 cmd finished after 23.946s timeout 200s is caused by a bug in a driver in the kernel. Status byte == 2 (Check Condition) together with empty sense data and unset sense key is impossible. Cdrecord can only behave in a useful way if SCSI error messages are correctly returned by the kernel. I recommend you to run scgcheck in order to find whether the driver yiu are using always behaves incorectly or whether this may be a result os a situation the autor of the driver did not expect. If you don't know how to run scgcheck, you may start with scgcheck -auto. 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
So maybe it's worth while getting in contact with him? I wanted to confirm problem is related to ahci before bugging him directly. I'm long time ahci user and would like to retain it, it would be nice If somebody with working cdrecord would load ahci for a test (by default it's not used in GENERIC) + run scgcheck. Scgcheck 3.00 (amd64-unknown-freebsd8.1) SCSI user level transport library ABI checker. Copyright (C) 1998-2008 Jörg Schilling ** Checking whether your implementation supports to scan the SCSI bus. Trying to open device: '(NULL POINTER)'. Using libscg version 'schily-0.9' Max DMA buffer size: 65536 scsibus0: 0,0,0 0) '' '' '' NON CCS Disk 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) 'HL-DT-ST' 'DVDRAM GSA-U20N ' 'HX11' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * -- SCSI scan bus test PASSED For the next test we need to open a single SCSI device. Best results will be obtained if you specify a modern CD-ROM drive. No target specified, trying to find one... Using dev=1,0,0. Enter SCSI device name [1,0,0]: Trying to open device: '1,0,0'. Using libscg version 'schily-0.9' Max DMA buffer size: 65536 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'DVDRAM GSA-U20N ' Revision : 'HX11' Ready to start test for second SCSI open? Enter CR to continue: First SCSI open OK - device usable ** Checking for second SCSI open. Second SCSI open for same device succeeded, 1 additional file descriptor(s) used. Second SCSI open is usable Closing second SCSI. Checking first SCSI. First SCSI open is still usable -- Second SCSI open test PASSED. First SCSI open is still usable Ready to start test for succeeded command? Enter CR to continue: ** Checking for succeeded SCSI command. Executing 'inquiry' command on Bus 1 Target 0, Lun 0 timeout 40s CDB: 12 00 00 00 24 00 cmd finished after 0.001s timeout 40s Inquiry Data : 05 80 00 32 5B 00 00 00 48 4C 2D 44 54 2D 53 54 44 56 44 52 41 4D 20 47 53 41 2D 55 32 30 4E 20 48 58 31 31 -- SCSI succeeded command test PASSED Ready to start test for failing command? Enter CR to continue: ** Testing for failed SCSI command. scgcheck: Input/output error. inquiry: scsi sendcmd: retryable error CDB: 12 00 00 FF 24 00 status: 0x0 (GOOD STATUS) cmd finished after 0.013s timeout 40s -- SCSI Transport return != SCG_NO_ERROR (1) -- SCSI status byte set to 0 (0x0) -- SCSI failed command test FAILED Ready to start test for sense data count? Enter CR to continue: ** Testing for SCSI sense data count. ** Testing if at least CCS_SENSE_LEN (18) is supported... Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0x00: expected: 18 reported: 32 max found: 0 Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0xFF: expected: 18 reported: 32 max found: 18 -- Wanted 18 sense bytes, got it. -- Libscg says 32 sense bytes but got (18) ** Testing for 32 bytes of sense data... Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0x00: expected: 32 reported: 32 max found: 0 Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0xFF: expected: 32 reported: 32 max found: 32 -- Wanted 32 sense bytes, got it. -- Got a maximum of 32 sense bytes -- SCSI sense count test FAILED Ready to start test for working DMA residual count? Enter CR to continue: ** Testing for working DMA residual count. ** Testing for working DMA residual count == 0. CDB cnt: 36 DMA cnt: 36 got really: 36 (System says: RDMA cnt: 36 resid 0) CDB cnt: 36 DMA cnt: 36 got really: 36 (System says: RDMA cnt: 36 resid 0) -- Wanted 36 bytes, got it. -- SCSI DMA residual count == 0 test PASSED Ready to start test for working DMA residual count == DMA count? Enter CR to continue: CDB cnt: 0 DMA cnt: 36 got really: 0 (System says: RDMA cnt: 36 resid 0) CDB cnt: 0 DMA cnt: 36 got really: 0 (System says: RDMA cnt: 36 resid 0) -- Wanted 0 bytes, got it. -- Libscg says 36 bytes but got (0) -- SCSI DMA residual count == DMA count test FAILED -- SCSI DMA residual count not working - no further tests -- SCSI transport code test NOT YET READY regards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p30077727.html Sent from the
Re: cdrtools /devel and wodim broken
Sean C. Farley-2 wrote: For me, the solution appeared to be setting the grace time to three seconds to avoid the slowdown of the drive: gracetime=3 At least, the disc worked on subsequent burns this way. Jakub, you may try to see if this setting helps. No, gracetime doesn't help. Maybe Alexander Motin could shed some light on (ahci?) problem? thanks for assistance, Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p30071221.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
You wrote: # cdrecord(wodim) dev=1,0,0 -v -data *.iso Track 01:0 of 2858 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 22.883s timeout 40s write track data: error after 0 bytes wodim: A write error occured. wodim: Please properly read the error message above. Writing time: 32.681s Average write speed 77.7x. wodim is a dead end from a 6 year old version of cdrecord with the DVD support ripped off and replaced by something broken. But there have been even more bugs added to wodim and it is not under development since May 2007. If cdrecord gives the same message, I encourage you to make a kernel bug report. This message is a hint to a serious kernel problem. A sense key value -1 cannot happen, so you need to find out why the SCSI command has not been transported correctly by the kernel. 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Joerg Schilling-3 wrote: wodim is a dead end from a 6 year old version of cdrecord with the DVD support ripped off and replaced by something broken. But there have been even more bugs added to wodim and it is not under development since May 2007. If cdrecord gives the same message, I encourage you to make a kernel bug report. This message is a hint to a serious kernel problem. A sense key value -1 cannot happen, so you need to find out why the SCSI command has not been transported correctly by the kernel. Hi Jörg. I usually prefer cdrtools, wodim was convenient way to try old code. After booting GENERIC kernel + ahci driver and compiling cdrtools release problem is still present. Full message. cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,0,0' scsibus: 1 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: 'HL-DT-ST' Identifikation : 'DVDRAM GSA-U20N ' Revision : 'HX11' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: DVD-R sequential recording Profile: DVD-RAM Profile: DVD-R sequential recording (current) Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R Profile: CD-RW Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 1114112 = 1088 KB Drive pbuf size: 1966080 = 1920 KB Drive DMA Speed: 15100 kB/s 85x CD 10x DVD 3x BD FIFO size : 4194304 = 4096 KB Track 01: data 2858 MB Total size: 2858 MB = 1463428 sectors Current Secsize: 2048 Total power on hours: 0 Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 835068 Starting to write CD/DVD/BD at speed 8 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is ON. Turning BURN-Free off Starting new track at sector: 0 Track 01:0 of 2858 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 20 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 23.946s timeout 200s write track data: error after 0 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. Writing time: 29.002s Average write speed 74.7x. Fixating... Fixating time: 22.355s cdrecord: fifo had 64 puts and 1 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. I destroyed all my spare media, so I'm also spared from burning problems for now ;) I'm quite puzzled that only I have reported such problems, it's like I'm on CURRENT again.. best regards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p30056250.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
On 10/26/10, Jakub Lach jakub_l...@mailplus.pl wrote: Joerg Schilling-3 wrote: wodim is a dead end from a 6 year old version of cdrecord with the DVD support ripped off and replaced by something broken. But there have been even more bugs added to wodim and it is not under development since May 2007. If cdrecord gives the same message, I encourage you to make a kernel bug report. This message is a hint to a serious kernel problem. A sense key value -1 cannot happen, so you need to find out why the SCSI command has not been transported correctly by the kernel. Hi Joerg. I usually prefer cdrtools, wodim was convenient way to try old code. After booting GENERIC kernel + ahci driver and compiling cdrtools release problem is still present. Full message. cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Joerg Schilling TOC Type: 1 = CD-ROM scsidev: '1,0,0' scsibus: 1 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: 'HL-DT-ST' Identifikation : 'DVDRAM GSA-U20N ' Revision : 'HX11' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: DVD-R sequential recording Profile: DVD-RAM Profile: DVD-R sequential recording (current) Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R Profile: CD-RW Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 1114112 = 1088 KB Drive pbuf size: 1966080 = 1920 KB Drive DMA Speed: 15100 kB/s 85x CD 10x DVD 3x BD FIFO size : 4194304 = 4096 KB Track 01: data 2858 MB Total size: 2858 MB = 1463428 sectors Current Secsize: 2048 Total power on hours: 0 Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 835068 Starting to write CD/DVD/BD at speed 8 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is ON. Turning BURN-Free off Starting new track at sector: 0 Track 01:0 of 2858 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 20 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 23.946s timeout 200s write track data: error after 0 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. Writing time: 29.002s Average write speed 74.7x. Fixating... Fixating time: 22.355s cdrecord: fifo had 64 puts and 1 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. I destroyed all my spare media, so I'm also spared from burning problems for now ;) And what kind of spare media was that? I'm quite puzzled that only I have reported such problems, it's like I'm on CURRENT again.. I burned bunch of DVD-R, DVD+R and DVD+R DL on FreeBSD 9.0 without any problems, using growisofs from ports. Only problem I ever had was mounting multi-sesion after 4GB (but -r flag is nice workaround). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Paul B Mahol wrote: And what kind of spare media was that? DVD-R, to be honest I didn't have this kind of problems on 8-CURRENT :). regards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p30058682.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
I have problem in burning DVD with ahci on 9-CURRENT. without ahci everything works fine. With or without ahci, burning CD is okay. -- Buganini ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
On Tue, 26 Oct 2010, Paul B Mahol wrote: On 10/26/10, Jakub Lach jakub_l...@mailplus.pl wrote: Joerg Schilling-3 wrote: wodim is a dead end from a 6 year old version of cdrecord with the DVD support ripped off and replaced by something broken. But there have been even more bugs added to wodim and it is not under development since May 2007. If cdrecord gives the same message, I encourage you to make a kernel bug report. This message is a hint to a serious kernel problem. A sense key value -1 cannot happen, so you need to find out why the SCSI command has not been transported correctly by the kernel. Hi Joerg. I usually prefer cdrtools, wodim was convenient way to try old code. After booting GENERIC kernel + ahci driver and compiling cdrtools release problem is still present. *snip* I burned bunch of DVD-R, DVD+R and DVD+R DL on FreeBSD 9.0 without any problems, using growisofs from ports. Only problem I ever had was mounting multi-sesion after 4GB (but -r flag is nice workaround). Personally, I have had trouble burning to a DVD+R using cdrecord. DVD+RW has generally worked for me on my workstation, however, I noticed something interesting last night. When trying to burn a recovery disc using my laptop onto a DVD-RW, a pause occurred near the start of the burn, maybe after two blocks were written, with the disc completing the burn successfully. I use quotes because the disc did not boot. I am not sure why exactly it would fail (the disc may have been blank, but I do not recall), but here is my observation: 1. cdrecord starts examining the disc. 2. Drive spins up. 3. During grace time before burn the drive starts to slow. 4. Burn starts. 5. cdrecord (or driver or drive) pauses a brief amount of time. I think this is what happened with the DVD+R on my workstation when the drive increased its speed. 6. Drive spins up. 7. Burn continues until end. For me, the solution appeared to be setting the grace time to three seconds to avoid the slowdown of the drive: gracetime=3 At least, the disc worked on subsequent burns this way. Jakub, you may try to see if this setting helps. Sean -- s...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Warren Block wrote: I've had mixed success with cdrecord (sysutils/cdrtools-devel) over the years. Although growisofs is reputed to be less correct, I can't recall it ever having a problem. Isn't cdrtools dependency of growisofs? regards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p30048354.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
On Mon, 25 Oct 2010, Jakub Lach wrote: Warren Block wrote: I've had mixed success with cdrecord (sysutils/cdrtools-devel) over the years. Although growisofs is reputed to be less correct, I can't recall it ever having a problem. Isn't cdrtools dependency of growisofs? Yes, although maybe for mkisofs, not the DVD recording code. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Andriy Gapon wrote: on 16/10/2010 20:21 Jakub Lach said the following: No, I don't use hal. Since when it's requirement? Hm, why did you decide that it is a requirement? I just asked a question, and thanks for the answer. I thought this was that stupid mistake on my part. Sorry for confusion. Yes, wodim is based on earlier cdrecord branch, that's why I checked it too, problems started after cdrtools got updated, but I wanted to rule it out as coincidence, because I just rarely burn cd/dvds. BTW, it is in ports, /usr/ports/sysutils/cdrkit/. best regards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29983168.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Forgot to mention device. cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 cd0: HL-DT-ST DVDRAM GSA-U20N HX11 Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) Previously it worked. -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29978949.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
on 16/10/2010 17:26 Jakub Lach said the following: Hello. Usually attempting to write DVD-R bombs out, after writing can't fixate DVD+R. Increasing timeout helps with fixating, but following error just destroys media. Any stupid mistake on my part? And you have hald running? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
Andriy Gapon wrote: on 16/10/2010 17:26 Jakub Lach said the following: Hello. Usually attempting to write DVD-R bombs out, after writing can't fixate DVD+R. Increasing timeout helps with fixating, but following error just destroys media. Any stupid mistake on my part? And you have hald running? -- Andriy Gapon No, I don't use hal. Since when it's requirement? -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29979695.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
On Sat, 16 Oct 2010, Jakub Lach wrote: Usually attempting to write DVD-R bombs out, after writing can't fixate DVD+R. Increasing timeout helps with fixating, but following error just destroys media. Any stupid mistake on my part? # cdrecord(wodim) dev=1,0,0 -v -data *.iso Isn't wodim a branch of the real cdrecord? I can't find it in ports. Track 01:0 of 2858 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 22.883s timeout 40s I've had mixed success with cdrecord (sysutils/cdrtools-devel) over the years. Although growisofs is reputed to be less correct, I can't recall it ever having a problem. Oh, and I don't recall hal causing problems lately. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cdrtools /devel and wodim broken
on 16/10/2010 20:21 Jakub Lach said the following: No, I don't use hal. Since when it's requirement? Hm, why did you decide that it is a requirement? I just asked a question, and thanks for the answer. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
