*BSD News Article 35349


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!gatech!newsxfer.itd.umich.edu!gumby!andrews-cc!gillham
From: gillham@andrews.edu (Andrew Gillham)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD, 16 to 32MB unrecognized on EISA machine
Date: 3 Sep 1994 00:03:06 GMT
Organization: Andrews University
Lines: 27
Distribution: world
Message-ID: <348efq$l1v@orion.cc.andrews.edu>
References: <348au2$bd@csnews.cs.colorado.edu>
NNTP-Posting-Host: edmund.cs.andrews.edu

In article <348au2$bd@csnews.cs.colorado.edu> rickcole@redwood.cs.Colorado.EDU (Rick Cole) writes:
>
>I recently saw someone ask this same question, but can't find it now.
>Upgrading from 16 to 32MB mem. on a Dell EISA machine with an EISA
>SCSI controller.  The new 16MB are not recognized/used.  However,
>boot-up does give some indication that it is there (first line of
>boot-up says "386bsd  ... at ... 639/31744" or somesuch), and my CMOS
>setup says it's there, and DOS thinks it's there, but I still get
>"Testing 15MB" only.  Ideas?  -Rick

I have the same problem on a Dell 466SE.  Dell must store the
extended memory differently in the CMOS.  I ended up having to
"hardcode" my RAM in /sys/arch/i386/i386/machdep.c (this is netbsd)
The line looks like:
	biosextmem = (rtcin(RTC_EXTHI)<<8) | (rtcin(RTC_EXTLO));
You change it to be:
	biosextmem = 31 * 1024; /* 31MB of extended, 1MB of base */
Or '63 * 1024', etc..

-Andrew


-- 
#!/bin/sh - ==============================================
echo "Andrew Gillham                 gillham@andrews.edu"
echo "Winix Hacker"
#=========================================================