From: Christof Petig <christof.petig@wtal.de>
To: Benjamin Herrenschmidt <benh@mipsys.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.17pre9-ben1 gmac problems on iBook
Date: Wed, 12 Jul 2000 12:12:32 +0200 [thread overview]
Message-ID: <396C4490.F4ACF357@wtal.de> (raw)
In-Reply-To: 20000705133728.28733@mailhost.mipsys.com
Benjamin Herrenschmidt wrote:
> >
> >You're right.
> >Strange though that BootX gives this kind of weird behaviour (2.2.15pre14
> >works fine for me).
> >I'll report about yaboot soon.
>
> You "think" it worked right, but I'm pretty sure that if you do an
> extensive memory testing, you'll discover that random bits of memory are
> damaged and that the kernel is actually not fully reliable when booting
> with BootX.
After wrestling about two days with yaboot, the kernel boots fine.
Now I can recommend (on iBooks and alike):
- make yaboot's partition of type Apple_Bootstrap (anything else didn't work
for me)
- 1MB is fine (800k is minimum (still true?))
- splitting the swap partition is a good choice if you have a running system
- move it up/downwards to the second position (moving partitions is a nice
feature)
- if you want MacOS press option while booting
- "video=ofonly" is a good last resort help
Could someone please put the following explanations into the yaboot-faq:
Option is the key with alt and a half-fork on it.
Command is the key with the apple and the knotlike figure
I had not been a Mac expert, so I had to guess.
Christof
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-12 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200007040459.XAA32533@lists.linuxppc.org>
2000-07-04 9:50 ` 2.2.17pre9-ben1 gmac problems on iBook Christof Petig
2000-07-04 10:18 ` Benjamin Herrenschmidt
2000-07-04 15:25 ` Christof Petig
2000-07-05 13:37 ` Benjamin Herrenschmidt
2000-07-12 10:12 ` Christof Petig [this message]
2000-07-12 10:58 ` Benjamin Herrenschmidt
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=396C4490.F4ACF357@wtal.de \
--to=christof.petig@wtal.de \
--cc=benh@mipsys.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 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.