From: Dan Malek <dmalek@jlc.net>
To: hollis@andrew.cmu.edu
Cc: Neil Russell <caret@c-side.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: RevD iMac USB errors (was Problems compiling ppc kernels)
Date: Wed, 27 Oct 1999 14:35:36 -0400 [thread overview]
Message-ID: <381745F8.B3C225@jlc.net> (raw)
In-Reply-To: 3816973A.375F987D@andrew.cmu.edu
hollis@andrew.cmu.edu wrote:
> Those kernels should definately boot... are you downloading them from
> the Mac OS side? Linux apparently has some issues copying to HFS that
> can render kernels unbootable (this is from personal experience).
>
> If those still don't work, try the kernel at
> ftp://ftp.linuxppc.org/kernels/BlueG3/v2.2.6/vmlinux-2.2.6-rev1.gz
Thanks for all of the information, but I still haven't found anything
that will boot on my iMac. I am trying to catch the messages as they
scroll by :-). The first one that seems suspicious is something
about "hub 0 timeout" trying to attach or initialize. After that I
get continuous "USB-HUBM Cannot attach to port 0 of hub....." and
"USBD: Transaction....endpoint 0, timed out".
Hacking code now.......I have the 2.2.5 kernel patched up to 2.2.6
with the other keyboard and usb patches as described on johnb's
imaclinux.net pages, as my starting point. Should I be using something
else?
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-27 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 3:00 Problems compiling ppc kernels bob
1999-10-27 3:43 ` RevD iMac USB errors (was Problems compiling ppc kernels) hollis
1999-10-27 5:57 ` Neil Russell
1999-10-27 6:10 ` hollis
1999-10-27 18:35 ` Dan Malek [this message]
1999-11-01 5:11 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
1999-10-28 1:31 Dan Malek
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=381745F8.B3C225@jlc.net \
--to=dmalek@jlc.net \
--cc=caret@c-side.com \
--cc=hollis@andrew.cmu.edu \
--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).