From: Sven Hartge <hartge@ds9.gnuu.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-pre* does not boot on my PReP PPC
Date: Sat, 27 Mar 2004 14:55:09 +0100 [thread overview]
Message-ID: <E1B7EHF-0004Jm-DY@ds9.argh.org> (raw)
In-Reply-To: <20040326185103.GB20819@smtp.west.cox.net>
Tom Rini <trini@kernel.crashing.org> wrote:
> On Fri, Mar 26, 2004 at 08:33:18PM +0200, Meelis Roos wrote:
>> Recent 2.6.5-pre* and -rc1 and -BK don't boot on my Motorola Powerstack
>> (PReP with no RTAS but with OF).
>>
>> I use netboot to test new kernels. Normally, the screen is changed to
>> VGA text mode and the bootloader speaks some lines of info and asks for
>> the kernel command line. Now, the image is loaded via tftp (as shown by
>> tcpdump, the last datagram is smaller) and nothing more happens. The
>> cursor stays where it is - at the beginning of the Booting ... line in
>> graphics mode OF environment and that's all.
> Hmm. Can you hook up a serial line, enable serial console as well and
> see if anything pops out there?
I am seeing the same problem here too (Powerstack II with OF).
Using the serial console does not change to behavior in any way, it is
just stuck after the transmission of the kernel and no further
information is printed.
I even let it stay this way for a long time (read: over 12 hours) and
nothing changed.
The only difference is: Is see this problem since the 2.6.4 (or maybe
even 2.6.3) kernel. I'm a bit short on time right now, so I am
currently not able to specify a correct -BK-release.
At least I know, 2.6.1 and 2.6.2-rc2 were able to boot, until the
problem with the Tulip/3Com cards hits me
(http://bugzilla.kernel.org/show_bug.cgi?id=1494)
Grüße,
S°
--
Fachbegriffe der Informatik - Einfach erklärt
91: Emacs
Eight Megabytes And Continously Swapping
next prev parent reply other threads:[~2004-03-27 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 18:33 Meelis Roos
2004-03-26 18:51 ` Tom Rini
2004-03-27 13:55 ` Sven Hartge [this message]
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
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=E1B7EHF-0004Jm-DY@ds9.argh.org \
--to=hartge@ds9.gnuu.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®