From: Mikael Pettersson <mikpe@csd.uu.se>
To: ajschrotenboer@lycosmail.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB
Date: Wed, 31 Jan 2001 11:57:02 +0100 (MET) [thread overview]
Message-ID: <200101311057.LAA03114@harpo.it.uu.se> (raw)
On Tue, 30 Jan 2001 23:25:22 -0500, Adam Schrotenboer wrote:
>2.4.1 detects 64 MB, but 2.4.0 detects 192 (Maybe 191, not sure).
>...
>Linux version 2.4.1 (root@tabriel) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #9 Tue Jan 30 15:35:21 EST 2001
>BIOS-provided physical RAM map:
> BIOS-88: 000000000009f000 @ 0000000000000000 (usable)
> BIOS-88: 0000000003ff0000 @ 0000000000100000 (usable)
>On node 0 totalpages: 16624
>...
>CPU: AMD-K7(tm) Processor stepping 02
>...
>BIOS Vendor: Award Software International, Inc.
>BIOS Version: 6.0 PG
>BIOS Release: 11/23/99
>Board Vendor: MICRO-STAR INTERNATIONAL CO., LTD.
>Board Name: MS-6167 (AMD751).
>Board Version: 1.X.
Why on earth is this fairly recent motherboard using BIOS-88
to report available memory? I would have expected E820 here.
Can you send the dmesg output from 2.4.0 and/or 2.2.19pre7?
/Mikael
-
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/
next reply other threads:[~2001-01-31 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 10:57 Mikael Pettersson [this message]
2001-01-31 11:18 ` Dr. David Gilbert
2001-01-31 16:05 ` Adam Schrotenboer
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 2:22 Dunlap, Randy
2001-02-01 2:57 ` Adam Schrotenboer
2001-02-06 0:05 ` Ricky Beam
2001-02-06 1:53 ` Ricky Beam
2001-01-31 23:19 Mikael Pettersson
2001-02-01 0:23 ` Adam Schrotenboer
2001-01-31 4:25 Adam Schrotenboer
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=200101311057.LAA03114@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=ajschrotenboer@lycosmail.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 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®