From owner-freebsd-isp Mon Jan 12 10:38:29 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09320 for isp-outgoing; Mon, 12 Jan 1998 10:38:29 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09314 for ; Mon, 12 Jan 1998 10:38:27 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id MAA23749; Mon, 12 Jan 1998 12:37:30 -0600 (CST) From: Kevin Day Message-Id: <199801121837.MAA23749@home.dragondata.com> Subject: Re: [fbsd-isp] Designing for a very large ISP In-Reply-To: <19980112192343.62449@reactor> from Lukas Wunner at "Jan 12, 98 07:23:43 pm" To: lukas@design.de (Lukas Wunner) Date: Mon, 12 Jan 1998 12:37:30 -0600 (CST) Cc: lukas@design.de, mountin.man@mixcom.com, lem@cantv.net, freebsd-isp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > > I had the same problem with the III's... The IV's can handle it correctly. > > The problem with the 3's was having a higher chip count per simm than tyan > > allowed. (if you read between the lines on their specs)... You *can* get > > 256MB to work on a III if you use simms with very few chips per somm. > > Interesting. What do you mean by "IV's can handle it correctly"? Do you > mean more than 256MB? If so, can you elaborate exactly which type of SIMM > you put into which slot? That would be really helpful. Thanks! I had 512MB in our shell machine for a while, and it was quite happy. > > In our news box, I use four standard 64MB PS/2 SIMMS w/o parity or ECC > and 36 chips per SIMM. Surprisingly, it works extremely stable. However, > when you insert more SIMMs, it will still only count up to 256MB on > bootup. It does not matter how many SIMMs you put in and of what type > they are (64MB, 16MB, 8MB,... tested them all), nor does it make a > difference if you permutate the sequence of the SIMMs in the available slots. > Interestingly enough, the board will count up to 262xxxKB on bootup, where > xxx is a three-digit number which changes on *every* bootup. And as I said, > if the machine is cold, it will occasionally count up to 288MB. Try going into CMOS setup, under 'Advanced settings' I think, and change 'Cacheable range' from whatever it's at now to 2G, and see if it helps. Their BIOS is rather broken in trying to cache regions outside of available tag. > > We tried this with the Tomcat IV as well to no avail. So if someone has > managed to get more than 256MB working in the IV, please let me know. > (of course, the documentation and webpage for the Tomcat IV still states > that 512MB are supported *sigh*). > > Lukas. I've only got 256MB in my IV now, but I did get it to work with 512MB. Kevin