Jump to content

maleorderbride

maleorderbride

Member Since 17 Jan 2009
Offline Last Active Today, 05:03 AM
-----

Posts I've Made

In Topic: El Capitan: Realtek ALC AppleHDA Audio

Yesterday, 07:23 PM

config.plist is corrupt

AppleHDA.kext not attached.

Installation: use Post #1/cloverALC

 

I just solved this today (finally) with my own system. I finally solved by re-doing the SSDT. Attached is the SSDT that I used, but obviously this depends a bit upon your motherboard.

 

This is for my ASUS P9X79 PRO. You could strip it down to just the HDEF section, per Toleda's many guides.

In Topic: AppleGraphicsDevicePolicy "on the fly" patching - impossible? (altern...

03 February 2016 - 04:51 AM

Yeah, so it seems we have different solutions and we also need them all:

  1. DSDT solution does not seem to work for everyone
  2. Binpatch by Pike also seems to have problems with multiple GPUs
  3. Manual plist patching seems to work for everyone, but needs manual work after updates and does not work with boot stick or recovery partitions

So, choose what works best I guess.

 

 

I want to add a small hint for those who are using their recovery partitions - instead of having to set nv_disable manually, you can also do the following:

  1. Clone your standard info.plist and name it for example "config_alt.plist". Save it in the same location.
  2. Change the SMBIOS type in this plist to, for example "MacPro 5,1" - or set nv_disable in the boot args, that should also work
  3. Add a custom entry for your recovery partition
  4. Use a  Clover setting described here: http://www.insanelym...ions/?p=2168344
  5. I.e. add a key named "Settings" with the name of your alternate config.plist (but omit the suffix!), like this:
<dict>
    ....
    <key>Settings</key>
    <string>config_alt</string>
</dict>

Now each time you boot into recovery this config is used automatically instead of the default one. Plus, in case of needing to patch AGDP you also can choose this config for regular booting manually in the clover boot screen (under "options"). It might also be a good idea to set csr-active-config to "allow all" in this special config, to have a kind of fallback just in case your "standard boot" goes wrong bc of SIP issues.

 

The DSDT patch does always work I think. However, if you have "nvda_drv=1" as a boot arg then it will lead to a black screen if old versions of the Nvidia drivers are present on that installation. That is why you are able to boot your Recovery HD, but not your main install.

 

So, if you want to boot after an update, you need to not only have GFX1 set in the DSDT, but you must also temporarily remove the nvda_drv=1 boot arg before starting up. As far as I can tell, this is required no matter what method you choose to get around AGC.kext, as this is a separate NVDAStartup.kext issue.

 

Test it yourself and you will see that you do not need nv_disable=1 when you have GFX1 set, so long as nvda_drv=1 is also not present.

 

 

 

Maybe editing NVDAStartup's Info.plist should be the next task?

 

Can we patch with Clover to an older OS version so that the driver loads even after an OS update? Although, the target for that patch would change each time a new driver is installed, unless Clover allows wildcards in the search parameters (which I do not believe it does).

 

I suppose I can handle some slight user interaction in order to get to desktop after an update, but leave any ideas you have. This is the only thing that is currently required after an update and I would sure love to get rid of it ;p

In Topic: Request: X99 DSDT w/ working resume

02 February 2016 - 05:03 AM

Do you have USB 2.0 working in El Capitan on that motherboard? If so, what did you do?

In Topic: El Capitan 10.11.1 versus the 5960X - A Collaborative Work-Thru

01 February 2016 - 12:55 AM

I am Jack's complete surprise.

In Topic: AppleGraphicsDevicePolicy "on the fly" patching - impossible? (altern...

30 January 2016 - 05:08 PM

The MacPro6,1 kexts must be doing something tricky under the hood. Even though the plist declares "GFX1" "unload", it seems that GFX1 remains the functional device and GFX2 is dead after OS X loads on a hackintosh. Maybe something to do with "Device (GCON)" in the OEM DSDT. I'm no coder so I don't know. The usual school of thought says, give all individual devices unique names IE: GPU # 1 = GFX1 GPU # 2 = GFX2 etc etc, but naming multiple GPUs GFX1 works! If you have multiple discrete GPUs, use GFX1 in ACPI for all GPUs and they will all work. No kext binary patch or plist edit necessary.

 

If you name discrete GPU to GFX1 and leave the IGPU name alone, does the integrated graphics still work? I don't have a system with integrated graphics to test.

Thanks shilohhh. This allows me to get a multi-card setup working with MacPro6,1.

 

Adding an SSDT with GFX1 and voila ;) 

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy