From: Peter DeVries <peter@devries.tv>
To: linux-kernel@vger.kernel.org
Subject: Re: Drvie Corruption CONSTANTLY with Linux and KT7-RAID
Date: Tue, 20 Mar 2001 22:21:46 -0500 [thread overview]
Message-ID: <3AB81E4A.9060604@devries.tv> (raw)
In-Reply-To: <Pine.LNX.4.10.10103151153050.28602-100000@coffee.psychology.mcmaster.ca>
I have noiw tried the following
Diffrent Ram
No PNP/ Manual set IRQ's
All bios settings are manual. CPU speed etc
-X 34
Diffrent Controlllers ide0,ide1,ide2
Still getting drive corruption as soon as I turn on DMA mode.. I even
tested 2 HD's and only activating DMA on 1. (seperate controllers) and
the both got corrupted.
any ideas?
Mark Hahn wrote:
>> least 30 times now. I have a ABIT KT7-RAID and no
>
>
> have you installed the latest bios, and/or turned off the
> bugusly agressive pci-bridge settings? they are responsible
> for all verified kt133/ide problems reported so far.
>
>
>
next parent reply other threads:[~2001-03-21 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10103151153050.28602-100000@coffee.psychology.mcmaster.ca>
2001-03-21 3:21 ` Peter DeVries [this message]
2001-03-15 14:20 Drvie Corruption CONSTANTLY with Linux and KT7-RAID Peter DeVries
2001-03-15 15:44 ` Jonathan Morton
2001-03-15 22:34 ` Russell King
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=3AB81E4A.9060604@devries.tv \
--to=peter@devries.tv \
--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