From: "Glenn C. Hofmann" <hofmanng@swbell.net>
To: "Frédéric L. W. Meunier" <0@pervalidus.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA IDE driver status ?
Date: Sat, 31 Mar 2001 12:00:41 -0600 [thread overview]
Message-ID: <986061646.10078.0.camel@hofmann1> (raw)
In-Reply-To: <20010331004132.D111@pervalidus>
In-Reply-To: <20010331004132.D111@pervalidus>
I am not sure if this applies in your case, but I was getting problems
such as this on my Abit KT7-RAID and had the correct cables, also. One
day, on a hunch after reading a post from Alan about overclocking, I
took my Athlon 750 down to 850 from 1.05 GHz and all is working great
now. If your overclocking, I would suggest not doing so (at least not
so much), based on my experience. I am also using the v4.0 driver.
Chris
On 31 Mar 2001 00:41:32 -0300, Frédéric L. W. Meunier wrote:
> Hi. I really can't get UDMA66 with the VIA driver. I tried
> everything, also a new motherboard (ASUS A7Pro) with a
> ATA100/ATA66 cable (using both ends...)!
>
> All I get are the usual CRC error messages.
>
> So, there's no UDMA66 for any vt82c686a ? I'm using 2.4.3.
>
> If there's no UDMA66, what are the advantages using this
> driver ?
>
> TIA.
>
> --
> 0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-03-31 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 3:41 VIA IDE driver status ? Frédéric L. W. Meunier
2001-03-31 18:00 ` Glenn C. Hofmann [this message]
2001-03-31 18:14 ` Frédéric L. W. Meunier
2001-03-31 21:06 ` Glenn C. Hofmann
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=986061646.10078.0.camel@hofmann1 \
--to=hofmanng@swbell.net \
--cc=0@pervalidus.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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