On Sun, Dec 12, 1999 at 11:08:24PM -0800, Mike Smith wrote:
> You'll need to take this up with Soren; I suspect though that the simplest
> answer for you is going to be to stick with 'wd' until you get yourself a
> less-broken disk, or manage to analyse the problem in greater depth.
Ideally I (w
It seems Adam Wight wrote:
> Against my better judgment, I've been running -current on, among other
> machines, a Dell Latitude XP 475C... The wd driver manages to deal with
> the inevitable cruft quite nicely, but the ata driver refuses to mount
> the root partition.
>
> To the best of my knowl
> > > boot -v output using the wd driver follows:
> >
> > That's not very helpful; we know it works. How about some information on
> > the problem?
>
> Well... I'd sure like to send a boot -v for a kernel using ata... I don't
> have the right hardware here to use a serial console, however.
Th
> > boot -v output using the wd driver follows:
>
> That's not very helpful; we know it works. How about some information on
> the problem?
Well... I'd sure like to send a boot -v for a kernel using ata... I don't
have the right hardware here to use a serial console, however.
Here are the rel
> Against my better judgment, I've been running -current on, among other
> machines, a Dell Latitude XP 475C... The wd driver manages to deal with
> the inevitable cruft quite nicely, but the ata driver refuses to mount
> the root partition.
>
> To the best of my knowledge the chipset is the Wes
