[Success] nab’s INTEL NUC DC3217IYE (CLOVER/Yosemite)

[marsofearth]

[Problems] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

Upload an image of my Kernel Panic on Boot after doing the MultiBeast Patch thingy.

Installed Mavericks fine using UniBeast
ReBooted into Mavericks SSD
Did the MultiBeast Patch as in SynGatesFan200's NUC
ReBoot - Boot from Mavericks SSD

Kernel Panic.

6th time now installing Mavericks into this NUC.

 

[TimW]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

...
MultiBeast - Mavericks 6.2.1 : There is no Intel -hnak's AppleIntelIE1000e in Multibeast that I can see. What should I choose?
...

I can help a little. In Multibeast 6.2.1 hnak's AppleIntelIE1000e driver is now just the AppleIntelIE1000e driver (no hnak). See http://www.tonymacx86.com/announcements/126815-multibeast-6-2-1-released.html where it says "Moved Drivers -> Network -> Intel - hnak's AppleIntelE1000e v2.4.14 to Drivers -> Network -> Intel -> AppleIntelE1000e v2.4.14"
I'm actually using the v3.0.4 version without any problems.
I'm on an older version of the bios than you and my install was very straight-forward with 10.9.2 and Multibeast v6.2.1. Maybe that was the difference?

 

[TimW]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

Upload an image of my Kernel Panic on Boot after doing the MultiBeast Patch thingy.

Installed Mavericks fine using UniBeast
ReBooted into Mavericks SSD
Did the MultiBeast Patch as in SynGatesFan200's NUC
ReBoot - Boot from Mavericks SSD

Kernel Panic.

6th time now installing Mavericks into this NUC.

You are installing the patched AppleIntelCPUManagement, aren't you? (As per the picture here http://www.tonymacx86.com/user-buil...nderbolt-edition-non-thunderbolt-edition.html)

 

[marsofearth]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

You are installing the patched AppleIntelCPUManagement, aren't you? (As per the picture here http://www.tonymacx86.com/user-buil...nderbolt-edition-non-thunderbolt-edition.html)

Here is a copy of my MultiBeast Setup I used last:
***************

MultiBeast Configuration - 2014-04-02 02:15:08 -----------------------------------------------------------------
Quick Start > DSDT Free
Drivers > Disk > TRIM Enabler > 10.9.x TRIM Patch Drivers > Misc > FakeSMC v6.0.1123
Drivers > Network > Intel > AppleIntelE1000e v2.4.14
Drivers > System > Patched AppleIntelCPUPowerManagement > OS X 10.9.0 Drivers > System > AppleRTC Patch for CMOS Reset
Bootloaders > Chimera v2.2.1
Customize > Boot Options > Basic Boot Options
Customize > System Definitions > Mac mini > Mac mini 5,1
Customize > Themes > tonymacx86 Black

***************

I hope you see something to fix!~

 

[TimW]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

This is what I used - the DSDT was that from the thread I linked to above:

Quick Start > UserDSDT - /Documents/DSDT.aml
Drivers > Disk > TRIM Enabler > 10.9.x TRIM Patch
Drivers > Misc > FakeSMC v6.0.1123
Drivers > Network > Intel > AppleIntelE1000e v2.4.14
Drivers > System > Patched AppleIntelCPUPowerManagement > OS X 10.9.0Drivers > System > AppleRTC Patch for CMOS Reset
Bootloaders > Chimera v2.2.1
Customize > Boot Options > Basic Boot Options
Customize > Boot Options > Generate CPU States
Customize > Boot Options > Hibernate Mode - Desktop
Customize > Boot Options > Use KernelCache
Customize > System Definitions > Mac mini > Mac mini 5,1
Customize > Themes > tonymacx86 Black

This came from the saved config I had before Multibeast 6.2.1 which is why it has the older version of the IntelE1000e driver listed. I updated that later.

 

[marsofearth]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

This is what I used - the DSDT was that from the thread I linked to above:

Quick Start > UserDSDT - /Documents/DSDT.aml
Drivers > Disk > TRIM Enabler > 10.9.x TRIM Patch
Drivers > Misc > FakeSMC v6.0.1123
Drivers > Network > Intel > AppleIntelE1000e v2.4.14
Drivers > System > Patched AppleIntelCPUPowerManagement > OS X 10.9.0Drivers > System > AppleRTC Patch for CMOS Reset
Bootloaders > Chimera v2.2.1
Customize > Boot Options > Basic Boot Options
Customize > Boot Options > Generate CPU States
Customize > Boot Options > Hibernate Mode - Desktop
Customize > Boot Options > Use KernelCache
Customize > System Definitions > Mac mini > Mac mini 5,1
Customize > Themes > tonymacx86 Black

This came from the saved config I had before Multibeast 6.2.1 which is why it has the older version of the IntelE1000e driver listed. I updated that later.

Very interesting.

Seems the only difference here is that I had not added:

Customize > Boot Options > Hibernate Mode - Desktop
Customize > Boot Options > Use KernelCache

I did find a solution to my problem, thanks to: monkeytrash's post here

By "removing" (renaming) the AppleIntelCPUPowerManagement.kext

located here> /Volumes/{Mavericks_Volume}/System/Library/Extensions

- I booted into my USB Unibeast Installer and opened up Terminal.app from the Menu Bar and entered the following commands:

cd /
cd volumes
cd {Mavericks_System_Volume}/system/library/extensions
mv appleintelcpupowermanagement.kext appleintelcpupowermanagement.old

Where {Mavericks_System_Volume} equals the name of MY (or yours if you choose to do the same) Mavericks System Disk Volume.

- From there Rebooted
- Booted into my Mavericks SSD Volume with no problems.
- Re patched with MultiBeast as per my parameters above a couple posts
- Rebooted
- Booted into Mavericks with no Problems, no need for Unibeast help.

This left me to start fixing the HDMI Audio issue...

I wonder why leaving out the Hibernate Mode and/or Use KernelCache would cause the KP, or perhaps it was another reason all together.

Thank you!

 

[TimW]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

Actually I think this was the important bit:

Customize > Boot Options > Generate CPU States

I think that allows the AppleIntelCPUManagement kext to work properly and enables e.g. speed step etc. But TBH, I don't know for sure.

Having googled a bit, it might be the DSDT - but I really, really don't know. At least we both have working systems

 

[marsofearth]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

Actually I think this was the important bit:

Customize > Boot Options > Generate CPU States

I think that allows the AppleIntelCPUManagement kext to work properly and enables e.g. speed step etc. But TBH, I don't know for sure.

Having googled a bit, it might be the DSDT - but I really, really don't know. At least we both have working systems

Brilliant!

I'm ordering another mSATA SSD for this little NUC, I will have to try this when I receive it with a new install.

Thank you for the back and forth, it really helps for understanding!

Cheers!

Mars

 

[nabs]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

Upload an image of my Kernel Panic on Boot after doing the MultiBeast Patch thingy..

I had a similar problem with 10.8.5 - for whatever reason your version of AppleIntelCPUPowerManagement
was not correct, as you found out, one way to get the the correctly patched version applied is to boot with unibeast and remove the currently installed kext from the filesystem first. In my case - and yours apparently - this allowed the system to boot.

The general advice at the time (September last year) was that the system should not boot if this kext is not present (unless you also have NullCPUPowerManagement installed), but this did not seem to be the case for me. Having said that, I have never gone back to repeat the test to be sure about this.

Either way, you were right to install the patched version since as Rehabman explains below, it enables cpu power management ("Speedstep")

http://www.tonymacx86.com/os-x-updates/108840-kernel-panic-after-update-10-8-5-a-3.html#post667521

 

[BerndVP]

[success] nab’s INTEL NUC DC3217IYE, i3-3217U (ethernet edition)

Hey Nabs,

I got a question.
Is your Intel Nuc sleeping without problems ?

Mine goes in sleep but after some times, and this is random, it wakes again, but then after the timer of sleeping is done, it goes sleeping again.

This goes on and on.

Any solution for this problem ?