LKML Archive on
help / color / mirror / Atom feed
From: Nicholas Knight <>
To: Sean Swallow <>, <>
Subject: Re: AMD viper chipset and UDMA100
Date: Thu, 27 Sep 2001 14:36:25 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>
In-Reply-To: <>

On Thursday 27 September 2001 02:26 pm, Sean Swallow wrote:
> List,
> I just got a tyan tiger w/ the AMD Viper chipset on it. For some
> reason Linux will only set the onboard (AMD viper) chains to UDMA33.
> I'm using linux 2.4.9, and I have also tried 2.4.10. Is there a
> limitation to the AMD Viper driver?
> PS. The cables (2) are BRAND new ata100 cables.
> cheers,

Welcome to hell.
I belive the solution is to enable the option "IGNORE word93 Validation 
BITS" at the bottom of the "IDE, ATA and ATAPI Block Devices" menu 
accessable in "ATA/IDE/MFM/RLL support"

  reply	other threads:[~2001-09-27 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 21:26 AMD viper chipset and UDMA100 Sean Swallow
2001-09-27 21:36 ` Nicholas Knight [this message]
2001-09-27 21:59 ` Vojtech Pavlik
2001-09-27 22:16   ` Dan Hollis
2001-09-27 22:24     ` Vojtech Pavlik
2001-09-27 22:54       ` Dan Hollis
2001-09-28  2:21         ` Jacob Luna Lundberg
2001-09-27 23:37       ` Sean Swallow
2001-09-28 10:21         ` [patch] " Vojtech Pavlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).