Re: atapi/cam driver
Hi, your kernel configuration looks good: # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering [...] # Yes they are for SCSI but umass needs them device scbus # SCSI bus (required) device da # Direct Access (disks) [...] # To access IDE devices via scsi system device atapicam device cd device pass Perhaps there is some strange conflict between your CDROM devices. Did you try and unplug one of them, use a different IDE channel, etc. You should see cd0/cd1 devices when you boot. Simon signature.asc Description: Digital signature
Re: atapi/cam driver
On Tuesday 22 June 2004 08:28 am, Simon Barner wrote: Hi, your kernel configuration looks good: # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering [...] # Yes they are for SCSI but umass needs them device scbus # SCSI bus (required) device da # Direct Access (disks) [...] # To access IDE devices via scsi system device atapicam device cd device pass Perhaps there is some strange conflict between your CDROM devices. Did you try and unplug one of them, use a different IDE channel, etc. You should see cd0/cd1 devices when you boot. I'll try your suggestions and see what I can come up with... Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atapi/cam driver
Im trying to set it up, and Im not getting any real output from camcontrol devlist. Im following instructions from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html#ATAPICAM. dmesg only shows the devices as atapi devices, and not scsi. Does anyone have an idea where Im going wrong. Thanks -- camcontrol devlist -- gladiator# camcontrol devlist -v scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) -- -- OS version -- gladiator# uname -a FreeBSD gladiator.trini0.org 5.2.1-RELEASE-p6 FreeBSD 5.2.1-RELEASE-p6 #0: Fri May 7 22:43:47 EDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GLADIATOR i386 -- -- dmesg snip -- ad0: 19473MB Maxtor 52049H3 [39566/16/63] at ata0-master UDMA100 acd0: CDROM LTN403 at ata1-master PIO4 acd1: CDRW CW038D ATAPI CD-R/RW at ata1-slave PIO4 -- -- fstab snip -- /dev/cd0/cdrom cd9660 ro,noauto 0 0 /dev/cd1/cdrom1 cd9660 ro,noauto 0 0 -- -- kernel -- machine i386 cpu I686_CPU ident GLADIATOR maxusers0 #To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints #Default places to look for devices. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options SCHED_4BSD #4BSD scheduler options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options NFSCLIENT #Network Filesystem Client options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop# Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) # USB support device uhci# UHCI PCI-USB interface device usb # USB Bus (required) device ugen# Generic device umass# Disks/Mass storage - Requires scbus and da # Yes they are for SCSI but umass needs them device scbus # SCSI bus (required) device da # Direct Access (disks) # To access IDE devices via scsi system device atapicam device cd device pass # Audio device pcm # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
atapi/cam driver
Im trying to set it up, and Im not getting any real output from camcontrol devlist. Im following instructions from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html#ATAPICAM. dmesg only shows the devices as atapi devices, and not scsi. Does anyone have an idea where Im going wrong. Thanks -- camcontrol devlist -- gladiator# camcontrol devlist -v scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) -- -- OS version -- gladiator# uname -a FreeBSD gladiator.trini0.org 5.2.1-RELEASE-p6 FreeBSD 5.2.1-RELEASE-p6 #0: Fri May 7 22:43:47 EDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GLADIATOR i386 -- -- dmesg snip -- ad0: 19473MB Maxtor 52049H3 [39566/16/63] at ata0-master UDMA100 acd0: CDROM LTN403 at ata1-master PIO4 acd1: CDRW CW038D ATAPI CD-R/RW at ata1-slave PIO4 -- -- fstab snip -- /dev/cd0/cdrom cd9660 ro,noauto 0 0 /dev/cd1/cdrom1 cd9660 ro,noauto 0 0 -- -- kernel -- machine i386 cpu I686_CPU ident GLADIATOR maxusers0 #To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints #Default places to look for devices. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options SCHED_4BSD #4BSD scheduler options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options NFSCLIENT #Network Filesystem Client options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop# Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) # USB support device uhci# UHCI PCI-USB interface device usb # USB Bus (required) device ugen# Generic device umass# Disks/Mass storage - Requires scbus and da # Yes they are for SCSI but umass needs them device scbus # SCSI bus (required) device da # Direct Access (disks) # To access IDE devices via scsi system device atapicam device cd device pass # Audio device pcm # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using the ATAPI/CAM Driver
+++ Jeff Elkins [freebsd] [30-01-04 15:44 -0500]: | | Date: Fri, 30 Jan 2004 15:44:00 -0500 | User-Agent: KMail/1.5.4 | MIME-Version: 1.0 | Content-Type: text/plain; | charset=us-ascii | Content-Transfer-Encoding: 7bit | Content-Disposition: inline | Message-Id: [EMAIL PROTECTED] | Status: RO | X-Status: Q | X-KMail-EncryptionState: | X-KMail-SignatureState: | | I've enabled the ATAPI/CAM driver in my kernel under freebsd 5.2 - this has | given me two devices: /dev/cd0 and /dev/cd1. Thus far, I'm able to burn | CDs/DVDs but I am having trouble mounting them (as root). | | If I issue the command: mount /cdrom or mount -t cd9660 /dev/cd0 /cdrom I get | the message: cd9660: /dev/cd0: Device not configured | | However, if I comment out the /dev/cd devices in fstab and enable the acd | devices: | | /dev/acd0 /cdrom cd9660 ro,noauto 0 0 | /dev/acd1 /cdrom1 cd9660 ro,noauto0 0 | #/dev/cd0 /cdrom cd9660 ro,noauto 0 0 | #/dev/cd1 /cdrom1 cd9660 ro,noauto0 0 | | I'm able to mount w/o problems. | | Do I have something misconfigured? Following worked for me. # mount_cd9660 /dev/cd0c /cdrom Shantanoo | | Thanks, | | Jeff Elkins | | | -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using the ATAPI/CAM Driver
On Sunday 01 February 2004 00:54, Jeff Elkins wrote: On Saturday 31 January 2004 6:35 pm, Melvyn Sopacua wrote: On Saturday 31 January 2004 18:54, Jeff Elkins wrote: I _can_ mount cds using the /dev/acd* devices, while using the /dev/cd* devices for writing. Is this the way atapi cdrws are supposed to work under freebsd? So, is cam compiled into the kernel? Do you have the xpt SCSI driver? If cam is configured correctly, there should be mentioning of cd0 in /var/run/dmesg.boot and the cd's should be listed via: camcontrol devlist kathix# camcontrol devlist DMI MultiFlash 3.00 at scbus0 target 0 lun 0 (pass0,da0) DMI MultiFlash 3.00 at scbus0 target 0 lun 1 (pass1,da1) DMI MultiFlash 3.00 at scbus0 target 0 lun 2 (pass2,da2) DMI MultiFlash 3.00 at scbus0 target 0 lun 3 (pass3,da3) SEAGATE ST15230N 0638at scbus1 target 0 lun 0 (pass4,da4) PLEXTOR DVDR PX-708A 1.03 at scbus3 target 0 lun 0 (pass5,cd0) TOSHIBA CD-ROM XM-6202B 1110 at scbus3 target 1 lun 0 (pass6,cd1) cd0 at ata1 bus 0 target 0 lun 0 cd0: PLEXTOR DVDR PX-708A 1.03 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd1 at ata1 bus 0 target 1 lun 0 cd1: TOSHIBA CD-ROM XM-6202B 1110 Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers Try getting rid of the DMI devices. As you can see above, the cd's claim bus0, while cam puts them on bus 3. Still a chance that the seagate overrides them though. If: cdrecord dev=3,0,0 yourfiles.iso works correctly, you might want to follow this up to -current or -hardware. Thanks. All recording functions work, both with cdrecord and growisofs. The only issue is being unable to mount with /dev/cd0, /dev/cd1. I realise that I'm in uncharted waters with 5.2, and I appreciate the reply. Does cdrecord work with dev=/dev/cd0 also? You did fixate those cd's (shouldn't give a device not configured, but I/O error if you didn't, but just to make sure). -- Melvyn === FreeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan 28 18:01:18 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
Re: Using the ATAPI/CAM Driver
On Sunday 01 February 2004 00:54, Jeff Elkins wrote: All recording functions work, both with cdrecord and growisofs. The only issue is being unable to mount with /dev/cd0, /dev/cd1. I realise that I'm in uncharted waters with 5.2, and I appreciate the reply. Actually - I just tried to mount a blank cd, and that now gives device not configured, so I guess you need to fixate the cd's. -- Melvyn === FreeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan 28 18:01:18 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
Re: Using the ATAPI/CAM Driver
On Saturday 31 January 2004 12:24 am, slave-mike wrote: Jeff Elkins wrote: No responses on this yet, but I can hope :) Another issue: After changing the permissions on the /dev/pass* devices, following a reboot, they all reverted, rendering k3b useless. I'd appreciate some help... I've enabled the ATAPI/CAM driver in my kernel under freebsd 5.2 - this has given me two devices: /dev/cd0 and /dev/cd1. Thus far, I'm able to burn CDs/DVDs but I am having trouble mounting them (as root). If I issue the command: mount /cdrom or mount -t cd9660 /dev/cd0 /cdrom I get the message: cd9660: /dev/cd0: Device not configured However, if I comment out the /dev/cd devices in fstab and enable the acd devices: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto0 0 #/dev/cd0 /cdrom cd9660 ro,noauto 0 0 #/dev/cd1 /cdrom1 cd9660 ro,noauto0 0 I'm able to mount w/o problems. Do I have something misconfigured? Thanks, Jeff Elkins ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] look in /etc/devfs.confcd9660: /dev/cd0: Device not configured try adding something like: ... # Commonly used by many ports permacd00660 linkacd0cdrom linkacd0rcdrom linkacd0racd0 permacd10660 linkacd1dvd linkacd1rdvd permast00660 linkast0sa0 permnast0 0660 linknast0 nsa0 permpass0 0660 permpass1 0660 permpass2 0660 permpass3 0660 permscanner00660 permugen0 0660 permugen0.0 0660 permugen0.1 0660 permugen0.2 0660 permugen0.3 0660 # Allow a user in the wheel group to query the smb0 device permsmb00660 # Allow members of group operator to cat things to the speaker own speaker root:operator permspeaker 0660 Thanks. That succeeded in freezing the permissions from boot to boot, but I still get the error cd9660: /dev/cd0: Device not configured when I try to mount a cd via the passthrough device: mount -t cd9660 /dev/cd0 /cdrom I _can_ mount cds using the /dev/acd* devices, while using the /dev/cd* devices for writing. Is this the way atapi cdrws are supposed to work under freebsd? Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using the ATAPI/CAM Driver
On Saturday 31 January 2004 11:31, Jeff Elkins wrote: That succeeded in freezing the permissions from boot to boot, but I still get the error cd9660: /dev/cd0: Device not configured when I try to mount a cd via the passthrough device: mount -t cd9660 /dev/cd0 /cdrom I _can_ mount cds using the /dev/acd* devices, while using the /dev/cd* devices for writing. Is this the way atapi cdrws are supposed to work under freebsd? So, is cam compiled into the kernel? Do you have the xpt SCSI driver? If cam is configured correctly, there should be mentioning of cd0 in /var/run/dmesg.boot and the cd's should be listed via: camcontrol devlist -- Melvyn === FreeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan 28 18:01:18 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
Re: Using the ATAPI/CAM Driver
On Saturday 31 January 2004 11:25 am, Melvyn Sopacua wrote: On Saturday 31 January 2004 11:31, Jeff Elkins wrote: That succeeded in freezing the permissions from boot to boot, but I still get the error cd9660: /dev/cd0: Device not configured when I try to mount a cd via the passthrough device: mount -t cd9660 /dev/cd0 /cdrom I _can_ mount cds using the /dev/acd* devices, while using the /dev/cd* devices for writing. Is this the way atapi cdrws are supposed to work under freebsd? So, is cam compiled into the kernel? Do you have the xpt SCSI driver? If cam is configured correctly, there should be mentioning of cd0 in /var/run/dmesg.boot and the cd's should be listed via: camcontrol devlist kathix# camcontrol devlist DMI MultiFlash 3.00 at scbus0 target 0 lun 0 (pass0,da0) DMI MultiFlash 3.00 at scbus0 target 0 lun 1 (pass1,da1) DMI MultiFlash 3.00 at scbus0 target 0 lun 2 (pass2,da2) DMI MultiFlash 3.00 at scbus0 target 0 lun 3 (pass3,da3) SEAGATE ST15230N 0638at scbus1 target 0 lun 0 (pass4,da4) PLEXTOR DVDR PX-708A 1.03 at scbus3 target 0 lun 0 (pass5,cd0) TOSHIBA CD-ROM XM-6202B 1110 at scbus3 target 1 lun 0 (pass6,cd1) cd0 at ata1 bus 0 target 0 lun 0 cd0: PLEXTOR DVDR PX-708A 1.03 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd1 at ata1 bus 0 target 1 lun 0 cd1: TOSHIBA CD-ROM XM-6202B 1110 Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using the ATAPI/CAM Driver
On Saturday 31 January 2004 18:54, Jeff Elkins wrote: I _can_ mount cds using the /dev/acd* devices, while using the /dev/cd* devices for writing. Is this the way atapi cdrws are supposed to work under freebsd? So, is cam compiled into the kernel? Do you have the xpt SCSI driver? If cam is configured correctly, there should be mentioning of cd0 in /var/run/dmesg.boot and the cd's should be listed via: camcontrol devlist kathix# camcontrol devlist DMI MultiFlash 3.00 at scbus0 target 0 lun 0 (pass0,da0) DMI MultiFlash 3.00 at scbus0 target 0 lun 1 (pass1,da1) DMI MultiFlash 3.00 at scbus0 target 0 lun 2 (pass2,da2) DMI MultiFlash 3.00 at scbus0 target 0 lun 3 (pass3,da3) SEAGATE ST15230N 0638at scbus1 target 0 lun 0 (pass4,da4) PLEXTOR DVDR PX-708A 1.03 at scbus3 target 0 lun 0 (pass5,cd0) TOSHIBA CD-ROM XM-6202B 1110 at scbus3 target 1 lun 0 (pass6,cd1) cd0 at ata1 bus 0 target 0 lun 0 cd0: PLEXTOR DVDR PX-708A 1.03 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd1 at ata1 bus 0 target 1 lun 0 cd1: TOSHIBA CD-ROM XM-6202B 1110 Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers Try getting rid of the DMI devices. As you can see above, the cd's claim bus0, while cam puts them on bus 3. Still a chance that the seagate overrides them though. If: cdrecord dev=3,0,0 yourfiles.iso works correctly, you might want to follow this up to -current or -hardware. -- Melvyn === FreeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan 28 18:01:18 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
Re: Using the ATAPI/CAM Driver
On Saturday 31 January 2004 6:35 pm, Melvyn Sopacua wrote: On Saturday 31 January 2004 18:54, Jeff Elkins wrote: I _can_ mount cds using the /dev/acd* devices, while using the /dev/cd* devices for writing. Is this the way atapi cdrws are supposed to work under freebsd? So, is cam compiled into the kernel? Do you have the xpt SCSI driver? If cam is configured correctly, there should be mentioning of cd0 in /var/run/dmesg.boot and the cd's should be listed via: camcontrol devlist kathix# camcontrol devlist DMI MultiFlash 3.00 at scbus0 target 0 lun 0 (pass0,da0) DMI MultiFlash 3.00 at scbus0 target 0 lun 1 (pass1,da1) DMI MultiFlash 3.00 at scbus0 target 0 lun 2 (pass2,da2) DMI MultiFlash 3.00 at scbus0 target 0 lun 3 (pass3,da3) SEAGATE ST15230N 0638at scbus1 target 0 lun 0 (pass4,da4) PLEXTOR DVDR PX-708A 1.03 at scbus3 target 0 lun 0 (pass5,cd0) TOSHIBA CD-ROM XM-6202B 1110 at scbus3 target 1 lun 0 (pass6,cd1) cd0 at ata1 bus 0 target 0 lun 0 cd0: PLEXTOR DVDR PX-708A 1.03 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd1 at ata1 bus 0 target 1 lun 0 cd1: TOSHIBA CD-ROM XM-6202B 1110 Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers Try getting rid of the DMI devices. As you can see above, the cd's claim bus0, while cam puts them on bus 3. Still a chance that the seagate overrides them though. If: cdrecord dev=3,0,0 yourfiles.iso works correctly, you might want to follow this up to -current or -hardware. Thanks. All recording functions work, both with cdrecord and growisofs. The only issue is being unable to mount with /dev/cd0, /dev/cd1. I realise that I'm in uncharted waters with 5.2, and I appreciate the reply. Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using the ATAPI/CAM Driver
Date: Fri, 30 Jan 2004 15:44:00 -0500 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: [EMAIL PROTECTED] Status: RO X-Status: Q X-KMail-EncryptionState: X-KMail-SignatureState: I've enabled the ATAPI/CAM driver in my kernel under freebsd 5.2 - this has given me two devices: /dev/cd0 and /dev/cd1. Thus far, I'm able to burn CDs/DVDs but I am having trouble mounting them (as root). If I issue the command: mount /cdrom or mount -t cd9660 /dev/cd0 /cdrom I get the message: cd9660: /dev/cd0: Device not configured However, if I comment out the /dev/cd devices in fstab and enable the acd devices: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto0 0 #/dev/cd0 /cdrom cd9660 ro,noauto 0 0 #/dev/cd1 /cdrom1 cd9660 ro,noauto0 0 I'm able to mount w/o problems. Do I have something misconfigured? Thanks, Jeff Elkins ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using the ATAPI/CAM Driver
No responses on this yet, but I can hope :) Another issue: After changing the permissions on the /dev/pass* devices, following a reboot, they all reverted, rendering k3b useless. I'd appreciate some help... I've enabled the ATAPI/CAM driver in my kernel under freebsd 5.2 - this has given me two devices: /dev/cd0 and /dev/cd1. Thus far, I'm able to burn CDs/DVDs but I am having trouble mounting them (as root). If I issue the command: mount /cdrom or mount -t cd9660 /dev/cd0 /cdrom I get the message: cd9660: /dev/cd0: Device not configured However, if I comment out the /dev/cd devices in fstab and enable the acd devices: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto0 0 #/dev/cd0 /cdrom cd9660 ro,noauto 0 0 #/dev/cd1 /cdrom1 cd9660 ro,noauto0 0 I'm able to mount w/o problems. Do I have something misconfigured? Thanks, Jeff Elkins ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using the ATAPI/CAM Driver
Jeff Elkins wrote: No responses on this yet, but I can hope :) Another issue: After changing the permissions on the /dev/pass* devices, following a reboot, they all reverted, rendering k3b useless. I'd appreciate some help... I've enabled the ATAPI/CAM driver in my kernel under freebsd 5.2 - this has given me two devices: /dev/cd0 and /dev/cd1. Thus far, I'm able to burn CDs/DVDs but I am having trouble mounting them (as root). If I issue the command: mount /cdrom or mount -t cd9660 /dev/cd0 /cdrom I get the message: cd9660: /dev/cd0: Device not configured However, if I comment out the /dev/cd devices in fstab and enable the acd devices: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto0 0 #/dev/cd0 /cdrom cd9660 ro,noauto 0 0 #/dev/cd1 /cdrom1 cd9660 ro,noauto0 0 I'm able to mount w/o problems. Do I have something misconfigured? Thanks, Jeff Elkins ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] look in /etc/devfs.conf try adding something like: ... # Commonly used by many ports permacd00660 linkacd0cdrom linkacd0rcdrom linkacd0racd0 permacd10660 linkacd1dvd linkacd1rdvd permast00660 linkast0sa0 permnast0 0660 linknast0 nsa0 permpass0 0660 permpass1 0660 permpass2 0660 permpass3 0660 permscanner00660 permugen0 0660 permugen0.0 0660 permugen0.1 0660 permugen0.2 0660 permugen0.3 0660 # Allow a user in the wheel group to query the smb0 device permsmb00660 # Allow members of group operator to cat things to the speaker own speaker root:operator permspeaker 0660 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
