Date: Thu, 18 Mar 1999 13:41:43 -0800 (PST) From: "Richard J. Dawes" <rjdawes@physics.ucsd.edu> To: Chris Coleman <chris@bbcc.ctc.edu> Cc: "Matthew D. Fuller" <fullermd@futuresouth.com>, hackers@FreeBSD.ORG Subject: Re: Broken memory (was Re: Proposal: Define MAXMEM in GENERIC) Message-ID: <Pine.SOL.3.96.990318133808.2786A-100000@huntington> In-Reply-To: <Pine.BSF.3.96.990317232512.9146C-100000@bbcc.ctc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmm. So what about the that stuff about machines with >64 MB? Poor m/b design? (Just curious -- what m/b does the Presario have?) Thanks. --Rich On Wed, 17 Mar 1999, Chris Coleman wrote: > Date: Wed, 17 Mar 1999 23:26:37 -0800 (PST) > From: Chris Coleman <chris@bbcc.ctc.edu> > To: "Matthew D. Fuller" <fullermd@futuresouth.com> > Cc: Richard Dawes <rdawes@ucsd.edu>, hackers@FreeBSD.ORG > Subject: Re: Broken memory (was Re: Proposal: Define MAXMEM in GENERIC) > > 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 > ======================================== Richard J. Dawes rdawes@ucsd.edu ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.3.96.990318133808.2786A-100000>