Jump to content

[Guide] Mac OSX 10.12 and 10.13 with X99 Broadwell-E family and Haswell-E family

nmano

By nmano,
in Installation Guides

 Share
1954 posts in this topic

Recommended Posts

mfc88
mfc88
Posted
Posted

I have lots of KP when I was using fakesmc from RehabMan. Now I only using Slice version

Guess I was using an old netkas version. Switched to newest. Testing again...

 

Update: Newest FakeSMC breaks WIFI despite FakeSMC patch/config.plist patches/SSDT injection.

 

Update: Kernel panics galore. Switched back to old setup.

  • Like 1
Sygey02
Sygey02
Posted
Posted
Hello, boys! I have a problem and I was wondering if anyone could help me.

I have noticed that if I overclock to xmp profile 1 - 4.2 does not boot MacOS Sierra, I always have kernel panic with this message. I'll paste pictures below if someone can explain what's going on.

I can say that if I set the normal profile I can boot in the mac, if I overclock then it gives me kernel panic

post-1219427-0-59949600-1493217630_thumb.jpg

post-1219427-0-20622900-1493217632_thumb.jpg

post-1219427-0-24243800-1493217634_thumb.jpg

post-1219427-0-40653400-1493217635_thumb.jpg

post-1219427-0-40608600-1493217636_thumb.jpg

nmano
nmano
Posted
  • Author
Posted

 

Hello, boys! I have a problem and I was wondering if anyone could help me.
I have noticed that if I overclock to xmp profile 1 - 4.2 does not boot MacOS Sierra, I always have kernel panic with this message. I'll paste pictures below if someone can explain what's going on.
I can say that if I set the normal profile I can boot in the mac, if I overclock then it gives me kernel panic

 

I thing wrong fakecpu ID

sent your EFI folder

  • Like 2
DexterOX
DexterOX
Posted
Posted

@nmano

 

In The Capitan you use this DSDT Path for LPC

Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Return (Buffer (One)
                        {
                             0x03                                           
                        })
                    }

                    Return (Package (0x0C)
                    {
                        "AAPL,slot-name", 
                        Buffer (0x09)
                        {
                            "Built In"
                        }, 

                        "name", 
                        Buffer (0x15)
                        {
                            "Intel LPC Controller"
                        }, 

                        "model", 
                        "Intel C610/X99 Series Chipset LPC Controller", 
                        "compatible", 
                        Buffer (0x3C)
                        {
                            /* 0000 */  0x70, 0x63, 0x69, 0x31, 0x30, 0x34, 0x33, 0x2C,
                            /* 0008 */  0x38, 0x36, 0x30, 0x30, 0x00, 0x70, 0x63, 0x69,
                            /* 0010 */  0x38, 0x30, 0x38, 0x36, 0x2C, 0x38, 0x64, 0x34,
                            /* 0018 */  0x37, 0x00, 0x70, 0x63, 0x69, 0x38, 0x30, 0x38,
                            /* 0020 */  0x36, 0x2C, 0x38, 0x63, 0x34, 0x62, 0x00, 0x70,
                            /* 0028 */  0x63, 0x69, 0x63, 0x6C, 0x61, 0x73, 0x73, 0x2C,
                            /* 0030 */  0x30, 0x36, 0x30, 0x31, 0x30, 0x30, 0x00, 0x4C,
                            /* 0038 */  0x50, 0x43, 0x42                               
                        }, 

                        "IOName", 
                        "pci8086,8d47", 
                        "device-id", 
                        Buffer (0x04)
                        {
                             0x47, 0x8D, 0x00, 0x00                         
                        }
                    })
                }
            }

I see this too

X99 AppleLPC.kext for 10.11.2

Just install and patch DSDT or set clover
into method label _DSM parent_adr 0x001F0000 remove_entry;
into device name_adr 0x001F0000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
Store (Package (0x02)\n
{\n
"compatible", \n
Buffer (0x0D)\n
{\n
"pci8086,8d47"\n
}\n
}, Local0)\n
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
Return (Local0)\n
}
end

But now you have added this patch for the Rampage V Extreme, in the attachments at the beginning of this post

#Maintained by: N.Mano
# 1. Under Device LPC0 - Verify IOReg/LPC0
into method label _adr parent_adr 0x001F0000 remove_entry;
into device name_adr 0x001F0000 insert
begin
Name (_SUN, 0x0F)  // _SUN: Slot User Number\n
Method (_DSM, 4, NotSerialized)\n
{\n
    Store (Package ()\n
        {\n
            "compatible", \n
            Buffer ()\n
            {\n
                "pci8086,9c43"\n
            }\n
        }, Local0)\n
    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
    Return (Local0)\n
}
end;

Can you tell me which one is right for my Rampage V extreme x99 chipset?

 

Thanks!

  • Like 1
nmano
nmano
Posted
  • Author
Posted

@nmano

 

In The Capitan you use this DSDT Path for LPC

Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Return (Buffer (One)
                        {
                             0x03                                           
                        })
                    }

                    Return (Package (0x0C)
                    {
                        "AAPL,slot-name", 
                        Buffer (0x09)
                        {
                            "Built In"
                        }, 

                        "name", 
                        Buffer (0x15)
                        {
                            "Intel LPC Controller"
                        }, 

                        "model", 
                        "Intel C610/X99 Series Chipset LPC Controller", 
                        "compatible", 
                        Buffer (0x3C)
                        {
                            /* 0000 */  0x70, 0x63, 0x69, 0x31, 0x30, 0x34, 0x33, 0x2C,
                            /* 0008 */  0x38, 0x36, 0x30, 0x30, 0x00, 0x70, 0x63, 0x69,
                            /* 0010 */  0x38, 0x30, 0x38, 0x36, 0x2C, 0x38, 0x64, 0x34,
                            /* 0018 */  0x37, 0x00, 0x70, 0x63, 0x69, 0x38, 0x30, 0x38,
                            /* 0020 */  0x36, 0x2C, 0x38, 0x63, 0x34, 0x62, 0x00, 0x70,
                            /* 0028 */  0x63, 0x69, 0x63, 0x6C, 0x61, 0x73, 0x73, 0x2C,
                            /* 0030 */  0x30, 0x36, 0x30, 0x31, 0x30, 0x30, 0x00, 0x4C,
                            /* 0038 */  0x50, 0x43, 0x42                               
                        }, 

                        "IOName", 
                        "pci8086,8d47", 
                        "device-id", 
                        Buffer (0x04)
                        {
                             0x47, 0x8D, 0x00, 0x00                         
                        }
                    })
                }
            }

I see this too

X99 AppleLPC.kext for 10.11.2

Just install and patch DSDT or set clover
into method label _DSM parent_adr 0x001F0000 remove_entry;
into device name_adr 0x001F0000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
Store (Package (0x02)\n
{\n
"compatible", \n
Buffer (0x0D)\n
{\n
"pci8086,8d47"\n
}\n
}, Local0)\n
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
Return (Local0)\n
}
end

But now you have added this patch for the Rampage V Extreme, in the attachments at the beginning of this post

#Maintained by: N.Mano
# 1. Under Device LPC0 - Verify IOReg/LPC0
into method label _adr parent_adr 0x001F0000 remove_entry;
into device name_adr 0x001F0000 insert
begin
Name (_SUN, 0x0F)  // _SUN: Slot User Number\n
Method (_DSM, 4, NotSerialized)\n
{\n
    Store (Package ()\n
        {\n
            "compatible", \n
            Buffer ()\n
            {\n
                "pci8086,9c43"\n
            }\n
        }, Local0)\n
    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
    Return (Local0)\n
}
end;

Can you tell me which one is right for my Rampage V extreme x99 chipset?

 

Thanks!

check rehapman

https://github.com/RehabMan/Laptop-DSDT-Patch

MaLd0n
MaLd0n
Posted
Posted

for LPC, use it, work in all

Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Return (Buffer ()
                        {
                             0x03                                           
                        })
                    }

                    Return (Package ()
                    {
                        "device-id", 
                        Buffer ()
                        {
                             0x43, 0x9C, 0x00, 0x00                         
                        }, 

                        "name", 
                        Buffer ()
                        {
                            "pci8086,9c43"
                        }, 

                        "compatible", 
                        Buffer ()
                        {
                            "pci8086,9c43"
                        }
                    })
                }
  • Like 2
Fergarth
Fergarth
Posted
Posted

Hello everyone!

After a period of absence due to having moved to another house... just only today I reassemble and connect the hack and took the opportunity to test the news.

Updated to Sierra 12.5 Beta 4, last Clover and FakeSMC suggested by MaldOn.

Tested PMdrvr.kext without SSDT and liked the result. Although I do not think it behaves very differently from SSDT. It just seems to have a more stable idle. Tomorrow I need to test better and see if the 3 patches I use are still needed or not!

But the system is stable and seems better with EIST disabled.

post-1313347-0-64344000-1493330665_thumb.png

post-1313347-0-05541800-1493330674_thumb.png

post-1313347-0-39481000-1493330688_thumb.png

  • Like 2
Fergarth
Fergarth
Posted
Posted

Very good result! :yes:;)

Thanks Maldon, I also liked it. But so suddenly and at first glance, in my case it does not differ much from SSDT behavior. In a moment, I'll play with the patches and the PMdrvr and see the result. I do not know PMdrv.kext well, but I think it can be influenced by the patches and this is the doubt that I will clarify soon.
  • Like 1
PMheart
PMheart
Posted
Posted

IMHO we have no need for any 3rd-party Power Management Kexts, XCPM is enough I guess.

IMHO XCPM shouldn't be designed for more P-States, the most important thing is having a complete Power Management. As for more P-States, we don't really need it. I suppose that 800 MHz, base frequency, turbo frequency are enough under XCPM mechanism.

 

 

Sent from my iPhone 7 using Tapatalk

  • Like 2
Fergarth
Fergarth
Posted
Posted

IMHO we have no need for any 3rd-party Power Management Kexts, XCPM is enough I guess.

IMHO XCPM shouldn't be designed for more P-States, the most important thing is having a complete Power Management. As for more P-States, we don't really need it. I suppose that 800 MHz, base frequency, turbo frequency are enough under XCPM mechanism.

 

 

Sent from my iPhone 7 using Tapatalk

I agree with you PMheart, I tried kext out of curiosity, but as I said, in my case it did not change in almost anything. Besides I miss the sleep. I already reversed the previous situation. DSDT, SSDT for PM and the 3 patches. And it's very good as it is ?
  • Like 2
Fergarth
Fergarth
Posted
Posted

Ok, the strange freezings I've been having a while ago, finally have ended. What I took to solve this!...

From the moment I overclocked the processor, memory and set new SSDT PM to 4000 MHz, it never happened again.

Yes in my case, I also think it had to do with the frequency of memory. Now the RAM is working with the native frequency and before was with a much lower freq. Much better, fast and stable now!  :yes: 

post-1313347-0-60540000-1493654755_thumb.png

post-1313347-0-60344100-1493654789_thumb.png

post-1313347-0-64911700-1493654798_thumb.png

post-1313347-0-78982400-1493654810_thumb.png

post-1313347-0-46037600-1493654820_thumb.png

  • Like 2
MICKHAEL
MICKHAEL
Posted
Posted

Ok, the strange freezings I've been having a while ago, finally have ended. What I took to solve this!...

From the moment I overclocked the processor, memory and set new SSDT PM to 4000 MHz, it never happened again.

Yes in my case, I also think it had to do with the frequency of memory. Now the RAM is working with the native frequency and before was with a much lower freq. Much better, fast and stable now! :yes:

Glad to hear) but the strange freezing come back to me
  • Like 1
Fergarth
Fergarth
Posted
Posted

@MaLd0n

Yeah man, but this time I'm not getting away from the black screen and I do not know why! I already tried several old tricks that resulted, until I tried changing the DP port in the graph and nothing... only with the flag nv_disabled = 1 I can get to login...

But for the rest everything is perfect and stable.

  • Like 1
Fergarth
Fergarth
Posted
Posted

Strange

try Clover update

Clover_v2.4k_r4067.pkg.zip

 

16F71b

NVDAStartupWeb.kext.zip

I updated for 12.5 beta 5 (16F71b), even experimented with the Clover and kext that you suggested and nothing!

I can switch between the OS X Default G Driver and the NVIDIA Web Driver, but as soon as I reboot it comes out black screen and I still do not know why! I never had such a thing! What is worth in the middle of this is that the random freezings are gone lol...

post-1313347-0-11868400-1493742867_thumb.png

post-1313347-0-86239100-1493742877_thumb.png

Fergarth
Fergarth
Posted
Posted

Use nvda_drv=1 in Boot section and NvidiaWeb in System Parameters

work only with two options for me

I also tested with that and nothing happens. Even with my old DSDT I have tried it and it always gives black. Incidentally all the old tricks and options I know do not work ... I think I'll have to wait for a new Web Driver or go back to 12.4 Final...
mfc88
mfc88
Posted
Posted

I also tested with that and nothing happens. Even with my old DSDT I have tried it and it always gives black. Incidentally all the old tricks and options I know do not work ... I think I'll have to wait for a new Web Driver or go back to 12.4 Final...

Have you tried this patch?

 

http://www.insanelymac.com/forum/topic/319764-guide-dell-xps-15-9550-sierra-10122-quick-installation/page-22?do=findComment&comment=2396871

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...