From owner-freebsd-hackers Wed Mar 17 23:34:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bbcc.ctc.edu (bbcc.ctc.edu [134.39.180.254]) by hub.freebsd.org (Postfix) with ESMTP id 7F38814C57 for ; Wed, 17 Mar 1999 23:34:28 -0800 (PST) (envelope-from chris@bbcc.ctc.edu) Received: from localhost (chris@localhost) by bbcc.ctc.edu (8.8.8/8.6.12) with SMTP id XAA09173; Wed, 17 Mar 1999 23:26:38 -0800 (PST) Date: Wed, 17 Mar 1999 23:26:37 -0800 (PST) From: Chris Coleman To: "Matthew D. Fuller" Cc: Richard Dawes , hackers@FreeBSD.ORG Subject: Re: Broken memory (was Re: Proposal: Define MAXMEM in GENERIC) In-Reply-To: <19990317230822.Y25217@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having this problem now with my Compaq presario 9564. I am runnig 2.2.6 and it only detects 16 meg and I have 24 in there. I thought it might have been because the memory I added was not "Compaq" memory or something like that. I will define MAXMEM and fix this tonite. :-) -Chris On Wed, 17 Mar 1999, Matthew D. Fuller wrote: > On Wed, Mar 17, 1999 at 08:53:12PM -0800, a little birdie told me > that Richard J. Dawes remarked > > Hello, all! > > I have belatedly started reading this thread, and I am mystified > > as to what is meant by "broken" hardware (which I take it is shipped > > that way?), with regard to memory. What exactly is broken? Do some > > cheapo motherboards use specific chips that are bad at managing memory? > > I guess what I'm asking is if this problem is well-defined, and, > > if so, some pointers on further information would greatly be appreci- > > ated. (My quick perusal of HARDWARE.TXT produced nothing.) > > I suspect it's not a -hackers topic as such, but as long as it's here > I'll leave it until somebody bites my head off. > This was a Compaq Presario 9232, shipped with 16 megs of RAM and a P120. > Bought it (on closeout) in August '96. I've seen this with the vast > majority (I'm tempted to say all, but I'll err on the side of caution) of > Compaq's I've seen exhibit this, even up through some 3.0 SNAP's from mid > last year (I think). Define MAXMEM, you're golden. Don't, it'll only > detect 16 megs. I don't know if the npx0 trick works on the later > versions; I've always had space/etc to do custom kernels since then, so I > haven't bothered. But under 2.1.6 I could never get it to recognize the > full 24; only the first 16. > > > ======================================== > > Richard J. Dawes rdawes@ucsd.edu > > ======================================== > > > > --- > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > | Matthew Fuller http://www.over-yonder.net/ | > * fullermd@futuresouth.com fullermd@over-yonder.net * > | UNIX Systems Administrator Specializing in FreeBSD | > * FutureSouth Communications ISPHelp ISP Consulting * > | "The only reason I'm burning my candle at both ends, | > * is because I haven't figured out how to light the * > | middle yet" | > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message