I have the boradwell based i3 with the 2.5in HDD option. I have both m2 SSD and a HDD installed along with 4gb of ram.

Anyone else having the issue of when using the two usb ports in the back at the same time, the computer freezes? I had a my wireless MS keyboard/mouse combo and external plugged in and the computer froze on me until I unplugged my external. Same thing with a flash drive. I test this out on both ports in the back same thing. Oddly enough, if I plug in say a my phone, or camera(or possibly any powered usb device), this issue does not occur. Nor does this issue occur if I have the usb stick and usb powered externals both in the back, while the keyboard is in the front usb port(with and without another usb device plugged into the open front usb). It's not a full freeze either as if I press the power button the shut down menu pops up. And all is fixed if i remove the usb driver or relocate the keyboard combo. Any ideas?

BTW: This under gnome Ubuntu 14.10 64bit with the 3.18.8 Thank you.

All drivers I try to install results in errors. I have two devises with exclamation marks:

-SM Bus controller: Exclamation mark

-Unknown unit: Exclamation mark

Why is it not possible to install the drivers pack manually? Why does the automatic driver detection utility fail miserably ??

My NUC seem in general to work ok, but I find it ackward with lots of signals that there is something wrong without being able to detect / remedy.

I am using Intel DE3815TYBE in which i want to access UART1 and UART2 ports available in serial port headers in both windows 7 and also windriver linux. so in windows any drivers require for it ?? and also how can i get the access/COM port for the same uart like ??

I use LogMeIn to access client computers.

Replaced many with the Intel NUC.

Find that the LMI Inventory function does not retrieve any data from the NUC.

It works for other non-NUC computers at the same or other locations.

cs

Frequently from a startup (not restart but from S5), all of my USB ports will not be recognized.  I have a 4GB flash drive as D:, a Seagate external HDD as E: and a 64GB flash as F:, and sometimes the Seagate device does not show up.  I have to restart to get it to show up.  Sometimes one of the other drives will not show up. The Seagate device and the 64GB flash drive are plugged directly into the NUC while the 4GB flash (and a printer) are plugged into a powered USB replicator.  I also have a Logitech receiver plugged into a USB extension plugged directly into the NUC to keep it out of the way of the electromagnetic radiation, as discussed in Intel's white paper on the matter.  My OS is W7HP 64-bit and my BIOS is the January 15, 2015 version.

Do I have a defective NUC?  This is a fairly replicable occurrence, although I'm not sure it occurs 100% of the time since I only power down the NUC for OS updates and such.

After days of struggling this is how I came up with a functioning solution of a headless ubuntu server 14.04.2 on a NUC DN2820FYK.

Hope this saves some pain to someone

1. BIOS

This is where the big problems are because not every intel bios supports headless boot, with some bios it won't boot if there is no video attached. I have not tested every bios but I can tell you that the version 0034 is working while the 0048 (the last available now) is not. If you have tested other bios write it in the comment, so I can update the list.

WORKING BIOS

0034

NOT WORKING BIOS

0048

So the first thing to do is to upgrade or downgrade the bios to a working version.

Download it from here:

http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProdId=3782

Here is the procedures, I personally used the F7 BIOS Flash update

http://www.intel.com/support/motherboards/desktop/sb/CS-034499.htm

Important note: If the standard procedure doesn't work (as in my case downgrading from 0048 to 0034) you have to do a BIOS Recovery Update

http://www.intel.com/support/motherboards/desktop/sb/CS-034524.htm

If you have problem booting after the bios upgrade, clear the CMOS

http://www.intel.com/support/motherboards/desktop/sb/CS-034634.htm

2. BIOS SETUP

Enter the bios setup with F2 and first of all load the default configuration with F9

In the boot configuration DISABLE UEFI BOOT and ENABLE LEGACY BOOT

Other default settings left unchanged.

3. LINUX INSTALLATION

Nothing special about the linux installation, it will create 2 partitions (ext and swap) and not 3 as with EFI boot.

The only strange thing was during the installation of grub because by default it is installed on /dev/sda but during the installation that was the usb key I was installing from so I manually had to change the path to /dev/sdb which was the hard disk.

Hope this helps!

I have a DE3815TYKHE with the latest v41 BIOS update.  I installed Debian 7.6 to the internal drive without any GUI.  This is a command line only installation.

Everything works fine when I have a monitor connected via either the HDMI port or the VGA header.  However, when I attempt to boot without a monitor attached the system, it just hangs.

Is anyone running the DE3815TYKHE with Debian or Ubuntu Server (with no GUI) headless?

Is there a setting that I am missing in the BIOS that removes the requirement of a connected monitor (or EDID reply) in order to boot?

Cheers!

Hello,

I have a DE3815TYBE updated to the 7/10/14 bios.  I've installed Debian 7.6 to the internal drive and everything works fine when I have a monitor connected via either the HDMI port or the VGA header.

When I attempt to boot without a monitor attached however the system just hangs.  I've tried to log via netconsole and it doesn't even get that far.  If I boot with the monitor connected then disconnect it after everything is loaded the system runs just fine.

I've tried a variety of kernel parameters and nothing seems to help.

To Intel:  Does the NUC require a connected monitor (or EDID reply) in order to boot?

Is anyone else running Debian headless?

Thank you.

Has anybody success with a headless nuc DE3815 with Linux?

regards

gillib

Turns out turning off n-key rollover (NKRO) on my Ducky keyboard finally allowed me to get into the BIOS setup on my DE3815TYKHE. With NKRO on, F2 (and F7, but not F10) was being ignored during the boot sequence.

I can find no mention of this particular issue on the forum so maybe this post will save someone a few hours of troubleshooting.

Hi

I have just bought my first Intel NUC the NUC5I3RYK to be specific. But i have unfortunately found out that the ir receiver aren't working out of the box. I have tried with Openelec 5.0.

I have tried updating the firmware and tried the following fix that seemed to work on haswell NUC but without any luck.

Re: Haswell NUC CIR receiver (ACPI issue?)

when I ssh into my NUC and type the dmesg i get the following text:

[ 3016.364580] nuvoton-cir 00:01: [io 0x03e0-0x03e7]

[ 3016.364625] nuvoton-cir 00:01: [irq 10]

[ 3016.364628] nuvoton-cir 00:01: [io 0x03f0-0x03f7]

[ 3016.365146] nuvoton-cir 00:01: activated

[ 3016.365149] nuvoton-cir 00:01: IR PNP Port not valid!

[ 3016.365276] nuvoton-cir 00:01: disabled

does anybody have a solution for this? then it would be much appreciated.

I installed Windows XP SP3 in D54250WYK.

I could install almost drivers excepted the Display Driver.

I installed XP Haswell Graphic driver 6.14.10.5441 and 6.14.10.5445, but it shows BSoD after reboot.

STOP: 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA

Could anyone help me?

I currently have BIOS Update [WYLPT10H.86A] WY0035.BIO installed on my NUC D54250WYK.

The unit has a "Crucial CT256M550SSD3 256GB M550 mSATA Internal SSD" and 1x "Crucial CT102464BF160B 8GB DDR3 PC3-12800 Unbuffered NON-ECC 1.35V 1024Meg x 64" which I believe are both on your supported hardware list (or at least the "this might work" hardware list). I'm currently getting a Error 500 when trying to access the tech docs at http://www.intel.com/p/en_US/support/category/dsktpboards/dk-d54250wyk/doc_guide so I can't confirm that.

I installed OpenBSD in a very standard way, but something that the installer has done has left my NUC unbootable as long as the mSATA drive is still inserted into its slot. It remains, as far as I can tell indefinitely, on the "Intel NUC" power-on/post screen (the screen with the F2, F7, F10 options in the lower right). No keyboard actions seem to get me further than this.

If I remove the mSATA drive I can choose the F? options and get into the UEFI/BIOS settings. After this the thing can boot from USB or network just fine, just not while the mSATA drive is inserted.

This is a recurrence of a problem I had earlier with another OpenBSD install. I had solved the earlier issue with a UEFI/BIOS upgrade (from 22 -> 35) and was able to boot from the mSATA. I have now reset the UEFI/BIOS to factory defaults (but I'm still on BIOS 35) and I'm still unable to boot.

I have a couple of questions:

a. Presumably the only thing the OpenBSD installer has done is perhaps write some dubious data or MBR to the mSATA. Why would this prevent the NUC from at least being able to boot into the UEFI/BIOS config screen or boot from some other medium?

b. Is there a way I can re-flash BIOS 35 (or a newer one) and fix the issue?

UPDATE: I tried reflashing both BIOS 35 and 33 and I have the same problem. I also set the hard disk detection delay in the Devices -> SATA section to 10 seconds to see I could somehow select another boot medium before it tried to detect the mSATA but still same issue.

This is a posting for others seeking confirmation. When trying to upgrade my DC3217IYE to Wifi AC using the 7260.HMWG.R on a Linux Mint distro, the unit freezes repeatedly.

If I revert to the previously installed Ultimate-N 6300 (rev 3e) the unit performs normally. Additional info:

BIOS: v. 0055

NUC: DC3217IYE

Linux Kernel: all tested, including 3.16.0-29

I thought I would summarize approx. 2 weeks of experience with a new NUC5i5RYH is case it helps others.

The unboxing was uneventful as was the installation of 4GB of Crucial RAM and an old Intel X25-M 2.5inch 80GB SSD. New users would be well advised to purchase only the Intel recommended RAM:

Intel® NUC Boards and Kits — System Memory

Next, I used a USB DVD drive to install Windows 7 Pro SP1. This was easy enough although you'll want to grab the Intel Driver Bundle to get network support:

Intel® Download Center

After finishing Windows Update everything seemed okay.

I wasn't really interested in running Windows but I imaged the system drive so I could slam that back at a later date for testing, curiosity or whatever.

Next, I moved on to Linux and specifically Lubuntu 14.10. This didn't go so well. Most of the stable Linux releases are not yet ready for prime time of the 5th Gen NUC. Looks like a lot of issues with the X-server and HD6000 graphics. It seems that you'll need at least a 3.18 kernel but that alone is probably not sufficient. I wasn't able to make any flavor of Mint 17 to work fully, even with the 3.19 kernel. You can get it to run with "nosetmode xforcevesa" but that uses software rendering for all the graphics.

However, the good news is that the Lubuntu (and Xubuntu) 15.04 betas work just fine. Installation is a breeze!

Working off that base, I've largely succeeded in building the HTPC of my dreams based on Kodi. However, I still have two outstanding technical issues:

1. The infra-red sensor (CIR) makes the Intel NUC very attractive for HTPC applications. However, the CIR does not appear to work at all with Linux on the Broadwell NUC's. The workarounds that helped 4th Gen NUC owners do not work on the Broadwell devices. Intel say the CIR works with Windows (I haven't verified). Fingers have been pointed at the Linux kernel although I'm more inclined to believe the BIOS has an ACPI compliance issue. Intel appear to acknowledge the problem and maybe they're looking at it. But they're certainly not making any bold promises of a fix.

Meanwhile, I went and splashed $20 on a FLIRC:

http://www.amazon.com/FLIRC-Dongle-Media-Centre-Raspberry/dp/B00BB0ETW8

And this works pretty much perfectly. I'm really quite impressed and for any impatient folks out there, I highly recommend it. I even have my IR remote powering on the NUC from the S5 state.

2. My NUC will randomly power itself on from the S5 (off) state after two or three hours, even in the middle of the night, or with nobody in the house. I have tried numerous things including BIOS settings to:

* Disable WoL

* Disable wake on RTC

* Disable wake on IR

* Disable PCIe ASPM

Again, I suspect a BIOS issue although I can't rule out the possibility that this problem is specific to my sample. So I'm agonizing over whether to RMA this unit.

I wanted to love my new NUC, but overall, I'm a little disappointed. The CIR and random power-on issues are quite irritating. I'm also less than thrilled with Intel's stance on Linux support. I think it's a little disingenuous to advertize, market and promote "Linux compatibility" but then deny all support obligations at the first hint of a problem.

Right now, I'll give the 5th Gen NUC a C+. Fixing the CIR and random power on will raise the grade quite a bit. And if new stable Linux distros work well out-of-the-box with the HD6000 graphics an A grade is still achievable by the late spring or early summer. Fingers crossed....

greetings, I just set up a new NUC5i5RYK.  I boot the live CD (off a USB stick) for Ubuntu 14.10 and it comes up fine, except the video does not refresh inside new windows I open up.  if I right click on the background the menu is either color noise or just blank.  if I open up system settings there are no icons until I roll over them.  if I try and install, the options to pick languange and whatnot just don't display.  the window us just blank grey inside.

this is true whether I connect via Display Port or HDMI.

this is true with Linux Mint 17.1 (Rebecca) as well.

I assume that installing the Intel graphics drivers will fix the issue, but I can't get that far because even the terminal is unreadable.

any ideas how to get around this?

I just picked up a NUC5i5RYK and Crucial 4x2 GB (CT51264BF160BJ) memory. As soon as I installed both sticks of ram and tried to power on the NUC, I got three flashing lights indicating memory issue. After much trial and error, it turned out the NUC didn't like anytime I plugged anything into the top memory slot. However both sticks of RAM works individually when plugged into the bottom slot. Still don't know why this would be the case. However, it turned out a different set of Crucial 4x2 GB ram (BLS2K4G3N169ES4) works just fine on both slots, which I borrowed for a friend. Still don't know why the first set of ram didn't work, since it used to work just fine on previous generation i5 NUC boxes.

Anyway, after getting the system up and running (Windows 7 Professional 64 bit) and installing the latest driver bundle RYH-RYK-Win7-64bit-Driver-Bundle-Mar2015.zip  I thought everything was good to go...until I tried to play a video from youtube (through chrome). The CPU usage hit almost 100% trying to play a 1080p video, and trying to play 4k content was out of the question. I was barely getting 10-15 fps and needless to say, the video was unwatchable. Seeing this, I tried to play some local content from the ssd, and the results were identical. My 7 year old thinkpad handles video better than this. It's as if the GPU was doing nothing, while the CPU was trying to render the video. Intel claims that HD6000 graphics can handle 4k content, but I would beg to differ based on my experience. Even opening 2-3 chrome tabs each playing 720p videos caused the CPU usage to reach almost 100%. I don't know if this strange system behavior is some sort of driver problem, or related to the RAM issue I first observed (although, this is repeatable regardless of which RAM i used), or something is actually wrong with the box. Any help from anyone about this would be much appreciated. Would be interested to know if others also ran into similar issues.

On a related note, one of my friends also bought the exact same combination (NUC5i5RYK and Crucial 4x2 GB CT51264BF160BJ ram) and his system completely failed to boot with the exact same 3 flashing light memory error.

Can anyone provide the URL for the previous graphics drivers as I have updated to the latest and now have a problem when I exit Kodi, my screen flickers and goes all weird. Device manager doen't have the option to roll back to previous driver.

Windows 8.1 x64

Thanks

Hello Intel community

I'm writing to share my experience with NUC'S.

My first NUC was D34010WYK, I mounted additionally following components on it:

Crucial mSSD 120 GB

Samsung RAM 2x4GB

Intel 2777324 dual adapter (Bluetooth, WLAN)

After mounting the HW and updating the BIOS to latest revision I installed Ubuntu 14.10 on it. It's was really easy.

Ubuntu was booting in secure mode, which is default in BIOS.

While using the NUC for approximately 3 Weeks I only noticed sporadic freezes while watching Soccer over Sopcast links with VLC player. During the freeze audio was continuing to play, however video was freezed and controlling of NUC wasn't possible, only hard reset over power button helped.

At the end of the third week at some point the NUC didn't wake up anymore from suspend mode. The power button was blinking with ca. 0.25 Hz frequency.

After pulling the power cable it stopped blinking but also stopped working.

I couldn't power on the NUC again, it was dead, unfortunately.

Amazon returned me the money for defect NUC and I ordered a new one, this time D54250WYK.

Guess what, after approximately 3 weeks of usage this one died the same way the first one died!

I think there is something wrong with NUC's and Linux suspend mode in general.

Does anyone know a workaround for this issue?

My first ideas were:

Switch in BIOS to Legacy boot (Not using secure boot)

Disable suspend mode, but this isn't the way I want to use the NUC.

Is Intel aware of this problem?

I think it can be reproduced very quickly ...

This issue reminds me about Samsung Notebooks, which were also killed by Linux due to some bugs in their BIOS/EFI FW.

Thanks

Hi. I'm trying to power up my BOXNUC5I5RYK, I've installed 2X 1.35v Crucial RAM and a Kingston M.2 SSD. I've plugged in the power with the PSU that came with it.

I pressed the button on the top of the unit. It did nothing. I held the button down. It did nothing. The button has a definite click when pressed which suggests I'm pressing it properly.

The wall socket is confirmed working.

I tried unplugging the PSU and from the NUC and back in again.

I tried removing the RAM completely.

Neither helped.

Would I expect to see an LED light up as soon as I pressed the button?

edit: just seen on a video that the power button CONTAINS a blue LED. This does not light up on mine. Can I assume it needs to be sent back to the reseller?