burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Input/output error
Hello, I get this error when I try to write (under root) a CD-RW or CD-R as is found in handbook: besa# burncd data FC-5-i386-disc1.iso fixate burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Input/output error Here are my (SMP) system details: besa# uname -a FreeBSD besa.org 6.1-STABLE FreeBSD 6.1-STABLE #24: Thu Jun 22 21:36:23 EEST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/besa i386 besa# dmesg | grep acd acd0: DVDR ASUS DRW-1608P2S/1.37 at ata1-master UDMA66 acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 Is there any way to make it work? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
burncd: ioctl(CDRIOCFLUSH): Input/output error
Hi, When I try to burn data with burncd here what I get : written this track 136368 KB total 136368 KB only wrote -1 of 32768 bytes: Input/output error burncd: ioctl(CDRIOCFLUSH): Input/output error and in dmesg : acd0: timeout waiting for ATAPI ready after it's impossible to access cd drive without rebooting. trying atacontrol reinit 1 get me this : Master: no device present Slave: no device present in dmesg : acd0: WARNING - removed from configuration I've tried to include device atapicam and to burn with cdrecord, same result. another weird thing is that when I'm perfoming a test burnd, it's always successful... here is some details on my computer : Laptop Medion FreeBSD 5.3 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2390.31-MHz 686-class CPU) atapci0: SiS 962/963 UDMA133 controller port 0x1000-0x100f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ata0-master: DMA limited to UDMA33, non-ATA66 cable or device ad0: 38154MB HITACHI DK23DA-40/00J0A0A1 [77520/16/63] at ata0-master UDMA33 acd0: CDRW QSI CD-RW/DVD-ROM SBW-241/VF02 at ata1-master UDMA33 Thanks for any help. -- Guzman [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
burncd + ioctl
FBSD 4.10 $ burncd -s4 -f/dev/cdrom erase erasing CD, please wait.. burncd: ioctl(CDRIOCBLANK): Device busy everyone seems to have this problem, and i have had it myself for years. most times, powering off/on fixes it - but if that is a satisfactory fix for FBSD - i may as well use MS Windows. this time, no amount of powering off/on is fixing the problem. i have tried 10 different blank CD's (the problem seems to occur with blanks most often - usually occuring after a burncd operation is aborted). i have seen the bug reports closed with the advice of turning off DMA, but after trying every single 'atacontrol' option, nothing changes. everything works ok as long as i use CD's that have been written at one time, but nothing works with 'from the store' blanks now. yet the same drive and CD's work under MS Windows just fine. please fix this problem. it's a real pain. and it's been going on for years. problem reports shouldn't be closed because someone resolved something by powering off and on. that's MS technique. i don't suppose i will hear it is fixed, and i don't suppose anyone has a sure fire way to get around it - there are no satisfactory answers on google or in the maillists or bug reports. so for whatever it's worth, the problems continue. -- [as an aside, why isn't it 'atactl', i hate having to type out the whole word - it feels so 'boneheaded' - and how about some consistency - sometimes it's 'ctl' then 'cntl' then 'control' - good grief]. [as another aside - i have been using FBSD since the 1.x days, and ever since the 3.x series - more so in the 4.x series - i have been able to easily crash/lock up machines - especially in X - especially when doing multimedia stuff and then CTRL-ALT-F?-ing to a ttyv? terminal. i hate having to be careful of how heavily i am stressing my machine. FBSD didn't used to be like that - it used to stand up to any amount of abuse - and without all the response latency i experience these days.] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
burncd + ioctl
FBSD 4.10 CREATIVE CDRW acd0: CD-RW CREATIVE CD-RW RW8435E at ata1-master PIO4 after rebooting and power down and spending more time trying to trick the CDRW into doing something, i finally tried: $ burncd -f /dev/acd0 erase file.iso the 'file.iso' seemed to force 'burncd' to do something - eg - make the CD light blink. after hitting up arrow-enter 100x, after a lot of -1 errors, it finally started to erase. and then it started to work again. i can't make complete sense of it yet, but possibly there are software methods around the glitch of the previous post. another method i had success with a few times was to put a CD with files and a filesystem in the drive, which would mount/list OK, and then 'detach' the CDRW with atacontrol, and then stick a problematic 'from the store' blank in the drive, then 'attach', and then it could be 'erased' with burncd. the best i can figure is, there's something funky about 700MB CDRW media, everyone seems to have a problem with it in a freaky way: RE: PCWorks: 700 MB versus 650 MB CDRW? _ * From: Carol Warman * Subject: RE: PCWorks: 700 MB versus 650 MB CDRW? * Date: Sat, 22 Jun 2002 19:27:09 -0700 _ Peter: Yes, this was exactly the problem. They were Memorex 700MB discs, right out of a brand new box. The firmware probably needed upgrading to see these discs. The issue was resolved by using Imation 650 MB discs. Thanks so much for the input. Carol Warman Computers Were Us, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Kaulback Sent: Saturday, June 22, 2002 7:05 PM Subject: RE: PCWorks: 700 MB versus 650 MB CDRW? Some cdrw discs manufactured by Memorex in particular, my burner will not even see. In effect they fail to exist. What drives do you have, they may only need their firmware to be updated. Peter Kaulback In the hour of 11:11 AM 6/22/2002 -0700, Carol Warman spoke this: Gerry: Thanks for the reply and for the valuable links. Would you know whether a CD RW drive manufactured 1-2 years ago (the age of the two machines in question) would have a problem in writing a 700 MB disc? I'm interested in tracking down the reason that the 650 MB media worked flawlessly and the 700 MB did not. Any thoughts? Thanks. Carol Warman Computers Were Us, Inc. [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Gerald E. Boyd Sent: Saturday, June 22, 2002 8:22 AM Subject: Re: PCWorks: 700 MB versus 650 MB CDRW? At 07:41 PM 6/21/02 -0700, Carol Warman wrote the following: Could someone please explain the difference (other than the obvious capacity) of a 700 MB CDRW versus a 650 MB CDRW. I am asking because we helped a client back up his files today and both of his CDRW drives (in two separate machines) would not recognize this media. Once we inserted a 650 MB CD, both drives recognized the media and the copying worked fine. I am used to working with the 650 MB media and the 700 is new to me. Early CD drives hold about 74 minutes of audio, or about 650MB of data. Later models hold about 80 minutes of audio, or about 700MB of data. The change came about because of all the audio fans overburning the original CD (circa 1997) to achieve longer play times. Hence, the manufacturers just started making the newer sizes. For more info, see the CD-R FAQ (start at section 7-6) http://www.cdrfaq.org/faq01.html -- Gerry Boyd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
burncd: ioctl(CDIOCSTART): Device busy
hi there, i'm running freebsd 4.10 with a kodak CR-R drive. i can mount CD-ROM's in the drive with no problems, but when i insert a blank CD-R (cdr not cdrw... i checked!!) into the drive and attempt burncd i get the error burncd: ioctl(CDIOCSTART): Device busy i tried fstat -n | grep acd but no programs appear to be using the drive. the light on the CD drive keeps blinking orange too, indicating that it is trying to read the drive or something similar, but i have not issued any 'mount /cdrom' command. i found a similar problem in the lists archive posted by a guy named willian denton last year, but couldn't find any resolution to the problem. i emailed him to find out if he ever solved his problem but have not yet received a reply. http://lists.freebsd.org/pipermail/freebsd-stable/2003-October/004262.html any ideas? cheers iain _ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd: ioctl(CDIOCSTART): Device busy
On Tue, 10 Aug 2004, Iain Dooley wrote: i tried fstat -n | grep acd but no programs appear to be using the drive. the light on the CD drive keeps blinking orange too, indicating that it is trying to read the drive or something similar, but i have not issued any 'mount /cdrom' command. [...] any ideas? More of a question, really. Why are you using 'fstat -n'? The -n option would appear to print only device numbers, not device names - therefore grepping for 'acd' will be fruitless, correct?. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd: ioctl(CDIOCSTART): Device busy
More of a question, really. Why are you using 'fstat -n'? The -n option would appear to print only device numbers, not device names - therefore grepping for 'acd' will be fruitless, correct?. okay, so fstat | grep cd doesn't reveal anything either. cheers iain ORIGINAL MESSAGE hi there, i'm running freebsd 4.10 with a kodak CR-R drive. i can mount CD-ROM's in the drive with no problems, but when i insert a blank CD-R (cdr not cdrw... i checked!!) into the drive and attempt burncd i get the error burncd: ioctl(CDIOCSTART): Device busy i tried fstat -n | grep acd but no programs appear to be using the drive. the light on the CD drive keeps blinking orange too, indicating that it is trying to read the drive or something similar, but i have not issued any 'mount /cdrom' command. i found a similar problem in the lists archive posted by a guy named willian denton last year, but couldn't find any resolution to the problem. i emailed him to find out if he ever solved his problem but have not yet received a reply. [actually, i have now received a reply... he said he never solved the problem, he just bought a new drive. my drive works fine in other machines, and i can mount CD-ROM's with it, so i don't think it is broken] http://lists.freebsd.org/pipermail/freebsd-stable/2003-October/004262.html _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Acer CDRW [ burncd: ioctl(CDRIOCBLANK): Device busy ]
I'm having a bad month. My harddrive died and I lost ALOT of data that is gonna take time to get back, I didn't have a good backup policy. I now have installed a cd-rewriter into my box, and plan to burn a cd once a week or so. My problem is that I can't seem to get is working... even though I've the same drive working on another FreeBSD box. FreeBSD nowhere.nowhere.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Nov 27 23:17:53 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/NOWHERE i386 gaspra# burncd -f /dev/acd0c blank burncd: ioctl(CDRIOCBLANK): Device busy gaspra# /usr/sbin/burncd -f /dev/acd0 data /backup.iso fixate burncd: ioctl(CDIOCSTART): Input/output error When I burn with a normal cdr disc, it works fine. What does this mean? How do I fix it? A search on google and the mail list doesn't exactly report a slew or questions or answers. Thanks, Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Acer CDRW [ burncd: ioctl(CDRIOCBLANK): Device busy ]
I'm having a bad month. My harddrive died and I lost ALOT of data that is gonna take time to get back, I didn't have a good backup policy. I now have installed a cd-rewriter into my box, and plan to burn a cd once a week or so. My problem is that I can't seem to get it working... FreeBSD nowhere.nowhere.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Nov 27 23:17:53 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/NOWHERE i386 gaspra# burncd -f /dev/acd0c blank burncd: ioctl(CDRIOCBLANK): Device busy gaspra# /usr/sbin/burncd -f /dev/acd0 data /backup.iso fixate burncd: ioctl(CDIOCSTART): Input/output error When I burn with a normal cdr disc, it works fine. I gives the above errors for cdrw discs. What does this mean? How do I fix it? A search on google and the mail list doesn't exactly report a slew of questions or answers. Thanks, Matt. -- Matt Gostick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Acer CDRW [ burncd: ioctl(CDRIOCBLANK): Device busy ]
I'm having a bad month. My harddrive died and I lost ALOT of data that is gonna take time to get back, I didn't have a good backup policy. I now have installed a cd-rewriter into my box, and plan to burn a cd once a week or so. My problem is that I can't seem to get it working... FreeBSD nowhere.nowhere.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Nov 27 23:17:53 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/NOWHERE i386 gaspra# burncd -f /dev/acd0c blank burncd: ioctl(CDRIOCBLANK): Device busy gaspra# /usr/sbin/burncd -f /dev/acd0 data /backup.iso fixate burncd: ioctl(CDIOCSTART): Input/output error When I burn with a normal cdr disc, it works fine. I gives the above errors for cdrw discs. What does this mean? How do I fix it? A search on google and the mail list doesn't exactly report a slew of questions or answers. Thanks, Matt. -- Matt Gostick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
