Jump to content



Member Since 25 Jun 2012
Online Last Active 20 minutes ago

Posts I've Made

In Topic: Patch for using NVMe under macOS Sierra is ready.

27 August 2016 - 01:09 AM

I am able to generate the kext. However I can see, using kextstat, that OS X is not loading it....even when I put it in the /EFI/Clover/kexts folder?

If you have FakeSMC.kext installed in the system volume (therefore in kernel cache) and config.plist/SystemParameters/InjectKexts=Detect, all kexts in EFI/Clover/kexts are ignored by Clover.

Is this a kext signing issue?

You should install to the system volume and see if you get errors from kextcache:
sudo kextcache -i /
Then you'll know if you properly disabled SIP.

I am a registered developer, so to avoid this signing problem, is there a way I can compile the kext in Xcode?

The kext is patched from the Apple provided binary. Hence, "compile the kext in Xcode?" is nonsense. Apple does not provide source to the kext... if Apple did make it open source, creating a generic version would have been a lot easier (thanks Pike!).

In Topic: Patch for using NVMe under macOS Sierra is ready.

25 August 2016 - 05:29 PM

Hello rehab, I think you should write it even in read.me files, just my point of view

It is already very clear in the README:

- you must run the script with the parameter that corresponds to the version of OS X you are running

In Topic: Patch for using NVMe under macOS Sierra is ready.

25 August 2016 - 05:24 PM

I am trying to install OS X to a computer with an ASUS Maximus VIII (which has an M.2 NVME slot) and a 950 Pro.
The problem I am running in to is that the OS X installer cannot see the M.2 drive. Even when I open Disk Util on the installer, it still doesn't see it.
I generated HackrNVMeFamily-10_11_6.kext on a different computer. Could that be the problem? When I read the git repo, I wasn't entirely sure if the kext needed to be generated ON the computer with the NVME drive itself or not.
Could that be the problem?

You can generate HackrNVMeFamily-10_11_6.kext on another computer, but the computer must be running 10.11.6.

In Topic: SSDT contains floating region

25 August 2016 - 04:56 PM

Yes, the value do change on a random basis, and that's what troubles me. I can't just drop the tables and replace them with static ones because when the value changes, OS X refuses to boot.
I wonder if there is a way to dynamically fix that value.

Your only choice is to not use a statically patched file. Use Clover "hot patching" instead. Renaming GFX0->IGPU is easy with config.plist/ACPI/DSDT/Patches.

In Topic: SSDT contains floating region

25 August 2016 - 02:15 PM

I am trying to patch one of the SSDT's that contains GFX0, but dropping it causes a kernel panic because it contains a floating region as follows:
    OperationRegion (SANV, SystemMemory, 0x8AF74D98, 0x013F)
    Field (SANV, AnyAcc, Lock, Preserve)
I appreciate your help if anyone has a workaround.

Do you understand what the term "floating region" means? Are you seeing the address 0x8af74d98 change randomly? If not, no floating region.

When you drop SSDTs (DropOem=true), you must be sure to replace all of them (placing all static SSDTs in ACPI/patched), and make sure they load in the correct order (config.plist/ACPI/SortedOrder).
© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy