From: Ethan Benson <erbenson@alaska.net>
To: Steven Hanley <sjh@wibble.net>
Cc: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: success sort of with 2.2.10
Date: Fri, 10 Nov 2000 23:51:07 -0900 [thread overview]
Message-ID: <20001110235107.X4577@plato.local.lan> (raw)
In-Reply-To: <20001111190841.A8799@wibble.net>; from sjh@svana.org on Sat, Nov 11, 2000 at 07:08:41PM +1100
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
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! ;-)
> Anyway once I have found a way to make the thing get past this point in the
> kernel booting, I will have to start going through the kernels from 2.2.10
> up and see which do and dont work. Now for that I need some way to get the
> different revisions. Are there any places other than bitkeeper that will let
> me do this? like a cvs tree? Paulus' rsync I dont think will let me get
> anything but the latest version that he has up there.
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.
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2000-11-11 8:51 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 [this message]
2000-11-11 9:37 ` Steven Hanley
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=20001110235107.X4577@plato.local.lan \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.