Very Computer

Hi,
I am on a dual-boot machine, and at the power-on self test it reports
160M (or a little more) of RAM. Under DOS or Windows98 it reports a
similar amount. When I run 'top' or 'free' under Slackware 7.0, 2.2.13
kernel, or the KDE task manager, it reports only 64M of RAM. Why isn't
it seeing the other 100M or so? I put in the 128M chip in the slot
myself, I know it's there, so why can't I access it? In the BIOS setup
there is some kind of option regarding memory over 64M, intended for
OS/2, I've set it both ways, and it still does not work. I've read all
the documentation that I thought might be relevant, but I didn't find
anything appropriate. What might be the problem? BTW it's an AMD K6-2
366Mhz, if that makes a difference.

On Mon, 26 Jun 2000 01:09:04 -0500, Nelson Muntz

Quote:>Hi,
>I am on a dual-boot machine, and at the power-on self test it reports
>160M (or a little more) of RAM. Under DOS or Windows98 it reports a
>similar amount. When I run 'top' or 'free' under Slackware 7.0, 2.2.13
>kernel, or the KDE task manager, it reports only 64M of RAM. Why isn't

RTFFAQ!!  This question gets asked here every other day, and it's
addressed in every manual in every boxed set I've seen, as well as the
LILO documentation, the FAQs available on http://linuxdoc.org/ and
http://linuxnewbie.org/ , and on Deja if you spend 30 seconds searching
this NG.

Set the BIOS to "non-OS/2" and boot your machine with "linux mem=160M" at
the LILO prompt.  Replace "160" with the actual amount of memory, of
course.  Read the documentation to make this process automatic on every
boot.

--
Matt G / Dances With Crows      /\    "Man could not stare too long at the face
\----[this space for rent]-----/  \   of the Computer or her children and still
 \There is no Darkness in Eternity \  remain as Man." --David Zindell "So did
But only Light too dim for us to see\ they become Gods, or Usenetters?" --/me