EFI Studio and Chameleon Use

[eyemac]

Chameleon uses it's own com.apple.Boot.plist as I understand it. When using EFI Studio for Video, does EFI Studio write to the com.apple.Boot.plist in Library/Preferences/SystemConfiguration/com.apple.Boot.plist or the one in /Extra?

Thanks

SG

[shoarthing]

Chameleon uses it's own com.apple.Boot.plist as I understand it. When using EFI Studio for Video, does EFI Studio write to the com.apple.Boot.plist in Library/Preferences/SystemConfiguration/com.apple.Boot.plist or the one in /Extra?

Thanks

SG

§ . . the former.

[eyemac]

Thanks! In that regard, what is the best method for managing video via Chameleon? Or is EFI Studio the 'preferred' method? I would prefer a method that allows Updates without having to reload kexts after the update etc.

Thanks. SG

[vilpostus]

I would prefer a method that allows Updates without having to reload kexts after the update etc.

http://www.insanelymac.com/forum/index.php...=127330&hl=

[shoarthing]

Thanks! In that regard, what is the best method for managing video via Chameleon? Or is EFI Studio the 'preferred' method? I would prefer a method that allows Updates without having to reload kexts after the update etc.

Thanks. SG

. . . there's an admirable simplicity for the end-user in Chameleon's graphicsenabler [for Nvidia users] or the extended version of the same thing, including some ATI support, in PC-EFI 10.3

 

There are a few reasons why one might want to use EFI-strings - the best perhaps being that it keeps things under your own control.

 

If you use an EFI string for graphics, you obviously want to have your edited apple.com.boot.plist to be the one loaded from /Extra

 

I personally prefer to inject [Nvidia] graphics from a custom dsdt.aml

 

If you just want to minimise the hassle, use Chameleon having read the compact documentation plus had a browse over this useful FAQ