Contribute
Register

Sebinouse's Build : CustoMacMini 2014 - Intel NUC Haswell i5-4250U - El Capitan

Status
Not open for further replies.
from what i understand this is happen because CodecCommander.kext that is responsible with wakening our sound , more here
https://github.com/Dolnor/EAPD-Codec-Commander



I use mini HDMI to HDMI and sound is OK (you do not have access to control volume, sound being pass trough.

Check in sound -> output if HDMI is selected

Thanks Mosu. I'll check out the CodeCommander.kext link. Actually HDMI never shows as an output. All I ever see is internal speakers and external headphone. The internal speakers listing threw me.

I'll do a clean build today and see what happens.
 
Did a clean install and followed the instructions in the original post and the updates and helpful posts. I now have the NUC running just about perfectly

Shows as MacMini 7.1 with Serial. Bluetooth and Wifi working perfectly. Sound out via speakers and HDMI. Still get crackling via speakers so need to look closer into that. I have the trial version of Boom 2 running and it boosts the low sound significantly and gives an on screen volume control when using sound through HDMI.

Screen resolution is 1920 x 1080. Anything higher and everything becomes too small on my Dell 27 inch quad screen so I'll keep it at 1080.

One problem I have noticed is that if I use VGA (playing with the NUC at work and no HDMI connection so have to use VGA) and the unit goes to sleep it will not recover. The monitor stays dark and no mouse or keyboard input will resurrect it. I checked with HDMI and it is OK, it wakes up and LAN is active. VGA requires a shutdown and restart.

Other than that and the speaker crackling (which actually isn't a problem as I use HDMI sound) this little NUC is running fantastically well. Big thanks to Sebinouse and everyone who helped me get this far.
 
Did a clean install and followed the instructions in the original post and the updates and helpful posts. I now have the NUC running just about perfectly

Shows as MacMini 7.1 with Serial. Bluetooth and Wifi working perfectly. Sound out via speakers and HDMI. Still get crackling via speakers so need to look closer into that. I have the trial version of Boom 2 running and it boosts the low sound significantly and gives an on screen volume control when using sound through HDMI.

Screen resolution is 1920 x 1080. Anything higher and everything becomes too small on my Dell 27 inch quad screen so I'll keep it at 1080.

One problem I have noticed is that if I use VGA (playing with the NUC at work and no HDMI connection so have to use VGA) and the unit goes to sleep it will not recover. The monitor stays dark and no mouse or keyboard input will resurrect it. I checked with HDMI and it is OK, it wakes up and LAN is active. VGA requires a shutdown and restart.

Other than that and the speaker crackling (which actually isn't a problem as I use HDMI sound) this little NUC is running fantastically well. Big thanks to Sebinouse and everyone who helped me get this far.


For HDMI audio volume control you can use the (free) trick of post#426.

For Jack audio it depends on what you want to use :
3,5 mm Jack out only : the kext of post#405
3,5 mm Jack in & out : use the kext of post#1 AND the trick with LineIn (see link above for HDMI with this setting : Built-in Input: LineIn PlayThu Silence output)
 

Attachments

  • Capture d’écran 2016-02-24 à 17.20.47.png
    Capture d’écran 2016-02-24 à 17.20.47.png
    18.3 KB · Views: 127
For HDMI audio volume control you can use the (free) trick of post#426.

For Jack audio it depends on what you want to use :
3,5 mm Jack out only : the kext of post#405
3,5 mm Jack in & out : use the kext of post#1 AND the trick with LineIn (see link above for HDMI with this setting : Built-in Input: LineIn PlayThu Silence output)

Sebinouse, thanks again. I read through the whole thread before starting the build, but forgot about that. I'll give its a shot.
 
Hy, lately is quiet here, so let make same noise with an issue that I have.

First, there is anyone here that uses Bluetooth headphones with Azurewave AW-CE123H ?

I use a this clipper http://www.microsoft.com/en/mobile/accessory/bh-121/ and is horrible, it interrupts all over the place, with my phone is SUPER, but with Bluetooth on my NUC is unusable, I use kext made by @rehabman downloaded from his bitbucket link that is uninstalled in S/L/E.

Till now I try to see if I switch antennas between them there is a improvement but with no success.

Any suggestions ?

EDITED

After some search I am inclined to try this combination

1. Mini-PCI-E-to-BCM94360CD-BCM94331CD-Flexible-Adapter-With-Wireless-Antenna

2. BroadCom-BCM94360CS2
I choose this card because his 2 antenna connection instead others cards that have 3 or 4 antenna connectors.

What is you thoughts on this combination ?

I do not use m-SATA connector on my NUC, but I think if I will need that connector with this this will be possible.
 
Last edited:
Thank you very much Sebinouse (and the rest of contributors in this thread) for this great guide.

I've been living and working with my old Mavericks build (courtesy of WonkeyDonkey and Mariolillo -> thanks guys!) for a couple of years with very good results: WonkeyDonkey/Mariolillo's build revealed itself as a rock solid installation on my NUC Haswell 4th gen. (so I skipped Yosemite).

A month ago I decided to migrate to El Capitan encouraged by the good reviews of the OS and the discovery of this nice guide. But since I installed Sebinouse's Build, I've been experiencing random crashes and eventually, a fatal corruption of the file system. Trying to fix it with fsck, Disk Utility and Disk Warrior didn't work, so I erased the volume and installed again (several times) with the same random crashes (and eventual irrecoverable disk corruption). Changed the brand and type of the hard drive (HDD[Toshiba, Samsung] and SSD[KingFast]), removed unused kexts and patches in config.plist (since I don't have a Wifi/BT card I removed: SSDT-WIFI.aml, BrcmPatchRAM2.kext & BrcmFirmwareData.kext, BCM94352 Handoff 10.11 patch & BCM94352 5 GHz patch), but same behaviour arrived.

I've monitorized CPU temperature and fan functioning and seems that crashes are not related to overheating: temperature never exceeded 50ºC/122ºF before chashes.

I've been thinking of patching my own SSDTs and/or create a DSDT (in the WonkeyDonkey style) but I'm quite a noob on this area and after all I'm not sure if this will make any difference... Can somebody indicate me the right procedure or any advice in order to recover some stabillity in my system?

In order to patch my SSDTs, I've already extracted them through Clover-F4 method... I guess MaciASL is what I should use but, which patches should I apply for my NUC Haswell (PJALM, MacMan, RehabMan, Toleda)?

Any other idea?

Thanks in advance


This is my hardware configuration:
Intel® NUC D54250WYKH
BIOS 41
Clover r3320
RAM - 16GB G Skill Intl
HDD - 1TB Samsung
SSD - 128GB King Fast
 
Thank you very much Sebinouse (and the rest of contributors in this thread) for this great guide.

I've been living and working with my old Mavericks build (courtesy of WonkeyDonkey and Mariolillo -> thanks guys!) for a couple of years with very good results: WonkeyDonkey/Mariolillo's build revealed itself as a rock solid installation on my NUC Haswell 4th gen. (so I skipped Yosemite).

A month ago I decided to migrate to El Capitan encouraged by the good reviews of the OS and the discovery of this nice guide. But since I installed Sebinouse's Build, I've been experiencing random crashes and eventually, a fatal corruption of the file system. Trying to fix it with fsck, Disk Utility and Disk Warrior didn't work, so I erased the volume and installed again (several times) with the same random crashes (and eventual irrecoverable disk corruption). Changed the brand and type of the hard drive (HDD[Toshiba, Samsung] and SSD[KingFast]), removed unused kexts and patches in config.plist (since I don't have a Wifi/BT card I removed: SSDT-WIFI.aml, BrcmPatchRAM2.kext & BrcmFirmwareData.kext, BCM94352 Handoff 10.11 patch & BCM94352 5 GHz patch), but same behaviour arrived.

I've monitorized CPU temperature and fan functioning and seems that crashes are not related to overheating: temperature never exceeded 50ºC/122ºF before chashes.

I've been thinking of patching my own SSDTs and/or create a DSDT (in the WonkeyDonkey style) but I'm quite a noob on this area and after all I'm not sure if this will make any difference... Can somebody indicate me the right procedure or any advice in order to recover some stabillity in my system?

In order to patch my SSDTs, I've already extracted them through Clover-F4 method... I guess MaciASL is what I should use but, which patches should I apply for my NUC Haswell (PJALM, MacMan, RehabMan, Toleda)?

Any other idea?

Thanks in advance


This is my hardware configuration:
Intel® NUC D54250WYKH
BIOS 41
Clover r3320
RAM - 16GB G Skill Intl
HDD - 1TB Samsung
SSD - 128GB King Fast

question is good. In this guide only me use DSDT. I have 2 method: 1) only DSDT 2) DSDT + ssdtprgen. I think sebinouse' package is fine but patch DSDT still good than clover patch :D. temperature is less 43ºC.
 
#Sebinouse Can you sleep about 10 minutes after wake and type syslog | grep -i "wake reason" in terminal ? You give me your report. thanks
 
#pure.wisdom Can you please share your DSDT & DSDT+SSDT solutions?
 
Status
Not open for further replies.
Back
Top