Jump to content
5 posts in this topic

Recommended Posts

Hi,

 

I setup two partitions on the same drive to test changes before commiting them and found out that Chameleon loads the 'com.apple.boot.plist' file and possible DSDTs and others from the first partition and ignores the second one when booting into the second partition. Maybe its because I had it installed to the first partition and it has it down as the default partition to load up configuration files. So for testing changes and such it either has to be a completely different drive or pass a preboot arguement to chameleon somehow?

 

Thanks.

Hi,

 

I setup two partitions on the same drive to test changes before commiting them and found out that Chameleon loads the 'com.apple.boot.plist' file and possible DSDTs and others from the first partition and ignores the second one when booting into the second partition. Maybe its because I had it installed to the first partition and it has it down as the default partition to load up configuration files. So for testing changes and such it either has to be a completely different drive or pass a preboot arguement to chameleon somehow?

 

Thanks.

 

Did you use Migration Assistant to import any settings from the first SL partition

during the installation onto your second partition?

No, I used Carbon Copy Cloner. My guess is that during Chameleons installation it writes a boot file to the main partition and at boot looks for the first occurance of that signature and hats from where it pullls its dsdt info from. Otherwise it actually is aware of the installation partition. Not sure..

Chameleon always loads the kexts and other bootloader support files (boot.plist, smbios.plist, dsdt.aml, etc.) from the first active partition it finds on the drive, regardless of what drive/partition is selected later on in the bootloader screen.

 

For example, if you have 3 partitions on one volume and you have partition 2 set "active" and it contains the /Extra directory, the Chameleon stage-0 booter will locate partition 2 and load the kexts. If you select partition 3 in the bootloader screen, that changes little for Chameleon, as the kexts and files have already been loaded. The selection at the bootloader screen basically tells Chameleon which system to hand off to. This is by design and makes boot CDs possible.

 

If you want/need to do testings of different installs on the same volume, either set "active" the correct partition or install on a different drive and select the drive via BIOS drive selection option (F12).

 

To be fair, this is a major point of confusion among many users and some of us have asked that this procedure be changed, so that Chameleon always loads the kexts from the selected partition, unless specifically told not to. :(

 

Hope that helps.

 

best regards,

MAJ

Thanks. that was very informative. There must be a preboot command to get around this like how you use the 'Dsdt=.....' command. Then should be no need to set actie partitions or reinstall Chameleon. I do have two separate drives that I can select at boot which one to use by hitting 'F8' but I had two partitions on the second as I was trying to get Lion working. Glad this is almost cleared up...

×
×
  • Create New...