burning cd
* igor denisov denisovigor1...@rambler.ru [Fri, 18 Sep 2009 05:18:58 +0400]: hi there, cdrecord emulation as it looks like is done with /dev/rcd0c, and why they do not mention it in the faq. It is as simple as that: #cdrecord dev=/dev/rcd0c -scanbus output is what is shown in the faq13 for SCSI hardware. And there is something else, when i issue: #cdrecord -multi -tao /dev=/dev/rcd0c myfile.pdf everything starts fine, the only WARNING: padding to something size. and when i try to mount cd after burning, i get a message #bla bla device is not configured when change the cd to another cd, mount works fine. any ideas? regards, igor.
Re: burning cd
On Sat, Sep 19, 2009 at 07:25:40AM +0400, igor denisov wrote: * igor denisov denisovigor1...@rambler.ru [Fri, 18 Sep 2009 05:18:58 +0400]: hi there, cdrecord emulation as it looks like is done with /dev/rcd0c, and why they do not mention it in the faq. It is as simple as that: #cdrecord dev=/dev/rcd0c -scanbus the point of -scanbus is to find devices. it doesn't make much sense to provide the device identifier, then look for devices. also, using just the 'bus,target,lun' tupple doesn't work on OpenBSD, so the info from cdrecord -scanbus is really useless. output is what is shown in the faq13 for SCSI hardware. And there is something else, when i issue: #cdrecord -multi -tao /dev=/dev/rcd0c myfile.pdf everything starts fine, the only WARNING: padding to something size. and when i try to mount cd after burning, i get a message #bla bla device is not configured when change the cd to another cd, mount works fine. any ideas? you can't mount a pdf. but you can put your pdf on a cd9660 (ISO9660 if you will) filesystem and mount that. see mkhybrid(8) or mkisofs(8). regards, igor. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
burning cd
Hello there, when i issue #cdrecord -scanbus I get cdrecord: No such file or directory. Cannot open SCSI driver. dmesg | grep 'cd' cd0 at scsibus0 targ 0 lun 0: Optiarc, DVD RW AD-7540A, 1.01 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 may somebody to tell me how to use cdrecord the hardware I have with? Regards, igor denisov. -- Sgm`i, wrn mnbncn b P`lakep.Onwre http://mail.rambler.ru/new/
Re: burning cd
On Thu, Sep 17, 2009 at 03:40:19PM +0400, igor denisov wrote: Hello there, when i issue #cdrecord -scanbus I get cdrecord: No such file or directory. Cannot open SCSI driver. dmesg | grep 'cd' cd0 at scsibus0 targ 0 lun 0: Optiarc, DVD RW AD-7540A, 1.01 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 may somebody to tell me how to use cdrecord the hardware I have with? Regards, igor denisov. http://www.openbsd.org/faq/faq13.html#burnCD -- Sgm`i, wrn mnbncn b P`lakep.Onwre http://mail.rambler.ru/new/
Re: burning cd
On 2009-09-17, igor denisov denisovigor1...@rambler.ru wrote: Hello there, when i issue #cdrecord -scanbus I get cdrecord: No such file or directory. Cannot open SCSI driver. dmesg | grep 'cd' cd0 at scsibus0 targ 0 lun 0: Optiarc, DVD RW AD-7540A, 1.01 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 may somebody to tell me how to use cdrecord the hardware I have with? Regards, igor denisov. the easiest way to burn a cd is probably to use the cdio(1) tool that comes with the base system. Best regards, Jona -- Worse is better Richard P. Gabriel
ambiguities around burning CD
I am trying to write a CD and I have atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CDRW/DVD SN-324S, U303 SCSI0 5/cdrom removable man cdrecord says: Some operating systems or SCSI transport implementations may require to specify a filename in addition. In this case the correct syntax for the device is: dev= devicename:scsibus,target,lun[...] May OpenBSD require to specify a filename in addition? If OpenBSD requires a filename in addition, does cdrecord have any further requirements on the filename apart that it is somehow associated with the writer in question? As dmesg suggests, I have a filename /dev/cd0a and /dev/cd0c. However, cdrecord dev=help suggests another filename: Transport name: SCIOCCOMMAND Transport descr.: SCSI for devices known by *BSD Transp. layer ind.: Target specifier: device or bus,target,lun Target example: /dev/rcd0a:@ or 1,2,0 SCSI Bus scanning: not supported Open via UNIX device: supported In this case it's filename /dev/rcd0a, which I have on my system, too. So the possible values for dev= according to this documentation are so far dev=0,0,0 dev=/dev/cd0a:0,0,0 dev=/dev/cd0c:0,0,0 dev=/dev/rcd0a:0,0,0 $ cdrecord dev=0,0,0 disk1.iso cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01 (i386-unknown-openbsd3.9) Copyright (C) 1995-2004 Jvrg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. $ cdrecord dev=/dev/cd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0a'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/cd0c:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0c'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/rcd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/rcd0a'. Cannot open SCSI driver. [...] Seems like there exists at least one operation which is not supported by these devices. But is it the write operation? Or something else? Does this mean OpenBSD doesn't support writing on my unit? Or does it mean the cryptic identifier I passed to dev= is just not cryptic enough? CL OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.50GHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 cpu0: Enhanced SpeedStep 1500 MHz (1340 mV) (not in table) real mem = 535052288 (522512K) avail mem = 481202176 (469924K) using 4278 buffers containing 26857472 bytes (26228K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 01/28/05, BIOS32 rev. 0 @ 0xffe90 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc590/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xd800! 0xcd800/0x800 0xce000/0x800 0xce800/0x800 0xcf000/0x800 0xcf800/0x800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82852GM Hub-PCI rev 0x02 Intel 82852GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82852GM Configuration rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xf000, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82852GM AGP rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci1 at ppb0 bus 1 cbb0 at pci1 dev 1 function 0 Texas Instruments PCI4510
Re: ambiguities around burning CD
On Tue, 5 Sep 2006, Karel Kulhavy wrote: I am trying to write a CD and I have atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CDRW/DVD SN-324S, U303 SCSI0 5/cdrom removable man cdrecord says: Some operating systems or SCSI transport implementations may require to specify a filename in addition. In this case the correct syntax for the device is: dev= devicename:scsibus,target,lun[...] May OpenBSD require to specify a filename in addition? http://www.openbsd.org/faq/faq13.html#burnCD If OpenBSD requires a filename in addition, does cdrecord have any further requirements on the filename apart that it is somehow associated with the writer in question? As dmesg suggests, I have a filename /dev/cd0a and /dev/cd0c. However, cdrecord dev=help suggests another filename: Transport name: SCIOCCOMMAND Transport descr.: SCSI for devices known by *BSD Transp. layer ind.: Target specifier: device or bus,target,lun Target example: /dev/rcd0a:@ or 1,2,0 SCSI Bus scanning: not supported Open via UNIX device: supported In this case it's filename /dev/rcd0a, which I have on my system, too. So the possible values for dev= according to this documentation are so far dev=0,0,0 dev=/dev/cd0a:0,0,0 dev=/dev/cd0c:0,0,0 dev=/dev/rcd0a:0,0,0 $ cdrecord dev=0,0,0 disk1.iso cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01 (i386-unknown-openbsd3.9) Copyright (C) 1995-2004 Jvrg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. $ cdrecord dev=/dev/cd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0a'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/cd0c:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0c'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/rcd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/rcd0a'. Cannot open SCSI driver. [...] Seems like there exists at least one operation which is not supported by these devices. But is it the write operation? Or something else? Does this mean OpenBSD doesn't support writing on my unit? Or does it mean the cryptic identifier I passed to dev= is just not cryptic enough? CL OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.50GHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 cpu0: Enhanced SpeedStep 1500 MHz (1340 mV) (not in table) real mem = 535052288 (522512K) avail mem = 481202176 (469924K) using 4278 buffers containing 26857472 bytes (26228K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 01/28/05, BIOS32 rev. 0 @ 0xffe90 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc590/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xd800! 0xcd800/0x800 0xce000/0x800 0xce800/0x800 0xcf000/0x800 0xcf800/0x800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82852GM Hub-PCI rev 0x02 Intel 82852GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82852GM Configuration rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xf000, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82852GM AGP rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root
Re: ambiguities around burning CD
Hi Karel, On 06/09/2006, at 6:13 AM, Karel Kulhavy wrote: So the possible values for dev= according to this documentation are so far dev=0,0,0 dev=/dev/cd0a:0,0,0 dev=/dev/cd0c:0,0,0 dev=/dev/rcd0a:0,0,0 I use: cdrecord dev=/dev/rcd0c ^ ^ Which works fine for me. Shane
