mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Wiesecke <j_wiese@hrzpub.tu-darmstadt.de>
To: Justin Heesemann <jh@ionium.org>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	tspinillo@yahoo.com
Subject: Re: P4 with i845E not booting with 2.4.19 / 3.5.31
Date: Wed, 04 Sep 2002 09:05:05 +0200	[thread overview]
Message-ID: <3D75B0A1.3070707@hrzpub.tu-darmstadt.de> (raw)
In-Reply-To: <200209030153.47433.jh@ionium.org>

Justin Heesemann wrote:
>>I tested:
>>2.4.19-pre6 -> boots with mem=512M parameter
>>2.4.19-pre7 -> didn't boot at all
>>2.4.19-pre7 with arch/i386/kernel/setup.c from 2.4.19-pre6 -> boots with
>>mem=512M parameter
> 
> 
> I have another update:
> some might know the memtest86 utility.
> 
> it has three ways of detecting the memory size "BIOS - Std", "BIOS - All" and 
> "Probe"
> 
> on my Athlon Mainboard (which has no Problems with 2.4.19 or later kernels) 
> all methods show the same (or nearly same) ammount of memory.
> 
> on my Epox 4G4A+ i845g Mainboard, which has all the Problems Jens Wiesecke 
> has, it's different:
> BIOS - Std : 640k (!!)
> BIOS - All : 4091M (!!!!)
> Probe: 511M (which seems correct as I have 512 MB Ram and 1 MB is shared 
> graphics ram)

ok. I tested my Chaintech 9EJL i845E mainboard the same way and I have 
exactly the same output with memtest86

BIOS - Std : 640k
BIOS - All : 4091M (memtest stops working afterwards)
Probe: 512M (since I have no shared graphics ram)

so the problem seems to be BIOS related. But what I don't understand is 
that since I tell the kernel to use 512 MByte of RAM (mem=512M) and 
kernels up to 2.4.19pre6 can handle this:

What changed and is there a workaround for kernels newer than 2.4.19pre6 
(for example telling the kernel not to rely on the memory information of 
the BIOS e820 procedure) ?

I tried to compile 2.4.20pre5-(ac) with the arch/i386/kernel/setup.c 
from 2.4.19pre6 but that didn't work.

Best regards
-- 
Jens Wiesecke
Institute for Macromolecular Chemistry
Darmstadt - Germany
e-mail: j_wiese@hrzpub.tu-darmstadt.de


  reply	other threads:[~2002-09-04  7:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 23:53 Justin Heesemann
2002-09-04  7:05 ` Jens Wiesecke [this message]
2002-09-04 11:36   ` Alan Cox
2002-09-04 19:35     ` Justin Heesemann
2002-09-08 21:57       ` Justin Heesemann
2002-09-09  8:49         ` Jens Wiesecke
  -- strict thread matches above, loose matches on Subject: below --
2002-08-20 13:36 Jens Wiesecke
2002-08-20 13:46 ` Rohan Deshpande
2002-08-20 14:44   ` Justin Heesemann
2002-08-21  8:56   ` Jens Wiesecke
2002-08-21 13:36     ` Alan Cox
2002-08-22  9:15       ` Jens Wiesecke
2002-08-22 17:48         ` Alan Cox
2002-08-22 18:28           ` Justin Heesemann
2002-08-23 12:24           ` Jens Wiesecke

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=3D75B0A1.3070707@hrzpub.tu-darmstadt.de \
    --to=j_wiese@hrzpub.tu-darmstadt.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jh@ionium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tspinillo@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®