Re: 7.2 burncd and cdrecord problem
On Fri, Aug 14, 2009 at 08:23:49PM +0200, Fernando Apestegu?a typed: Hi all, I'm trying to get my CD drive to work without so much success. Reading is fine, but when I try to burn a CD I get errors in dmesg. Using cdrecord -blank=fast dev=3,0,0 I get: [...] Using generic SCSI-3/mmc CD-ROM driver (mmc_cd). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD at speed 18 in real BLANK mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. This drive or media does not support the 'BLANK media' command cdrecord: Cannot blank disk, aborting. cdrecord: Some drives do not support all blank types. cdrecord: Try again with cdrecord blank=all. So what happened when you tried the blank=all option instead of your blank=fast? You did try that, didn't you? Ruben ___ 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: 7.2 burncd and cdrecord problem
On Sat, Aug 15, 2009 at 12:20 PM, Ruben de Grootmai...@bzerk.org wrote: On Fri, Aug 14, 2009 at 08:23:49PM +0200, Fernando Apestegu?a typed: Hi all, I'm trying to get my CD drive to work without so much success. Reading is fine, but when I try to burn a CD I get errors in dmesg. Using cdrecord -blank=fast dev=3,0,0 I get: [...] Using generic SCSI-3/mmc CD-ROM driver (mmc_cd). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD at speed 18 in real BLANK mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. This drive or media does not support the 'BLANK media' command cdrecord: Cannot blank disk, aborting. cdrecord: Some drives do not support all blank types. cdrecord: Try again with cdrecord blank=all. So what happened when you tried the blank=all option instead of your blank=fast? You did try that, didn't you? I did, sorry I didn't mention that. It shows the same errors. Ruben ___ 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: 7.2 burncd and cdrecord problem
I'm trying to get my CD drive to work without so much success. Reading is fine, but when I try to burn a CD I get errors in dmesg. Using cdrecord -blank=fast dev=3,0,0 I get: First, I hope that you are using sysutils/cdrtools-devel rather than sysutils/cdrtools. The latter is several years out of date, and the upstream maintainer of the software has said that no one should be using it, but the maintainer of the FreeBSD port has so far been unwilling to update it. ... And dmesg shows: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 It is not unusual for some errors to appear, even during normal operation, so these don't necessarily indicate a problem, although it was good that you posted them. You should run the cdrecord command with -vv (yes, two v's) to get verbose error messages from cdrecord. This should give you a better idea of why cdrecord is failing. If the error messages from -vv are not enough, you can also add -VV, although this affects the timing of the operations, and should be used with care when recording. I have had problems like this in the past, when a disk was corrupted, and cdrecord balked at blanking it. I used blank=all with either the -immed flag, or the -force flag, or both, to solve the problems. If you are using cdrtools, you should probably use the cd(4) driver together with atapicam(4), rather than the acd(4) driver. To prevent possible problems, it is safer to prevent both drivers from attaching to the same device. I usually remove: device atapicd from my kernel, and just use: device ata device atapicam device scbus device cd device pass I don't know whether it is possible to disable the acd(4) driver using just loader.conf(5), device.hints(5), or some other means at boot- or run-time, but you could look into that if you don't want to go to the trouble of removing it from your kernel. b. ___ 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: 7.2 burncd and cdrecord problem
On Sat, Aug 15, 2009 at 8:02 PM, b. f.bf1...@googlemail.com wrote: I'm trying to get my CD drive to work without so much success. Reading is fine, but when I try to burn a CD I get errors in dmesg. Using cdrecord -blank=fast dev=3,0,0 I get: First, I hope that you are using sysutils/cdrtools-devel rather than sysutils/cdrtools. The latter is several years out of date, and the upstream maintainer of the software has said that no one should be using it, but the maintainer of the FreeBSD port has so far been unwilling to update it. ... And dmesg shows: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 It is not unusual for some errors to appear, even during normal operation, so these don't necessarily indicate a problem, although it was good that you posted them. You should run the cdrecord command with -vv (yes, two v's) to get verbose error messages from cdrecord. This should give you a better idea of why cdrecord is failing. If the error messages from -vv are not enough, you can also add -VV, although this affects the timing of the operations, and should be used with care when recording. I have had problems like this in the past, when a disk was corrupted, and cdrecord balked at blanking it. I used blank=all with either the -immed flag, or the -force flag, or both, to solve the problems. Honestly I didn't think this was the problem, but it seems I've had a bad virgin CD set. Two of them (of a set of 5) seem to work fine. I can write, rewrite and blank them. Aaarrghh! sorry for the noise. Nevertheless, I will try to update to cdrtools-devel since I have cdrtools installed Thanks to all of you. If you are using cdrtools, you should probably use the cd(4) driver together with atapicam(4), rather than the acd(4) driver. To prevent possible problems, it is safer to prevent both drivers from attaching to the same device. I usually remove: device atapicd from my kernel, and just use: device ata device atapicam device scbus device cd device pass I don't know whether it is possible to disable the acd(4) driver using just loader.conf(5), device.hints(5), or some other means at boot- or run-time, but you could look into that if you don't want to go to the trouble of removing it from your kernel. b. ___ 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
7.2 burncd and cdrecord problem
Hi all, I'm trying to get my CD drive to work without so much success. Reading is fine, but when I try to burn a CD I get errors in dmesg. Using cdrecord -blank=fast dev=3,0,0 I get: [...] Using generic SCSI-3/mmc CD-ROM driver (mmc_cd). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD at speed 18 in real BLANK mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. This drive or media does not support the 'BLANK media' command cdrecord: Cannot blank disk, aborting. cdrecord: Some drives do not support all blank types. cdrecord: Try again with cdrecord blank=all. And dmesg shows: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 Using burncd blank I get: burncd: ioctl(CDRIOCBLANK): Input/output error and in dmesg: acd0: FAILURE - BLANK_CMD ILLEGAL REQUEST asc=0x30 ascq=0x05 The drive works perfectly with other OS, so I don't think the hardware is the problem. The device is identified as: acd0: DVDR TSSTcorp CDDVDW TS-H653N/0208 at ata3-master SATA150 I have scbus, atapicd and atapicam in my kernel configuration. Any ideas? Thanks in advance. ___ 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: 7.2 burncd and cdrecord problem
First thing I'd suspect is that your drive is a read-only, write-only, but no rewrite, so that means it's unable to blank RW medium. The 'DVDR' and CDDVDW both indicate a write once kind of mindset. does the bezel on the drive itself say rewrite anywhere? --TJ On 8/14/09, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: Hi all, I'm trying to get my CD drive to work without so much success. Reading is fine, but when I try to burn a CD I get errors in dmesg. Using cdrecord -blank=fast dev=3,0,0 I get: [...] Using generic SCSI-3/mmc CD-ROM driver (mmc_cd). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD at speed 18 in real BLANK mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. This drive or media does not support the 'BLANK media' command cdrecord: Cannot blank disk, aborting. cdrecord: Some drives do not support all blank types. cdrecord: Try again with cdrecord blank=all. And dmesg shows: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 Using burncd blank I get: burncd: ioctl(CDRIOCBLANK): Input/output error and in dmesg: acd0: FAILURE - BLANK_CMD ILLEGAL REQUEST asc=0x30 ascq=0x05 The drive works perfectly with other OS, so I don't think the hardware is the problem. The device is identified as: acd0: DVDR TSSTcorp CDDVDW TS-H653N/0208 at ata3-master SATA150 I have scbus, atapicd and atapicam in my kernel configuration. Any ideas? Thanks in advance. ___ 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 ___ 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: 7.2 burncd and cdrecord problem
On Fri, 14 Aug 2009 18:47:48 -0600, Tim Judd taj...@gmail.com wrote: First thing I'd suspect is that your drive is a read-only, write-only, but no rewrite, so that means it's unable to blank RW medium. The 'DVDR' and CDDVDW both indicate a write once kind of mindset. does the bezel on the drive itself say rewrite anywhere? Check the output of % cdrecord -prcap dev=3,0,0 which will list what the drive does support. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
