Sorry if this is short, but I don't have much time...
I followed the help in the text file that came with the current Chameleon 2.0 bootloader.
Text file?.. I'm not familiar with a text file included in the official v2 release or in the latest v2.1 download? Maybe I've just missed it.
But I only ask as maybe we could find something in your steps which is causing the installation to fail.
You can find manual installation instructions in the official docs
Is there something equivalent to making a particular partition "active" like you do with MBR that is required for a GPT drive?
You can use fdisk (or Chameleon's fdisk440) - for flagging a partition active they both do the exact same thing.
For an example, see Gringo's install guide
- Search the post for the word flagged
and read below.
rdiskX will be your disk number, fX will be the partition number.
For a thorough overview of this, try googling Setting Your Partition "Active" Using Fdisk in MacOSX
at the InsanelyMac forum.
One additional note, I noticed after I manually installed the Chameleon 2.0 stages to the SDD, the bdmesg command was still showing that Chameleon 1.6 was loaded on the drive.
Chameleon 1.6? I'm not sure what you mean. Chameleon is identified by it's revision number, for example rev1520. But if you saw a version on the screen that was not what you installed then you know your installation didn't work. This text comes from the stage 2 file and just replacing this file, providing you have a recent installation of the stage 0 and stage 1 files can change the bootloader version you're using.
I seem to remember seeing a message along the way when trying to load the 0 stage, that it found a previously installed stage and did not overwrite it.
Loading and installing are different.
The chameleon package installer (found on Buildbot
) prints a message in the install log along the lines of what you say here.. For example:Target disk already has existing Chameleon stage 0 loader - boot0hfs
Stage 0 loader not written to *diskname*
The stage 0 loader is the file that lives in the MBR of the disk (be it a disk using either MBR or GUID (using a hybrid GPT/MBR) partition tables). This file is what's needed to start the Chameleon loading process and once loaded, it then proceeds to look for stage 1.
This goes back to the first part of this post - are you using an installer to install Chameleon for you or are you installing by hand by entering commands in the Terminal?