From owner-freebsd-questions@FreeBSD.ORG Sat Sep 4 15:10:35 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A96A16A4CE for ; Sat, 4 Sep 2004 15:10:35 +0000 (GMT) Received: from advmail.lsn.net (advmail.lsn.net [66.90.138.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id B59C643D1F for ; Sat, 4 Sep 2004 15:10:34 +0000 (GMT) (envelope-from norm@etherealconsulting.com) Received: from etherealconsulting.com (216-82-208-18.dyn.grandenetworks.net [216.82.208.18]) by advmail.lsn.net (8.12.8/8.12.4) with ESMTP id i84FAY0A006980 for ; Sat, 4 Sep 2004 10:10:36 -0500 Message-ID: <4139DAEA.80504@etherealconsulting.com> Date: Sat, 04 Sep 2004 10:10:34 -0500 From: Norm Vilmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiVirus: checked by Vexira Milter 1.0.6; VAE 6.27.0.6; VDF 6.27.0.46 Subject: [Re: Unable to write to CD-R] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 15:10:35 -0000 -------- Original Message -------- Subject: Unable to write to CD-R Date: Fri, 03 Sep 2004 15:56:45 -0500 From: Norm Vilmer To: freebsd-questions@freebsd.org I am having trouble burning an iso image to a CD-R using FreeBSD 4.10. I have tried using burncd , cdrecord, and growifofs, all appear to have basically the same problem (see details below) "Operation not permitted". One thing that bugs me is that dmesg reports my drive as a DVD-R. I am not sure if this is the problem or how to addressing correcting it. Note: the BIOS reports the drive to be TOSHIBA DVD-ROM SD-R6112 1031, not a DVD-RW. Can anyone give me some direction as to what I should try next, or better yet, how I can get the burner working? Details: FYI: I read the CD-Writing Howto and several other articles and followed the instructions therein to the best of my ability (you be the judge). This included: - logging in as root; - adding "device atapicam" to the kernel configuration and rebuilding the kernel; - creating /etc/devfs.conf as follows: link acd0 cdrom link acd0 dvd perm acd0 0660 perm cd0 0660 perm pass0 0660 perm pass1 0660 perm pass2 0660 perm pass3 0660 perm xpt0 0666 - installing cdrecord, dvd+rw-tools - ensure that the drive can read CD's and DVDs - running ./MAKEDEV pass10 in the /dev directory also added these hw.ata.ata_dma="1" hw.ata.atapi_dma="1" to /boot/loader.conf mount -t cd9660 /dev/cd0 /cdrom # works fine CD's and DVD's Here's some things I tried: burncd -f /dev/acd0c -s 12 data 5.2.1-RELEASE-i386-disc1.iso fixate burncd: open(/dev/acd0c): Operation not permitted cdrecord -scanbus Cdrecord 2.00.3 (I386 ..... cdrecord: Operation not permitted. Error opening /dev/pass0 Cam error 'camreal_ opendevice: coundn't open passthr. Cannot open SCSI driver. growisofs -dvd-compat -speed=4 -Z /dev/cd0c=5.2.1-RELEASE-i386-disc1.iso :-( unable to cam_open_pass("/dev/pass0", O_RDWR): Operation not permitted. dmesg |grep DVD acd0: DVD-R at ata1-master UDMA33 cd0: Removable CD-ROM SCSI-0 device atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI rev 6 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI rev 5 Slave: no device present camcontrol devlist at scbus1 target 0 lun 0 (pass0, cd0) Hardware: MB: VIA EPIA-CL10000, 512MB RAM, Award BIOS 6.00pw Burner: Toshiba SD-R6112 DVD-RW Andrew L. Gould wrote: Were you logged in as root? Andrew Gould Norm Vilmer wrote: Sorry about the last response, I think I have my mail client setup better for text and continuing the message at the botton rather than the top. Yes. I was logged in as root. I also played with the permissions in /dev giving the u=rw,o=rw,u=rw, but it did not do anything so I put the permissions back. Is it possible the OS thinks the device is a read-only device? How Do I go about debugging this problem, i.e., can I find out where the problem is in the code? Can I get a more verbosity show why the operation is not permitted? Norm Vilmer