From: Andreas Tobler <toa@pop.agri.ch>
To: Ethan Benson <erbenson@alaska.net>
Cc: Debian-PowerPC <debian-powerpc@lists.debian.org>,
Linux/PPC-devel <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Paul's 2.2.15 does not boot a 7200
Date: Sat, 20 May 2000 18:04:53 +0200 [thread overview]
Message-ID: <3926B7A3.F66027C@pop.agri.ch> (raw)
In-Reply-To: 20000520002947.A6452@plato.local.lan
Ethan Benson wrote:
>
> Hi,
>
> I have rsynced paul's stable kernel tree to 2.2.15 proper (no pre),
> this kernel works quite well with a G3 via yaboot, but will not boot a
> 7200 (via quik). I have tried my own custom config as well as Paul's
> config included in the rsync tree. quik loads the kernel successfully
> and prints `Copying Device tree' just like it does for 2.2.14 but the
> monitor just stays black and nothing else happens, it never boots any
> further.
>
> the quik used is the current debian quik sources, patched by Dan
> Jacobowitz to support powermacs. (there is no macos on this machine so
> bootx is not an option, nor testable)
>
> has anyone else had problems with 2.2.15 on 7200s?
>
> the system runs Debian potato, and runs paul's 2.2.14.
No problems here, 2.2.15 and pre16-3 vanilla, with bootx(1.2b1). I don't
boot from MESH, I use my adaptec 2940UW. The same with dev kernels...
make pmac_config
make menuconfig (enable some eth dev's, disable parport and dos fs)
make vmlinux
make modules
make modules_install
put it to MacOS, reboot with 2.2.15, it still runs....
I know, not very helpful.
Andreas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-20 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-20 8:29 Paul's 2.2.15 does not boot a 7200 Ethan Benson
2000-05-20 14:37 ` Steven Hanley
2000-05-20 14:45 ` Ethan Benson
2000-05-20 16:04 ` Andreas Tobler [this message]
2000-05-20 22:38 ` Matt McLean
2000-05-21 2:17 ` 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=3926B7A3.F66027C@pop.agri.ch \
--to=toa@pop.agri.ch \
--cc=debian-powerpc@lists.debian.org \
--cc=erbenson@alaska.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).