Contribute
Register

[Guide] How to patch DSDT for working battery status

I've also fixed those errors by disabling Trim Force and enabling Trim Hotpatch via config file.

Code:
AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion.
AppleDataSetManagement.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion.
Here's the output after disabling Trim Force. Strange, I was using Trim Force with 10.12.4 but I wasn't getting these errors.
Code:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext Shiki.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Broadcom_WiFi.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext DummyHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AsusNBFnKeys.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ApplePS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ApplePS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ApplePS2SmartTouchPad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleBacklightInjector.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
 
Hi RehabMan,

Here's Problem Reporting files after I've disabled EC rename and replaced it with a face SSDT-EC.aml file. I've also added it to SortedOrder list. Can you check if it's ok? Battery is still not showing me how long will it last though.

Thanks.

Using the _OSI->XOSI patch without SSDT-XOSI.aml is a mistake.
Due to this obvious/huge mistake, I didn't check anything else.
 
Using the _OSI->XOSI patch without SSDT-XOSI.aml is a mistake.
Due to this obvious/huge mistake, I didn't check anything else.

I used both your guide then this guide, [Guide] macOS on the ASUS-TP500LA (Broadwell Edition).

Attached config file has the _OSI -> XOSI rename, so have I. As for kexts it has only FakePCIID. And the acpi files attached has no SSDT-XOSI.aml. And no, I didn't use those acpi files, I've patched mines. Now, are you telling me that guide is wrong? Using that rename without that file? Maybe TP500L models don't need that file? How can we make sure that we need that rename and file or even we need that rename at all? As far as I know, my usb 3.0 is working. How to test if it is?
 
_OSI->XOSI requries SSDT-XOSI.aml.
With the patch, but without SSDT-XOSI.aml is very wrong.

Thanks for the info, Do I really need that rename? Can you check my IOReg to confirm that I need that rename and .aml file, please?

Thanks! I really appreciate your help!
 
Thanks for the info, Do I really need that rename? Can you check my IOReg to confirm that I need that rename and .aml file, please?

The _OSI->XOSI fix is to simulate a version of Windows when running Darwin.
It serves the same purpose as the "OS Check Fix" series of patches.
But doing the _OSI->XOSI patch without SSDT-XOSI.aml is a step backwards, as it will cause all calls to _OSI to cause an ACPI abort.
 
The _OSI->XOSI fix is to simulate a version of Windows when running Darwin.
It serves the same purpose as the "OS Check Fix" series of patches.
But doing the _OSI->XOSI patch without SSDT-XOSI.aml is a step backwards, as it will cause all calls to _OSI to cause an ACPI abort.
Thank you for the explanation. Since I already applied Os Check Fix Win8, then I can simply disable the rename. Or Should I still use it with SSDT-XOSI.aml?
 
Renames must be balanced. So no matter what you do, you must end up with the same name used consistently in all ACPI binaries injected ... EC/EC0.

It is one of those things where you have to pay attention to what you're doing.

Sorry for the hijacking, but even if you patch with Clover, you need to rename in every SSDT (even those who aren't patched)? Because I didn't do a lot of patching because I thought clover would do it to all of the SSDT (Which I didn't dropped, because it's not 2001 and ACPI is important.)
 
Thank you for the explanation. Since I already applied Os Check Fix Win8, then I can simply disable the rename. Or Should I still use it with SSDT-XOSI.aml?

If you apply an "OS Check Fix" patch via static patching (MaciASL), then you have no need for _OSI->XOSI patch+SSDT.
 
Sorry for the hijacking, but even if you patch with Clover, you need to rename in every SSDT (even those who aren't patched)? Because I didn't do a lot of patching because I thought clover would do it to all of the SSDT (Which I didn't dropped, because it's not 2001 and ACPI is important.)

config.plist/ACPI/DSDT/Patches applies to:
- DSDT and SSDTs extracted by Clover from BIOS
- ACPI/patched/DSDT.aml

In particular, the patches in config.plist/ACPI/DSDT/Patches DO NOT apply to ACPI/patched/SSDT*.aml.
 
Back
Top