From: hollis@andrew.cmu.edu
To: Neil Russell <caret@c-side.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: RevD iMac USB errors (was Problems compiling ppc kernels)
Date: Wed, 27 Oct 1999 02:10:02 -0400 [thread overview]
Message-ID: <3816973A.375F987D@andrew.cmu.edu> (raw)
In-Reply-To: 19991026225703.G11654@lx.c-side.com
Neil Russell wrote:
>
> On Tue, Oct 26, 1999 at 11:43:17PM -0400, hollis@andrew.cmu.edu wrote:
> > > Does anyone else have any insight into this? Can anyone point me to
> > > a kernel binary that works on the iMac? How about the config file for
> > > the said kernel?
> > >
> > > I have a rev.D iMac, purchased about a month ago (just before the new
> > > iMac came out).
> >
> > The kernels on rshaw's pages (http://www.linuxppc.org/blueg3) should
> > work fine. The trick is just to comment out the USB version-checking
> > code. I think he has the patch there as well.
>
> I tried several of those kernels and they would not even boot. I also
> built a kernel with the version checking commented out and those kernels
> would not even find the keyboard.
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
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-27 6:10 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 [this message]
1999-10-27 18:35 ` Dan Malek
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=3816973A.375F987D@andrew.cmu.edu \
--to=hollis@andrew.cmu.edu \
--cc=caret@c-side.com \
--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).