Alpha arch development list
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-alpha@vger.kernel.org
Subject: Re: XLT366 Memory Compatiblity...
Date: Tue, 8 Jun 2004 14:52:50 +0200	[thread overview]
Message-ID: <20040608125250.GD20632@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0406080536550.13212-100000@magellan.rkirkpat.net>

[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]

On Tue, 2004-06-08 05:46:54 -0600, Ryan Kirkpatrick <linux@rkirkpat.net>
wrote in message <Pine.LNX.4.21.0406080536550.13212-100000@magellan.rkirkpat.net>:
> 16Mbit in size. The SIMMs are parity (from the chip count). There is also

So they have an extra parity bit...

> a sticker on one of chips that has '3163667/23BT S023039 64MB'. I was told
> they came out of a Compaq Proliant server (don't know the model). All of
> this seems to indicate they _should_ be compatible with the XLTs.
> 
> One XLT366 is able to post AlpahBIOS with either four or eight of these
> SIMMs installed, and the memory count is either 256MB or 512MB
> respectively. Yet, when I boot Linux, I get an endless stream of ECC
> errors and corrections, slowing the system down so badly Linux is never
> able to fully boot. AlphaBIOS version is 5.66.

...but ECC requires more than one:)

> Lastly, I tested them in a Sparc LX (which also takes 72pin parity
> SIMMs). I installed the maximum of six SIMMs (384MB), and it was able to
> see the maximum 96MB it supports. Furthermore it was able to boot and run
> Linux without issue. It appears that as long as the SIMMs are not fully
> utilized they work fine. When fully utilized, they just don't work.

As I said, parity != ECC.

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-08 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 11:46 XLT366 Memory Compatiblity Ryan Kirkpatrick
2004-06-08 12:52 ` Jan-Benedict Glaw [this message]
2004-06-08 17:56   ` Thorsten Kranzkowski
2004-06-08 18:03     ` Jan-Benedict Glaw
2004-06-08 19:32       ` Thorsten Kranzkowski
2004-06-08 20:26         ` Jan-Benedict Glaw
2004-06-09  0:29           ` Thorsten Kranzkowski
2004-06-09 11:28     ` Ryan Kirkpatrick
2004-06-14 11:55       ` Ryan Kirkpatrick
2004-06-14 21:04         ` Thorsten Kranzkowski
2004-06-16 12:40           ` Ryan Kirkpatrick

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=20040608125250.GD20632@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-alpha@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