linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: IDE problems with 2.3.49?- same with 2.2.15pre3
Date: Fri, 10 Mar 2000 10:40:38 +0100	[thread overview]
Message-ID: <20000310104038.012318@mailhost.mipsys.com> (raw)
In-Reply-To: <v03110701b4edaa5c1f3e@[129.100.29.243]>


On Thu, Mar 9, 2000, Kevin B. Hendricks <khendricks@ivey.uwo.ca> wrote:

>1. Where can I get the yaboot-0.5 version as a MacOS app that can be used
>from zip
>
>2.  I do not want to again repartition.  Is booting from a zip using the
>o-f keys my only choice now?  Instead of using a zip, could I burn a cd-rom
>with yaboot on it that I put in when I want to of boot and then restart and
>hold down the c key?  Would it be better to put your of-booting script on
>the cdrom?

If you used BootX, then I beleive you already have an HFS or HFS+
partition. Just put yaboot there along with a yaboot.conf file, and set
the OF "boot-device" path to point to it. If you want to dual boot MacOS
and Linux, copy also the dual boot OF script I posted some time ago (it's
also in the ybin package from Ethan Benson) and set OF to boot this
script (and don't forget to edit the OF path inside the script). Then,
use the space bar at boot to choose which OS you want.

>Also, is there any chance BootX will be fixed to work with these machines
>or am I SOL (I spend as much time using MacOS as LinuxPPC and liked the
>control of simple dual booting without messing with of).

There are more chances that we finally make a tool to configure OF and
yaboot easily than for BootX to be fixed. The BootX problem with the
iMacDV is not simple since MacOS actualy shuts down some hardware devices
completely (apparently, the clock of the ATI controller seems to be
switched off) before I take control. With other machines, we would have
to find a way to stop all devices that may do bus mastering and reset
them to a known state.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-03-10  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-09 16:32 IDE problems with 2.3.49? Michael Thompson
2000-03-09 11:44 ` IDE problems with 2.3.49?- same with 2.2.15pre3 Kevin B. Hendricks
2000-03-09 19:08   ` David A. Gatwood
2000-03-09 19:41     ` Michael Thompson
2000-03-09 19:17   ` Benjamin Herrenschmidt
2000-03-09 19:01     ` Kevin B. Hendricks
2000-03-09 19:28       ` Kevin B. Hendricks
2000-03-10  9:40         ` Benjamin Herrenschmidt [this message]
2000-03-10  9:43       ` 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=20000310104038.012318@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=khendricks@ivey.uwo.ca \
    --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).