From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Fighting with K7VZA (via KT133A/686B): Any news?
Date: Thu, 27 Sep 2001 13:28:23 -0400 [thread overview]
Message-ID: <200109271728.f8RHSNN08448@deathstar.prodigy.com> (raw)
In-Reply-To: <01092523011505.01149@localhost.localdomain>
In article <01092523011505.01149@localhost.localdomain>,
Rob Landley <landley@trommello.org> wrote:
| Does the best course of action at this point involve attempting to get money
| back, and if so, which motherboard can actually accept ~gigahertz athlon and
| PC133 memory and possibly even do something useful with it under any known or
| expected 2.4 kernel variant?
I would certainly return the board ASAP. The chances are that you have
a defective example rather than a bad design, but you might want to be
prepared for a brand switch if the next one doesn't work. But see below...
| Thanks for your time. (How much did Tom's Hardware get paid to recommend
| this motherboard as "Rock Solid"? What, Talc? Pumice? Sandstone? Perhaps
| a particularly flaky vein of mica?)
I wouldn't say that even in jest. I sometimes question the competence
of those reviews, and often the relevance, but I think they're honest.
Possible causes:
Power supply. BIOS option setting. Memory (memtest doesn't use the cpu
specific stuff to get the high data rate, at least my old copy).
Board I use:
Abit KK266. With the Athlon optimization and 2.4.9ac14+patch. Runs
solid with 1GB RAM, high memory enabled, 1.4GHz CPU speed. And is stable
for 10% (146MHz FSB) o/c as well, so I think it's really stable.
--
bill davidsen <davidsen@tmr.com>
"If I were a diplomat, in the best case I'd go hungry. In the worst
case, people would die."
-- Robert Lipe
prev parent reply other threads:[~2001-09-27 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 3:01 Fighting with K7VZA (via KT133A/686B): Any news? Rob Landley
2001-09-27 17:28 ` bill davidsen [this message]
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=200109271728.f8RHSNN08448@deathstar.prodigy.com \
--to=davidsen@tmr.com \
--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