wierd problem involving the command make install

[Vulpes Velox]

On Fri, 2 May 2003 09:25:05 -0700
Kris Kennaway <kris at obsecurity.org> wrote:

> On Sat, May 03, 2003 at 09:25:47AM -0500, Vulpes Velox wrote:
> > On Thu, 1 May 2003 22:31:16 -0700
> > Kris Kennaway <kris at obsecurity.org> wrote:
> > 
> > > On Sat, May 03, 2003 at 12:39:58AM -0500, Vulpes Velox wrote:
> > > 
> > > > In the last few days when I use the command 'make install' I get the
> > > > following error message...
> > > > 
> > > > ad1: READ command timeout tag=0 serv=0 - resetting
> > > > ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device
> > > > done
> > > > 
> > > > 
> > > > ...the drive appears to be working fine and I have managed to cat
> > > > and cp large chunks of both file systems with out problems. The only
> > > thing I have managed to come up with is a possible virus or something
> > > is major misconfigured. Any one have any ideas one this.
> > > 
> > > The drive is timing out in response to a read command.  It's most
> > > likely to either be marginal hardware or a low-quality IDE controller.
> > > If it really bothers you, try replacing the hardware.
> > 
> > Cool, thanks for the info. I think I am going to try putting the drive in
> > another box and see what happens.
> 
> I forgot to mention it could also be due to a poor quality cable
> (e.g. the message suggests that you don't have an ATA66-capable cable
> anyway, so your drive access speed is being limited to 33MHz).

The odd thing about that tought is that the cable I am using with it has
worked for close to two months with out any problems and nothing about it
has changed since then.

Another odd thing is I can install with out a problem using /stand/sysinstall, when the package part of it is working.