Contribute
Register

Chimera 2.2 Update

Status
Not open for further replies.
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+.
 
Thanks for the update!

I want to enable QE on my HD2500 connected to a Thunderbolt Display. I've tried almost everything I found on the internet but nothing seems to work, is it even possible?

I've got a Intel i5 3570 and a GA-Z77-D3H-TH motherboard.

Since Chimera 2.2 my HD2500 is recognized in "About this Mac".
 
Article: Chimera 2.2 Update

Thanks for the update!

I want to enable QE on my HD2500 connected to a Thunderbolt Display. I've tried almost everything I found on the internet but nothing seems to work, is it even possible?

I've got a Intel i5 3570 and a GA-Z77-D3H-TH motherboard.

Since Chimera 2.2 my HD2500 is recognized in "About this Mac".

Tynzo do you have the 3570 non k version?? and gtx 640??
how does it performs i got the same combo but z68x-ud3h-b3 mobo
 
Article: Chimera 2.2 Update

how did you upgrade downgrade chimera?
Just ran Multibeast and only checked Chimera 2.1.2 and i ran the 2.2 installer. Both leave me hanging with an apple without a progress bar. When i run the MB5.3.1 and just check chimera 2.0.1 my system is back.
 
Article: Chimera 2.2 Update

Tynzo do you have the 3570 non k version?? and gtx 640??
how does it performs i got the same combo but z68x-ud3h-b3 mobo

It's indeed the 3570 non k version and an EVGA GT 640. It performs pretty well, I've a working Mac OS X and everything that doesn't need QE works great without any lag (photoshop, illustrator, chrome, zbrush, itunes,...). I'm hoping the 2013 Mac Pro will allow us to use our CG over Thunderbolt. How about your hackintosh?
 
Article: Chimera 2.2 Update

How did you did it i also have gt 640 but hd 2500 graphics, did you just overwrited chimera??
i want 640 as primary

thanks in advance wolfintosh

640 works OOB!
install new chimera and add to org.chameleon.Boot.plist:

<key>IGPEnabler</key>
<string>Yes</string>
 
Article: Chimera 2.2 Update

Chimera 2.01 works on my system, but when i install 2.1.2 or the recent 2.2 the system doesn't boot. It hangs with the apple logo.
As soon as i reinstall 2.01 it runs fine again.
What's up?

GA-Z77X-UP4-TH - i7 3770K - HD 4000
OSX 10.8.4

Using Chimera 2.2 you need to change your Org.Chameleon.boot.Plist in /Extra.
How To Edit a .plist
Before you restart after installing Chimera 2.2

Where is says this, change
Code:
[COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<key>GraphicsEnabler</key> [/COLOR][/LEFT]
[/COLOR][COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<string>Yes</string>[/COLOR][/LEFT]
[/COLOR]
to
Code:
[COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<key>IGPEnabler</key> [/COLOR][/LEFT]
[/COLOR][COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<string>Yes</string>[/COLOR][/LEFT]
[/COLOR]
 
Article: Chimera 2.2 Update

I'm having trouble getting this to work the way I was hoping it would.

I have the following in my org.chameleon.Boot.plist:

<key>GraphicsEnabler</key>
<string>No</string>
<key>IGPEnabler</key>
<string>Yes</string>
<key>IGPlatformID</key>
<string>0166000A</string>

If I have autologon turned on, it works. With my monitor connected only to my Titan, it turns on after OS X finishes starting. However, if I have autologin turned off (name and password prompt at startup), the monitor connected to the Titan will not work. Even if I unplug it from the Titan and plug it into the IGP, it won't turn on. I have to startup with the monitor connected to the IGP to be able to see the login screen.

I've tried this without the IGPlatformID key and it doesn't work at all. I also tried changing BIOS settings, but found I still need to have the priority set to IGP and the memory set to 64M.

It seems the IGPEnabler and IGPlatformID don't kick in until after login. Even if I type my name and password without being able to see the screen the monitor won't turn on with either the Titan or IGP ports.

I was hoping to be able to leave the priority and memory in the BIOS set to Auto or PCIE and Auto because Windows won't work with my HD4000 graphics if they're set to IGP and 64M.

Is there any possibility to get it to work that way?
 
Article: Chimera 2.2 Update

Using Chimera 2.2 you need to change your Org.Chameleon.boot.Plist in /Extra.
How To Edit a .plist
Before you restart after installing Chimera 2.2

Where is says this, change
Code:
[COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<key>GraphicsEnabler</key> [/COLOR][/LEFT]
[/COLOR][COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<string>Yes</string>[/COLOR][/LEFT]
[/COLOR]
to
Code:
[COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<key>IGPEnabler</key> [/COLOR][/LEFT]
[/COLOR][COLOR=#3E3E3E][LEFT][COLOR=#3E3E3E]<string>Yes</string>[/COLOR][/LEFT]
[/COLOR]

Thank you for your reply. However, it still doesn't boot.
 
Article: Chimera 2.2 Update

Does running IGPEnabler=Yes change the fact that in order to have the integrated graphics recognized you must set Igfx to Enabled and Init display first to the Igfx along with connecting a display to the integrated graphics during startup? Is it possible to boot with the display connected to your PCIe graphics card, but still have the integrated graphics recognized so Airplay can be enabled?
 
Status
Not open for further replies.
Back
Top