-On [2315 00:00], Will Saxon ([EMAIL PROTECTED]) wrote:
>I will continue to use ata because my drives work (albeit in PIO mode
>apparently) and I don't play audio off the cdrom. Some people will
>probably hold off on upgrading to 4.0 because of this, and I don't know if
>anyone important cares
Well, while this isn't a problem that causes panics or makes people unable
to use their machines, I think maybe the removal of the older wd driver
ought to be held off until the ata driver provides all the features wdc
does don't you think? I guess the philosophy here is that there shouldn't
be dr
On Tue, 14 Mar 2000, Patrik Sundberg wrote:
> Tested my CDROM for audio just now - works fine (at least pressing the
> buttons on the unit, have no softwareplayer to test with so it might not
> work anyway - my cd is total crap and usually has all kinds of problems..)
The problem is with cdcontr
On Tue, Mar 14, 2000 at 01:33:55PM -0800, Kris Kennaway wrote:
> On Tue, 14 Mar 2000, Patrik Sundberg wrote:
>
> > I also get this when booting - think it started happening when I started
> > using the new ata-driver. For me it happens when the root is supposed to be
> > mounted (from dmesg):
>
Will Saxon <[EMAIL PROTECTED]> writes:
> ad0: READ command timeout - resetting
> ata0: resetting devices .. done
(...)
> I dont get any panics or anything, and after the reset to PIO everything
> seems to work fine.
You're lucky ;-)
I have the same kind of messages, but it ends with a dead fre
On Tue, 14 Mar 2000, Patrik Sundberg wrote:
> I also get this when booting - think it started happening when I started
> using the new ata-driver. For me it happens when the root is supposed to be
> mounted (from dmesg):
> As you can see I am using a seagate disk and I am having the same problem
On Tue, Mar 14, 2000 at 12:17:15PM -0500, Will Saxon wrote:
> Hello,
>
> I think this may have already been presented/answered but I am not
> certain. I have noticed recently that every so often I will get the
> following set of messages, generally right after the bootup sequence
> finishes:
>
>
Hello,
I think this may have already been presented/answered but I am not
certain. I have noticed recently that every so often I will get the
following set of messages, generally right after the bootup sequence
finishes:
ad0: READ command timeout - resetting
ata0: resetting devices .. done
ad0:
