Re: pciide flags

----- Original Message -----
From: <[email protected]>
To: "Nick Hudson" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, April 17, 2002 6:29 PM
Subject: Re: pciide flags


> [email protected] wrote:
> > On Wednesday 17 April 2002 5:58 pm, [email protected] wrote:
> > > [email protected] wrote:
> > > > On Wednesday 17 April 2002 4:25 pm, [email protected] wrote:
> > > > [...]
> > > >
> > > > > The connected drives are two Quantum Fireballs.
> > > >
> > > > I believe this is your problem. See
> > > >
> > > > http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=10502
> > > >
> > >
> > > I don't think it is exactly the same, unless some change has made
> > > the problem in that PR happen all the time.
> > >
> > > The point is that the kernel from the 20020121 snapshot won't boot
> > > on my system. I presume that someone tried it after building it, so
> > > I would like to work out what is different.

I'd be surprised if it's that, unless you get fsck going hard on both disks.

> > I'm fairly certain I ran this for a while with no problems. I'd download
the
> > kernel and try it, but I'm not near my CATS atm.
> >
> > BTW, if you've got a fast machine you can build a snapshot yourself
using
> >
> > build.sh -m cats -R ... -D ...
> >
> > it'll be ELF as well.
>
> I don't want to build a snapshot, I just want to try out a CATS kernel
> built from my development tree.
>
> When that didn't work I thought I would try a pre-built kernel. The fact
> that it doesn't work either makes me think that it isn't my modified
source
> that is broken, but instead something strange about the machine
> configuration.

What configuration are the disks in?  IE channel, master slave?

Also what firmware are you running (not that it should really have an
effect, but you never know)

Cheers,
Chris