Contribute
Register

Install Guide : Intel Haswell NUC Core i5 (D54250WYK) V2 (Mavericks)

Status
Not open for further replies.
Joined
Aug 31, 2010
Messages
3,888
Motherboard
Asrock Z87E-ITX
CPU
i7-4770S
Graphics
GTX 760
Mac
  1. iMac
  2. Mac mini
Mobile Phone
  1. iOS
Introduction

New Yosemite Version of this guide available here :thumbup:

First of all, welcome to the new and updated install guide for the Intel Haswell NUC !

I decided to rewrite the guide since my original, detailed here (No longer supported), was a little dated and dealt mainly with older bios versions and older OS X versions. This new guide is written specifically for the latest bios version (0028) and the most recent version of OS X (10.9.5).

Since the time of writing the original guide, a couple of things have changed. My original NUC is now permanently relocated with a family member, doing its duty as a small media server, something it is very suited to. However, in exchange for this I received a brand new NUC together with the necessary hardware to get it up and running again. This time though, since big brother was footing the bill, I took the 'opportunity' to 'upgrade' at his expense :p

So my revised hardware now reads like this (The hardware used in the original guide will still work of course) :

Intel Haswell NUC Model D54250WYKH

Amazon : http://www.amazon.com/dp/B00IEDGMRK

16Gb G.Skill Ripjaws DDR3 Ram (F3-1600C9D-16GRSL)

Amazon : http://www.amazon.com/dp/B00EOTYZOA

Samsung 840 EVO 1Tb mSata SSD (MZ-MTE1T0BW)

Amazon : http://www.amazon.com/dp/B00HWHVNUU

The NUC is the slightly newer version that has a larger chassis and can accommodate a 2.5" SSD in addition to the mSata.

The ram is a newer product from G.Skill. It runs at the same 1.35v, but is very fast, and has a lower latency of CL9. It is the ram I recommend for anyone considering an NUC.

The new SSD really needs no introduction. The 840 EVO range from Samsung are great little performers and at 1Tb will give me room for my entire media collection with plenty of space remaining. Not a bad exchange from my original hardware spec; it seems big brothers can be useful after all :lol:

This time around, the guide is much simpler than before. We will use the same tools, but there is no need to mess about using Chameleon for bits of the process.

Gone are the days of having to patch and compile a DSDT file every time the bios is updated. In fact, the DSDT file has been completely removed. The tweaks that were provided by the DSDT file are still present but have been moved, and should survive any future updates. The audio section has changed (Again!), but the audio now sounds excellent! It is no longer fuzzy sounding and does not drop out like some users found in previous versions.

For those who used the original guide to install OS X 10.9.1, you will be pleased to know that performance and stability is back to those levels too !

As before, the guide is only verified to work with the versions stated; that is version 0028 for the bios and 10.9.5 OS X. Previous bios versions and previous versions of OSX have worked well together, but I do not have the time to test and verify every OSX version with every bios version ever released. Since 10.9 is stable and 100% working on the NUC, there is no need to use older versions of the software. Several changes have enabled this since last time, including the newer builds of OSX, Multibeast and Chimera.

As previously, I recommend you do your homework; read this guide from start to finish before commencing the install. We will be using the standard TonyMacX86 tools to achieve this (Chimera/Multibeast/Unibeast). There is an alternative install method using Clover, which is detailed here; you are free to choose either method of course, but please do not attempt to mix and match these methods; it just wont work.

Finally before we start, thanks and a hi-five go to resident mod Toleda and user minihack for their help. Without it this guide would not have been possible.

Right then, lets gets started !

!!! IMPORTANT !!!

Take your time and pay attention to the guide; follow it to the letter. Copy the files to the exact locations specified. Run the programs from the locations specified. This is important to help ensure a successful build.


Guide Layout

The guide is broken down into 9 simple sections; you are recommended to read and complete them all in the order stated. They are :

1. Hardware Covered By The Guide

2. What Works And What Doesn’t Work

3. Download The Software

4. Setup The Bios

5. Create The Unibeast Installer

6. Install OS X

7. Configure Multibeast

8. Setup The Audio

9. Customize The System


Section 1 - Hardware Covered By The Guide

There are several variations of the Core i5 model NUC; they are all supported by this guide :

Intel Haswell NUC D54250WYB : Motherboard Only Package
Intel Haswell NUC D54250WYK : Motherboard In Standard Chassis
Intel Haswell NUC D54250WYKH : Motherboard In Enhanced Chassis, Space For 2.5” SSD

Note : The motherboard in each of the 3 packages contains the same hardware.


Section 2 - What Works And What Doesn't Work

Built-In Hardware :

Working : Audio (Realtek ALC283)
Working : Ethernet (Intel I218-V)
Working : Graphics (Intel HD5000)
Working : USB3 (Intel)

Additional Hardware :

Working : Apple Cinema Display 27" (DP Version)
Working : Broadcom BCM4322 (Airport Extreme)
Working : G.Skill Ripjaws Ram Memory (F3-1600C9D-16GSRL)
Working : Samsung EVO 840 SSD (1Tb)

Additional Functionality :

Working : Audio Over DisplayPort
Working : Audio Over HDMI
Working : GPU Power Management
Working : Power Management (P-States upto 2.6Ghz)
Working : Sleep & Shutdown

Note : The built-in microphone doesn't work.
Note : Other wireless LAN/bluetooth cards may work but have not been tested at this time.
Note : CIR (Consumer Infra-Red) on the NUC is NOT working at this time.
Note : P-states have been tested and showed the following : 8, 13, 14, 16, 17, 18, 19, 22, 23, 26
Summary : The working state of the hardware looks good with the minor exception of the CIR device, which is not likely to ever have support. The microphone does not work at the expense of getting a good quality of sound instead. If you absolutely need a microphone then you should consider a USB solution.


Section 3 - Download The Software

Follow the links below to download the programs and patches we will use for the install. Download them all before you begin :

Chimera (3.0.1)
Bootloader Install Program
Credit : MacMan
[Link]
DPCIManager (1.5)
PCI Hardware Viewer & Utility
Credit : phpdev32 (Sourceforge)
[Link]
Mac OS X (10.9.5)
Main OSX Install Package
Credit : Apple Inc.
[Link]
Multibeast (6.5)
Post Install Utility
Credit : tonymacx86 LLC
[Link]
PlistEdit Pro (1.7.4)
Plist File Editor
Credit : FatCat Software
[Link]
TextWrangler (4.5.10)
Free Text Editor
Credit : Bare Bones Software Inc
[Link]
Unibeast (4.0.2)
Tool To Create The USB Installer
Credit : tonymacx86 LLC
[Link]
NUC Install Pack (5.6)
Supporting Files For The Install
Credit : Take a guess ;)
Link : View attachment NUC-Install-PackV5.6.zip
Azul Framebuffer Patch (2.1)
DP / HDMI Audio Enabler
Credit : Toleda
[Link] (View Raw/Save File)
SSDT-1 (1.1)
Additional SSDT Configuration File
Credit : Toleda
[Link] (View Raw/Save File)


Note : Azul Framebufer Patch filename : [graphics_intel_hd5k-azul-f-90_patch.command.zip]
Note : SSDT-1 filename : [NUC-HD4600-A1.zip]
Note : Some site registrations may be required.
Note : Other software versions *may* work but are not supported by this guide.
Summary : Download the specified versions of the software we use, using the links provided.


Section 4 - Setup The Bios

The bios version should be 0028, and the version string should read WYLPT10H.86A.0028.2014.0814.1906.

Below is an example of how it looks in the bios itself :

105243-biosversion.jpg


Follow the bios screenshots included in the NUC Install Pack to set your bios settings correctly. Pay particular attention to the following :

a. Security > Intel(R) VT for Directed I/O (VT-d).

It is recommended to de-select this for OS X to work correctly. There is a workaround where you can have it enabled, but VT-d has no real use in OS X anyway :

93380-security.jpg


b. Boot > Boot Priority.

At this time, you should enable both 'UEFI Boot' and 'Legacy Boot' :

93379-boot-bootpri.jpg


c. Devices > Video.

Set the ‘IGD Primary Video Port’ according to the type of display connection you are using. I have set the secondary port to 'None' and the 'IGD Minimum Memory' to 1Gb. This memory setting does not appear to have any effect on the actual amount of memory used by OS X :

93378-dev-video.jpg


Note : The NUC Install Pack includes screenshots of all the bios settings you should use.
Summary : Make sure you setup the bios correctly before you begin, otherwise it might not work.


Section 5 - Create The Unibeast Installer

To create the Unibeast Installer we will use the official Unibeast guide and then customize it to work with the NUC. You will need a blank USB memory key for this; it should be at least 8Gb capacity.

First, head over to the official Unibeast creation guide which can be found here, and follow Steps 1 and 2 of that guide. Be sure to label the chosen memory key as 'USB', as directed in that guide.

Once those 2 steps are complete, you have a standard Unibeast Installer. Before we can use it, we need to customize it to make it work with our NUC.

Start by opening the 'Terminal' app and at the terminal prompt, type in the following and press Enter :

Code:
[COLOR="#FF0000"]sudo -s[/COLOR]

You will be prompted for your password; go ahead and type in your password then press Enter.

Next, type in the following at the prompt and press Enter:

Code:
[COLOR="#FF0000"]chflags nohidden /Volumes/USB/*[/COLOR]

Then type in this line and press Enter :

Code:
[COLOR="#FF0000"]chflags nohidden /Volumes/USB/Extra/*[/COLOR]

And finally this one and press Enter :

Code:
[COLOR="#FF0000"]chflags nohidden /Volumes/USB/Extra/modules/*[/COLOR]

This has made some files and folders visible on the Unibeast installer, which were hidden when it was created. You can now exit the 'Terminal' app.

Next, unzip the NUC Install Pack; we are interested in 3 files which are :

  • mach_kernel
  • smbios.plist
  • org.chameleon.boot.plist
We need to copy those 3 files to the Unibeast Installer.

In Finder, copy the file mach_kernel FROM the NUC Install Pack TO the root of the Unibeast Installer, overwriting the existing one.

Copy the files smbios.plist and org.chameleon.boot.plist FROM the NUC Install Pack TO the /Extra folder of the Unibeast Installer, overwriting the existing ones.

Next, go to the '/Extra/modules' folder on the Unibeast Installer and delete the file called 'HDAEnabler.dylib'.

At the root of your Unibeast Installer drive, create a folder called 'Software', and copy all the software you downloaded into this folder, including the NUC Install Pack. However, do NOT copy the OSX Installer app, just the other software. This will save you having to swap drives around later.

Summary : We have created a standard Unibeast Installer, with customized kernel and configuration files, as well as the necessary software we will need during installation.


Section 6 - Install OS X

We are now ready to commence the installation of OS X to the NUC. Insert your Unibeast Installer drive to a free USB port on the NUC and reboot it. When it boots, press F10 to get to the boot menu and select the Unibeast Installer drive to boot from.

Now you will see the Chimera boot screen with the 'USB' icon in the middle. Hit the space bar, type in the following boot flags and then press Enter:

Code:
[COLOR="#FF0000"]-v UseKernelCache=No GraphicsEnabler=No IGPEnabler=Yes IGPlatformID=0D220003[/COLOR]

Point of note : If you use a monitor that has a resolution of anything other than 1920 x 1080, you may need to add this additional boot flag :

Code:
[COLOR="#FF0000"]"Graphics Mode"="1920x1080x32"[/COLOR]

The reason for this is because sometimes the graphic display on the installer screen can otherwise appear corrupted and unusable. You should add this additional boot flag throughout the installation steps; once your NUC is booting on its own, the additional flag is no longer needed.

After a minute or so of loading files, you will see the usual OS X installer screen.

First thing to do is load the Disk Utility and partition your drive accordingly. I used the entire capacity of the drive and labelled it 'Mavericks'. The rest of the guide assumes you have used the same label; you are free to rename it after the installation is complete.

When you are done partitioning, start the installation and let the OSX Installer do its magic.

At the end of the install when prompted you should reboot your NUC, but leave the Unibeast Installer connected. Once again, when the NUC boots, press F10 to get to the boot menu and select the Unibeast Installer drive to boot from.

This time you will see the Chimera boot screen with a 'USB' icon and also a 'Mavericks' icon.

Highlight the 'USB' icon, hit the space bar and type in the same boot flags followed by the Enter key :

Code:
[COLOR="#FF0000"]-v UseKernelCache=No GraphicsEnabler=No IGPEnabler=Yes IGPlatformID=0D220003[/COLOR]

This will start the OS X Installer a second time; when you reach the installer screen, start the 'Terminal' app from the 'Utilities' menu at the top. You should see the bash prompt like this :

Code:
bash-3.2#

Copy the modified kernel file FROM the Unibeast Installer TO the NUC system drive (Mavericks). To do that type in the following and press Enter :

Code:
bash-3.2# [COLOR="#FF0000"]cp -v '/Volumes/[B]USB[/B]/mach_kernel' '/Volumes/[B]Mavericks[/B]/[/COLOR]'

Now exit the 'Terminal' app.

Summary : We now have OS X fully installed to the NUC system drive (Mavericks) and the modified kernel in place that will allow it to boot correctly.


Section 7 - Configure Multibeast

The time has now come to setup Multibeast on your NUC. Quit the OS X Installer and reboot your NUC but leave the Unibeast Installer plugged in. Press F10 to get the boot selection screen and select the Unibeast Installer drive to boot from.

This time at the Chimera boot screen, highlight the 'Mavericks' icon. Hit the space bar and use the same boot flags as before, then press Enter :

Code:
[COLOR="#FF0000"]-v UseKernelCache=No GraphicsEnabler=No IGPEnabler=Yes IGPlatformID=0D220003[/COLOR]

After a minute or so of scrolling files up the screen, the NUC should now boot into the OS X installation. You will be presented with the usual configuration steps where you complete the network selection, license agreement and create a new User Account. Complete these steps as normal and you will reach the OS X desktop screen.

Before we go any further, copy all of the software FROM the 'Software' folder you created on the Unibeast Installer drive TO the Downloads folder of your NUC. Unzip the NUC Install Pack in the Downloads folder.

Now, from the Downloads folder of your NUC, unzip and start Multibeast and load the NUC.mb configuration file from the NUC Install Pack. This will pre-select all the files and options we are interested in.

The '10.9.4+ TRIM Patch' is optional but recommended if you are installing to an SSD drive, unless of course you have your own trim method, such as the Cindori TrimEnabler.

The theme can be changed to whichever one you prefer.

Whatever you do though, please do NOT select the QuickStart option in Multibeast as this will cause issues. The default selection in the NUC.mb configuration file as shown below should be suitable for most users.

Install Multibeast making sure you select your NUC system drive (Mavericks) as the install target :

105245-multibeast-settings.jpg


You will see some warnings generated during the Multibeast installation about kernel extensions being from unidentified developers; this is fine and you should dismiss these warnings by clicking 'Ok' when prompted.

Close Multibeast when it has finished installing.

On the NUC system drive (Mavericks), go to the '/Extra/modules' folder. Delete the file called 'HDAEnabler.dylib'.

Next, using OSX Finder, copy the following 3 files FROM the NUC Install Pack TO the /Extra folder of your NUC system drive (Mavericks) :

  • SSDT.aml
  • smbios.plist
  • org.chameleon.boot.plist

Finally, unzip the file called 'NUC-HD4600-A1.zip' in your Downloads folder. In the resulting folder you will find a file called 'SSDT-1.aml'; you should copy this to the /Extra folder of your NUC system drive (Mavericks).

You can now eject the Unibeast Installer and reboot the NUC.

When you reboot it, type in the following flags at the boot screen (This only needs to be done once) and press the Enter key :

Code:
[COLOR="#FF0000"]-v UseKernelCache=No[/COLOR]

Your NUC should now boot on its own.

Do a quick check to make sure the graphics are working as expected; go to About This Mac > More Info > System Report then select the 'Graphics/Displays' section. If all is well it should look similar to this :

93664-hd5000.jpg


Now close System Information.

Summary : We now have a basic configuration installed and made the NUC bootable.


Section 8 - Setup The Audio

Before you run through this section, you should backup a couple of important files and keep the originals in a safe place.

On your NUC system drive (Mavericks), go to '/System/Library/Extensions'. Take a copy of the following 2 files from that folder :

'AppleHDA.kext'
'AppleIntelFramebufferAzul.kext'

Store them somewhere safe so that if the audio patches change in the future, you can restore these and run the patches on original versions of the file.

Unzip and install the DPCIManager program found in your Downloads folder, and then run it. In DPCIManager, click on the icon at the top centre to 'Install Kext'. Using the file selector, point it to the file in the NUC Install Pack called 'AppleHDA.kext', and allow it to install the file. When prompted, allow it overwrite the existing one.

Keep a watch on the 'Log' window that opens and allow it to finish; you will see some text scroll down. It has finished when you see the following lines at the top of the Log window :

Code:
/: no supported helper partitions to update
Lock acquired; proceeding.
/: no supported helper partitions to update
Created prelinked kernel /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.
It may take a couple of minutes for this to happen; be patient. Once you see the above code in the Log window, you can close the DPCIManager program.

Now we will apply the Azul Framebuffer patch. This is located in your Downloads folder and is called :

'graphics_intel_hd5k-azul-f-90_patch.command.zip'

Double click the file to unzip it, and then double click the unpacked file to apply the actual patch.

Now, run DPCIManager again, but this time select the option to 'Rebuild Cache' and enter your password when prompted. As above, wait until you see those lines appear at the top of the Log window; this may take a minute or so to complete.

Finally, go to 'Applications/Utilities' and start the 'Audio MIDI Setup' program. On the left hand side of the window that appears you will see an option for 'Built-In Output'. In the main window you will see 3 channel sliders that are labelled 'Master', '1' and '2'.

Tick the 'Mute' box to the right of the Channel 1 slider. Once completed it should look like this :

105255-audiosetup.jpg


Do not omit the step above. If you do then your audio quality will be very poor and sound quite fuzzy and distorted.

Using this method to setup the audio gives us the best quality sound available from many hours of audio testing with different configurations. The minor downside is this : if at any point in the future you change the default balance settings in Sound Preferences, then the mute option above will be de-selected and the sound will be fuzzy and distorted. You can simply go back and mute channel 1 as described above. What this basically means is that you cant change the balance for the built-in ALC283 audio. This should not be an issue for regular desktop use though, and if you absolutely need balance control then you should consider a USB audio solution.

Thats it. HDMI audio, DisplayPort audio and ALC283 audio are all now enabled and setup !

You can now quit DPCIManager and reboot the NUC. Go to About This Mac > More Info > System Report and click on the 'Audio' section. You should see the HDMI/DisplayPort Output device :

93621-hdmi-audio2.jpg


Now go to System Preferences > Sound; you should see the HDMI/DisplayPort device as an output option, as well as an output option for the internal audio that uses the 3.5mm connector on the front of the NUC (This will be called 'Internal Speakers') :

93620-hdmi-audio.jpg


Yours may look a little different depending which display you have connected. HDMI displays do not offer volume control in Sound Preferences or the volume slider at the top of the screen; the idea is that you use the remote control or on-screen settings to adjust the volume for that type of display. This is by design and how it is meant to work.

The AppleHDA supplied in the Install Pack will automatically switch the output device to 'Internal Speakers' when you plug headphones or speakers into the 3.5mm audio connector on the front of the NUC, and will revert back when you unplug them. Nice !

Summary : OS X is now configured with full audio capability.


Section 9 - Customize The System

This section is not strictly necessary as your NUC is now fully configured, but I have included this to help make it look and feel more like a real mac.

We will make 4 small changes here. They are :

About This Mac > More Info > Overview > Image
About This Mac > More Info > Overview > Title & Year
About This Mac > More Info > Overview > Processor/Memory/Serial Number/Software
About This Mac > More Info > System Report > SMC Version

About This Mac (Image)

From the NUC Install Pack, right-click and copy the file called 'com.apple.macbookair-13-unibody.icns'.

Navigate to 'System/Library/CoreServices'. Right click on the file 'CoreTypes.bundle' and click on 'Show Package Contents'.

Then click on 'Contents' and then 'Resources'. Here you will see lots of colorful icons and folders.

In this resources folder, right-click and then 'Paste' the file. It will ask if you wish to overwrite the existing file; go ahead and allow it to overwrite.

About This Mac (Title & Year)

Unzip and install TextWrangler from your Downloads folder. Start the TextWrangler program and select File > Open; tick the 'Show hidden items' option and then open the following file, where 'YourUserName' represents your account name :

Code:
/Mavericks/Users/[B]YourUserName[/B]/Library/Preferences/com.apple.SystemProfiler.plist

In here you will see several text lines, the one we are interested in is at or around line number 8, and is enclosed in <string> and </string> tags. It contains the Macbook Air model & Year.

Copy and paste this text in its place :

Code:
Intel® Haswell NUC (D54250WYKH)

You can change the exact model name in brackets above, based on which model of NUC you have.

Go ahead and save the file.

About This Mac (Processor/Memory/Serial Number/Software)

Still within TextWrangler, navigate to and open the following file :

Code:
'/Applications/Utilities/System Information.app/Contents/Resources/English.lproj/SPInfo.strings'

(If you use a different language then open the file in the appropriate .lproj folder for your language)

You will see 2 columns in the file; the first is a set of labels, the second is a set of strings, a bit like this :

// localizable strings used in the system information window

// overview panel

MAC_MODEL = "%@ model";
MAC_CPU_LABEL = "Processor";
MAC_MEMORY_LABEL = "Memory";

The lines I have changed are listed below with the replacement values :

Code:
MAC_CPU_TEXT = "%1$@  1.3 Ghz Intel\U00ae Core\U2122 i5 4250U";

Code:
MAC_MEMORY_TEXT = "%1$@  %2$@ G.Skill %3$@";

Code:
MAC_SERIAL_TEXT = "%1$@  G6YK40900BLM";

Code:
OS_VERSION_TEXT = "%1$@  %2$@ Mavericks %3$@ (%4$@)";

You can copy & paste from the replacement lines above, and change the Serial Number and ram manufacturer to match yours. In the examples I give, pay particular attention to the 2 spaces immediately after the '%1$@'. Those 2 spaces must remain, irrespective of what values you use. If you don't leave the spaces, it will not work correctly.

Once you have finished your changes, save the file and close TextWrangler. You may be prompted for your password when you do the save.

About This Mac (SMC Version)

Here we will make a small change to the FakeSMC.kext to make it report the correct SMC version for our System Definition (MacbookAir6,2) and also SMC type.

First of all, you need to update to the latest version of the FakeSMC file. It is initially installed as part of Multibeast, but the developers update FakeSMC and its associated plugins quite regular.

To update FakeSMC and the plugins, first open the 'HWMonitor' program in your 'Applications' folder. This will display as a small icon in the top right hand side of the main OS X screen. Left click on this icon, and in the popup display that appears, click on the 'gearwheel' icon in the top right, as shown below :

105260-hwmonitor.jpg


This will show a small context menu with an option to 'Check For Updates...'. Select the updates option; the program will then do a check (You must have a working internet connection for this to work). Take the option to run the update where the latest version will then be downloaded to your computer and it will automatically run the installer.

This is a standard OS X style installer and you should click through the initial screens until you get to the 'Installation Type' section; on this part make sure you click on the 'Customize' option and select ALL options and plugins, as shown below :

105261-hwmonitor2.jpg


Allow the install to complete and then reboot your NUC.

Next, using OS X Finder, copy the file FakeSMC.kext from '/System/Library/Extensions' to your OS X Desktop.

Right click on this file and select 'Show Package Contents'. Open the 'Contents' folder, and copy the file Info.plist to your desktop.

In your Downloads folder, unzip and install the 'PlistEditPro' program. Open PlistEdit Pro and open the Info.plist file on your desktop.

In the top window of PlistEdit Pro, using the navigation triangles, navigate to the following location :

'IOKitPersonalities/FakeSMC/Configuration'

In the list you will see a string entry for 'smc-compatible' with a value of 'smc-napa'. Double click on the text that says smc-napa so it becomes editable, and change it from 'smc-napa' to 'smc-huronriver'. It should look like this when done :

93665-plisedit-smc.jpg


Next, navigate to :

'IOKitPersonalities/FakeSMC/Configuration/Keys/REV'

Item 1 under the 'REV' subkey is where we make the next change. It currently holds the default SMC version of 1.30f3. We want to change this to the correct version for the MacbookAir6,2, which is version 2.13f9.

To do this, double click on the data value of Item 1 and change it from :

01300F00 0003

To this new value :

02130F00 0009

Now drop down one key level from 'REV' to 'RVBF' and repeat the process.

Finally drop down one level again from 'RVBF' to 'RVUF' and repeat the process again.

At the end, it should look like this :

96080-plistedit-version.jpg


What we have done is set the correct SMC type, and changed 3 instances of the SMC version to the correct version number.

Save the file and close PlistEdit Pro.

Right click on the Info.plist file on the desktop and select 'Copy Info.plist'.

Now, right click on FakeSMC.kext on the desktop and once again select 'Show Package Contents'.

Navigate into the 'Contents' folder and then paste the updated Info.plist by right clicking and selecting 'Paste Item'. Replace the existing one when prompted.

What we have now done is to extract the Info.plist file from FakeSMC.kext, made some changes and put the updated file back. All we need to do now is install the updated FakeSMC.kext on our system and reboot.

Open the DPCIManager program, click on the 'Install Kext' icon at the top center of the screen, and select the FakeSMC.kext file on the desktop. You will be asked if you want to overwrite the existing one, to which you should click on 'Ok', and after entering your password, the newly updated FakeSMC.kext will be installed.

Again, you should wait for the kext to finish installing, by waiting for the text to appear at the top of the Log window. Here is a reminder of what you are looking for :

Code:
/: no supported helper partitions to update
Lock acquired; proceeding.
/: no supported helper partitions to update
Created prelinked kernel /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.
Now close DPCIManager and reboot your NUC. Take a look in System Information. The value for 'SMC Version' should now show the correct value of 2.13f9 as seen highlighted here :

96081-system-smc.jpg


Something to consider is that FakeSMC is updated often; each time you run the update option, the correctly edited FakeSMC will be overwritten, so you will need to go back and repeat the edit for the SMC Version as described above.

You can also download the latest version of the FakeSMC and plugins manually by checking here. The package name is called 'HWSensors'.

Summary : The NUC now has a few extra tweaks to make it look more mac-like. You have now reached the end of the guide.

:thumbup:

As with the previous guide, if you have any issues with something not working as expected, please make a post detailing what you think is wrong and why. Screenshots help with this too.

And above all, when posting requests for help, state clearly the make, model and capacity you are using for the following hardware:

Ram Memory
SSD / Hard Drive
Wifi/Bluetooth card or devices
Make & Model of display
Display connection type i.e HDMI or DisplayPort
Whether you are using an adaptor cable or not
If it is a boot related error, a clear and legible screenshot

I will not respond to requests for help without this information provided.

Known Issues

HWmonitor generates a warning in the system log about being unable to parse the maximum RPM for Fan1 and Fan2. This is an issue with HWmonitor itself and not with your NUC.

Credits :

ReHabMan for his kernel patching code
PikeRAlpha for his kernel patching code
Pjalm for his USB power fix
Macman for providing Chimera, Multibeast & Unibeast
Toleda for his help with HDMI audio & SSDT
Minihack for his help providing the audio kext file
TonyMac team for the website and install tools
All the developers of the HWSensors package
Resident mod Stork for his guidance and assistance

ChangeLog

23/05/2014 - Initial release
23/05/2014 - Clarified location to store downloaded software
23/05/2014 - Section 5 wording improved
23/05/2014 - Added some extra explanations; made others more clear
27/05/2014 - Added reminder to copy and run files from correct locations.
27/05/2014 - Remove HDAEnabler.dylib after Chimera installation
31/05/2014 - Bios update version 0026
01/06/2014 - HDMI audio patch v2.1
01/06/2014 - Add recommendation to backup original files at Section 8
15/06/2014 - SMC Version bump to 2.13f9
04/07/2014 - 10.9.4 Upgrade note added - See post #315
04/07/2014 - Install Pack V5.1 (10.9.4 Update)
04/07/2014 - Guide updated to OSX version 10.9.4
04/07/2014 - Install Pack V5.2 (Minor update)
04/07/2014 - TextWrangler bump to V4.5.9
05/07/2014 - Install Pack V5.3 (Change default resolution)
08/07/2014 - Install Pack V5.4 (Include Technical Product Spec)
21/09/2014 - Bios update version 0028
21/09/2014 - OS X Update to 10.9.5
21/09/2014 - Multibeast version 6.4.2 update
21/09/2014 - TextWrangler bump to V4.5.10
21/09/2014 - Unibeast version 4.0.2 update
21/09/2014 - Install Pack V5.5 (OSX 10.9.5 update)
25/09/2014 - Install Pack V5.6 (Updated configurations)
25/09/2014 - Completion of guide for OS X 10.9.5
 
Last edited by a moderator:
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

Nice update!

I have cherry picked the guide to try out and use your SSDT methods instead of DSDT and also to incorporate the FakeSMC edits on my Clover build and all looks good.

Just wondering if there are any downsides to having a DSDT in the system that is "broken"? Obviously the new SSDT methods make everything a lot easier, but (just from an academic/curiosity point of view) are there any differences between a "fixed' DSDT + SSDT, versus a vanilla DSDT + "fixed" SSDTs?
 
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

are there any differences between a "fixed' DSDT + SSDT, versus a vanilla DSDT + "fixed" SSDTs?
There is no binary if the compiler reports errors. The native dsdt is not broken; it simply means a different iASL compiler was used to decompile than what was used to compile. If there is no need to edit the dsdt, there is no need to fix native dsdt compile errors.

Back to your question, there is no "fixed" ssdt, there is one ssdt that works the same with the native dsdt and the "fixed" dsdt. The result is only one case; native dsdt and ssdt.
 
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

Nice update!

I have cherry picked the guide to try out and use your SSDT methods instead of DSDT and also to incorporate the FakeSMC edits on my Clover build and all looks good.

Just wondering if there are any downsides to having a DSDT in the system that is "broken"? Obviously the new SSDT methods make everything a lot easier, but (just from an academic/curiosity point of view) are there any differences between a "fixed' DSDT + SSDT, versus a vanilla DSDT + "fixed" SSDTs?

Put simpy, I dont think cherry picking is a good idea, although anyone is free to do that. The whole idea was to get away from the somewhat flakey results of the last guide and have something that is much more robust. However as our guest of honour and provider of the new AppleHDA you have 'cherry picking' rights :lol:

In short, no downsides but plenty of advantages:

The performance is much better; back to 10.9.1 days for those of us who remember, i know you do.
Everything is fully recognised and PM is improved.
Its easier to maintain for those who use this method.
Its easier for me to support.
It should survive updates quite nicely.
Its quicker to setup and install.
No error messages whatsoever in the system logs; call me a pedant but i think thats good to aim for.
The end result is very smooth and slick.

The DSDT method gave us 'some' of these things.

Ditching the DSDT as a file and going this method is advantageous for all concerned.

Technically, the DSDT still exists though :thumbup:
 
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

Put simpy, I dont think cherry picking is a good idea, although anyone is free to do that. The whole idea was to get away from the somewhat flakey results of the last guide and have something that is much more robust. However as our guest of honour and provider of the new AppleHDA you have 'cherry picking' rights :lol:

In short, no downsides but plenty of advantages:

The performance is much better; back to 10.9.1 days for those of us who remember, i know you do.
Everything is fully recognised and PM is improved.
Its easier to maintain for those who use this method.
Its easier for me to support.
It should survive updates quite nicely.
Its quicker to setup and install.
No error messages whatsoever in the system logs; call me a pedant but i think thats good to aim for.
The end result is very smooth and slick.

The DSDT method gave us 'some' of these things.

Ditching the DSDT as a file and going this method is advantageous for all concerned.

Technically, the DSDT still exists though :thumbup:

We all share and share alike here. That's why we contribute and post.

All I am doing is replacing my own DSDT and SSDT with the SSDT/SSDT-1 from the new pack (i.e. leave the DSDT native and use the SSDTs from the package). As I understand this is a good swap/upgrade and avoids me having to edit DSDTs anymore (which is nice!).

Also I liked the idea of the key change in FakeSMC, so I have popped that in my build too.

Both of these items are install method and boot loader independent and help to keep us a little more Mac-like. So thank you WD, Toleda and all for the continued support. For my part I will continue to help and contribute whenever I can.

All best,

:thumbup:
 
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

There is no binary if the compiler reports errors. The native dsdt is not broken; it simply means a different iASL compiler was used to decompile than what was used to compile. If there is no need to edit the dsdt, there is no need to fix native dsdt compile errors.

Back to your question, there is no "fixed" ssdt, there is one ssdt that works the same with the native dsdt and the "fixed" dsdt. The result is only one case; native dsdt and ssdt.

Thank you for the succinct explanation Toleda. I will happily enter the new era of not having to edit DSDTs!
 
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

We all share and share alike here. That's why we contribute and post.

All I am doing is replacing my own DSDT and SSDT with the SSDT/SSDT-1 from the new pack (i.e. leave the DSDT native and use the SSDTs from the package). As I understand this is a good swap/upgrade and avoids me having to edit DSDTs anymore (which is nice!).

Also I liked the idea of the key change in FakeSMC, so I have popped that in my build too.

Both of these items are install method and boot loader independent and help to keep us a little more Mac-like. So thank you WD, Toleda and all for the continued support. For my part I will continue to help and contribute whenever I can.

All best,

:thumbup:

I dont know how the system logs look in Clover, but check them out and see what if any errors you have in there.

Start by filtering on 'kernel' as a keyword and have a look...
 
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

Awesome guide!! Even better than the last! Just finished the install, works great! I noticed the Broadcom chip is not enabled in this guide, I have the Azurewave AW-CE123H, Broadcom BCM94352HMB installed. Any recommendations for the best way to enable the bluetooth and wireless? Thanks!!!

learjet7
 
Installation Guide : Intel Haswell NUC Core i5 (D54250WYK) V2

Awesome guide!! Even better than the last! Just finished the install, works great! I noticed the Broadcom chip is not enabled in this guide, I have the Azurewave AW-CE123H, Broadcom BCM94352HMB installed. Any recommendations for the best way to enable the bluetooth and wireless? Thanks!!!

learjet7

Have a read of this thread.

I believe there are some instructions in there to get it working.

I have one of those cards here too, but have not had chance to try it under the new guide. This is planned for future testing, and if it works, I will add it.

Good to see the new guide has worked well for you!

:thumbup:
 
Status
Not open for further replies.
Back
Top