From: Steven Hanley <sjh@svana.org>
To: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: success sort of with 2.2.10
Date: Sat, 11 Nov 2000 19:08:41 +1100 [thread overview]
Message-ID: <20001111190841.A8799@wibble.net> (raw)
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.
Now it has frozen booting the kernel at the line after detecting hdc
the output looks like
hda: QUANTUM FIREBALL ST2100A, ATA DISK drive
hdc: MATSHITA CR-585, ATAP CDROM drive
ide0 at 0x01020000-0x1020007,0x1020160 on irq 13
is that the right output? on my x86 it says ide0 0x1f0-0x1f7,0x3f6 on irq 14
the addresses are very different, however this could just be because the ppc
uses a very different address space model or some such.
I just compiled the 2.2.10 kernel I am using and I left out pci ide support,
but it has the built in powermac ide support still selected, so this could
be the problem. It has been a long time since I had 2.2.10 on this powermac
last so I dont have my old .configs around anymore.
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.
Also should I maybe try out 2.2.4someversion ?
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/
next reply other threads:[~2000-11-11 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 8:08 Steven Hanley [this message]
2000-11-11 8:51 ` success sort of with 2.2.10 Ethan Benson
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=20001111190841.A8799@wibble.net \
--to=sjh@svana.org \
--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).