Mavericks install from USB fails on Intel NUC D34010WYK

[octavp]

I do not seem to get to the Mavericks installer on this device. I tried both legacy and UEFI options in BIOS, changed the graphics memory to 128MB, used -v with and without the GraphicsEnabler=No and PCIRootUID=0. All I manage to get is a short view of the apple logo (or with -v all the text messages) followed by a NUC restart. I am using the miniDisplay port to drive my display. Any ideas?
Thanks,
octavp

 

[trancestar]

Hey,

You need to put this mach_kernel on your USB stick: http://www.tonymacx86.com/mavericks-laptop-support/114677-haswell-early-reboot-mavericks-locked-msrs-hp-envy-15-j063cl-i7-4700mq.html
When you have installed OS X, boot into the USB stick again and use the Terminal to copy over the mach_kernel to the disk where you installed OS X with command cp /mach_kernel /volumes/NAMEOFDISK

I have the D54250WYK and have installed OSX with both myHack and Unibeast. But something is not working as it should with UniBeast when Chimera is installed f.ex the spinning wheel spins crazy fast and when you type something it writes several letters at a time like "ccccccccpppppp //////" and when you logout from OS X the countdown timer runs the 60secs in like 10secs. With the myHack (chameleon) this does not happen and OSX behaves as expected. Anyone knows what causes speedy behavior?

Also how do I get it to be installed as a macbook air 6,2 as that has the same CPU and GPU?

Kind Regards
David

 

[octavp]

Hey David,

Thanks for the pointers but my understanding from the link you've sent is that he patched a retail mach_kernel and that building it from the source was anyway not the right way to go.
I patched my mach_kernel as indicated and I managed to get it past of the reboot point however this time it ends up complaining about timing out when loading AppleIntelCPUPowerManagement and an unknown CPU model 0x45. The last line says "power management may be incomplete or unsupported" and it does not go any further than that however it does not restart itself. I could only go that far with the -x option.

Any other idea?
Thanks,
Octavp

 

[octavp]

Update: I took the mach_kernel from the link below and put it on my USB to install OSX. I managed to get to the OSX installer with -x option after that. OSX installed fine however to boot into the freshly installed OS I used the following parameters : -x -IGPEnabler=Yes IGPlatformID=04260000.
I did run MultiBeast for Mavericks app however I did not get a working WiFi and my USB keyboard is behaving very strange - typing is very sensitive.
Any ideas?
Second, how would I get rid of typing the parameters above and just start the OSX on the NUC?
Thanks,
Octavp

 

[st3ffen]

I've the same problem

 

[jespera]

Hey,

You need to put this mach_kernel on your USB stick: http://www.tonymacx86.com/mavericks-laptop-support/114677-haswell-early-reboot-mavericks-locked-msrs-hp-envy-15-j063cl-i7-4700mq.html
When you have installed OS X, boot into the USB stick again and use the Terminal to copy over the mach_kernel to the disk where you installed OS X with command cp /mach_kernel /volumes/NAMEOFDISK

I have the D54250WYK and have installed OSX with both myHack and Unibeast. But something is not working as it should with UniBeast when Chimera is installed f.ex the spinning wheel spins crazy fast and when you type something it writes several letters at a time like "ccccccccpppppp //////" and when you logout from OS X the countdown timer runs the 60secs in like 10secs. With the myHack (chameleon) this does not happen and OSX behaves as expected. Anyone knows what causes speedy behavior?

Also how do I get it to be installed as a macbook air 6,2 as that has the same CPU and GPU?

Kind Regards
David

We seem to experience the same issues. Lets try to to smash our heads together.

 

[akm144]

same here

did any one get any solution??

 

[WonkeyDonkey]

same here

did any one get any solution??

I posted an NUC guide here. Apart from the CPU i think most of it should be identical.

The kernel patching guide is the same for your model though.

 

[akm144]

it dint worked bro...
it just lagged at one position