mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cliff Albert <cliff@oisec.net>
To: Vieri Di Paola <vieridipaola@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 128M
Date: Sun, 5 Aug 2001 14:55:18 +0200	[thread overview]
Message-ID: <20010805145518.A23485@oisec.net> (raw)
In-Reply-To: <20010805115418.28773.qmail@web4902.mail.yahoo.com>
In-Reply-To: <20010805115418.28773.qmail@web4902.mail.yahoo.com>

On Sun, Aug 05, 2001 at 04:54:18AM -0700, Vieri Di Paola wrote:
> I just bought a DIMM 128M RAM module and inserted it
> in the motherboard. I took the old 2x8M SIMM modules.
> However, my BIOS sees only 32M. I read though that I
> can pass the kernel the argument "mem=128m" and Linux
> should use all the available RAM. But this operation
> leads to an error: "protection fault" and the boot
> halts. Could there be a hardware problem with the DIMM
> card? Or is just a BIOS thing, in which case there's
> isn't anything I can do, or is there? I tried SuSE 6.3
> and BestLinux Release 3 with both lilo and grub. I
> passed kernel ... vmlinuz mem=128m but boot fails.
> However any mem value below 32m works and the command
> "top" shows the correct amount of memory.

It's your motherboard that can't cope with the DIMM. The only                                                          
dimm's it probably will support are 32MB DIMM's. All other                                                             
(bigger) DIMMs wil not work.     

-- 
Cliff Albert		| RIPE:	     CA3348-RIPE | www.oisec.net
cliff@oisec.net		| 6BONE:     CA2-6BONE	 | icq 18461740

      reply	other threads:[~2001-08-05 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-05 11:54 128M Vieri Di Paola
2001-08-05 12:55 ` Cliff Albert [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=20010805145518.A23485@oisec.net \
    --to=cliff@oisec.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vieridipaola@yahoo.com \
    /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

all inboxes | Powered by JetHome®