Search results

Aaaaand it works! Around page 8, (I can't find the specific post again) someone posted that 2 monitors works if you boot with one and connect the second later, but you may have to do it in a specific order. Here's what works for me: Boot to desktop with only one monitor connected to HDMI...

Worked perfectly on my NUC7i7. Documented nonworking features are definitely not working (multiple displays) but I'm working through all the posts to see if anyone has tried to address this. I'll try what I can and let anyone know if there's progress as dual monitors are a very nice thing.

Thanks, napoleonn! I'll try that this evening. That's a great workaround!

I got the same sign a couple of times but then after another restart, the setup continued properly. Now that I think about it, I changed to another USB drive and built the Installer again before it worked.

Maybe I'll try 0x19260004 as I'm having a problem with the NUC6i5SYH video going blank after the monitor is turned off or switching inputs on my monitor (hooked to the NUC w/HDMI). The NUC does show the video for a few seconds to many minutes after the video switch or turning the monitor off...

FYI, I updated my NUC6i5 to 10.11.6 via the App Store and it worked with no problems. Previously I made the 3D Graphics enabling change suggested by iwasready, "change the ig-platform-id to 0x19260002 and reboot" which worked great as that's a role for this machine.

Updating a NUC6i5 and NUC5i7 to 10.11.6 via the App Store worked fine for me, no problems.

I just updated from 10.11.5 to 10.11.6 via the App Store on my 5i7 and all went well. TRIM still enabled as others have said.

The 10.11.5 update went fine on my NUC5i7RYH. I never did the 10.11.4 update on my NUC5i5 so I assume when I go to 10.11.5, I'll have to do the CsrActiveConfig change from 0x3 to 0x67 as my i7 is currently set that way. If I ever do the update, I'll chime in on how the direct .3 - .5 update...

Thanks for the info, _mikey! I'm currently saving my pennies for the Skull Canyon NUC but your initial success has encouraged me to, ah, bend the rules ASAP. I hope to join you soon!

I'd like to clarify something here. I'm using "HDMI out" for audio through the MiniDisplayport output and reported it as "HDMI out" because this is how it's described by the OS. I assume if I hook up through the HDMI output, it will also describe it the same way (maybe as "HDMI out 2"). The...

Hi emmetbrown, Sorry for the delay, I'm using the non-curved LG 34UM95 with the Broadwell NUC5I7RYH hooked up with an MD-MD cable. The full 3440x1440 resolution is available at the monitor's 60Hz default refresh rate. My NUC5I5RYH behaves the same. The monitor will to 3440x1440 at 50Hz...

I have the same issue but haven't spent the time to troubleshoot the permanent fix yet. One thing which helps without logging out or restarting is to switch the audio output to HDMI or another and then back. However, this doesn't work every time and in fact I've just switched to using the HDMI...

After reading the initial issues upgrading to 10.11.4, I sat tight but finally followed the advice in post #574 and changed CsrActiveConfig from 0x3 to 0x67 prior to updating NUC #1 to 10.11.4 and everything worked perfectly. Now for NUC #2… Thanks ammulder and the rest of the community!

Awesome! I bought the original 2011 quad core Mini for that feature and traded up to a 2012 after those became available. Wait for 2 years and when the 2014 dual core-only Minis came out I quickly snatched up another quad 2012 from the refurb store the first day those became available with the...

I can enable 2560x1440 at 50Hz through mini-HDMI on an LG Ultrawide (3440x1440 native) using the SwitchResX System Preference on a NUCi7RYH. It does 2560x1440 at 60Hz through mini-Displayport. For those interested, those same refresh rates are available at this monitor's full 3440 pixel width...

Thanks to everyone who has contributed to making this work with the Broadwell NUCs, especially ammulder! :clap::clap: I had 10.11.1 working on a NUC5i7RYH and updated to 10.11.2 without major incident though sound failed the first time I tried it (working OK now). I didn't test Ethernet after...