I have just installed a discrete GPU and had a rough time getting to boot other than using built-in graphics, interrupting the bootloader and typing GraphicsEnabler=No each time. No amount of reinstalling and fiddling with org.chameleon.Boot.plist would change the behaviour. It was as if Chimera was totally ignoring it. Then I noticed that Chimera was still showing as 2.1.2 in the bootup sequence - after multiple re-installs!!!!
Well, it transpires that all my problems were due to using Core Storage to format my HD & SSD as one Fusion Drive ('logical volume' in Core Storage parlance). The same issue arises if a disk has a partition encrypted by Time Machine - Core Storage is activated again. Chimera, Unibeast and Muiltibeast do not respect the nuances of Core Storage Logical Volumes. The 'Extras' folder needs to be put on the boot partitions of each of the physical drives making up a logical volume to be read. These boot partitions are not mounted by default and therefore not normally visible. Hence, my 'Extra' folder on the root of the logical Volume (the 'Fusion Drive')
was being ignored. The details are
here.
My setup is increasingly mainstream. A modestly sized but fast SSD and a large HD togethr formatted under Core Storage as one 'Fusion Drive' then backed up by Time Machine to an encrypted partition on a 2nd HD which has also has small partition for 'Mac OS Recovery' - a great and pragmatic Apple-ony balance of speed, storage space, convenience, safety and security.
I have not been able to fathom a means of installing Chimera 2.2 on a Core Storage volume despite following the linked, rather tedious procedure to the letter three or so times.
I hope there is some ambition to upgrade these tools to better cope with Apple's shiny new volume manager. Many see Core Storage as the means by which Apple will dump the antiquated HFS+.
