On 11/27/11, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote:
b. f. bf1...@googlemail.com writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but
will it make things
Now I think I'll try to rebuild the kernel with options ATA_CAM and drop
device atapicam.
This question needs to be better resolved in time for FreeBSD 9.0-RELEASE.
I cross-post this message to freebsd-curr...@freebsd.org so the developers
will see it. FreeBSD users want to be able to burn
b. f. bf1...@googlemail.com writes:
The handbook does contain some oblique and scattered references to the
new code, or at least to constructs that are common to both the old
and the new code, but the addition of a brief discussion of the
differences between the new and old ATA code in the
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but will
it make things go awry? Is ATA_CAM deprecated?
They are redundant and incompatible. atapicam is deprecated, and
ATA_CAM
b. f. bf1...@googlemail.com writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but will
it make things go awry? Is ATA_CAM deprecated?
They are redundant and incompatible
On 11/27/11, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote:
b. f. bf1...@googlemail.com writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but
will it make things go
Thomas Mueller mueller6...@bellsouth.net writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but will it
make things go awry? Is ATA_CAM deprecated?
Lowell Gilbert freebsd-questions
Thomas Mueller mueller6...@bellsouth.net writes:
What is the role of options atapicam and device ATA_CAM in kernel config
file?
Are they redundant? Kernel will build with both these options, but will it
make things go awry? Is ATA_CAM deprecated?
As far as I can see, ATA_CAM isn't
What is the role of options atapicam and device ATA_CAM in kernel config
file?
Are they redundant? Kernel will build with both these options, but will it
make things go awry? Is ATA_CAM deprecated?
I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtools don't
work.
Also, how
I have 2 systems running 8.0 installed from the same CD. One of them shows 2
PASS devices as expected and camcontrol devlist shows the appropriate devices.
They work as expected.
The other does not show any PASS devices and camcontrol devlist shows nothing.
Doing a kldload atapicam installs
and camcontrol devlist shows
nothing. Doing a kldload atapicam installs the PASS devices and then
camcontrol works properly. Why would that system require atapicam to be
manually added? That module was not loaded on the working system. I
installed it there first by accident but it had
as expected.
The other does not show any PASS devices and camcontrol devlist shows
nothing. Doing a kldload atapicam installs the PASS devices and then
camcontrol works properly. Why would that system require atapicam to be
manually added? That module was not loaded on the working system. I
that atapicam needs to be loaded in /boot/loader.conf. I'll add that to
both machines. Makes me wonder why the one worked. kldstat showed it was
not loaded.
Well I assumed the hardware is identical but is it a scsi optical drive in
the one worked?
--
Adam Vande More
. Reading through the handbook page above it indicates
that atapicam needs to be loaded in /boot/loader.conf. I'll add that to both
machines. Makes me wonder why the one worked. kldstat showed it was not
loaded.
Well I assumed the hardware is identical but is it a scsi optical drive
except for adding atapicam. Willl send, off-list, if same fault
hang up during boot. ...But IIRC, *not* haviing removed the
/usr/obj tree has caused problems before.
gary
I don't burn // copy audio
discs that often and haven't ever copied a DVD; I
Folks (to the whole list, but esp'ly Messes Smith [NL AU],
I'll believe that my ISDN link is working when/if I see this
echoed from the -questions list. I was busy rebuilding my 6.2
GENERIC kernel after having added
^device atapicam
72
having added
^device atapicam
Lest I stray *too* far OT, I'll share the results of my 3rd
kernel rebuild on this Dell. It crapped out; it hung after
printing out the sio0 line. I had to powercycle and went in by
typing 8 (??) and by hand booting
Hi all,
I'm using FreeBSD 6.2-RELEASE-p5, with the standard SMP kernel found
in /
usr/src/sys/i386/conf/SMP, when i 'kldload atapicam' i get the following
error message which just makes no sense to me: WARNING - PREVENT_ALLOW
taskqueue timeout - completing request directly xptioctl: put device
Actually, on my system I can do mount_udf /dev/acd0 and copy a 3GB
file, I just tried. My problem is adding CAM support, which the
handbook tells me I have to use to burn dvd.
johan
I'm unable to copy a file from a udf-mounted DVD regardless of whether
atapicam is loaded or not, so I'm
regardless of whether
atapicam is loaded or not, so I'm not sure if atapicam is just making
a problem more apparent or what. Are you able to do so?
Thanks,
Josh
On 10/16/06, Johan Johansen [EMAIL PROTECTED] wrote:
I still have the same problem as below, even when running 6.2-BETA2
with atapicd, but atapicam do not work.
kldload atapicam causes an interrupt storm, I guess.
I tried to take out atapicd from the kernel after reading
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73675
In fact, I removed ataraid atapifd atapist too, without any luck.
Here is output from top
atapicam is loaded or not, so I'm not sure if atapicam is just making
a problem more apparent or what. Are you able to do so?
Thanks,
Josh
On 10/16/06, Johan Johansen [EMAIL PROTECTED] wrote:
I still have the same problem as below, even when running 6.2-BETA2 from
a FreeSBIE - cd. I wonder
I run 6.1-STABLE-200607 on my brand new box with
Intel Core 2 Duo E6600 2 x 2,40 GHz cpu (beautiful piece of machinery)
I can use my dvd-devices with atapicd, but atapicam do not work.
kldload atapicam causes an interrupt storm, I guess.
I tried to take out atapicd from the kernel after reading
At Sun, 10 Sep 2006 it looks like Johan Johansen composed:
I run 6.1-STABLE-200607 on my brand new box with
Intel Core 2 Duo E6600 2 x 2,40 GHz cpu (beautiful piece of machinery)
I can use my dvd-devices with atapicd, but atapicam do not work.
kldload atapicam causes an interrupt storm
Neither disabling atapicam nor atapicd works on my Core2Duo system. I
don't know whether it's related to the new IDE controllers (JMicron
363 and Intel ICH8) or a similar problem to what you're reporting. The
best I can do is about 3MB/s with atapicd and DMA disabled and also
with atapicam. Both
At Sun, 10 Sep 2006 it looks like Josh Carroll composed:
Neither disabling atapicam nor atapicd works on my Core2Duo system. I
don't know whether it's related to the new IDE controllers (JMicron
363 and Intel ICH8) or a similar problem to what you're reporting. The
best I can do is about 3MB
Hi.
In the FreeBSD manual on '17.6.9 Using the ATAPI/CAM Driver', it only talks
about rebuilding the kernel with device atapicam.
I think it should mention that it actually is possible to just add
'atapicam_load=YES' to /boot/loader.conf.
Perhaps I have missed or overlooked something
How do I load atapicam at boot time. I tried to have it load the same
way I have the sound modules load, and it doesn't work. After the
system is up and running I can load just fine.
Thanks,
Chris Maness
___
freebsd-questions@freebsd.org mailing
On Tuesday 11 July 2006 18:33, Chris Maness wrote:
How do I load atapicam at boot time. I tried to have it load the same
way I have the sound modules load, and it doesn't work. After the
system is up and running I can load just fine.
Why don't you add device atapicam to your kernel
On Tuesday 11 July 2006 14:16, Beni wrote:
On Tuesday 11 July 2006 18:33, Chris Maness wrote:
How do I load atapicam at boot time. I tried to have it load the same
way I have the sound modules load, and it doesn't work. After the
system is up and running I can load just fine.
Why don't
This may be a silly question, but I wanted to make sure:
I have a SCSI R/W CD-ROM drive and an IDE DVD read-only drive. There have been
times with linux where enabling SCSI emulation made the actual SCSI drive
unavailable to k3b. I just want to make sure that adding ATAPICAM won't
somehow get
to make sure that
adding ATAPICAM won't somehow get in the way of the actual SCSI
device. Will it?
At worst it may shuffle the device number if the atapi drive gets
probed first.
--
Dan Nelson
[EMAIL PROTECTED]
___
freebsd-questions
On Monday 06 March 2006 14:11, Duane Whitty wrote:
On Monday March 6 2006 16:09
David J Brooks [EMAIL PROTECTED]
wrote
This reminds me to ask: I have
ATAPICAM enable in my kernal,
specifically so that k3b can find my
dvd+rw ... but no cd* devives appear
in /dev, and k3b cannot
, Duane Whitty wrote:
Hi,
Just wondering if anyone has
any information/opinion as to
why device atapicam is not
enabled by default in the
GENERIC kernel.
It's not an appropriate default,
since it modifies the way the ata
subsystem works in ways
On Monday March 6 2006 16:09
David J Brooks [EMAIL PROTECTED]
wrote
This reminds me to ask: I have
ATAPICAM enable in my kernal,
specifically so that k3b can find my
dvd+rw ... but no cd* devives appear
in /dev, and k3b cannot find anything
no matter where I tell it to look ..
I must
On Saturday 04 March 2006 17:30, Kris
Kennaway wrote:
On Sat, Mar 04, 2006 at 05:26:37PM
-0400, Duane Whitty wrote:
Hi,
Just wondering if anyone has any
information/opinion as to why
device atapicam is not enabled by
default in the GENERIC kernel.
It's not an appropriate default
On Sun, Mar 05, 2006 at 05:12:36PM -0400, Duane Whitty wrote:
On Saturday 04 March 2006 17:30, Kris
Kennaway wrote:
On Sat, Mar 04, 2006 at 05:26:37PM
-0400, Duane Whitty wrote:
Hi,
Just wondering if anyone has any
information/opinion as to why
device atapicam is not enabled
any information/opinion as to
why device atapicam is not
enabled by default in the
GENERIC kernel.
It's not an appropriate default,
since it modifies the way the ata
subsystem works in ways the
maintainer does not wish to
support,
Sorry, but do you mean the ata
Hi,
Just wondering if anyone has any
information/opinion as to why
device atapicam is not enabled by
default in the GENERIC kernel.
Does this apply to releases other than
6?
Thanks in advance,
--Duane
___
freebsd-questions@freebsd.org mailing list
On Sat, Mar 04, 2006 at 05:26:37PM -0400, Duane Whitty wrote:
Hi,
Just wondering if anyone has any
information/opinion as to why
device atapicam is not enabled by
default in the GENERIC kernel.
It's not an appropriate default, since it modifies the way the ata
subsystem works in ways
On Thu, 23 Feb 2006 22:06:22 -0800
Chris Maness [EMAIL PROTECTED] wrote:
How do I load atapicam at boot time? I can load it with no
problems after the system has started, but I if I ad the line
atapicam_load=YES in /*boot*/loader.conf, the kernel turns to
fried chicken at boot time
Vulpes Velox wrote:
On Thu, 23 Feb 2006 22:06:22 -0800
Chris Maness [EMAIL PROTECTED] wrote:
How do I load atapicam at boot time? I can load it with no
problems after the system has started, but I if I ad the line
atapicam_load=YES in /*boot*/loader.conf, the kernel turns to
fried chicken
Date: Fri, 24 Feb 2006 01:18:21 -0500
From: Kris Kennaway [EMAIL PROTECTED]
Subject: Re: ATAPICAM?
To: Chris Maness [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
On Thu, Feb 23, 2006 at 10:06:22PM -0800, Chris
Kris Kennaway wrote:
On Fri, Feb 24, 2006 at 06:49:34AM -0800, Chris Maness wrote:
Kris Kennaway wrote:
On Thu, Feb 23, 2006 at 10:06:22PM -0800, Chris Maness wrote:
How do I load atapicam at boot time? I can load it with no problems
after the system has started, but I if I
How do I load atapicam at boot time? I can load it with no problems
after the system has started, but I if I ad the line atapicam_load=YES
in /*boot*/loader.conf, the kernel turns to fried chicken at boot time.
Is there a secrete recipe ;o) to get this to work correctly
On Thu, Feb 23, 2006 at 10:06:22PM -0800, Chris Maness wrote:
How do I load atapicam at boot time? I can load it with no problems
after the system has started, but I if I ad the line atapicam_load=YES
in /*boot*/loader.conf, the kernel turns to fried chicken at boot time.
Fried chicken
atapicam
tries to query it, it just repeats the follwoing (output from dmesg with
boot -v):
Start with some more basic information, like how it is recognized at
boot, and whether it works *without* ATAPICAM.
___
freebsd-questions@freebsd.org mailing
Hello all,
Whilew trying to get CD burning working under FreeBSD 6.0 (and
6.1-PreRelease), I keep getting the following error in my dmesg and cd1
is never created. The drive is a Philips CDRW4012P. It shows up
as /dev/acd1 and reports correctly in dmesg. However, once atapicam
tries to query
Hello all,
Whilew trying to get CD burning working under FreeBSD 6.0 (and
6.1-PreRelease), I keep getting the following error in my dmesg and cd1
is never created. The drive is a Philips CDRW4012P. It shows up
as /dev/acd1 and reports correctly in dmesg. However, once atapicam
tries to query
Hi,
When I kldload atapicam the permissions in /etc/devfs.conf for cd0
are _not_ honored. (I want cd0 to have 0666)
When I put atapicam_load=YES in /boot/loader.conf the permissions are
set the way I want them.
I would like to make the choice for atapicam later if posssible, so my
question
dick hoogendijk [EMAIL PROTECTED] wrote:
When I kldload atapicam the permissions in /etc/devfs.conf for cd0
are _not_ honored. (I want cd0 to have 0666)
When I put atapicam_load=YES in /boot/loader.conf the permissions
are set the way I want them.
I would like to make the choice
On Saturday 21 January 2006 14:26, Fabian Keil wrote:
dick hoogendijk [EMAIL PROTECTED] wrote:
When I kldload atapicam the permissions in /etc/devfs.conf for cd0
are _not_ honored. (I want cd0 to have 0666)
When I put atapicam_load=YES in /boot/loader.conf the permissions
are set the way
-version: 3.113
X-GNATS-Notify:
Submitter-Id: current-users
Originator:Daniel S. Haischt
Organization: Daniel S. Haischt IT Consulting
Confidential: no
Synopsis: FreeBSD 5.3 ATA unreliability if using ATAPICAM
Severity: serious
Priority: high
Category: kern
Class
--- Daniel S. Haischt wrote:
Can you read through the attached PR and comment
its contents, please?
It's a little too technical for me, but let me add
the components of one of my trouble PCs:
atapci0: VIA 82C596B UDMA66 controller
ad0: 43979MB IBM-DTLA-307045/TX6OA50C [89355/16/63]
at
--- Rob [EMAIL PROTECTED] wrote:
--- Daniel S. Haischt wrote:
Can you read through the attached PR and comment
its contents, please?
It's a little too technical for me, but let me add
the components of one of my trouble PCs:
atapci0: VIA 82C596B UDMA66 controller
ad0: 43979MB
Greetings,
I seem to have made a small amount of progress with my atapicam boggle.
I was able to get a kernel with the atapicam driver configured to boot
by taking the drive off of the 2nd channel of my PDC20269-based atapter
and configure it as a slave on the 2nd channel of my motherboard's
Greetings,
Just an update I pulled out the Promise adapter and connected my disk to the
primary embedded IDE controller (max speed PIO 4) Left the atapi CDRW drive
as a SLAVE on the secondary controller. Next, I tried ripping an audio CD with
cdda2wav, and to my surprise, it was
Hope this helps someone. I'm not at all sure
where/what the problem is but
I'll be happy to run on the embedded controller for
the time being. (while
PIO 4 != DMA 133, reliability/functionality is
king!)
Neither have I an idea what going on here, but
after having upgraded a few PCs from
Date: Fri, 28 Jan 2005 14:38:14 +0100
Subject: Re: 5.3 interrupt storm (atapicam) and I/O error
oops, did forget the tixt file ...brbrDaniel S. Haischt schrieb:br I
don't know whether this is related to your issue,br but on one of my boxes I
am also getting an interruptbr storm with atapicam
will boot with atapicam enabled. I don't seem to be able to use my
motherboard's embedded EIDE controller with the Promise adapter installed.
I don't see any obvious I/O or interrupt conflicts, but I also don't have
too much control over it with this old SuperMicro mainboard.
Seems odd to me
whether this is related to your issue,
but on one of my boxes I am also getting an interrupt
storm with atapicam enabled.
On FreeBSD 5.2.1 I did not experience any interrupt
storm issues, even if using the same hardware configuration.
Have a look at the attached text file for a detailed
description
Greetings,
I seem to have made a little progress with the atapicam driver. It seems if I
force PIO mode (hw.ata.atapi_dma=0 in /boot/loader.conf) a kernel with the
atapicam device will boot. I still cannot access a disk in the drive however
either via the acdx device or the new cdx device
On 01/28/05 08:38:14, Daniel S. Haischt wrote:
oops, did forget the tixt file ...
Daniel S. Haischt schrieb:
I don't know whether this is related to your issue,
but on one of my boxes I am also getting an interrupt
storm with atapicam enabled.
On FreeBSD 5.2.1 I did not experience any interrupt
-device atapist # ATAPI tape drives
+#deviceatapifd # ATAPI floppy drives
+#deviceatapist # ATAPI tape drives
optionsATA_STATIC_ID # Static device numbering
+# FOR CDRECORD to work with ATAPI device.
+device atapicam
Hi,
Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM
(using KsCD)? Maybe we have fallen on the same kind of bug concerning
atapicam.
If you have KDE, maybe you should try to reproduce the problem I had. I've no
time to test your scenario (the one with the EIDE
I don't know whether this is related to your issue,
but on one of my boxes I am also getting an interrupt
storm with atapicam enabled.
On FreeBSD 5.2.1 I did not experience any interrupt
storm issues, even if using the same hardware configuration.
Have a look at the attached text file
oops, did forget the tixt file ...
Daniel S. Haischt schrieb:
I don't know whether this is related to your issue,
but on one of my boxes I am also getting an interrupt
storm with atapicam enabled.
On FreeBSD 5.2.1 I did not experience any interrupt
storm issues, even if using the same hardware
Greetings,
My problem might be slightly different than yours. My system hangs during the
boot process whenever I boot a kernel with atapicam enabled. A can't do
anything but reboot the box at that point.
Maybe this is a good time to learn to use the kernel debugger. When I get home
Greetings,
Not sure what to think about this yet but it definitely has something to do
with having my ATAPI CD connected to the 2nd channel of my Promise Ultra 133
TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the kernel
will boot with atapicam enabled. I don't seem
STATUS)
resid: 24576
So I thought I'd try enabling atapicam and trying to use my EIDE CD drive but
the system hangs on boot with a message about an interrupt storm (throttling
input).
I tried to disable the 'atapicd' device but it didn't seem to help.
Hoping someone has the magic potion
atapicam to access the atapi CD
through the SCSI interface.
In addition to this message there is a very
annoying 30 something second delay.
15 seconds, perhaps? As in
options SCSI_DELAY=15000# Delay (in ms) before probing SCSI
in the GENERIC kernel?
You
Hello All,
I am referring to the standard non-critical kernel error message:
cd0: Attempt to query device size failed: NOT READY, Medium not present
This occurs when one compiles the device atapicam to access the atapi CD
through the SCSI interface. In addition to this message there is a very
I'm running 5.3-RELEASE and want to use k3b for CD burning. I have an
IDE CD burner and IDE DVD drive. Do I need to have atapicam loaded in
the kernel? Has this been depricated in 5.3? I notice the following in
my GENERIC kernel config:
salamander# cat /sys/i386/conf/GENERIC | grep atapi
On Sun, Jan 02, 2005 at 10:59:05AM -0500, Trey Sizemore wrote:
I'm running 5.3-RELEASE and want to use k3b for CD burning. I have an
IDE CD burner and IDE DVD drive. Do I need to have atapicam loaded in
the kernel? Has this been depricated in 5.3? I notice the following in
my GENERIC
On Tue, 7 Dec 2004 19:26:33 -0500, Dev Tugnait [EMAIL PROTECTED] wrote:
Post your dmesg.
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD
for ATAPICAM...
Drive is ATAPI (using ATAPICAM)
Checking for MMC style command set...
Drive is MMC style
Setting default read size to 26 sectors (61152 bytes).
Verifying CDDA command set...
Expected command set reads OK.
Table of contents (audio tracks only):
track
: No such file or directory
Checking /dev/cd0c for cdrom...
CDROM model sensed: SONY CD-RW CRX175A1 5YS3
Checking for ATAPICAM...
Drive is ATAPI (using ATAPICAM)
Checking for MMC style command set...
Drive is MMC style
Setting default read size to 26 sectors
of the relevant ATAPICAM options are in the kernel.
However, when I fire it up, it just sits there and does nothing.
Nothing meaning no recording, no timing out, nothing. It won't even
respond to kill -9. I've also tried camcontrol with the test unit
ready option, same response. Anyone know what's going
Hello all,
I'm trying to get some CDs of mine onto the hard drive, using
cdparanoia. All of the relevant ATAPICAM options are in the kernel.
However, when I fire it up, it just sits there and does nothing.
Nothing meaning no recording, no timing out, nothing. It won't even
respond to kill -9
I been following the progress of the 5.3 release and I thought they were
changing the shceduler from SCHED_4BSD to SCHED_ULE? Also I recently
acquired a DVD+-RW and was wondering if I should stick with using burncd
and growisfs with the standard /dev/acd0 or should I switch to using
atapicam
with the standard /dev/acd0 or should I switch to using
atapicam? Is there any sort of a performance gain? What are the
advantages and disadvantages of both?
FYI,
Using burncd has been broken for me in -CURRENT since early June. The
process reaches the stage of fixating, but then my kernel panics
needed the
P1003_1B option added to a kernel. (It's now just the _KPOSIX option, and
it's already in there.)
I got as far as putting in the atapicam and related devices. This happens
whether or not I leave the atapicd driver in place. (dmesg output below is
without.)
I enclose dmesg
In message [EMAIL PROTECTED], FreeBsdBeni writes:
I'm having _exactly_ the same problem... :-( Mine is a Pioneer DVR-107D,
firmware v1.18 on a 5.2.1-REL-p11.
dmesg :
cd1 at ata1 bus 0 target 0 lun 0
cd1: PIONEER DVD-RW DVR-107D 1.18 Removable CD-ROM SCSI-0 device
cd1: 16.000MB/s transfers.
I
On Friday 15 October 2004 21:35, Peter Seebach wrote:
In message [EMAIL PROTECTED], FreeBsdBeni writes:
I'm having _exactly_ the same problem... :-( Mine is a Pioneer DVR-107D,
firmware v1.18 on a 5.2.1-REL-p11.
dmesg :
cd1 at ata1 bus 0 target 0 lun 0
cd1: PIONEER DVD-RW DVR-107D 1.18
the P1003_1B
option added to a kernel. (It's now just the _KPOSIX option, and it's already
in there.)
I got as far as putting in the atapicam and related devices. This happens
whether or not I leave the atapicd driver in place. (dmesg output below is
without.)
I enclose dmesg and config file
In message [EMAIL PROTECTED], Peter Seebach write
s:
Problem: CD burning Always Fails. Failure mode is 100% repeatable and
consistent:
A followup: I have an HP DVD Writer dvd630i.
1. If I install only the DVD Writer dvd630i, as a master, the kernel panics
and won't boot.
2. If I install
FreeBSD Enthusiasts,
I have been using cdrecord since I built my system. I
have an Asus A7N8X delux motherboard, AMD 3200+ cpu,
2G of ram and (2) 15,000 rpm scsi drives.
I recently bought a Toshiba DVD+r/-r burner, which I
replaced my DVDr/CDRW drive with.
The new drive is detected at bootup:
with.
The new drive is detected at bootup:
acd0: DVDR TSSTcorpCD/DVDW TS-H552B at ata0-master
PIO4
Do you later see lines like:
cd0 at ata0 bus 0 target 0 lun 0
cd1 at ata1 bus 0 target 0 lun 0
cd2 at ata1 bus 0 target 1 lun 0?
If not, you probably need to add
device atapicam
to your
?
If not, you probably need to add
device atapicam
You also need
devicecd
So it will attach to the DVD burner.
See the handbook on adding atatpicam to your kernel:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html#ATAPICAM
to your kernel
?
If not, you probably need to add
device atapicam
to your kernel configuration.
However, cdrecord --scanbus no longer can see the
drive through scsi emulation.
What does it see?
Regards
Fabian
Other than what I mention in my post, there's nothing
more detected at boot-up
--- Matt Navarre [EMAIL PROTECTED] wrote:
device atapicam
You also need
devicecd
Thank you for the info!
I didn't think it was no longer a kernel conf option
since I didn't see it in the NOTES file (replacement
for LINT??) and thought it should have been loaded
to
atapicam. I reinstalled 4.10 for testing and k3b works perfectly. Is
atapicam really the problem as I suspect? If so, will this be fixed prior to
5.3 release. Apologize in advance if this is a silly question.
Thanks for your assistance, please let me know if you need additional info.
Derrick
of
other people are having the same issue, and all theses guys are pointing to
atapicam. I reinstalled 4.10 for testing and k3b works perfectly. Is
atapicam really the problem as I suspect? If so, will this be fixed prior to
5.3 release. Apologize in advance if this is a silly question
theses guys are pointing to
atapicam. I reinstalled 4.10 for testing and k3b works perfectly. Is
atapicam really the problem as I suspect? If so, will this be fixed prior to
5.3 release. Apologize in advance if this is a silly question.
Thanks for your assistance, please let me know if you
): b_bcount 5 is not on a sector boundary (ssize 2048)
Is this an ATAPICAM or ATA issue or is it required that reads start at a
sector boundary? I assume that this code at least works on Linux systems
and I had always assumed that, even though the disk must start a
transfer at a sector boundary
I have added a Sony SDX-420 ATAPI tape drive to a FreeBSD 5.2.1-RELEASE system.
The following is part of the kernel build:
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device atapicam
# SCSI peripherals
device scbus
I have added a Sony SDX-420 ATAPI tape drive to a FreeBSD 5.2.1-RELEASE system.
The following is part of the kernel build:
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device atapicam
# SCSI peripherals
device scbus
On Wed, Mar 24, 2004 at 12:15:33AM -0500, Ed Alley wrote:
Andrew Gould wrote;
The description of the DVD burner states DVD+RW. Are you sure it can
burn DVD-R's?
OOPS ;)
Andrew also wrote:
A couple of us have experienced difficulties with Memorex media. Consider
testing
On Wed, Mar 24, 2004 at 12:15:33AM -0500, Ed Alley wrote:
Thanks for the hints. I'm new to DVDs and didn't realize that one DVD
media is not necessarily the same as another; or the fact that the little
- or + on the label means something important. (:-)
Have a look to
tools.
Chuck Swiger replied:
Yes-- consider using device atapicam + the sysutils/dvd+rw-tools port.
Thank-you Vulpes and Chuck; the atapicam mechanism looks like a fine idea.
However,
I am having problems getting it to work for me...
O.K. I am running FreeBSD 4.9. I built a new kernel
1 - 100 of 134 matches
Mail list logo
