From owner-freebsd-hackers Mon May 5 15:39:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA25126 for hackers-outgoing; Mon, 5 May 1997 15:39:51 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA25121 for ; Mon, 5 May 1997 15:39:48 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id PAA11267; Mon, 5 May 1997 15:39:46 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id PAA14771; Mon, 5 May 1997 15:39:45 -0700 (PDT) Date: Mon, 5 May 1997 15:39:45 -0700 (PDT) From: Chris Timmons To: Tom Samplonius cc: Andrzej Bialecki , freebsd-hackers@FreeBSD.ORG Subject: Re: SMP hardware recommendations In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You should be aware that ASUS P/I-P65UP5 among many other ASUS boards will not work correctly with very high density SIMMs - particulary 64MB modules which have more than 24 chips per module. This is stated in the motherboard documentation. Does anybody have a good source of 16x36 SIMMs built from fewer than 36 chips per module? I have several P6NP5 (uniprocessor) boards that work ok with two of these modules (128MB) but can't seem to handle 4 of them at once (for 256MB). I've ordered a Tyan board to experiment with, as I have quite a few 36cpm 64MB SIMMs around. ASUS says their boards support 64MB SIMMs but I wonder if that is "theoretically, if you can find 64MB simms made of 24 or fewer chips per module" ??? -Chris On Mon, 5 May 1997, Tom Samplonius wrote: [...] > ASUS makes very good boards. They make a dual-CPU motherboard, that the > CPUs are installed on a daughtercard. Very nice. I'm using one of these > now with just one CPU, but the SMP web page mentions that this board. > > > * RAM: 256 MB (EDO ???) > > For servers, always, always get parity memory. [...]