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 driver redundancy in a -RELEASE or something?
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 about that but imho it kind of looks bad.
Just a thought. Again, my box works, just not as advertised :). Could very
well be user error, I just don't know.
-will
On Tue, 14 Mar 2000, 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):
>
> > As you can see I am using a seagate disk and I am having the same problem.
>
> I've always had this problem with the new ata drivers (on a Western
> Digital, though). Looks like it's just something we have to Deal With :-(
> Plus, my CDROM doesn't do audio any more.
>
> Kris
>
> ----
> In God we Trust -- all others must submit an X.509 certificate.
> -- Charles Forsythe <[EMAIL PROTECTED]>
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
