From: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
To: "Dunlap, Randy" <randy.dunlap@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Mem detection problem
Date: Thu, 08 Feb 2001 19:44:52 -0500 [thread overview]
Message-ID: <3A833D84.7060302@lycosmail.com> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBE021@orsmsx31.jf.intel.com>
Dunlap, Randy wrote:
>> From: Adam Schrotenboer [mailto:ajschrotenboer@lycosmail.com]
>>
>> This is actually a repost of a problem that received few
>> serious replies (IMNSHO).
>
>
> Well, I claim not to have ignored it.
> I have gone thru the entire patch-2.4.1 file and can't see
> anything there that would cause what you are seeing.
>
> You aren't using ACPI, right? (not in your log files)
> [That just makes the patch file of interest smaller.]
Nope, result of grep ACPI .config
# CONFIG_ACPI is not set
>
>
>> Basically 2.4.0 detects 192 MB(maybe 191, but big whoop) of
>> memory. This
>> is correct. However, 2.4.1-ac6 (as did Linus-blessed 2.4.1)
>> detects 64.
>> The problem is simple. 2.4.1 and later for some reason uses bios-88,
>> instead of e820.
>>
>> Attached are the dmesgs from 2.4.0 and 2.4.1-ac6.
>
>
> Have you booted 2.4.0 again (lately)? You log file is from
> Jan-08-2001. It may also report only 64 MB now, based on
> some kind of BIOS change (or ESCD ...) since Jan-08.
Yes I have booted 2.4.0 much more recently than Jan 8.
Just checked, Jan 8 is the build date, not the boot date.
>
>
> Someone else with a similar "problem" actually had a fruit fly
> in one of their slots that caused a problem, so I would ask that
> you (a) boot 2.4.0 again to see if it works now and (b) remove
> adapters, clean slots, reseat adapters, boot 2.4.1 again.
>
> ~Randy
>
Weird, but might be worth the try, about as soon as I grab my
screwdriver from my car (in parking lot ~1/5 mile away)
-
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 prev parent reply other threads:[~2001-02-09 0:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 0:19 Mem detection problem Dunlap, Randy
2001-02-09 0:44 ` Adam Schrotenboer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-08 23:54 Adam Schrotenboer
2001-02-08 16:52 Adam Schrotenboer
2001-02-08 23:09 ` Michael Hobgood
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=3A833D84.7060302@lycosmail.com \
--to=ajschrotenboer@lycosmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@intel.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