public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.2.x-BUG(?) memmory not detected
Date: Mon, 13 Nov 2000 02:24:32 +0100	[thread overview]
Message-ID: <20001113022432.C886@werewolf.able.es> (raw)
In-Reply-To: <5.0.0.25.2.20001113002439.0572d070@pop.cus.cam.ac.uk>
In-Reply-To: <5.0.0.25.2.20001113002439.0572d070@pop.cus.cam.ac.uk>; from aia21@cam.ac.uk on Mon, Nov 13, 2000 at 01:43:44 +0100


On Mon, 13 Nov 2000 01:43:44 Anton Altaparmakov wrote:
> Hi,
> 
> Just noticed that both 2.2.18pre21 and RedHat-7.0-patched-2.2.16 kernels 
> only detect 64Mb out of 192Mb RAM on my Dual Celeron/Intel 440GX chipset 
> based workstation. - I haven't tried any other 2.2 kernels on that 
> particular PC so maybe this is a general 2.2.x thing.
> 
> The setup is one 64Mb SDRAM and one 128Mb SDRAM so it would seem that the 
> 128Mb one is not detected at all.
> 
> All 2.3/2.4 kernels I have tried have always detected the full 192Mb RAM.
> 

It's a bug, but in the mobo. Some motherboards lie about its installed ram.
2.3+ kernels have a workaround for detection, but in 2.2 you still have
to manually add <append="mem=128M"> in your lilo.conf file.

-- 
Juan Antonio Magallon Lacarta                                 #> cd /pub
mailto:jamagallon@able.es                                     #> more beer

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-13  1:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13  0:43 Linux-2.2.x-BUG(?) memmory not detected Anton Altaparmakov
2000-11-13  1:24 ` J . A . Magallon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001113022432.C886@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox