- Joined
- Sep 3, 2015
- Messages
- 11
- Motherboard
- Gigabyte H61M-S2P-R3
- CPU
- Intel Pentium G2030 3.0 GHz (Ivy Bridge)
- Graphics
- NVIDIA GeForce GT 710
- Mobile Phone
Hi
I've built this hackintosh which was working perfectly with Yosemite and El Capitan and now with Sierra I'm facing these weird issues. I have spent the last two weeks trying to work it out but getting nowhere!
Build Info:
Motherboard: Gigabyte GA-H61M-S2P-R3 (Native NVRAM and Unlocked MSR 0xE2)
CPU: Intel® Pentium® Processor G2030 (3M Cache, 3.00 GHz)
GPU: Asus NVIDIA GeForce GT 710 2GB (Using VGA port since it's the only port my Display is supporting)
RAM: Patriot 4GB 1333Mhz DDR3
BIOS Settings:
EIST Disabled
C1E Enhanced, C3/C6, Thermal Monitor Enabled
Turbo Boost Disabled (since my CPU does not support this feature)
OS Type Windows 8 with CSM set to Never (To get UEFI Video Output and clover native resolution)
EHCI/XHCI hand-off Enabled
xHCI Mode Auto
Installed with Vanilla method on Clover 3811 with the latest FakeSMC (RehabMan version)
DSDT dumped and patched by the latest MaciASL (RehabMan version)
SSDT Generated by ssdtPRGen beta 20.5 (tried with and without -xcpm flag)
Problem #1 (Fixed in a way):
So here's the issue, certain Apps like Messages, Preview crash reporting "Namespace SIGNAL, Code 0x4" as the reason, also the same error pops up when changing Color Profiles on Display Preferences and Mail App goes white screen when viewing certain messages! I've realized this error relates to CPUs lacking SSE4.1 support but my CPU supports both SSE4.1 and SSE4.2!
I found a fix (here) by vandroiy2012 on InsanelyMac requiring clover hot patching the kernel but there's no description regarding what it does and why it fixes the issue, I've been wondering if someone could shed some light on this and see if there's a DSDT patch or Kext that I can implement to fix this? I can't seem to understand why Sierra would KP on this build while it clearly supports genuine Macs with Ivy Bridge CPU architechtures! Guessing it maybe power management related I tried to switch to XCPM with clover patches but no matter what I can't seem to get XCPM working on Sierra!
Problem #2:
Sierra reboots automatically almost 5 minutes after waking up from sleep! Then it pops up a message saying Computer was shutdown due to a problem. And whenever I shutdown the machine, everything powers off except the CPU which goes on for like 5 seconds more and then going off, I never had these issues with 10.10 or 10.1.
Solutions I've tried so far:
1. Trying the clover patches with and without -xcpm
2. Generating SSDT with and without -xcpm
3. Tinkering with ACPI settings on Clover
4. Trying different kernel patches on Clover (KernelPm, KernelCPU, AICPUPM...)
5. Generating new DSDTs
6. Using different darkwake values to fix the reboot and shutdown issue
6. Clearing NVRAM
7. Having multiple Clean Installs ( Even with vandroiy2012's patch the first boot Kernel Panics on AppleIntelCPUPowerManagement.kext, Clover does 15 kernel replaces when booting on fresh install I have to disable the patch and setup Sierra and generate caches then re-enable the patch, then it does 1 kernel replaces thereafter. )
Thanks in advance
I've built this hackintosh which was working perfectly with Yosemite and El Capitan and now with Sierra I'm facing these weird issues. I have spent the last two weeks trying to work it out but getting nowhere!
Build Info:
Motherboard: Gigabyte GA-H61M-S2P-R3 (Native NVRAM and Unlocked MSR 0xE2)
CPU: Intel® Pentium® Processor G2030 (3M Cache, 3.00 GHz)
GPU: Asus NVIDIA GeForce GT 710 2GB (Using VGA port since it's the only port my Display is supporting)
RAM: Patriot 4GB 1333Mhz DDR3
BIOS Settings:
EIST Disabled
C1E Enhanced, C3/C6, Thermal Monitor Enabled
Turbo Boost Disabled (since my CPU does not support this feature)
OS Type Windows 8 with CSM set to Never (To get UEFI Video Output and clover native resolution)
EHCI/XHCI hand-off Enabled
xHCI Mode Auto
Installed with Vanilla method on Clover 3811 with the latest FakeSMC (RehabMan version)
DSDT dumped and patched by the latest MaciASL (RehabMan version)
SSDT Generated by ssdtPRGen beta 20.5 (tried with and without -xcpm flag)
Problem #1 (Fixed in a way):
So here's the issue, certain Apps like Messages, Preview crash reporting "Namespace SIGNAL, Code 0x4" as the reason, also the same error pops up when changing Color Profiles on Display Preferences and Mail App goes white screen when viewing certain messages! I've realized this error relates to CPUs lacking SSE4.1 support but my CPU supports both SSE4.1 and SSE4.2!
I found a fix (here) by vandroiy2012 on InsanelyMac requiring clover hot patching the kernel but there's no description regarding what it does and why it fixes the issue, I've been wondering if someone could shed some light on this and see if there's a DSDT patch or Kext that I can implement to fix this? I can't seem to understand why Sierra would KP on this build while it clearly supports genuine Macs with Ivy Bridge CPU architechtures! Guessing it maybe power management related I tried to switch to XCPM with clover patches but no matter what I can't seem to get XCPM working on Sierra!
Problem #2:
Sierra reboots automatically almost 5 minutes after waking up from sleep! Then it pops up a message saying Computer was shutdown due to a problem. And whenever I shutdown the machine, everything powers off except the CPU which goes on for like 5 seconds more and then going off, I never had these issues with 10.10 or 10.1.
Solutions I've tried so far:
1. Trying the clover patches with and without -xcpm
2. Generating SSDT with and without -xcpm
3. Tinkering with ACPI settings on Clover
4. Trying different kernel patches on Clover (KernelPm, KernelCPU, AICPUPM...)
5. Generating new DSDTs
6. Using different darkwake values to fix the reboot and shutdown issue
6. Clearing NVRAM
7. Having multiple Clean Installs ( Even with vandroiy2012's patch the first boot Kernel Panics on AppleIntelCPUPowerManagement.kext, Clover does 15 kernel replaces when booting on fresh install I have to disable the patch and setup Sierra and generate caches then re-enable the patch, then it does 1 kernel replaces thereafter. )
Thanks in advance
Attachments
Last edited: