From: Steven Hanley <sjh@svana.org>
To: Ethan Benson <erbenson@alaska.net>
Cc: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: success sort of with 2.2.10
Date: Sat, 11 Nov 2000 20:37:32 +1100 [thread overview]
Message-ID: <20001111203732.A12202@wibble.net> (raw)
In-Reply-To: <20001110235107.X4577@plato.local.lan>; from erbenson@alaska.net on Fri, Nov 10, 2000 at 11:51:07PM -0900
On Fri, Nov 10, 2000 at 11:51:07PM -0900, Ethan Benson wrote:
> On Sat, Nov 11, 2000 at 07:08:41PM +1100, Steven Hanley wrote:
> >
> > All
> >
> > well 2.2.10 will get past the blank screen on my 7220, 2.2.18pre18 and
> > 2.2.17 (came with debian) both dont.
>
> well that rules out quik breakage at least. progress! ;-)
yes it is good progress to have the fb penguin and some boot messages show
up :)
> one thing i just remembered, did you compile 2.2.17 withOUT
> CONFIG_BOOTX_TEXT ? BootXText screws up quik booting on some
> machines apparently. turning it off has made quik boot properly for
> others.
yes it is compiled out, I didnt know it may cause problems, but I thought
that now I didnt need bootx any more I could get rid of it anyway.
Now when I add the pci ide suport I get a repeatable kernel panic on boot
every time I boot. I typed out the dump, but wont look at tracking it down
just yet, first I will try to work out a way to get hold of a 2.2.14 paulus
tree or similar and see what that does.
See You
Steve
--
sjh@wibble.net http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-11-11 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 8:08 success sort of with 2.2.10 Steven Hanley
2000-11-11 8:51 ` Ethan Benson
2000-11-11 9:37 ` Steven Hanley [this message]
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=20001111203732.A12202@wibble.net \
--to=sjh@svana.org \
--cc=erbenson@alaska.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.net \
/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).