Re: CDRW Stopped Working Moving to 6.x
On Wed, Sep 19, 2007 at 03:24:16PM -0400, Lowell Gilbert wrote: > "Crist J. Clark" <[EMAIL PROTECTED]> writes: > > > On Fri, Sep 14, 2007 at 07:35:24AM -0400, Lowell Gilbert wrote: > >> "Crist J. Clark" <[EMAIL PROTECTED]> writes: > >> > >> > Looking at the dmesg(1) from the last boot, > >> > > >> > # fgrep cd0 /var/run/dmesg.boot > >> > acd0: CDROM at ata1-master UDMA33 > >> > > >> > Makes me think the system is not recognizing the device as CDRW, > >> > only CDROM. > >> > >> You're right, and that's the key point to start from. > >> Don't worry about ATAPI/CAM; it won't be used by burncd, and won't > >> work any better than direct ATAPI drivers if the device isn't > >> recognized as a CDRW. > >> > >> The funny thing is (unless I recall incorrectly, which is possible > >> before my first cup of coffee for the day), the ID string is provided > >> by the device itself. And I just looked it up; CRD-8400B is > >> definitely a CDROM. So I don't think the OS is confused; if anything, > >> the device itself is what's confused. > >> > >> Just to doublecheck: are you really sure you haven't changed the drive > >> since the last time you burned a CD? > > > > Nope, haven't changed the drive. Went and had a look at the front and > > it's got "CD/RW" on the "disc" symbol on the front of the tray. But > > going back to some old dmesg(1) from this same box when the buring > > worked back in 4.x, > > > > FreeBSD 4.11-STABLE #1: Sun Jun 19 00:18:37 PDT 2005 > > [EMAIL PROTECTED]:/var/tmp/tmp_cjc/obj/usr/src/sys/GOKU > > [snip] > > acd0: CDROM at ata1-master PIO4 > > > > H... > > Wow. Good thinking to check that. > > Definitely sounds like you are being bitten by something dodgy in the > device probing which has been there for a long time but was benign in > the past. You'll need someone who knows the probing code... S... After spending a few more hours trying to figure this out, I get some confusing messages when I just try to read a CDROM! Long story short, ha. ha. you'll laugh. I was looking at the wrong machine. The one with the drive clearly embosed with the "disc" symbol saying "Rewritable" is (besides also clearly being labeled with the system's name which is not the system I was trying to run the burncd(8) command on), acd0: CDRW at ata1-master PIO4 And the machine I was trying to actually run the command on, the machine above, is indeed a CDROM. -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
"Crist J. Clark" <[EMAIL PROTECTED]> writes: > On Fri, Sep 14, 2007 at 07:35:24AM -0400, Lowell Gilbert wrote: >> "Crist J. Clark" <[EMAIL PROTECTED]> writes: >> >> > Looking at the dmesg(1) from the last boot, >> > >> > # fgrep cd0 /var/run/dmesg.boot >> > acd0: CDROM at ata1-master UDMA33 >> > >> > Makes me think the system is not recognizing the device as CDRW, >> > only CDROM. >> >> You're right, and that's the key point to start from. >> Don't worry about ATAPI/CAM; it won't be used by burncd, and won't >> work any better than direct ATAPI drivers if the device isn't >> recognized as a CDRW. >> >> The funny thing is (unless I recall incorrectly, which is possible >> before my first cup of coffee for the day), the ID string is provided >> by the device itself. And I just looked it up; CRD-8400B is >> definitely a CDROM. So I don't think the OS is confused; if anything, >> the device itself is what's confused. >> >> Just to doublecheck: are you really sure you haven't changed the drive >> since the last time you burned a CD? > > Nope, haven't changed the drive. Went and had a look at the front and > it's got "CD/RW" on the "disc" symbol on the front of the tray. But > going back to some old dmesg(1) from this same box when the buring > worked back in 4.x, > > FreeBSD 4.11-STABLE #1: Sun Jun 19 00:18:37 PDT 2005 > [EMAIL PROTECTED]:/var/tmp/tmp_cjc/obj/usr/src/sys/GOKU > [snip] > acd0: CDROM at ata1-master PIO4 > > H... Wow. Good thinking to check that. Definitely sounds like you are being bitten by something dodgy in the device probing which has been there for a long time but was benign in the past. You'll need someone who knows the probing code... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
On Fri, Sep 14, 2007 at 07:35:24AM -0400, Lowell Gilbert wrote: > "Crist J. Clark" <[EMAIL PROTECTED]> writes: > > > Looking at the dmesg(1) from the last boot, > > > > # fgrep cd0 /var/run/dmesg.boot > > acd0: CDROM at ata1-master UDMA33 > > > > Makes me think the system is not recognizing the device as CDRW, > > only CDROM. > > You're right, and that's the key point to start from. > Don't worry about ATAPI/CAM; it won't be used by burncd, and won't > work any better than direct ATAPI drivers if the device isn't > recognized as a CDRW. > > The funny thing is (unless I recall incorrectly, which is possible > before my first cup of coffee for the day), the ID string is provided > by the device itself. And I just looked it up; CRD-8400B is > definitely a CDROM. So I don't think the OS is confused; if anything, > the device itself is what's confused. > > Just to doublecheck: are you really sure you haven't changed the drive > since the last time you burned a CD? Nope, haven't changed the drive. Went and had a look at the front and it's got "CD/RW" on the "disc" symbol on the front of the tray. But going back to some old dmesg(1) from this same box when the buring worked back in 4.x, FreeBSD 4.11-STABLE #1: Sun Jun 19 00:18:37 PDT 2005 [EMAIL PROTECTED]:/var/tmp/tmp_cjc/obj/usr/src/sys/GOKU [snip] acd0: CDROM at ata1-master PIO4 H... -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
Mel wrote: On Friday 14 September 2007 00:16:46 Predrag Punosevac wrote: I forgot to tell you assuming that you will do it your self Just add link acd0 cd0 but you have to use cd0. This is very bad advice, please don't ever do that. acd0 and cd0 are quite different devices under the hood. (posted for the googling masses) I am retracting what I said big time. Mel is 1000% right. I personally needed to access my ATAPI device through SCSI so that I can burn a DVD. My idiotic statement is wrong way to do it. Actually I had in my devfs.conf edited as it is outlined in the section 18.6.9 of the Handbook. Since I got error for DVD burn I posted a message and somebody pointed out that since I was running generic kernel I had to add atapicam_load="YES" into my /boot/loader.conf. After that I followed the example from section 18.7.3 to burn DVD and everything worked perfectly. Letter that day I used K3b to burn a few music CDs. I was following the direction from the Handbook and from FreeBSD-Gnome documentation to do that. I apologize to everyone for my spam mails. I will think twice before I post some stupidity again. In particularly, I apologize to the sender of original message for ill advice. Sincerely, Predrag Punosevac ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
Crist J. Clark wrote: > I just tried to burn a CD for the first time in a long time > on a machine. The burncd(8) command worked fine on this machine > in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, > [snip] It's unclear to me whether you got a satisfactory answer. Anyway, I run 6.2-RELEASE, and I burn CD-RW in this way: burncd -f /dev/acd0 blank burncd -f /dev/acd0 data cd.iso fixate -- Tore ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
On Friday 14 September 2007 00:16:46 Predrag Punosevac wrote: > I forgot to tell you assuming that you will do it your self > Just add > link acd0 cd0 > but you have to use cd0. This is very bad advice, please don't ever do that. acd0 and cd0 are quite different devices under the hood. (posted for the googling masses) -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
[reformatted] On Thursday 13 September 2007 22:21:09 Predrag Punosevac wrote: > Crist J. Clark wrote: > > I just tried to burn a CD for the first time in a long time > > on a machine. The burncd(8) command worked fine on this machine > > in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, > > > > # burncd -f /dev/acd0 -s 32 data hw.iso fixate > Make sure you add atapicam into your kernel it is not in generic! I had > the same problem. > > /etc/loader.conf atapicam_load="YES" Cam and burncd have no relation whatsoever. Cam is to make atapi cd's available as scsi cd's, so that cdrecord can work with them. Burncd operates on native atapi cd controllers. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
"Crist J. Clark" <[EMAIL PROTECTED]> writes: > Looking at the dmesg(1) from the last boot, > > # fgrep cd0 /var/run/dmesg.boot > acd0: CDROM at ata1-master UDMA33 > > Makes me think the system is not recognizing the device as CDRW, > only CDROM. You're right, and that's the key point to start from. Don't worry about ATAPI/CAM; it won't be used by burncd, and won't work any better than direct ATAPI drivers if the device isn't recognized as a CDRW. The funny thing is (unless I recall incorrectly, which is possible before my first cup of coffee for the day), the ID string is provided by the device itself. And I just looked it up; CRD-8400B is definitely a CDROM. So I don't think the OS is confused; if anything, the device itself is what's confused. Just to doublecheck: are you really sure you haven't changed the drive since the last time you burned a CD? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
Crist J. Clark wrote: On Thu, Sep 13, 2007 at 03:15:10PM -0700, Predrag Punosevac wrote: I know where is your problem the burning device is always cd0 Huh? Burncd(8) is explicitly for ATAPI CD-R/RW. From the man page, DESCRIPTION The burncd utility is used to burn CD-R/RW media using the ATAPI cd driver. All of the examples on the manpage use /dev/acd0. you must give the device node /dev/cd0 If I try it, # burncd -f /dev/cd0 -v -s 32 data hw.iso fixate burncd: ioctl(CDRIOCGETBLOCKSIZE): Device not configured Crist J. Clark wrote: On Thu, Sep 13, 2007 at 01:21:09PM -0700, Predrag Punosevac wrote: Make sure you add atapicam into your kernel it is not in generic! I had the same problem. /etc/loader.conf atapicam_load="YES" I did a, # kldload /boot/kernel/atapicam.ko And to reinitiallize the drive, # atacontrol detach ata1 # atacontrol attach ata1 I got the same console message, acd0: detached (cd0:ata1:0:0:0): lost device (cd0:ata1:0:0:0): removing device entry atapicam1: detached stray irq15 acd0: CDROM at ata1-master UDMA33 And still get, # burncd -f /dev/acd0 -t -s 32 data ~cjc/hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Crist J. Clark wrote: I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? I can just repeat what I read in the Gnome FreeBSD book that enable me to burn CD and DVD. kernel: device scbus device cd device pass This IS in GENERIC kernel or it was in 6.2 Stable. You must also make sure you have the following configured in your kernel if you are using an ATAPI CD/DVD drive: device atapicam THIS IS NOT IN THE GENERIC KERNEL! I added atapicam_load="YES" into my /boot/loader.conf file and rebooted my computer as it is not a server. To figure out which CD/DVD drive you will be using, run the following command as root: # camcontrol devlist Your output will look similar to the following: at scbus1 target 0 lun 0 (cd0,pass0) The devices in parentheses at the end are important. You must make sure the /dev entries for those devices are writable by the users that will be using nautilus-cd-burner, totem, goobox, or sound-juicer. In addition to those devices, /dev/xpt* must also be writable to your nautilus-cd-burner, totem, goobox, and sound-juicer users. The following /etc/devfs.conf configuration will achieve the desired results given the above devlist: permcd0 0666 permxpt00666 permpass0 0666 I also have link acd0 cd0 perm acd0 0666 perm cd0 0666 I did burn on Sunday iso DVD from the command line! The device node was /dev/cd0 since somebody told me that it has to be cd0 not acd0. (Maybe it is true only for DVD and if I remember examples from the book about DVD burning it was cd0) I was supper user during the burning to avoid any possibility of permission problems. I did burn at least 4 CD with music and one data CD using K3b since my Nautilus (I have Gnome on this system) is complaining about something. I was logged into my regular account when I used K3b. Obviously not supper user mode. I like K3B better than any of the Gnome applications anyway so I am not going to bother about Nautilus. I read the Handbook carefully and also FAQ. I am sure I forgot quite a bit as my system is fully configured and I am mostly light user (text editing, mail, browsing, FTP, VNC, and occasional multimedia)
Re: CDRW Stopped Working Moving to 6.x
On Thu, 13 Sep 2007, Predrag Punosevac wrote: I know where is your problem the burning device is always cd0 you must give the device node /dev/cd0 /dev/cd0 is provided by the atapicam kernel module, and used with Linux-type utilities that need it. However, burncd is FreeBSD native, and works fine with /dev/acd0. (please stop top posting) -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
On Thu, Sep 13, 2007 at 03:15:10PM -0700, Predrag Punosevac wrote: > I know where is your problem the burning device is always cd0 Huh? Burncd(8) is explicitly for ATAPI CD-R/RW. From the man page, DESCRIPTION The burncd utility is used to burn CD-R/RW media using the ATAPI cd driver. All of the examples on the manpage use /dev/acd0. > you must give the device node /dev/cd0 If I try it, # burncd -f /dev/cd0 -v -s 32 data hw.iso fixate burncd: ioctl(CDRIOCGETBLOCKSIZE): Device not configured > Crist J. Clark wrote: > >On Thu, Sep 13, 2007 at 01:21:09PM -0700, Predrag Punosevac wrote: > > > >>Make sure you add atapicam into your kernel it is not in generic! I had > >>the same problem. > >> > >>/etc/loader.conf atapicam_load="YES" > >> > > > >I did a, > > > > # kldload /boot/kernel/atapicam.ko > > > >And to reinitiallize the drive, > > > > # atacontrol detach ata1 > > # atacontrol attach ata1 > > > >I got the same console message, > > > > acd0: detached > > (cd0:ata1:0:0:0): lost device > > (cd0:ata1:0:0:0): removing device entry > > atapicam1: detached > > stray irq15 > > acd0: CDROM at ata1-master UDMA33 > > > >And still get, > > > > # burncd -f /dev/acd0 -t -s 32 data ~cjc/hw.iso fixate > > burncd: ioctl(CDIOCSTART): Input/output error > > > > > >>Crist J. Clark wrote: > >> > >>>I just tried to burn a CD for the first time in a long time > >>>on a machine. The burncd(8) command worked fine on this machine > >>>in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, > >>> > >>> # burncd -f /dev/acd0 -s 32 data hw.iso fixate > >>> burncd: ioctl(CDIOCSTART): Input/output error > >>> > >>>Looking at the dmesg(1) from the last boot, > >>> > >>> # fgrep cd0 /var/run/dmesg.boot > >>> acd0: CDROM at ata1-master UDMA33 > >>> > >>>Makes me think the system is not recognizing the device as CDRW, > >>>only CDROM. I get this from atacontrol(8), > >>> > >>> # atacontrol info ata1 > >>> Master: acd0 ATA/ATAPI revision 0 > >>> Slave: no device present > >>> # atacontrol cap acd0 > >>> > >>> Protocol ATA/ATAPI revision 0 > >>> device model CRD-8400B > >>> serial number 1999/10/12 > >>> firmware revision 1.06 > >>> cylinders 0 > >>> heads 0 > >>> sectors/track 0 > >>> lba supported > >>> lba48 not supported > >>> dma supported > >>> overlap not supported > >>> > >>> Feature Support EnableValue Vendor > >>> write cacheno no > >>> read ahead no no > >>> Tagged Command Queuing (TCQ) no no 0/0x00 > >>> SMART no no > >>> microcode download no no > >>> security no no > >>> power management no no > >>> advanced power management no no 0/0x00 > >>> automatic acoustic management no no 0/0x00 0/0x00 > >>> > >>>How can I restore burning capability? > >>> > >>> > > > > -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
I forgot to tell you assuming that you will do it your self Just add link acd0 cd0 but you have to use cd0. Pedja Crist J. Clark wrote: On Thu, Sep 13, 2007 at 01:21:09PM -0700, Predrag Punosevac wrote: Make sure you add atapicam into your kernel it is not in generic! I had the same problem. /etc/loader.conf atapicam_load="YES" I did a, # kldload /boot/kernel/atapicam.ko And to reinitiallize the drive, # atacontrol detach ata1 # atacontrol attach ata1 I got the same console message, acd0: detached (cd0:ata1:0:0:0): lost device (cd0:ata1:0:0:0): removing device entry atapicam1: detached stray irq15 acd0: CDROM at ata1-master UDMA33 And still get, # burncd -f /dev/acd0 -t -s 32 data ~cjc/hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Crist J. Clark wrote: I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
I know where is your problem the burning device is always cd0 you must give the device node /dev/cd0 Take care! Crist J. Clark wrote: On Thu, Sep 13, 2007 at 01:21:09PM -0700, Predrag Punosevac wrote: Make sure you add atapicam into your kernel it is not in generic! I had the same problem. /etc/loader.conf atapicam_load="YES" I did a, # kldload /boot/kernel/atapicam.ko And to reinitiallize the drive, # atacontrol detach ata1 # atacontrol attach ata1 I got the same console message, acd0: detached (cd0:ata1:0:0:0): lost device (cd0:ata1:0:0:0): removing device entry atapicam1: detached stray irq15 acd0: CDROM at ata1-master UDMA33 And still get, # burncd -f /dev/acd0 -t -s 32 data ~cjc/hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Crist J. Clark wrote: I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
On Thu, Sep 13, 2007 at 01:21:09PM -0700, Predrag Punosevac wrote: > Make sure you add atapicam into your kernel it is not in generic! I had > the same problem. > > /etc/loader.conf atapicam_load="YES" I did a, # kldload /boot/kernel/atapicam.ko And to reinitiallize the drive, # atacontrol detach ata1 # atacontrol attach ata1 I got the same console message, acd0: detached (cd0:ata1:0:0:0): lost device (cd0:ata1:0:0:0): removing device entry atapicam1: detached stray irq15 acd0: CDROM at ata1-master UDMA33 And still get, # burncd -f /dev/acd0 -t -s 32 data ~cjc/hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error > Crist J. Clark wrote: > >I just tried to burn a CD for the first time in a long time > >on a machine. The burncd(8) command worked fine on this machine > >in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, > > > > # burncd -f /dev/acd0 -s 32 data hw.iso fixate > > burncd: ioctl(CDIOCSTART): Input/output error > > > >Looking at the dmesg(1) from the last boot, > > > > # fgrep cd0 /var/run/dmesg.boot > > acd0: CDROM at ata1-master UDMA33 > > > >Makes me think the system is not recognizing the device as CDRW, > >only CDROM. I get this from atacontrol(8), > > > > # atacontrol info ata1 > > Master: acd0 ATA/ATAPI revision 0 > > Slave: no device present > > # atacontrol cap acd0 > > > > Protocol ATA/ATAPI revision 0 > > device model CRD-8400B > > serial number 1999/10/12 > > firmware revision 1.06 > > cylinders 0 > > heads 0 > > sectors/track 0 > > lba supported > > lba48 not supported > > dma supported > > overlap not supported > > > > Feature Support EnableValue Vendor > > write cacheno no > > read ahead no no > > Tagged Command Queuing (TCQ) no no 0/0x00 > > SMART no no > > microcode download no no > > security no no > > power management no no > > advanced power management no no 0/0x00 > > automatic acoustic management no no 0/0x00 0/0x00 > > > >How can I restore burning capability? > > -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDRW Stopped Working Moving to 6.x
Make sure you add atapicam into your kernel it is not in generic! I had the same problem. /etc/loader.conf atapicam_load="YES" Crist J. Clark wrote: I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CDRW Stopped Working Moving to 6.x
I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"