From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David A. Gatwood" <dgatwood@gatwood.net>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: G4 boot crash problems with 2.4 "stable"
Date: Wed, 13 Feb 2002 22:06:16 +0100 [thread overview]
Message-ID: <20020213210616.30410@smtp.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.3.96.1020213125526.27925B-100000@gatwood.net>
>> >Is there a 2.4 kernel source tarball around that is known to boot on
>> >Sawtooth (using BootX)? Is there a way to yank the OpenPIC support?
>>
>> BootX isn't supported on any newworld mac. You should boot from OF,
>> using yaboot.
>
>BootX works fine for me with every 2.2 kernel I've tried. It only fails
>for 2.4 TOT builds. I very much doubt the boot mechanism is at fault.
Well, it can be for various reasons. For example, the interrupt tree
cannot be properly parsed, we don't get the OF "phandles" and we now
rely on them (MacOS don't keep them when it gets the device-tree).
Also, some bus mastering devices aren't properly shut down, potentially
screwing things up in memory while the kernel loads.
I would really recommend you give a try to yaboot before investigating
much further.
(Note: I do have a sawtooth here which just works with latest kernels)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-13 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 22:37 performance monitor exceptions Werner Almesberger
2002-02-12 12:55 ` benh
2002-02-12 18:33 ` Werner Almesberger
2002-02-13 11:14 ` Anton Blanchard
2002-02-13 12:48 ` benh
2002-02-13 19:01 ` G4 boot crash problems with 2.4 "stable" David A. Gatwood
2002-02-13 19:07 ` benh
2002-02-13 21:09 ` David A. Gatwood
2002-02-13 21:06 ` Benjamin Herrenschmidt [this message]
2002-02-13 23:48 ` Ethan Benson
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=20020213210616.30410@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=dgatwood@gatwood.net \
--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;
as well as URLs for NNTP newsgroup(s).