public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Christian Kujau <evil@g-house.de>
Cc: Sven Hartge <hartge@ds9.gnuu.de>,
	linux-kernel@vger.kernel.org,
	linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.6.5-pre* does not boot on my PReP PPC
Date: Mon, 5 Apr 2004 08:50:22 -0700	[thread overview]
Message-ID: <20040405155022.GL31152@smtp.west.cox.net> (raw)
In-Reply-To: <40704743.3000909@g-house.de>

On Sun, Apr 04, 2004 at 07:34:59PM +0200, Christian Kujau wrote:

> [ cc'ing linuxppc-dev ]
> 
> Sven Hartge wrote:
> | Meelis Roos <mroos@linux.ee> wrote:
> |
> |
> |>>Ok.  Can both of you try the following patch on top of the version
> |>>which fails?
> |
> |
> |>Tried it on top of fresh 2.6.5-rc3, no changes, it still hangs.
> |
> |
> | Same here, still totally dead after tftp.
> 
> not so dead here. 2.6.4 is ok, 2.6.5-rc1|2|3 are loaded within the OF
> menu, but no bootprompt appears. but: i can hear the scsi disk
> initalizing, short after this, the atkbd is recognized and the LEDs on
> my keyboard are flashing. then again my nfs-root is supposed to be
> mounted, but my PReP still locks up completely upon network-init. (last
> working is still 2.5.30).

OK, hmm.  I've got some better ideas then.  It sounds like the code to
have puts show up on VGA isn't selected/compiled in.  Or, there's still
some other problem wrt the OF transition code.  Just having a serial
console selected still doesn't give output however, right?

> another issue here: i was finally able to cross-compile 2.5.x / 2.6.x
> kernels (on x86). i tried to compile kernels from 2.5.21 on with
> "allnoconfig" (was introduced in 2.5.21). only 2.5.30 can be built, all
> other attempts to build "zImage" fail...(still compiling 2.5.6x)...
> (full logs of builds available...)

The simple answer is, don't use allnoconfig :).  Do a 'make
common_defconfig' and then from there turn off stuff you don't need.

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-04-05 15:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 18:33 2.6.5-pre* does not boot on my PReP PPC Meelis Roos
2004-03-26 18:51 ` Tom Rini
2004-03-27 13:55   ` Sven Hartge
2004-03-29 15:09     ` Tom Rini
2004-03-29 15:15     ` Tom Rini
2004-03-30 11:31       ` Meelis Roos
2004-03-30 18:45         ` Sven Hartge
2004-04-04 17:34           ` Christian Kujau
2004-04-05 15:50             ` Tom Rini [this message]
2004-04-05 21:19               ` Christian Kujau
2004-04-05 21:48                 ` Hollis Blanchard
2004-04-05 22:30                 ` Hollis Blanchard
2004-04-05 21:45               ` Christian Kujau
2004-04-05 16:15             ` Tom Rini
2004-03-30 18:49       ` Sven Hartge
2004-03-30 19:09         ` Tom Rini
2004-03-26 21:54 ` Christian Kujau
2004-03-27 13:56   ` Sven Hartge

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=20040405155022.GL31152@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=evil@g-house.de \
    --cc=hartge@ds9.gnuu.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.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