Jump to content

RehabMan

RehabMan

Member Since 25 Jun 2012
Offline Last Active 12 minutes ago
*****

Posts I've Made

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

Today, 01:51 AM

Please Help-me to fix this.

 

Obs:. Sorry for my bad english.

 

Suggest you read the guide carefully, and stick only to what is written... (you have some additions in your SSDT that are not part of the guide... and wrong).

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

Yesterday, 06:30 PM

 

I tried, but there was a kernel panic. I tried the coexist patch, but I must be missing the path of the pci. My pci path on windows is:

 
PCIROOT (0) #PCI (0200) #PCI (0000) #PCI (0800) # PCI (0000)
ACPI (_SB _) # ACPI (PCI0) #ACPI (BR2A) #ACPI (H000) #PCI (0800) #PCI (0000)

 

 

You are doing very strange things in your SSDT for the NVMe.

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

Yesterday, 06:10 PM

Can someone help me ? My NVME always stays as external. I must be wrong about something.

 

 

The Board Is X99 Designare EX

 

If you implement the class-code spoof with HackrNVMeFamily, you won't have that issue...

In Topic: Clover General discussion

22 May 2017 - 04:20 PM

 

good point Rehabman about patch count - was thinking that using a 0 for patch count may help future proof the patch? i cant think of a scenario when we want anything but all occurrences patched?

 

Correct.

In Topic: Clover General discussion

22 May 2017 - 04:11 PM

Hi there, I was linked to this discussion on applelife. Could you explain me what's the issue, and what exactly fails?

Data patching is not an issue for Lilu, it works fine in AppleALC.

The only issue I could think of is a bug in Lilu prior to 1.1.1 that prevented two kexts patching the same kext, so make sure you are up to date.

 

You could specify 0 to replace all the occurrences, but specifying a correct value makes a faster patch.

 

@tluck resolved in post here: http://www.insanelym...50#entry2427524

 

I don't think the code at github (IntelGraphicsDVMTFixup) has been updated.

No problem in Lilu... just need to specify the number of max expected patches.

 

As you mention we can specify 0 to catch all of them, or an accurate value.

Since this data lies near the end of the kext, there is probably no significant performance advantage to specifying anything other than zero.

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