From: "Froggy / Froggy Corp." <froggy@froggycorp.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory problem
Date: Wed, 27 Apr 2005 18:29:34 +0200 [thread overview]
Message-ID: <426FBDEE.D50F8564@froggycorp.com> (raw)
In-Reply-To: 20050427131858.GC3918@harddisk-recovery.com
Thx, in fact i just solve my problem before reading your email.
Problem came from bios, but i dont understand where, because all "memory
hole" were disable ...
Thx again.
Erik Mouw wrote:
> Might be a BIOS bug, or the BIOS RAM tester decided only 275 MB is
> useable. Try upgrading the BIOS, or reset the CMOS.
>
> Erik
>
> --
> +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
> | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2005-04-27 16:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 14:40 Memory problem Froggy / Froggy Corp.
2005-04-27 13:18 ` Erik Mouw
2005-04-27 16:29 ` Froggy / Froggy Corp. [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 20:25 MEMORY PROBLEM ppclinux
2004-12-14 21:07 ` Jerry Van Baren
2004-12-15 16:51 ` ppclinux
2004-09-13 11:11 (unknown) Ankit Jain
2004-09-13 11:51 ` memory problem Ron Michael Khu
2004-05-26 10:14 Memory problem Pankaj
2003-07-03 16:10 Daniel Chemko
2003-07-03 9:53 Cilliè Burger
2003-07-03 9:15 ` Filip Sneppe
[not found] ` <3F044612.8020903@sadomain.co.za>
2003-07-03 14:42 ` Filip Sneppe
2003-04-03 0:40 memory problem 최영일
2002-10-07 14:33 Memory Problem Philipp Steinkrueger
2002-10-07 14:33 ` Philipp Steinkrueger
2002-10-07 15:21 ` Rik van Riel
2002-10-07 15:21 ` Rik van Riel
2002-10-07 15:52 ` Dave Hansen
2002-10-07 17:10 ` Glynn Clements
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=426FBDEE.D50F8564@froggycorp.com \
--to=froggy@froggycorp.com \
--cc=erik@harddisk-recovery.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.