[NEW / TESTING] Intel 7th Generation Kaby Lake CPUs + 200 Series Motherboards in macOS

[scottynl]

Hi Guys! Im killing myself here, haha. Finally i got past the Apple logo and started the installation but when Im gonna choose the location to install sierra, I can't find my SSD... I only see the USB.

Any thoughts? Thanks in advance.

Go to the disk utility in the top menu. format you're drive.
If that is visible in disk utililty.

EDIT: my bad did not refresh. duplicate.

 

[mannray]

Anybody think the v6 (kaby lake) Xeon chips will work? Rumors are that new apple computer will have these chips in october.

 

[Superbogey]

1. What version of MultiBeast did you use? Try moving your FakeSMC sensor kexts to the Desktop and (make sure that they are the only kexts on your Desktop) run KextBeast to install them back to the /Library/Extensions/ folder. Be advised that FakeSMCGPU kext has not been updated for Nvidia GTX 10x0 cards, and will cause Kernel Panic/Reboot.

Well, I get as far as DSMOS: SMC returned incorrect key: followed by a gazillion zeros and then after another line with panic(cpu 3 caller, a hex number and then a repeat of the DSMOS message followed by /buildroot/library/caches/com.apple.xbs/sources/don'tstealmacos/dontstealmacos-26.50.1/Dont_Steal_MacOS.cpp:221 And, no. It's not a stolen copy of macOS. I got it straight from the Apple Store, if anyone is wondering.
@Stork, @RehabMan
View attachment 254183

SUCCESS! I hit on the idea to use a different profile for the system settings so went into SMBIOS in Configurator and change it from iMac 17,1 to iMac 14,2 and the DSMOS error went away. I got clover installed on the boot drive and am now proceeding to run Multibeast. Thanks for the help @Xanny.

 

[Xanny]

SUCCESS! I hit on the idea to use a different profile for the system settings so went into SMBIOS in Configurator and change it from iMac 17,1 to iMac 14,2 and the DSMOS error went away. I got clover installed on the boot drive and am now proceeding to run Multibeast. Thanks for the help @Xanny.

Anyway that kind of problem happen because you used a clover config.plist yet used, to be more specific:
Mac Hardware is serial and uuid is checked and stored by Apple, if you use a config.plist taken from a forum or from another users, the serial result yet used, so you got that kind problem.
It's not a matter of SMBIOS but related regarding Serial etc...

 

[Superbogey]

Anyway that kind of problem happen because you used a clover config.plist yet used, to be more specific:
Mac Hardware is serial and uuid is checked and stored by Apple, if you use a config.plist taken from a forum or from another users, the serial result yet used, so you got that kind problem.
It's not a matter of SMBIOS but related regarding Serial etc...

I'm not a newbie. I don't keep the serial number from configs. I know better than that. I generate each one using the magic wand on the SMBIOS tab in Configurator and check the serial numbers on Apple's database. I've been in computer hardware tech for both Macs and PCs since the early 80s and have been building Hackintoshes for about 7 years so I know how to troubleshoot component problems that way. Software errors are another thing entirely and I don't do much coding outside rudimentary scripts or batch files from the "ye olde daies" (ever try to install MS-DOS on a DEC Rainbow 100?) thus why I couldn't decipher the DSMOS error.

 

[OscarPettersson]

What do you see in Disk Utility? (did you create a partition there?)
What kind of SSD? SATA, or NVMe?

I found it! I went to the disk utility and formated it (thanks @scottynl )I manage to install Sierra and do the Post installation with Multibeast (followed this guide) but after restarting the computer it won't boot from the Sierra HD... It end up with the cirkel and a cross.

I have a Intel 600p Series M.2 2280 SSD 512GB BTW. I will try to fix it tomorrow and can upload my files if you are interested. Thanks everyone for being so helpful!

 

[xxcesarioxx]

@aka80 yup, I received my Fendi t919 and both wifi and Bluetooth work instantly without any configuration.

No Bluetooth issue.

 

[Xanny]

I'm not a newbie. I don't keep the serial number from configs. I know better than that. I generate each one using the magic wand on the SMBIOS tab in Configurator and check the serial numbers on Apple's database. I've been in computer hardware tech for both Macs and PCs since the early 80s and have been building Hackintoshes for about 7 years so I know how to troubleshoot component problems that way. Software errors are another thing entirely and I don't do much coding outside rudimentary scripts or batch files from the "ye olde daies" (ever try to install MS-DOS on a DEC Rainbow 100?) thus why I couldn't decipher the DSMOS error.

I'm little older than you. I started on a ZX81, ZX Spectrum and then Apple IIe clone, a very long story, in early 80s PCs were far to be "popular". In 1987 I got my first PC clone (ms-dos 3.31 I think).

Anyway, old and un-useful stories apart, from the error you showed, there is normally only a reason, and the right solution for you was to change SMBIOS. What can I say coincidence?

I did not mean to offend you in any way, but I wrote that message not to you but for many people here that have taken config.plist's from everywhere.

 

[OscarPettersson]

Hi. I can't boot after post installation. Trying with screen connected to my gtx 1060. Attached black screen. Disclaimer: first hacky.

Any ideas?

 

[ralph123]

My motherboard has the same codec ALC1220, and my sound is working with AppleALC.kext+lilu.kext Audio id 1 but also with 7 or 11, change HDAS to HDEF has been done?
About TB3 support, i never worked on that particular hw.

Hi all, I'm new in the hackintosh world and I'm planning to build the desktop listed in my profile.
As I read your MB has almost the same USB, audio and Ethernet chipset, I read a lot and I understood that maybe the most tricky part is for the Asmedia controller but do you have any suggestion?
It seems that you know a lot in kexts and compatibility, can I ask you a little OT? How it works with kexts and future support in general, I mean, if I build something new now and I have to use community kexts, those kexts will be the same for future MacOS major updates or I have to hope that someone will release it? So for example there is the possibility that I will not be able to use USB in 2 or 3 years?
Thanks in advance