*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 J顤g Schilling
TOC Type: 1 = CD-ROM
scsidev: 'pci:0,0,0'
devname: 'pci'
scsibus: 0 target: 0 lun: 0
cdrecord: Invalid argument. Open by 'devname' not supported on this OS. Cannot o
pen SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'
# cdrecord -scanbus
Code:
Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 J顤g Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'
# cdrecord dev=help
Code:
Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 J顤g Schilling
Supported SCSI transports for this platform:
Transport name: CAM
Transport descr.: Generic transport independent SCSI (Common Access Method)
Transp. layer ind.:
Target specifier: bus,target,lun
Target example: 1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported
Transport name: RSCSI
Transport descr.: Remote SCSI
Transp. layer ind.: REMOTE:
Target specifier: rscsi@host:bus,target,lun
Target example: REMOTE:rscsi@host:1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported
# pkg_info | grep cdrecord
No printout
# pkg_info | grep mkisofs
cdrtools-2.0.3 Cdrecord, mkisofs and several other programs to record CD-R
mkisofs-2.0.3 Create iso9660/Rock Ridge/Joliet filesystems
I am not sure that the cdrecord command works exactly the same on BSD as on Linux but on Linux the valid command would be:
cdrecord dev=0,0,0 speed=4 -v -eject cdimage.raw
Originally posted by jailbait I am not sure that the cdrecord command works exactly the same on BSD as on Linux but on Linux the valid command would be:
cdrecord dev=0,0,0 speed=4 -v -eject cdimage.raw
----------------------------
Steve Stites
Hi jailbait,
Thanks for your advice.
Sorry 'cdrecord dev=0,0,0 speed=4 -v -eject cdimage.raw' did not work for me.
# cdrecord -scanbus
Code:
Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 J顤g Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
# cdrecord dev=help
Code:
Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 J顤g Schilling
Supported SCSI transports for this platform:
Transport name: CAM
Transport descr.: Generic transport independent SCSI (Common Access Method)
Transp. layer ind.:
Target specifier: bus,target,lun
Target example: 1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported
Transport name: RSCSI
Transport descr.: Remote SCSI
Transp. layer ind.: REMOTE:
Target specifier: rscsi@host:bus,target,lun
Target example: REMOTE:rscsi@host:1,2,0
SCSI Bus scanning: supported
Open via UNIX device: not supported
# camcontrol devlist
No printout
I think I have to add 'atapicam' to the kernel and rebuild it. That will be a little bid complicate. However I found a solution as follow;
I gave up on burncd and I got cdrecord working on 5.2.1 using the atapi/cam (12.5.9 HNDBK) driver through the scsi subsystem. Here is the section of my kernel conf containing the necessary info:
# ATA and ATAPI devices
device ata
device atapicam
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
device atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
options ATA_STATIC_ID #Static device numbering
# SCSI Controllers
# SCSI peripherals
device scbus # SCSI bus (required for SCSI)
device cd # CD
device pass # Passthrough device (direct SCSI access)
The line in BLUE was added by me. The lines in RED should already be included so add them if not. Then you need to compile the new kernel and all of this is in the handbook. After all is done you can check the info using "camcontrol devlist" and also greping dmesg to compare the scsi info. Hope this helps.
Originally posted by psamuel01 I gave up on burncd and I got cdrecord working on 5.2.1 using the atapi/cam (12.5.9 HNDBK) driver through the scsi subsystem. Here is the section of my kernel conf containing the necessary info:
# ATA and ATAPI devices
device ata
device atapicam
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
device atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
options ATA_STATIC_ID #Static device numbering
# SCSI Controllers
# SCSI peripherals
device scbus # SCSI bus (required for SCSI)
device cd # CD
device pass # Passthrough device (direct SCSI access)
The line in BLUE was added by me. The lines in RED should already be included so add them if not. Then you need to compile the new kernel and all of this is in the handbook. After all is done you can check the info using "camcontrol devlist" and also greping dmesg to compare the scsi info. Hope this helps.
I would also make a "kernels" directory under root and copy the kernel to it and symlink it to ../conf directory. That is shown in the handbook. I used the "make buildkernel/make installkernel" option as it is a few less steps. To use that option make sure you have installed all of the sources from sysinstall or manually. Other than that the way you are doing it looks good.
I would also make a "kernels" directory under root and copy the kernel to it and symlink it to ../conf directory. That is shown in the handbook. I used the "make buildkernel/make installkernel" option as it is a few less steps. To use that option make sure you have installed all of the sources from sysinstall or manually. Other than that the way you are doing it looks good.
This is the classic SCSI problem. basically you have to enable scsi emulation over an ide device. this is because burners use scsi commands. I know in linux you edit lilo.conf by 'append hdx=ide-scsi' and run /sbin/lilo. where 'x' is your device (usually c). freebsd doesnt use lilo so i would like to know myself thanks.
This is the classic SCSI problem. basically you have to enable scsi emulation over an ide device. this is because burners use scsi commands. I know in linux you edit lilo.conf by 'append hdx=ide-scsi' and run /sbin/lilo. where 'x' is your device (usually c). freebsd doesnt use lilo so i would like to know myself thanks.
Hey buddy!
In FreeBSD follow the aforementioned kernel compilation with the scsi subsystem and all should be fine. Let me kmow if there are any other issues.
should contain pretty specific information on building and configuring your kernel. You really shouldn't need to recompile your kernel to burn CD-Rs, though.
Also, I would contact the author of the burncd program about the Device Busy message you got. I've had the same problem when trying to immediately mount CDs in 4.9 and earlier systems. It very well could be a bug in the atapicd device or something.
should contain pretty specific information on building and configuring your kernel. You really shouldn't need to recompile your kernel to burn CD-Rs, though.
Also, I would contact the author of the burncd program about the Device Busy message you got. I've had the same problem when trying to immediately mount CDs in 4.9 and earlier systems. It very well could be a bug in the atapicd device or something.
Hi Alex Cavnar,
FreeBSD 5.2
Tks for your advice.
I'm now using 'burncd' without problem. I cease using 'cdrecord' on FreeBSD.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.