For years I have put 'device atapicam' in my kernel. If my memory
serves my well, this was to assist with dvd recording. I must have
missed something. Is it now as simple as adding hw.ata.atapi_dma="1"
to /boot/loader.conf?
atapicam is no longer needed after migrat
On 25.09.2012 07:51, Garrett Cooper wrote:
For years I have put 'device atapicam' in my kernel. If my memory
serves my well, this was to assist with dvd recording. I must have
missed something. Is it now as simple as adding hw.ata.atapi_dma="1"
to /boot/loader.conf?
a
Hello,
For years I have put 'device atapicam' in my kernel. If my memory serves
my well, this was to assist with dvd recording. I must have missed
something. Is it now as simple as adding hw.ata.atapi_dma="1" to
/boot/loader.conf?
cc -c -O2 -frename-registers -pipe
> 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-current@freebsd.org so the develope
> On 11/27/11, Lowell Gilbert wrote:
> > "b. f." writes:
> >>> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel
> >>> > > config file?
> >>> > > Are they redundant? Kern
I always have media in that drive, but I could try without media. I've
had to disable atapicam too. Only thing is, I have a CD-RW and a DVD-RW
that I can't use very well without atapicam.
On Tue, 2003-12-02 at 06:16, Mark Dixon wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Ha
I saw that message about rev.1.23 of ata_lowlevel.c. I had this problem
prior to that change.
On Tue, 2003-12-02 at 05:12, Bruce Evans wrote:
> On Tue, 2 Dec 2003, Sean McNeil wrote:
>
> > I've tried over several weeks to get ATAPICAM to work for me. I've
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 02 Dec 2003 11:48, Sean McNeil wrote:
> Hello,
>
> I've tried over several weeks to get ATAPICAM to work for me. I've
> tried with and without acpi (compiled in or disabled via. boot). I've
> tried turning o
On Tue, 2 Dec 2003, Sean McNeil wrote:
> I've tried over several weeks to get ATAPICAM to work for me. I've
> tried with and without acpi (compiled in or disabled via. boot). I've
> tried turning on all debug. I've tried a few misc. thigs. All leave my
Did yo
Hello,
I've tried over several weeks to get ATAPICAM to work for me. I've
tried with and without acpi (compiled in or disabled via. boot). I've
tried turning on all debug. I've tried a few misc. thigs. All leave my
system hanging after the GEOM initialization without any
Hi all,
Since the ATAnG commit I'm no longer able to burn any
Cd's. 5.X, 5.1R did work.
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
pregap1: -1
Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 Jörg Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.7'
Driveropts: 'bu
media
working on FreeBSD 5.1-current (Nov 10), on a Plextor PX708A. (DVD+RW
worked out of the box with "burncd -f /dev/acd0 dvdrw data.iso
fixate").
1) roll ata-lowlevel.c back to version 1.22
2) enable atapicam in the kernel
3) rebuild/reinstall kernel
4) install dvd+rw-tools from
At Thu, 27 Nov 2003 08:54:53 -0400,
Bremner David wrote:
>
> I have a 5.1-current system of Nov 10, also using rev 1.23 of
> ata-lowlevel.c.
>
> Without atapicam in the kernel, it boots ok. With atapicam in the
> kernel it hangs at the messages (written down from the screen)
&
At Thu, 27 Nov 2003 00:07:30 -0600,
Dan Nelson wrote:
>
> In the last episode (Nov 27), Bruce Evans said:
> > [Resending due to no response after 2 weeks.]
> >
> > Rev.1.23 of ata-lowlevel.c broke atapicam on my BP6 system as shown
> > by the enclosed boot -v m
In the last episode (Nov 27), Bruce Evans said:
> [Resending due to no response after 2 weeks.]
>
> Rev.1.23 of ata-lowlevel.c broke atapicam on my BP6 system as shown
> by the enclosed boot -v messages (the system just hangs, apparently
> waiting for a disk interrupt that never
* Stuart Walsh, 2003-10-18 :
> I have an easily reproducable panic when using atapicam. Vague trace
This has nothing to do whatsoever with ATAPI/CAM! this is an inconsistency
between cam_periph.c and vfs_bio.c, you need to update the latter to rev.
1.418 or newer.
Thomas.
--
[EM
atapicam seems to have ceased being functional as well.
Performing OPC...
/usr/local/bin/cdrecord: Input/output error. send opc: scsi sendcmd:
retryable error
CDB: 54 01 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
David Gilbert wrote:
First of all, as someone noted with disk-at-once
Hi,
I have an easily reproducable panic when using atapicam. Vague trace
follows:
panic was caused by this:
KASSERT(bp->b_flags & B_PHYS, ("vmapbuf"));
trace:
vmapbuf
cam_periph
xptioctl
spec_ioctl
spec_vnoperate
vn_ioctl
ioctl
syscall
Let me know if you need any further
On Wed, 24 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-19, Guillaume écrivait :
>
> > Thanks for the patch. cd0 is faster now and ATAPICAM works great.
> > Are you going to commit the patch?
>
> DMA is now enabled for ATAPI/CAM i/o, as of atapi-cam.c rev. 1.26.
> T
Le 2003-09-19, Guillaume écrivait :
> Thanks for the patch. cd0 is faster now and ATAPICAM works great.
> Are you going to commit the patch?
DMA is now enabled for ATAPI/CAM i/o, as of atapi-cam.c rev. 1.26.
Thanks to all who tested and reviewed the change.
Thomas.
--
[EMAIL PRO
Le 2003-09-21, Sascha Holzleiter écrivait :
> i still have problems with atapicam and atang, while booting with
> atapicam i get these messages:
There is nothing abnormal with these messages.
> When trying to burn a disk with cdrecord i get the following panic:
> panic: mutex v
Le 2003-09-22, Matthias Andree écrivait :
> I'm getting complaints from ata or atapicam during boot-up, but my
>From CAM actually, and you can safely ignore them.
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailin
I'm getting complaints from ata or atapicam during boot-up, but my
CD-ROM seems fine (reading, at least). ACPI enabled, sym driver enabled
+ in use with a 875 chip (Tekram DC-390F) and cd0, da0, sa0, sa1.
Is this something to worry about?
dmesg excerpt:
...
atapci0: port 0xffa0-0xff
Hi,
i still have problems with atapicam and atang, while booting with
atapicam i get these messages:
Sep 21 23:30:17 dreamland kernel: atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 10 at device
31.1 on pci0
Sep 21 23:30:17 dreamland kernel: ata0: at 0x1f0 irq 14 on atapci0
Sep 21
Today's kernel with atapicam said:
acd0: WARNING - REQUEST_SENCE record from missing interrupt
and can not boot. Without one is OK.
--
Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]>
http://diary.waishi.jp/~yosimoto/diary/
___
[EMAIL PROTECTED] m
Le 2003-09-19, Guillaume écrivait :
> Thanks for the patch. cd0 is faster now and ATAPICAM works great.
That's good news!
> Are you going to commit the patch?
Yes, the patch is currently being reviewed.
--
[EMAIL PROTECTED]
___
[EMAI
h. cd0 is faster now and ATAPICAM works great.
Are you going to commit the patch?
Guillaume
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
noticed or checked for speed issues before the
first patch that you issued, only that I noticed the reported speed
went from 3.3MB/s to 33.3MB/s.
There is a new issue, though. Soren commited a change to ata-queue.c
this morning. This change together with atapicam, causes the system
to hang indefini
Le Mer 17/09/2003 à 07:40, Thomas Quinot a écrit :
> Le 2003-09-17, Bryan Liesner écrivait :
>
> > The patch seems to work, my cd0 and cd1 lines in the dmesg now report
> > 33.000 MB/s insetad of 3.300 MB/s.
>
> OK, good, so that's one half of the problem resolved. Now, can you test
> whether the
Le 2003-09-17, Bryan Liesner écrivait :
> The patch seems to work, my cd0 and cd1 lines in the dmesg now report
> 33.000 MB/s insetad of 3.300 MB/s.
OK, good, so that's one half of the problem resolved. Now, can you test
whether the actual performances are improved or still slow?
Thomas.
--
On Wed, 17 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-17, Guillaume écrivait :
>
> > > + if (atapi_dma && atp->channel->dma &&
> > > + (atp->param->config & ATA_DRQ_MASK) != ATA_DRQ_INTR)
> > > + atp->setmode(atadev, ATA_DMA_MAX);
> > > + else
> > > + atp->setmode(atadev, ATA_PIO_MAX)
Le 2003-09-17, Guillaume écrivait :
> > + if (atapi_dma && atp->channel->dma &&
> > + (atp->param->config & ATA_DRQ_MASK) != ATA_DRQ_INTR)
> > + atp->setmode(atadev, ATA_DMA_MAX);
> > + else
> > + atp->setmode(atadev, ATA_PIO_MAX);
Ahem. Replace atadev with atp on both lines
Le Mar 16/09/2003 à 09:22, Thomas Quinot a écrit :
> Le 2003-09-06, Guillaume écrivait :
>
> > I'm running FreeBSD 5-CURRENT (Aug. 28 2003) on a P3 733MHz, 768MB ram
> > with a LG DVD-RW/DVD-RAM burner. I would like to know why ATAPICAM is so
> > slow with my system.
On Tue, 16 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-16, Daniel Eischen écrivait :
>
> > I get this even without atapicam in the kernel. Is trying
> > CAMDEBUG and CAM_DEBUG_CDB going to show anything interesting?
>
> No, indeed, probably not. Can you try the fo
Le 2003-09-16, Daniel Eischen écrivait :
> I get this even without atapicam in the kernel. Is trying
> CAMDEBUG and CAM_DEBUG_CDB going to show anything interesting?
No, indeed, probably not. Can you try the following patch:
Index: ata-lowl
Several others have reported similar completely bogus sector size data.
> I suspect a problem in the new autosense code. It would be interesting
> to see what the kernel says when compiled with CAMDEBUG and running
> with CAM_DEBUG_CDB traces enabled (camcontrol debug -c).
I get this ev
Le 2003-09-06, Guillaume écrivait :
> I'm running FreeBSD 5-CURRENT (Aug. 28 2003) on a P3 733MHz, 768MB ram
> with a LG DVD-RW/DVD-RAM burner. I would like to know why ATAPICAM is so
> slow with my system.
Maybe because ATAPI/CAM does not actually enable DMA. Can you try the
f
Le 2003-09-06, Petri Helenius écrivait :
> Should this work or is the work to port this to ATAng still undergoing?
This should work, but does not, so the work is still in progress...
> panic: mutex Giant not owned at ../../../dev/ata/atapi-cam.c:117
Please try this patch.
Index: atapi-cam.c
=
Le 2003-09-13, Daniel Eischen écrivait :
> cd0 at ata1 bus 0 target 0 lun 0
> cd0: Removable CD-ROM SCSI-0 device
> cd0: 33.000MB/s transfers
> cd0: cd present [3737169375 x 3737169374 byte records]
Several others have reported similar completely bogus sector size data.
I suspect a problem in t
sual ones due to cdrecord usage
> which nobody seem to care about :-(
I too have problems similar to this. On one box, the kernel panics
(see message posted Sep 10, subject "Panic with ATAng + atapicam").
With or without atapicam, a CD is detected as being present when
it is not. On
t;
> If you're getting bogus values for the media/blocksize, or if it says
> there's a disk there when there isn't one, then you've got a problem either
> with the ATAPI or atapicam code.
>
> Ken
Regards,
Vladimir
___
[EMA
On Fri, Sep 12, 2003 at 08:57:22AM -0700, Kevin Oberman wrote:
> I am seeing a peculiar, possibly timing sensitive, crash that looks
> like if is probably in either atapicam or scsi_cd. The system is
> CURRENT as of yesterday morning.
>
> The crash happens frequently when nautilu
> Date: Fri, 12 Sep 2003 18:50:30 +0200
> From: Thomas Quinot <[EMAIL PROTECTED]>
>
> Le 2003-09-12, Kevin Oberman écrivait :
>
> > cdstart(c419d500,c4192000,1,c407cc30,c407cc00) at cdstart+0xcb
> > xpt_run_dev_allocq(c40b8c00,c407cc08,1,c418d800,c419d500) at
> > xpt_run_dev_allocq+0xab
> > xpt_
> Date: Fri, 12 Sep 2003 10:50:39 -0600
> From: "Kenneth D. Merry" <[EMAIL PROTECTED]>
>
> On Fri, Sep 12, 2003 at 08:57:22 -0700, Kevin Oberman wrote:
> > I am seeing a peculiar, possibly timing sensitive, crash that looks
> > like if is probably in e
On Fri, Sep 12, 2003 at 08:57:22 -0700, Kevin Oberman wrote:
> I am seeing a peculiar, possibly timing sensitive, crash that looks
> like if is probably in either atapicam or scsi_cd. The system is
> CURRENT as of yesterday morning.
>
> The crash happens frequently when nautilu
Le 2003-09-12, Kevin Oberman écrivait :
> cdstart(c419d500,c4192000,1,c407cc30,c407cc00) at cdstart+0xcb
> xpt_run_dev_allocq(c40b8c00,c407cc08,1,c418d800,c419d500) at
> xpt_run_dev_allocq+0xab
> xpt_schedule(c419d500,1,0,ce54ec78,dd5b6c70) at xpt_schedule+0xca
> cdstrategy(ce54ec78,0,0,0,d439f00
I am seeing a peculiar, possibly timing sensitive, crash that looks
like if is probably in either atapicam or scsi_cd. The system is
CURRENT as of yesterday morning.
The crash happens frequently when nautilus starts up. It does not
always crash, but does so fairly frequently and leaves my laptop
FYI, a fresh cvsup from yesterdays sources causes a panic with atapicam
in the kernel. My previous kernel was before ATAng was imported.
Fatal trap 18: integer divide fault while in kernel mode
instruction pointer = 0x8:0xc03dcd5b
stack pointer = 0x10:0xd70977c0
frame pointer
: unknown transfer phase
Rebooting the old kernel, rebuilding a new kernel without atapicam or
any of the SCSI devices cured the problem.
--
Conrad Sabatier <[EMAIL PROTECTED]> - "In Unix veritas"
___
[EMAIL PROTECTED] m
I have hit this one.
>
> If I boot my system with no floppy in the LS-120, the system panics
> where atapicam creates da0 for it. If there is a disk in the drive, it
> works fine.
>
> As yet, I havn't got the details of the panic, but if this is of
> interest to
ic (no news on that yet),
Mark> but I have hit this one.
Mark> If I boot my system with no floppy in the LS-120, the system
Mark> panics where atapicam creates da0 for it. If there is a disk in
Mark> the drive, it works fine.
Mark> As yet, I havn't got the details of the panic, bu
ot my system with no floppy in the LS-120, the system panics
> where atapicam creates da0 for it. If there is a disk in the drive, it
> works fine.
>
> As yet, I havn't got the details of the panic, but if this is of
> interest to anyone here, I will be willing to provide them
m panics
where atapicam creates da0 for it. If there is a disk in the drive, it
works fine.
As yet, I havn't got the details of the panic, but if this is of
interest to anyone here, I will be willing to provide them with them
(they wil have to be be copied out by hand, so I'm lot
Atacontrol detach / attach seems to panic if atapicam is complied in the
kernel.
Should this work or is the work to port this to ATAng still undergoing?
This is current from four days ago, just after Soren's ar DMA size commit.
# atacontrol detach 4
ad8: deleted from ar0 disk1
ar0: WA
Hi,
I'm running FreeBSD 5-CURRENT (Aug. 28 2003) on a P3 733MHz, 768MB ram
with a LG DVD-RW/DVD-RAM burner. I would like to know why ATAPICAM is so
slow with my system.
DMA is enabled for my ATAPI burner.
When I'm copying something using cd0, my system is very slow. (e.g. my
mouse
Hello,
shortly after last sunday, ATAng broke for me with atapicam
enabled; on a Toshiba Satelite 6000 Notebook; first
versions of ATAng worked flawlessly with atapicam, never
tested without.
Things broke when the newer probe-code for CD-slaves etc was
introduced.
Now it hangs as follows
On Tue, 26 Aug 2003, Kenneth Culver wrote:
> I think some people are already tracking this down related to the recent
> update of the ata drivers.
It would be nice if those people would post regarding their progress. A
lot of people depend on atapicam.
Doug
--
This .signature san
> free_hcb()
> atapi_action()
> xpt_run_dev_sendq()
> xpt_action()
> probe_start()
> ...
>
I think some people are already tracking this down related to the recent
update of the ata drivers.
Ken
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
last night's sources:
free_hcb()
atapi_action()
xpt_run_dev_sendq()
xpt_action()
probe_start()
...
appears to be a memory access error.
-Alfred
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
On Wed, 30 Jul 2003, John Baldwin wrote:
> On 25-Jul-2003 Nate Lawson wrote:
> > Please test devices such as USB keys, USB cameras, Firewire hard disks,
> > and ATAPICAM cd drives to be sure they still work with this patch.
> > Especially if you've needed a quirk before,
On Wed, 30 Jul 2003, John Baldwin wrote:
> On 25-Jul-2003 Nate Lawson wrote:
> > Please test devices such as USB keys, USB cameras, Firewire hard disks,
> > and ATAPICAM cd drives to be sure they still work with this patch.
> > Especially if you've needed a quirk before,
re addressed by this patch and no longer need the
> quirk.
>
> Please test devices such as USB keys, USB cameras, Firewire hard disks,
> and ATAPICAM cd drives to be sure they still work with this patch.
> Especially if you've needed a quirk before, it is important to see if
comments out the scsi_da quirks for
> devices that I believe are addressed by this patch and no longer need the
> quirk.
>
> Please test devices such as USB keys, USB cameras, Firewire hard disks,
> and ATAPICAM cd drives to be sure they still work with this patch.
> Especial
In article <[EMAIL PROTECTED]>, Nate Lawson wrote:
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Attached is a patch that disables ever sending 6 byte commands to buses
> that do not support them.
Got this trap, it's sitting there at the prompt, let me know how I can
help. The clie should be
.
Please test devices such as USB keys, USB cameras, Firewire hard disks,
and ATAPICAM cd drives to be sure they still work with this patch.
Especially if you've needed a quirk before, it is important to see if this
patch does not break your device. I hope to get this into the tree early
so
Hi,
Since I upgraded to 5.0-Release the cam-stuff acted a bit weird.
During the boot-proces, right after the SCSI-bus reset it gives these messages:
(probe1:ata0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0
(probe1:ata0:0:1:0): CAM Status: SCSI Status Error
(probe1:ata0:0:1:0): SCSI Status: Check Conditi
My apologies to the list for not looking in /sys/conf/NOTES before
posting. I wasn't aware of the "split". :)
A.
msg52522/pgp0.pgp
Description: PGP signature
I can't seem to find atapicam in NOTES. Is this voluntary? On the
atapicam website, it says that it's been integrated into current.
I can build a 5.0-release kernel with it, so has it just been forgotten
from NOTES? :)
Thanks
A.
anarcat@lenny[~/dump/c/src/sys/i386/conf]% cvs -R st
"Søren Schmidt" wrote:
> It seems Samuel Tardieu wrote:
> > Has the ATAPICAM patch entered the kernel sources already? I cannot
> > seem to find the option in LINT.
>
> No, Justin has called for a timeout on that
Why?
Supposedly the "hang on boot"
No it hasn't, there are still patches.
Ken
On Tue, 19 Mar 2002, Samuel Tardieu wrote:
> Has the ATAPICAM patch entered the kernel sources already? I cannot
> seem to find the option in LINT.
>
> Sam
> --
> Samuel Tardieu -- [EMAIL PROTECTED] -- http://www.rfc1149.net/s
It seems Samuel Tardieu wrote:
> Has the ATAPICAM patch entered the kernel sources already? I cannot
> seem to find the option in LINT.
No, Justin has called for a timeout on that
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
Has the ATAPICAM patch entered the kernel sources already? I cannot
seem to find the option in LINT.
Sam
--
Samuel Tardieu -- [EMAIL PROTECTED] -- http://www.rfc1149.net/sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
72 matches
Mail list logo
