Contribute
Register

Install Guide : Intel Haswell NUC Core i5 (D54250WYK) V4 (Yosemite 10.10.4)

Status
Not open for further replies.
Thanks for the response, WD.

Nope, nothing worked to get me into BIOS without the USB key. When I enabled BIOS auto-load, I could get in.

Before loading OS X... when I had Linux Mint, BIOS was all default. I just remembered, though, that to get the Unibeast USB key to boot before the initial install of OS X, I had to disable UEFI in the BIOS. Afterwards, I re-enabled UEFI. This is probably my issue. No idea how to fix it, though.

No adapters for the monitor. I have a straight mini DP to DP cable.
 
Thanks for the response, WD.

Nope, nothing worked to get me into BIOS without the USB key. When I enabled BIOS auto-load, I could get in.

Before loading OS X... when I had Linux Mint, BIOS was all default. I just remembered, though, that to get the Unibeast USB key to boot before the initial install of OS X, I had to disable UEFI in the BIOS. Afterwards, I re-enabled UEFI. This is probably my issue. No idea how to fix it, though.

No adapters for the monitor. I have a straight mini DP to DP cable.

Ahh I misread. I thought you had said DP to HDMI. No issue for that then unless its a really cheap nasty cable. Ive seen some cases of those not working.

There is a section in the technical guide that explains how to reset the bios. Its included in the Install Pack. You will need a USB key, formatted to FAT32, with the latest bios file (.bio). With the jumper moved to the right position, it will fully restore the bios using the update file on the key and reset it.
 
Ahh I misread. I thought you had said DP to HDMI. No issue for that then unless its a really cheap nasty cable. Ive seen some cases of those not working.

There is a section in the technical guide that explains how to reset the bios. Its included in the Install Pack. You will need a USB key, formatted to FAT32, with the latest bios file (.bio). With the jumper moved to the right position, it will fully restore the bios using the update file on the key and reset it.

Thanks WD. I went down a crazy unnecessary rabbit hole this afternoon but I learned a lot about the NUC... and myself.

I messed around in BIOS some and stupidly enabled Fast Boot, which totally screwed me over. I couldn't get into BIOS. So I pulled the jumper and reflashed BIOS, only to be met with in the inability to get back into BIOS via F2 or F10. I found out that this is due to my monitor.

So my monitor problems are a known issue with Intel NUCs. It seems that when the NUC is connected to some monitors that are above a 1024x768 resolution, you may have difficulty getting into BIOS (per what I read on Intel's forums). My monitor is an LG Ultrawide; it's a totally messed up crazy resolution at 2560x1080. I was able in the past to get into BIOS but it felt very random and sporadic. I couldn't replicate it. Sometimes I could get in, sometimes I couldn't. After my reflash I couldn't get in at all.

My monitor has a feature called PBP (picture-by-picture) which allows for two machines to simultaneously be plugged in and both get displayed, giving me essentially two 1280x1080 screens on the same monitor. Switching to this configuration worked the first time... I was able to get into BIOS.

Once in to a totally refreshed BIOS I enabled a host of stuff to save my ass... boot to USB first, always prompt for a BIOS boot. Also, I figured out that my EFI boot weirdness was due to a setting I must have enabled in my idiocy... Boot > Boot Config > Boot Devices > Internal UEFI Shell ... I had that enabled and that's what was giving me the EFI shell boot issue. Disabling that, the NUC boots directly to Chimera.

Also, for anybody with a monitor resolution problem that makes it difficult to enter BIOS, I find enabling the "always boot BIOS first" switch does the trick. I can reliably get into BIOS now.

So my only other issue is with Bluetooth which, at the end of the day, is so minor that it doesn't even matter. I'm leaning toward my messed up secondary antenna as the culprit and I'll probably just pick up a USB BT receiver dongle to work it out. I love the Apple Magic Trackpad, such a pleasure to use, so I don't think I can stick with the standard USB mouse for too long.

What did I learn about myself, you might ask? I am so grateful that I no longer do this for a living. I've spent a lot of time troubleshooting this NUC/OSx86 project and it has been so much fun (frustrating but rewarding). Were I still doing IT as a career, I would have never even attempted this and I sure as hell wouldn't have spent so much of my free time troubleshooting something so inconsequential. I'm glad to recognize that my passion for computers is returning after a long slog of doing it professionally!
 
Thanks WD. I went down a crazy unnecessary rabbit hole this afternoon but I learned a lot about the NUC... and myself.

I messed around in BIOS some and stupidly enabled Fast Boot, which totally screwed me over. I couldn't get into BIOS. So I pulled the jumper and reflashed BIOS, only to be met with in the inability to get back into BIOS via F2 or F10. I found out that this is due to my monitor.

So my monitor problems are a known issue with Intel NUCs. It seems that when the NUC is connected to some monitors that are above a 1024x768 resolution, you may have difficulty getting into BIOS (per what I read on Intel's forums). My monitor is an LG Ultrawide; it's a totally messed up crazy resolution at 2560x1080. I was able in the past to get into BIOS but it felt very random and sporadic. I couldn't replicate it. Sometimes I could get in, sometimes I couldn't. After my reflash I couldn't get in at all.

My monitor has a feature called PBP (picture-by-picture) which allows for two machines to simultaneously be plugged in and both get displayed, giving me essentially two 1280x1080 screens on the same monitor. Switching to this configuration worked the first time... I was able to get into BIOS.

Once in to a totally refreshed BIOS I enabled a host of stuff to save my ass... boot to USB first, always prompt for a BIOS boot. Also, I figured out that my EFI boot weirdness was due to a setting I must have enabled in my idiocy... Boot > Boot Config > Boot Devices > Internal UEFI Shell ... I had that enabled and that's what was giving me the EFI shell boot issue. Disabling that, the NUC boots directly to Chimera.

Also, for anybody with a monitor resolution problem that makes it difficult to enter BIOS, I find enabling the "always boot BIOS first" switch does the trick. I can reliably get into BIOS now.

So my only other issue is with Bluetooth which, at the end of the day, is so minor that it doesn't even matter. I'm leaning toward my messed up secondary antenna as the culprit and I'll probably just pick up a USB BT receiver dongle to work it out. I love the Apple Magic Trackpad, such a pleasure to use, so I don't think I can stick with the standard USB mouse for too long.

What did I learn about myself, you might ask? I am so grateful that I no longer do this for a living. I've spent a lot of time troubleshooting this NUC/OSx86 project and it has been so much fun (frustrating but rewarding). Were I still doing IT as a career, I would have never even attempted this and I sure as hell wouldn't have spent so much of my free time troubleshooting something so inconsequential. I'm glad to recognize that my passion for computers is returning after a long slog of doing it professionally!

The latest version 40 bios here seems to show up in a smaller view window with my screen. That is a change I noticed from previous, but it still works for me.

While it might seem a bit boring, go to the Install Pack and look at the bios screenshots. It shows you every setting of every bios page to get an optimal setup. I've produced these following extensive testing at my end, so the hard work is done for you.

Your bluetooth issue is a different monster. You dont mention which bluetooth chip you have. These can be very picky to get working in OSX, and if bluetooth is a must, you would be wise to consider an external USB bluetooth dongle. Loads of these are documented in the forums. I wont recommend one personally since I dont use bluetooth here.

Finally, you should change your screen resolution in org.chameleon.boot.plist to match that of your monitor "2560x1080x32" in your case. And if you look closely in your theme folder (Located in /Extra) you will find one or more sections in there where you can define the screen setting as well. Between these 2, it should give a nice balanced appearance when going through the boot process.

:thumbup:
 
Followed the guide carefully and everything works except for my network. The NUC network connection lights are all lit up but in Mac OS is says cable is disconnected. What extra info/diagnostics can I provide? Any suggestions for resolving?

Note - The network was working fine through all steps up until I reboot direct from SSD without any boot flags
 
Followed the guide carefully and everything works except for my network. The NUC network connection lights are all lit up but in Mac OS is says cable is disconnected. What extra info/diagnostics can I provide? Any suggestions for resolving?

I would double check the connection at the other end of the cable and make sure it is configured properly.
 
It is. As I said, network worked fine with the '-v UseKernelCache=No' boot flags but when I boot without them I have no network. The guide stated that the flags were only needed once and then not again.
 
It is. As I said, network worked fine with the '-v UseKernelCache=No' boot flags but when I boot without them I have no network. The guide stated that the flags were only needed once and then not again.

You may like to try a different version of the ethernet kext from Multibeast. I've seen reports before of this happening on the Intel ethernet. I think the resolution was to back down to an older version, but I dont remember which.
 
Status
Not open for further replies.
Back
Top