Jump to content
11 posts in this topic

Recommended Posts

Hello there everyone. I recently put together a CL hackintosh for a somebody else and it mostly works fine; however, he's been having a problem that I (so far) haven't been able to replicate. He sometimes gets odd beachballs that end up freezing the computer into needing a cold shutdown and boot; which usually in turn freeze halfway through the boot process only for a reboot to work.

 

Recently he mentioned this happened after several hours of sleep (left the computer sleeping during the night), so I'll try reproducing it later.

 

However, I'm trying to figure out what the actual problem might be. I've got a theory: Wake-up issues with the NVME controller. Why? I've been experiencing similar issues on my real MBP (2011) because the secondary HD ribbon cable has been coming loose. Of course, since it's just a secondary drive, it's a large inconvenience but it doesn't completely shut the computer down. It would certainly be different if this was happening with the primary drive, though.

 

 

What do people think about this? It's the first time I've built a hackintosh with modern hardware (my own is Ivy Bridge) and I'd never tried NVME before, so there's been plenty of trial and error involved in this build.

 

Stats:

 

CPU: i7-8700

MB: Gigabyte Z370-HD3P

RAM: 32 GB DDR4

Video: Asus RX580

Drives: Samsung 940 EVO, 2x 1TB HDDs.

Wifi/BT: BCM94331

 

 

Other than this issue, pretty much everything seems to be working fine on 10.13.2 (with the exception of the CPU saying Unknown on "About this Mac" but I guess that's cosmetic and expected)

Link to comment
https://www.insanelymac.com/forum/topic/331070-i7-8700-weird-beachballs/
Share on other sites

I have an updated summary of the issue, as I reproduced and saw it for myself now.

 

After sleeping and waking (slept just long enough for the fans and lights to turn off), the computer works normally except that if you try to open any image or video file, the application used to do it (Be it Preview, VLC, QuickLook, you name it) becomes nonresponsive, to the point of preventing restart/shutdown. Although, it's still possible to Force Quit it from the dock or activity manager, as usual.

Check, replace full folder, reboot, send me new ioreg with new files

attachicon.gifClover.zip

 

btw, if u can extract original DSDT with F4 key in Clover boot screen

 

Could you please tell me what you changed/why? I like knowing what I'm doing.

From running a folder diff I can see you updated several kexts for which apparently new versions are now out. I also see you changed lots of things in the config.plist; some of those changes I cannot understand why; though. You removed the sensrhub table, and modified the SIP config, and removed some of my custom DSM from the DSDT (Wifi, USB3.1), why?

 

Some of those tables (for example sensorhub) were there because the stock ones didn't compile due to syntax errors and that resulted in missing functionality (in the case of sensrhub, I couldn't see half my sensors)

is a oem table, u dont need extract and use in ur clover folder if u dont drop oem

i just applied a correct coffeelake patches

report me one ioreg after reboot, I'll show you the patches.

 

 

I dropped it because the OEM version doesn't compile.

u dont need compile it, is a oem table, if u don't drop it, is load all time

 

check what tables load with Patchmatic

attachicon.gifPatchmatic extract.zip

 

put in /usr/bin and run .command

 

Even if it's an OEM table, if it is badly written, it will result in an ACPI error when it's loaded. What I did is drop the original and load a corrected version.

 

Anyway, your clover folder didn't really fix this issue. I managed to fix it in the end by applying a mixture of fixes.

 

I used your DSDT (but not your config.plist, although I did take some of your changes like SmartUPS and a couple other things), I kept my darkwake=10 and also added the fixes discussed here: https://pikeralpha.wordpress.com/2017/01/12/debugging-sleep-issues/

 

One thing I hadn't understood before is that deep sleep that doesn't wake with keyboard is actually intended behavior.

  • Like 1

u can use only my folder and enable intel HD for Hardware acceleration, use shiki and shikigva=60

- GRAPHICS : Check InjectIntel

- GRAPHICS : “ig-platform-id” changed to 0x59120000
- DEVICES : “Fake ID” for IntelGFX changed to 0x59128086
- BOOT : Add “-disablegfxfirmware” under Custom Flags
the other all in DSDT and minimal essential kexts
 
Enjoy!
×
×
  • Create New...