From: alex@foogod.com
To: Stephen Wille Padnos <stephenwp@adelphia.net>
Cc: Byron Stanoszek <gandalf@winds.org>,
"David D.W. Downey" <pgpkeys@hislinuxbox.com>,
linux-kernel@vger.kernel.org
Subject: Re: VIA VT82C686X
Date: Wed, 31 Jan 2001 09:49:29 -0800 [thread overview]
Message-ID: <20010131094929.B16787@draco.foogod.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101311148560.20840-100000@winds.org> <3A7847B1.C8ABDDE1@adelphia.net>
In-Reply-To: <3A7847B1.C8ABDDE1@adelphia.net>
On Wed, Jan 31, 2001 at 12:13:21PM -0500, Stephen Wille Padnos wrote:
> Even though the motherboard *should* perform the same regardless of the amount
> of RAM, it may not. Physically, the refresh needs higher current drive when
> there are more modules. I have seen a BIOS option to set the DRAM refresh
> current (RAS, CAS settable to 10 or 16 mA each), but that was only on one
> motherboard that I can remember - you might want to check for this.
It should also be noted that there are several motherboards out there that
claim to support 1GB or more of RAM which just plain don't, causing problems
like this because the design is inadequate for the power requirements of that
many chips (I have, unfortunately, had to work with some of these). Sometimes
you can work around it using different types of RAM (buffered vs. unbuffered,
etc) but even this is iffy and not something I'd rely on for anything too
important.
-alex
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 2:59 VIA VT82C686X David D.W. Downey
2001-01-31 3:10 ` Byron Stanoszek
2001-01-31 5:12 ` David D.W. Downey
2001-01-31 17:04 ` Byron Stanoszek
2001-01-31 17:13 ` Stephen Wille Padnos
2001-01-31 17:49 ` alex [this message]
2001-01-31 6:49 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 3:19 Frédéric L. W. Meunier
2001-01-31 6:52 ` Andre Hedrick
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=20010131094929.B16787@draco.foogod.com \
--to=alex@foogod.com \
--cc=gandalf@winds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgpkeys@hislinuxbox.com \
--cc=stephenwp@adelphia.net \
/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