In message <[EMAIL PROTECTED]>, Brian Fun
dakowski Feldman wrote:
>Have you either tried disabling DMA on the drive? This is easily achieved
>by the following (whitespace mangled):
>
>--- atapi-all.c 1999/10/10 18:08:38 1.19
>+++ atapi-all.c 1999/10/23 16:51:12
>@@ -135,7 +135,8 @@
>
It seems Doug Rabson wrote:
> On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote:
>
> > Have you either tried disabling DMA on the drive? This is easily achieved
> > by the following (whitespace mangled):
>
> I'll try it on Monday.
Hmm, as well as DMA might be the reason, it only applies to
On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote:
> Have you either tried disabling DMA on the drive? This is easily achieved
> by the following (whitespace mangled):
I'll try it on Monday.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd.
Have you either tried disabling DMA on the drive? This is easily achieved
by the following (whitespace mangled):
--- atapi-all.c 1999/10/10 18:08:38 1.19
+++ atapi-all.c 1999/10/23 16:51:12
@@ -135,7 +135,8 @@
udmamode(atp->atapi_parm),
In message <[EMAIL PROTECTED]>, Paul van der Zwan wrote:
>
>I switched to the 'new' atapi driver and I am having trouble with my cdrom
>which worked fine using the old wd driver.
>
>I have the following in my config file :
>
>controller ata0
>device atadisk0
>device
On Sun, 31 Oct 1999, Paul van der Zwan wrote:
>
> I switched to the 'new' atapi driver and I am having trouble with my cdrom
> which worked fine using the old wd driver.
>
> I have the following in my config file :
>
> controller ata0
> device atadisk0
> device a
I switched to the 'new' atapi driver and I am having trouble with my cdrom
which worked fine using the old wd driver.
I have the following in my config file :
controller ata0
device atadisk0
device atapicd0
The device exists:
$ ls -l /dev/acd0*
brw-r-
