My NUC5i5RYH is connected to a Benq 27" QHD monitor GW2765 via mini DP - DP cable. Running W10.

Issue: When waking up a black screen from sleep within relatively short time after going into sleep mode (5-10 minutes), there are mostly no problem. When longer time one of two things happen, 1) either the screen shows up as desktop and icons but without the windows, or 2) the screen is completely black.

I am - most of the times - able to solve issue 1) simply by pressing the on/off button on the monitor, first off and then on. Sometimes I need to unplug the DP cable for the NUC and re-insert

Issue 2) requires that I physically removes the power cable from the monitor, waits until the led light has gone out completely, and then re-inserts the power cable.

Have tried to ask Benq support, and they do not know this issue, but has offered to bring the screen to their lab under warranty. However, I suspect this is an issue with the NUC's port, so sending it to Benq will probably not solve anything (my colleage with the exact same NUC and exact same monitor has the exact same problem)

Anyone's got an idea how to solve this? Due to the amount of unplugging and plugging (20-30 times a day) I am fearing that over time the ports will be destroyed or eventually some voltage issue might occur and damage either the NUC or the monitor.

Hello,

I'm trying to install a Linux operating system on this NUC kit.

I have tried with CentOS 7 and almost all is ok but the video smoothness.

I'm using mate desktop to keep minimal impact but sometime I see sluggish and freezes.

Also I'm not able to play videos (only with option "-vo x11" but in this way without full screen)

I'm going to try with fedora 23 too and compare.

Is there any hint? Also in relation with bios video parameters?

By default I see this

IGD minimum memory 32mb

IGD aperture size 256mb

IGD primary video port auto

Do they influence behavior of OS video?

One note: I'm using a monitor that is connected through vga port and using 1280x1024 resolution, so not an extreme one...

BTW: I already updated to latest bios version 0047.

Thanks in advance,

Gianluca

Dear Intel community,

I am an happy owner of a NUC Intel NUC DN2820FYKH, yesterday I started playing around with various OS. I had before Ubuntu + Kodi on startup. Then I formatted and installed Kodibuntu. Then, I wanted to install Openelec. I stopped there, because various messages started to appear while I was booting from the USB, now it appears on a black screen:

"Reboot and select proper boot device"

I made the USB with my Mac using Unetbootin. Before yesterday, I successfully installed Ubuntu, Kodibuntu with USBs (2.0 or 3.0) made with my MacBook (El Capitan) both with the front USB or the back USBs, without success. Seems that something went wrong with the bios after inserting the Openelec USB, because before this attempt there weren't problem with the boot from USB. Tried UEFI, Legacy, both. Tried bios update, bios downgrade, bios reset, bios reset with F9, bios reset by moving the PIN from the motherboard (strange here that if I move the pin from 1-2 to 2-3 and I boot, it doesn't go to the recovery bios mode, but directly boots from SSD the current OS, which is Kodibuntu, the latest one I managed to install before this issue).

Right now I can use Kodibuntu, but I can't format nor install any new OS. Very annoying.

Are there any differences in hardware between these two?

In addition, how can I identify which of these boards I got?

Fiddling with the BIOS it says "D54250WY". What does it mean?

Thanks!

I asked this question in another thread but did not get any replies so I figured I would try here.

Does anyone else own a NUC5i7RYH whose fans hit max RPM during even minor computing, like web browsing or even if Windows update is installing something in the background?  6000+ rpm is as loud as a hair dryer and is disappointing considering I do not use this NUC for gaming or any intensive applications.

I have underclocked my CPU (in Windows 10 power management - set max frequency to 80%).  I think this disabled turbo boost as well.  So far there haven't been any fan outbursts, but if this doesn't solve the problem then I may attempt undervolting the CPU to control heat.  Has anyone had to do this or found any success with it?

Thank you!

I have the BOXD54250WYK1 NUC running Windows 10 (previously Win8) and it's been great.  For years now I have streamed h.264 and 1080 video across my cat 6e network from my NAS with no issues at all.  However, I've noticed that it is a little sluggish with h.265, and downright unwatchable with 4k video.  The 4k video plays, but is in slow motion and displaying visual flaws all over the place.

Is there a NUC built for 4k?  I love my NUC.  Would love to stay with the line of products, but 4k is becoming more mainstream and I need my device to be able to play it.  Any talk about the NUCs and 4k is welcome by me.

Thanks for your time.

I'm running openelec but I have concerns about my NUC's BIOS.

Originally has Win-8.1 installed but I was finding it too hard to get the Xbox One media remote to work on it so I moved to OpenElec to et the advertised 'out-of-the-box' functionality with this particular remote. There was a BIOS issue when trying to get wake-from-s5 and power-off functionality working from my remote, but other functionality worked. At some point I was seeing very laggy behaviour (>5s) with the remote, and I'm not sure how but at one point the remote stopped working altogether. I've been trying to find any IR signals using evtest, irw and ir-keytable -t, but no events appear like they used to. I've tried various protocols (NEC, RC-6, LIRC) to no avail. I've got an autostart.sh that is successfully reloading the driver for the IR sensor (for no particular reason):

#!/bin/sh
modprobe -r ite-cir
echo "auto" > “/sys/bus/acpi/devices/NTN0530:00/physical_node/resources”
modprobe ite-cir

Looking at output of dmesg shows driver is being loaded accordingly.

This is the DN2820FYKH NUC which has the ITE8713 IR transceiver running the driver 'ite_cir', and not the nuvoton driver for the NTN0530. Tried disabling and re-enabling CIR from BIOS. Tried resetting openelec back to defaults and expected to have the functionality I once had return.

Any advice would be very appreciated.

I have had NUC5i5RYK for about 2 months.  Running windows7.  On several occasions on start up I would have no HDMI out.  A restart of the computer and all would work.  Today, nothing will result in any HDMI output.  I downloaded drivers again and reinstalled but still nothing on hdmi.  Any suggestions on what else I might try.  Thanks.

Roger 

System is D34010WYKH, Intel SSD, win7.1

I have been making system images for a year and a half now, feeling great every time I get something to work. For the first time yesterday, I tried to reload a system image. Followed the instructions and got to the Windows screen asking for "keyboard language". I tried typing, nothing; mousing, nothing. checked and keyboard lights are off and mouse light is off. WTH...??? Searched all over the web; yes its been seen before but no answers. Tried all the different boots. Nothing. Started taking note of USB3 vs USB2 issues and win7 not being USB3 ready. Sooooo... if NUC is USB3 and win7 is not, then am I working into the wind? Surely some NUC owner has tried to restore a win7 produced system image? I checked the forum and nothing came up.

PS not to confuse by working a thread into a thread, I also tried hooking up a second monitor, prime on VGA and second on DP to HDMI). Failed first time and the forums were of the opinion that you should avoid going through an adapter as they do not all work. So thanks to the great return policy on the local large electronics supermarket, I got a monitor with DP input. It worked out of the box and NUC took care of all settings without my intervention. Also the monitor (DELL 27") is the very easiest I ever had to assemble.

Hi,

I got a NUC5i3RYH with 16GB DDR3 Ram and an Samsung EVO 850 SSD Drive with M.2 port.

Unfortunately it does not boot from the internal drive ...

I tried the following steps:

- Boot Linux Mint 17.3 from an USB stick ( copied .iso file to it with dd ) 

-> only legacy boot is possible, I was not able to get the stick booted with uefi ...???

- Install Linux Mint on SSD drive ( /dev/sda )

- Reboot

-> No boot drive found

In the BIOS only the USB stick is shown as bootable device

I tried also:

- update BIOS to newest version (.352)

- Install a  harddisk in the 2.5 inch bay and install Linux Mint on this drive -> also does not boot

Resume: Both devices are recognised by the BIOS ( the are listed in the SATA section) but no internal drive does show up in the BIOS as bootable device

Any Idea?

Thanks in advance for your help

Helmut

Dear Intelistas,

I have an Intel NUC5i5RYH (rebadged as a System76 Meerkat), which was delivered on 14 Oct 2015, with Intel BIOS v.0249 in firmware, and it booted from its M.2 SSD [1] into pre-installed Ubuntu 15.04 in around 15 seconds.

My NUC has now been bricked by the well-known 'Ubuntu Suspend > Dead NUC' problem [2] fivesix* times (in 54 58 days of usage), about which many threads exist here at communities.intel.com (dating back at least a year) – and here is a list of what steps I've taken from those threads as potential fixes and implemented on my NUC, but all to no avail:

• upgrading the BIOS firmware: neither Intel BIOS v.0350 nor v.0352 (nor System76 BIOS v.0350) eliminate the 'Ubuntu Suspend > Dead NUC' problem – and upgrading has slowed down its boot time from ~15 seconds to ~2 minutes <sigh>
• mikec_intel's BIOS settings fix [3] does not eliminate the 'Ubuntu Suspend > Dead NUC' problem
• prigaux's 'echo 0 > /sys/power/pm_async' fix [4] does not eliminate the 'Ubuntu Suspend > Dead NUC' problem

For now, the only effective way to avoid getting my NUC bricked for a sixthseventh time would seem to be the major inconvenience of avoiding using the Ubuntu Suspend function altogether; and I'd be very grateful if anybody could recommend a way to get my NUC back to booting up in ~15 seconds, as it did when new (and as might be expected from a motherboard-bound SSD boot drive).

Has Intel really failed completely to address this 'Ubuntu Suspend > Dead NUC' problem?

Or is there yet another potential fix to the 'Ubuntu Suspend > Dead NUC' problem I should try?

Thanks in advance for your attention and help.

Yours in frustration and disappointment,

Tim Jones

__________________________________________________________________

* UPDATES are in red: My NUC has now been bricked by the well-known 'Ubuntu Suspend > Dead NUC' problem SIX times (in 58 days of usage).

[1] Its M.2 SSD: "M.2 SATA: Samsung SSD 850 EVO M.2 250GB : PART 0 : Boot Drive"

[2] The well-known 'Ubuntu Suspend > Dead NUC' problem:

• Mean time between failures: 9.7 days (6 failures in 58 days use, in my personal experience)  10.8 days (5 failures in 54 days of use, in my personal experience)
• Symptoms #1: each use of the Ubuntu Suspend function carries a small but real risk of bricking the NUC. When Ubuntu Suspend is used and works normally, the NUC goes into sleep mode, and the Power button LED winks amber. When the 'Ubuntu Suspend > Dead NUC' problem occurs, these are the symptoms which afflict sleep mode:
  • a short press on the Power button does not wake the NUC (as it ought to, and usually does) – the amber winking just continues; and
  • a long press on the Power button does not switch the NUC off (as it ought to, and usually does) – the amber winking just continues.
• Symptoms #2: the only way to get the NUC to power off is by disconnecting the power cable. After the power cable is reconnected:
  • a short press on the Power button does not switch the NUC on (as it ought to, and usually does) – the NUC is bricked; and
  • a long press on the Power button does not start the NUC up in Power Button Menu mode (as it ought to, and usually does) – the NUC is bricked.
• Workaround: to get my NUC to work again, I have to fully disassemble the NUC, disconnect and reconnect the CMOS battery from the motherboard, and reassemble the NUC.
• Users of Linux distributions other than Ubuntu (eg: Arch Linux, Fedora) have also reported experiencing this NUC bricking on using Suspend, so it could be described more inclusively as the 'Linux Suspend > Dead NUC' problem.

[3] mikec_intel's BIOS settings fix – as detailed in:

● 'NUC5i7RYH did not wake from sleep mode', 11-Sep-2015 to 15-Nov-2015

» https://communities.intel.com/message/331090#331090

...and involves making changes in Intel Visual BIOS settings.

[4] prigaux's 'echo 0 > /sys/power/pm_async' fix – as detailed at post #10 in:

● 'NUC dead after suspend mode in Ubuntu 14.10', 23-Dec-2014 to 28-May-2015

» https://communities.intel.com/message/309188#309188

...and involves using rc.local to write '0' into /sys/power/pm_async at each boot up.

PS: I've sought help from System76 tech support, but sad to say they're about as useful as a chocolate teapot –  so I'm hoping the Intel NUC community might be of some actual help in addressing these problems.

Windows 7 stopped booting up after updating our NUC NUC5i7RYH to BIOS 0350 from 0249. I will just get a black screen will a flashing cursor (underscore) as soon as it goes past the BIOS and after a while I will get this error: "Invalid system disk. Replace the disk, and then press any key".

I did a lot of troubleshooting using the Windows 7 recovery DVD trying to fix the BCD (e.g. bootrec /rebuildbcd), but nothing would fix the bootup. The bootrec /rebuildbcd command actually failed with this error: "The requested system device cannot be found".

I went as far as reformatting the drive and trying to do a clean install (don't worry, I had a full backup), but the Windows Installed said "Windows cannot be installed to this disk. The computer's hardware may not support booting from this disk. Ensure the disk's controller is enabled in the computer's BIOS menu".

I did go through all the BIOS settings to see if there was an incorrect setting, but couldn't find anything, even after comparing the BIOS settings with another NUC that still had the old firmware and was still booting up. I was able to install Windows on the NUC after I downgraded the BIOS back to 0249 (the Windows Installer did not show that error any more).

I have now downgraded the BIOS back to 0249 and restored the Windows installation, and the drive booted up again. I then upgraded the BIOS to 0348 and immediately the PC wouldn't boot. BIOS 0350 also doesn't boot. The PC booted up fine once I downgraded again to 0249.

I am using a 256GB Samsung SM951, M.2 (22x80) PCIe 3.0 (x4) AHCI SSD in this NUC.

Has anyone seen this same problem?

Hi,

After setting up the NUC pre-xmas as a gift for my partner, of course didn't test the audio as it just one of those things that should just work.  Plugged it in on the day and there is loud static coming out speakers.

Plugged in headphones instead and the noise is still present.

After spending most of xmas day trying to isolate the noise, the best I could come up with is there noise interference around the place, mostly my wifi modem, and the NUC audio easily picks up that noise.

I removed all devices, including the monitor from the NUC, ie just power and headphones, I tried it in other locations and power sockets. In all cases the static noise persists, although in some locations it is less in volume.

I have several other computers and laptops that when plugged into the same speakers or headphones and power sockets, have no static noise.

Other threads suggest

• grounding issues. I purchase a ground loop isolator and this doubled the noise volume! The power adapter has no ground pin so not sure how this was going to help anyway.
• power board, I tried other power boards and sockets with no difference
• faulty adapter, I don't have another adapter to test

There are many other threads, this seems to be a common NUC issue.

Should I get the NUC replaced ?

Suggestions ?

NUC:

5i5RYH

Kingston KVR16LS11/8 8GB 1600Mhx DDR3

Crucial MX200 250GB M.2(80) SSD

WD Blue 1TB SATA 5Gbs 2.5 inch HDD

Hi all,

I have my own a new NUC5PPYH and tried to connect to SAMSUNG TV via HDMI.

This nuc had already have windows 8.1 in it.(I install it via other LCD)

It just boot to the Intel Nuc Logo with mention to F2,F7,F10.

After that it did not load the OS anymore.If i connect NUC to other LCD and reboot it.It is ok.Then i can reattach HDMI to the SAMSUNG and it works too.

The resolution i set on NUC is : 1280*720 and Fresh rate is 60Hz.

I also change the Samsung aspect ratio to Fit Screen and 16:9 .

The maximum resolution that Samsung support is 1366*768

But no successful to boot the NUC with Samsung TV.

Its so terrible.

Please help.

Hello,

I am developing an application for the NUC which requires an I2C device. I do not want to use an intermediary device such as microcontroller, etc. if there is native support. It appears that there is a Custom Expansion Header footprint on the underside of the board. It is not populated.

     Questions:

• Where can I find actual technical documentation for the internal motherboard?

          -I would like a pinout of the expansion header ideally.

• -Has anyone populated this header?

          -If so, where was the physical header sourced? Worst case, I do not mind soldering in directly if I can get a valid pinout diagram/dscription. It seems similar to the SamTec needed for the beaglebone black for baremetal programming/debugging.

*NOTE: Attached is a photograph of the NP header footprint.

With the i2c-tools installed on Ubuntu-14.04 I show (3) addresses on i2C bus 1.

Four (4) other buses exist, (all buses enumerated 0:4), of which, bus{0,2,3,4} show no connected devices.

Below is the output from the bus that DOES have devices associated. As per a forum comment, they may be the EFI controller?

/****************************SNIP******************************/

user_name@machine:~/SRC$ sudo i2cdetect 1

[sudo] password for minion1:

WARNING! This program can confuse your I2C bus, cause data loss and worse!

I will probe file /dev/i2c-1.

I will probe address range 0x03-0x77.

Continue? [Y/n] y

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00:          -- -- -- -- -- -- -- -- -- -- -- -- --

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

30: -- -- -- -- -- -- -- -- -- -- 3a -- -- -- -- --

40: 40 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

70: -- -- -- -- -- -- -- -- 

/****************************SNIP******************************/

Any help would be greatly appreciated, as would escalating this question to an engineer who can answer some more technical questions. Thanks!

I can see the Sandisk Ultra II SSD in my Bios but I cannot see the drive after I go into Windows 7.  Please advise.  Thanks.

I have installed Windows 8.1 32-bit on my new Intel NUC Atom (DE3815TYKHE). I have installed all the drivers for IO controllers(PROC_IO_Win8.1_32_603.9600.1948.32979.zip), but there are still two devices without a driver(80860f09). Windows show me Unknown device.

Where i can find the correct driver?

Hi,

I have a NUC5i3RYK (says NUC5i3RYB in VisualBIOS). I use it as a narrowcasting system I want to shut it down every evening (done through Windows) and restart it every morning at 7am (through BIOS). I am trying to get it to work, but if I try it, by setting a wake up time several minutes in the future, the NUC will not start up.

BIOS version: RYBDWi35.86A.0130.2014.1203.1639

I have the following power settings:

After power failure: Power On

Wake on LAN from S4/S5: Power On, normal boot

Wake system from S5: V

Recurrence: Daily

Wakeup hour: current hour

Wakeup minute: 10 minutes from now

USB S4/S5 Power: V

Wake on USB from S5: V

Expected behaviour: Start at selected time.

Does the NUC expect a midnight (0:00:00h) for this feature to work (start tomorrow?)

Edit: The NUC didn't start up the next morning either...

Cheers,

Mark

Message was edited by: Mark de Vries.

i have a Intel NUC D34010WYKH that ive been using since it was released, love the hardware, have Kodi 15.1 installed over Windows 8.1 as it also manages me media organizing and downloading.

I came into possession of an Xbox One Media remote that has the best feel and build quality of all the remotes ive owned, including many off-brand Chinese keyboard air-remotes and lower end Harmony ones. but for the life of me, i can't get the built in IR on the NUC to recognize commands sent by the remote.

i have tried EventGhost and WinLIRC and Intelliremote and any combination of the above but nothing ever clicks. i have seen posts related to this issue with sometimes no follow-up (like this) and other times success (on OpenElec for instance here). But even after messaging some of these users directly, i have gotten no further to getting this to work. For reference, the Intel NUC has a Nuvotron CIR that has drivers installed and up to date, and shows no errors in device manager and the bios is up to date with three options for the remote (generic remote, rc6, or xbox remote), all of which make no difference.

does anyone have experience with these two devices and how to get them to work better together?

Have had a Nuc for a few months now but only just purchased a new Logitech Harmony Touch remote and cannot get my NUC to power on via IR.  I have to power on via the case button and once my OS has loaded the remote works fine for what I have configured it for.

I've done a lot of googling and the articles I've found suggest the Nuc requires an RC6/MCE Remote profile to be used and so I've used the Logitech myharmony.com site to apply and test lots of profiles to get the NUC to power on but cannot find a solution.  To be clear, once powered on I can use my remote without issue, it is only powering on the NUC I cannot get to work.

Would appreciate any suggestions anyone has?

Kelvin

p.s. BIOS Power screen cap attached...have tried lots of setting combinations but none seem to work.  Nuc has the latest BIOS applied.