[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Adventures multi-booting late 2003 iBook G3 (was: What is this Apple Bootstrap thing of which the installer speaks?)

I blogged about this a couple of years back. (Fedora, rather than
Debian.) You may have discovered this all the hard way by now, but
I'll post the link anyway:


I think the only thing the blog really adds is that you can probably
get around the Mac OS 9 partition being walked on by something like
the following:

After your fresh install of Mac OS 9, make sure it's updated as far as
you want the Mac OS 9 system updated, and make sure there's a copy of
the Apple Hard Disk utility on the Mac OS 9 partition.

iBooks with Firewire can boot from an external drive. After a certain
model number (check Apple's hardware pages) hey can boot from USB as
well as Firewire. So you can make a copy of your booting Mac OS 9
partition (with Apple's disk imaging utility, or, even by
drag-and-drop copying, usually) and boot from an external drive in
some cases.

If that doesn't work for you, you should still be able to copy the
partition and burn a CD-R (but not CD-RW) from the copy, and end up
with a bootable CD from which to run Apple's HD Utilitiy.

(Ergo, to get you out of the bind when Debian's installer walks on the
Mac OS 9 partiions.)

(I did file a bug on this in Fedora's Bugzilla, but they couldn't get
the hardware and the spare personnel with the technical expertise all
together long enough to fix it, I think. Wish I had the time to look
at it myself.)

On Fri, May 20, 2011 at 4:10 AM,  <annathemermaid@hush.com> wrote:
> Hash: SHA1
> On Wed, 18 May 2011 17:23:26 +0000 annathemermaid@hush.com wrote:
>>On Thu, 05 May 2011 18:14:43 +0000 Roger Leigh
>><rleigh@codelibre.net> wrote:
>>>> Now that Debian is up and running, is there documentation
>>>> explaining how to make yaboot offer options to boot OpenBSD
>>>> NetBSD?
>>>It should be possible, but AFAIK it's currently broken:
>>>Looks like it's simple to fix, but there wasn't anyone who could
>>>test it properly.
>>I've been having a more serious issue with yaboot: it seems to
>>wreck the Mac Os Classic disk drivers so Mac OS 9.2.2 can't boot
>>anymore. Instead, it just shows this sort of flashing flopping
>>image. Apparently, the usual workaround is to boot into the
>>install CD and select the Update Drivers function from the Disk
>>Setup. Unfortunately, since I have a late 2003 model that barely
>>supports booting into Classic, the installation program is only
>>capable of running from withing OS X's Classic Mode; it doesn't
>>work when booted directly off the CD. The Tiger and Panther
>>installation disks only seem to be capable of installing the
>>drivers when partitioning the disk from scratch; they don't know
>>how to fix the drivers without wiping the disk. So, no Update
>>Drivers for me. The problem does not occur if Debian is installed
>>without the yaboot Apple_Bootstrap partition, but then, of course,
>>there's no way to boot Debian. Creating the Apple_Bootstrap
>>partition with OpenBSD's pdisk rather than Debian's mac-fdisk
>>doesn't help either, so I think the problem must occur when yaboot
>>actually installs itself onto the Apple_Bootstrap partition.
>>the disk and installing Mac OS X / Mac OS 9.2.2 from scratch will
>>resolve the issue, but then of course it will break again when I
>>install Debian again.
> I notice that the bug report is rather recent, being filed against
> squeeze.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604134
> I wonder if it would work properly if wiped the disk, and tried
> again, but this time used squeeze with lenny's yaboot.
> Charset: UTF8
> Note: This signature can be verified at https://www.hushtools.com/verify
> Version: Hush 3.0
> 2lGLzR+uLnmWAIlQiEChBoGxutvY82CDuNpbYUIS6qqMlGfDxN2H/9V8A/UrE/su3iw5
> pZjCPXloRxMwwwyq9oeYr2QDdAzAJn+XdiAW0n+NCpsz6V0IN6yrrfhmtC0ogtRHOQQ4
> CywOUcX6Ct3ewxshROKomH2WU3+4XbIIAhEdGnF5w6rDpUqt6NiQt4wiN8R8WjUXHVQX
> qDlaKoSZCx2nni/LkwF+NFpsr1XgKwsls3QuFxb0ycLzc+16JT4kW8ffgsv3D9IwJWyf
> lYwmWJzxyLVZaQxQqv6tERoluZrJyvqSOAVodvc3JIs=
> =Zurw

Reply to: