All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Heesemann <jh@ionium.org>
To: linux-kernel@vger.kernel.org
Subject: Re: P4 with i845E not booting with 2.4.19 / 3.5.31
Date: Thu, 22 Aug 2002 20:28:10 +0200	[thread overview]
Message-ID: <200208222028.10303.jh@ionium.org> (raw)
In-Reply-To: <1030038521.3161.17.camel@irongate.swansea.linux.org.uk>

On Thursday 22 August 2002 19:48, you wrote:
> On Thu, 2002-08-22 at 10:15, Jens Wiesecke wrote:
> > So again my question: Can I do anything to help to debug this problem ?
>
> The version it broke at it is itself a lot of help. Build a kernel with
> no apm, no acpi, no agp, no compiled in audio, non smp, non numa, no
> apic support.
>
> Let me know if that boots

i guess it won't help..
if Jens Problem really is the very same as mine (which looks like it.. same 
pre6 works, pre7 fails) then the problem seems to be located in 
arch/i386/kernel/setup.c

if i use a pre7 kernel, with the arch/i386/kernel/setup.c from pre6... then 
the kernel will boot !

--
Best Regards
Justin Heesemann

  reply	other threads:[~2002-08-22 18:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 13:36 P4 with i845E not booting with 2.4.19 / 3.5.31 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 [this message]
2002-08-23 12:24           ` Jens Wiesecke
  -- strict thread matches above, loose matches on Subject: below --
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
2002-09-09  8:49         ` 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=200208222028.10303.jh@ionium.org \
    --to=jh@ionium.org \
    --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.