From: Justin Heesemann <jh@ionium.org>
To: linux-kernel@vger.kernel.org
Cc: Jens Wiesecke <j_wiese@hrzpub.tu-darmstadt.de>
Subject: Re: P4 with i845E not booting with 2.4.19 / 3.5.31
Date: Sun, 8 Sep 2002 23:57:26 +0200 [thread overview]
Message-ID: <200209082357.27413.jh@ionium.org> (raw)
In-Reply-To: <200209042135.17630.jh@ionium.org>
On Wednesday 04 September 2002 21:35, Justin Heesemann wrote:
> On Wednesday 04 September 2002 13:36, Alan Cox wrote:
> > I don't know. Without a serial console oops dump I don't have time to
> > figure it out either
seems like serial console doesn't dump anything in my case.
>
> when i used the boot option:
> mem=exactmap mem=640K@0 mem=510M@1M
> i was able to boot the kernel.
>
> however.. when i tried to boot from a 2.4.19 kernel boot cd, it failed
> with:
>
> here is the dmesg:
>
> Linux version 2.4.20-pre5-ac1 (root@lux) (gcc version 2.95.3 20010315
> (release)) #1 Sun Sep 1 17:26:49 Local time zone must be set--see zic manua
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
> BIOS-e820: 00000000000a0000 - 000000001fef0000 (reserved)
> BIOS-e820: 000000001fef0000 - 000000001fef3000 (ACPI NVS)
> BIOS-e820: 000000001fef3000 - 000000001ff00000 (ACPI data)
> user-defined physical RAM map:
> user: 0000000000000000 - 00000000000a0000 (usable)
> user: 0000000000100000 - 000000001ff00000 (usable)
> 511MB LOWMEM available.
i tried again with a 2.2 kernel. they don't seem to require _any_ mem=xxx
parameters to work so i checked dmesg:
Linux version 2.2.20-idepci (herbert@gondolin) (gcc version 2.7.2.3) #1 Sat
Apr 20 12:45:19 EST 2002
BIOS-provided physical RAM map:
BIOS-e820: 0009f000 @ 00000000 (usuable)
BIOS-e820: 1fdf0000 @ 00100000 (usuable)
Detected 2019977 kHz processor.
This is the same computer, same RAM, same Bios.
how comes e820 provides these different results ?
--
Best Regards
Justin
next prev parent reply other threads:[~2002-09-08 21:52 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
2002-09-04 11:36 ` Alan Cox
2002-09-04 19:35 ` Justin Heesemann
2002-09-08 21:57 ` Justin Heesemann [this message]
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=200209082357.27413.jh@ionium.org \
--to=jh@ionium.org \
--cc=j_wiese@hrzpub.tu-darmstadt.de \
--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®