Jump to content

New build GA-Z170X-UD5 mac OS Sierra problems


tamorgen
 Share

13 posts in this topic

Recommended Posts

I've been running a GA-Z68XP-UD3 board for nearly 5 years, and I've decided to upgrade:

 

GA-Z170X-UD5 Motheboard

Intel Core i7 6700K CPU

G.SKILL F4-3000C15D-16GVRB Ripjaw Series 16 GB DDR 3000 DIMM

EVGA Geforce GTX 970 4GB FTW Gaming

Corsair HX850i PSU

Corsair Hydro Series H75 Closed Loop CPU cooler

Plextor M8Pe M.2 2280 512GB NVMe

 

My old system ran very solid for most of that time. I started off building it with utilites from (that sight that shall not be named), and moved from the dark side to Clover. Overall Clover has been a much better experience, once it's up and running.

 

I've based my BIOS settings on Cyberdevs post, and even tried variations of his config.plist. I've added PikerAlpha's IONVMEFamily.kext patch to the clover Kernel and Kexts patching, to try and get Sierra to recognize my NVMe SSD (no luck yet)

 

I'm only using FakeSMC.kext and NullCPUPowermanagement.kext (tried with and without the later)

 

I installed Sierra using a Vanilla install off of USB to my old Crucial 128 GB SSD, since the Sierra installer doesn't see my M.2 drive. Installation went fine. Upon reboot (still off of USB), I'm getting Kernel panics and not able to boot into mac OS.

 

panic(cpu 0 caller 0xffffff80003430d6): "zone_init: kmem_suballoc failed"/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.1.32/osfmk/kern/zalloc.c:2149

 

I've attached my EFI directory. Can anybody assist?

EFI.zip

Link to comment
Share on other sites

Anyone?

 

I've been working on this all day. I've removed some of the extra stuff in the clover folders, and I'm making very little progress. I stilll cannot boot.

 

I've attached the latest image of my panic screen.

post-516716-0-10571000-1477186296_thumb.jpg

Link to comment
Share on other sites

I have this board, and the NVMe patches are working for me with a Samsung 950 Pro. I don't believe I have seen any success reports from Plextor NVMe drives.

 

One thing I noticed in your zip is that your kexts are zips and not kext bundles.

Link to comment
Share on other sites

I have this board, and the NVMe patches are working for me with a Samsung 950 Pro. I don't believe I have seen any success reports from Plextor NVMe drives.

 

One thing I noticed in your zip is that your kexts are zips and not kext bundles.

That's really weird that they got zipped.  They definitely aren't on my /EFI directory.  Any chance you can post your directory what you have so I can compare?

Link to comment
Share on other sites

I still can't get past:

 

panic(cpu 4caller 0xffffff7f8cb99358): "Unsupported CPU"@/Users/kozlek/Documents/HWSensors/Shared/cpuid.h:698

 

I am just trying to boot off of the USB.  All I have is FakeSMC and NullCPUPowerManagement installed.  I'm getting very frustred.

Link to comment
Share on other sites

I still can't get past:

 

panic(cpu 4caller 0xffffff7f8cb99358): "Unsupported CPU"@/Users/kozlek/Documents/HWSensors/Shared/cpuid.h:698

 

I am just trying to boot off of the USB.  All I have is FakeSMC and NullCPUPowerManagement installed.  I'm getting very frustred.

Sure, I can post mine. This error looks to me like you have HWSensors installed either in /S/L/E or /L/E since I didn't see them in your EFI.

  • Like 1
Link to comment
Share on other sites

Sure, I can post mine. This error looks to me like you have HWSensors installed either in /S/L/E or /L/E since I didn't see them in your EFI.

 

Thanks.  I'll give them a looksie when I get home (and you get them posted).  While I don't remember having HWSensors installed, it's certainly possible.  I may need to wipe the drive and start clean as a next step.  It's certainly possible that there is something in my /S/L/E directory that I don't remember, and the Sierra installer isn't overwriting/clearing out.

Link to comment
Share on other sites

Sure, I can post mine. This error looks to me like you have HWSensors installed either in /S/L/E or /L/E since I didn't see them in your EFI.

 

So, good news/bad news.  Mostly good.

 

I got my system to boot finally.  I booted into the Mac OS installer, and then went into Terminal and mounted the system drive.  I went into /S/L/E, and sure enough, there was FakeSMC.kext, right where it shouldn't have been.  I originally built my old system using MB from TM (can't say the real names on this board), and his tools put FakeSMC in there.

 

So I'm up and now just need to fine tune (and there was much rejoicing).  The bad news, is that I had to remove my M.2 drive to see my other hard drives and SSDs.  I'm unclear why this is, but I suspect that some of the SATA ports get disabled if an M.2 drive is present.  The only thing I found in the manual is that a PCI slot gets disabled, but I'm sure I'm missing something somewhere.

 

I'd still like to take a look at your /EFI directory and config.pllst.  My System Report is showing my EVGA Geforce GTX 970, but at 0 MB.  Definitely something wonky there.

Link to comment
Share on other sites

So, good news/bad news.  Mostly good.

 

I got my system to boot finally.  I booted into the Mac OS installer, and then went into Terminal and mounted the system drive.  I went into /S/L/E, and sure enough, there was FakeSMC.kext, right where it shouldn't have been.  I originally built my old system using MB from TM (can't say the real names on this board), and his tools put FakeSMC in there.

 

So I'm up and now just need to fine tune (and there was much rejoicing).  The bad news, is that I had to remove my M.2 drive to see my other hard drives and SSDs.  I'm unclear why this is, but I suspect that some of the SATA ports get disabled if an M.2 drive is present.  The only thing I found in the manual is that a PCI slot gets disabled, but I'm sure I'm missing something somewhere.

 

I'd still like to take a look at your /EFI directory and config.pllst.  My System Report is showing my EVGA Geforce GTX 970, but at 0 MB.  Definitely something wonky there.

Try disabling InjectNvidia. Alternatively, you can inject your video RAM size to correct that value. Sorry, I didn't get around to posting last night (Battlefield 1.. :blush: )

Link to comment
Share on other sites

Try disabling InjectNvidia. Alternatively, you can inject your video RAM size to correct that value. Sorry, I didn't get around to posting last night (Battlefield 1.. :blush: )

 

I figured it out the hard drive/ssd issue.  I had to move the M.2 drive to the M2H_32G slot, but the Plextor NVMe drive still doesn't show up in BIOS or Disk Utility, even with the Pikeralpha's Kexts patches.  I'm returning the Plextor SSD and picking up the Samsung 950 Pro, which is a known quantity.  The plan will be to use Carbon Copy Cloner to copy my existing SSD over to the Samsung 950 when it comes in, and pray it boots.   :thumbsup_anim:

 

I did get the GTX 970 to show up correctly using a iMac 17,1 profile and another set of Kext patches to get past the black screen issue.  Unfortunately, as I left my Hackintosh running last night, it installed 10.12.1 and booted rebooted to VGA mode.  (No nvidia web driver for 10.2.1 yet, eek).  I started restoring from my Time Capsule when I left for work this morning, so hopefully all should be right with the world when I get home.

 

What works so far:

Sound (PikerAlpha's Kext patch)

Video (sort of)

I believe CPU states work, as the DSDT for the 6700k is installed.  Haven't verified/tested yet.

 

Still to do:

Get NVMe drive to work

Figure out the USB mapping.   I don't want to use third party kexts.  I prefer to patch the kexts.

Verify if sleep works

Link to comment
Share on other sites

Thanks, our config.plists where pretty close.  I added the SSDT_USB.aml code for this motherboard, which maps all the USB ports correctly and at the correct speeds, except for the USB-C and USB 3.1 ports, which somehow they both show up without any port mapping.  They have to be in another part of the IORegistry, so I'll just count my self luck that they work.

 

I also got the Samsung NVMe SSD via FedEx today, and it installed right away.  Mac OS told me that there was a drive attached that wasn't initialized, just like any other SSD or HDD.  Once I partitioned it, I used Carbon Copy Cloner to copy the system drive, and it made the recovery partition all by itself.  I had to manually format the EFI partition from the command line, and then copied my EFI directory from the old drive.   Shut down, remove the cable from my old OS drive, and then reboot.  Everything worked like a charm.

 

I'm still working with Clover to hide the drives I don't want seen, but overall, I can call it a victory.  I also need to figure out the correct way to inject the monitor settings for iMac 17,1.  I had to use the AGDPfix.app to get it to work.  I know there is a more vanilla way than modding the existing kext, so I need to figure that out.

 

I've attached the SSDT-USB file if you are interested.

SSDT-USB.zip

  • Like 1
Link to comment
Share on other sites

Thanks, our config.plists where pretty close.  I added the SSDT_USB.aml code for this motherboard, which maps all the USB ports correctly and at the correct speeds, except for the USB-C and USB 3.1 ports, which somehow they both show up without any port mapping.  They have to be in another part of the IORegistry, so I'll just count my self luck that they work.

 

I also got the Samsung NVMe SSD via FedEx today, and it installed right away.  Mac OS told me that there was a drive attached that wasn't initialized, just like any other SSD or HDD.  Once I partitioned it, I used Carbon Copy Cloner to copy the system drive, and it made the recovery partition all by itself.  I had to manually format the EFI partition from the command line, and then copied my EFI directory from the old drive.   Shut down, remove the cable from my old OS drive, and then reboot.  Everything worked like a charm.

 

I'm still working with Clover to hide the drives I don't want seen, but overall, I can call it a victory.  I also need to figure out the correct way to inject the monitor settings for iMac 17,1.  I had to use the AGDPfix.app to get it to work.  I know there is a more vanilla way than modding the existing kext, so I need to figure that out.

 

I've attached the SSDT-USB file if you are interested.

Glad to hear! I also am using AGDPFix.app currently, but there is another way I have not yet tried: https://pikeralpha.wordpress.com/2016/10/11/black-screen-tip-of-the-day/ 

 

Thanks for the USB SSDT. I will definitely give it a go!

Link to comment
Share on other sites

 Share

×
×
  • Create New...