I bought an Intel NUC D54250WYKH3 seven months ago and I have been having problems if I switch the monitor off when I am not working and switching it back on some time later.

The monitor will show 'No signal' and I have to wait a random length of time, possibly hours, for the monitor to display the screen contents.

I have upgraded the BIOS several times and I am currently at WY0040.BIO, but the problem still remains.

I am running Debian 7.7 and the situation can be significantly improved if I activate the screen saver before I switch the monitor off, so much so that I now stand a better than 50% chance of the monitor working when I switch it back on.

I am using the mini Display Port (DP) port on the NUC connected to the DP port on the monitor. I believe that it is the NUC at fault as connecting a Raspberry Pi/Raspbian to the HDMI port or a dual boot Windows 7/Linux to the DVI port all display the screen contents properly when I switch the monitor back on.

I would really like to make the connection 100% reliable because as it stands I cannot make the NUC my main PC.

I would be grateful if anybody has solved this problem. If not, is there any information that I can provide to help narrow down where the problem lies?

Hello,

I have built a custom yocto image for my NUC with the yocto tools.  I can dd the .img to a usb stick and boot, but now ike to format and partition a SSD.

I tried following the instructions here https://wiki.yoctoproject.org/wiki/How_do_I to no avail.  They are

"

Q: How do I put Yocto on a hard drive?

A: bitbake core-image-sato or core-image-sato-sdk

1. have a suitable partition on the disk - say partition #3
2. this partition will show up as sde3 on my host machine and sda3 on the atom
3. mkfs.ext3 /dev/sde3
4. mount /dev/sde3 /mnt/target
5. mount -o loop tmp/deploy/images/core-image-sato-sdk.ext3 /mnt/target-ext3
6. cp -a /mnt/target-ext3/* /mnt/target
7. grub-install --recheck --root-directory=/mnt/target /dev/sde

If grub install passed, copy the following to /mnt/target/boot/grub/grub.cfg

set default="0" set timeout="30"  menuentry 'Yocto SDK' { insmod part_msdos insmod ext2 set root='(hd0,msdos3)' linux /boot/bzImage root=/dev/sda3 }

"

Step 7 fails with: "grub-install: error: /mnt/target doesn't look like an EFI partition."

How can I install the ext3 to a SSD and boot?  What's the iso for?

Thanks.

Hi everyone,

I've got my first NUC today. It's a 5CPYH celeron based NUC.

From what I understand, it can work with 12-19V power sources, but the brick that came with it is a 19V 65W one. I intend to use the NUC as a telescope controller in the field as well as the main imaging device, since from what I've seen, it's power consumption should be lower than my laptop (laptop gets to around 2.5Ah without significant load).

My main powersource is a 12V car 55Ah battery. It gives me 12.5-13.1V over the entire night and I wonder if I can connect the NUC directly to it. If it works on 12V then I should be OK, right?

Hi to all.

Seems to be a BIOS bug; ingredients :

+NUC  DN2820FYKH

+SSD Kingston 60GB 450 MB/S SV300S37A/60G

+SO Centos 7.1  - July 2015

+ MEM Kingston 4GB KVR16LS11/4

+ BIOS version 050 and 051

No other USB devices are plugged into NUC.

I testing NUC doing a automatic reboot every 5 minutes.

After about one day max, the NUC reboot hang when bios display "Intel NUC", "press F2 ..." .

and CTR ALT CANC work for good reboot.

I start test with  bios default setings and SO UEFI boot : reboot hang.

I tried other changes but without solving the problem :

+ Disabling Legacy boot when SO have UEFI boot

+ Disabling UEFY boot when SO have Legacy  boot

+ Windows 8 mode and Windows 7 mode

+ disablig boot from network

+ disablig boot from network+optical

+ disablig post error messages

+ Bios 050 and some tests with 051

Seems that Bios sometime is unable to start with correct boot device/partition;

and the problems occurs more time when ssd boot disk is UEFI.

So now I'm testing NUC enabling only boot from SSD and disabling all other boot devices (USB,network,optical);

I hope at least that is ok;

hear news !

bye

Is the N2820 capable of 720p/1080p Netflix playback?

I'm considering getting one for a minimal Windows 8.1 install for Plex, Netflix and Skype.

Is there any reason that I should not update my D54250wykh, which is currently running Windows 8.1, to Windows 10? Is Windows 10 "officially" supported on this device?

thanks

Keith

Hi,

before I start digging in system settings -

I have two displays in DP chain connected to the NUC - Dell U2713H as first display and Dell U2711 as the last display in the chain - both displays work perfectly with full resolution on HD5000,

until they go to sleep, after that it's impossible to turn them back on, both displays show only factory power management messages.

I have turned off system sleep in W8.1 on the NUC, displays only can may go to sleep after 15 minutes of inactivity, but still the behaviour is extremely annoying as stated above.

The only way to get displays working again is to power cycle NUC - power-cycling main display (unplugging/plugging power cable from/to the socket)

- has anyone had this experience before?

Such behaviour makes using NUC with two DP chained displays very hard.

Marcin

Hi Guys,

Has anyone already used the DE3815 with a Linux OS? Mainly Ubuntu and Fedora.

I am trying to use it and noticed a poor performance. I think that the mainly problem is the graphic performance because I notice some lags of the OS graphic interface and it is impossible to run a fullHD movie. In Windows 7 and 8 I don't noticed this. I know that the E3815 processor is limited, but in Windows I can use the Aero and run a fullHD in WMP movie without problem.

I tried to use Ubuntu 12.04, 14.04 and Fedora 21 and the graphic interface is too slow that is difficult to use it. I looked for drivers but the "Intel Open Source" drivers supports only Ubuntu 14.10 and Fedora 21 at now and soon will be upgraded to Ubuntu 15.04 and Fedora 22.

Is there a way to improve its performance?

I am trying to build all driver source code for more than a week, but my Linux knowledge is poor and the Intel Open Source documentation is confused and I couldn't build all the packages yet. Is an easier way or other way to improve its performance?

I am looking for this because I am developping some products based on this board  and we need that it be used with Linux, without especific distribution or version. Because we can't control what version our client needs to use.

Could someone help me?

I have an Intel NUC Atom DE3815TYKE. My problem is that it doesn't boot if there is no screen plugged in the VGA port. I updated the BIOS to the latest version (0036 dated October 23, 2014), but the problem is still the same. I experienced this issue with 2 NUC Atom units (2 units purchased at different dates). In the BIOS, the only parameters that I changed are "OS Selection" = "Linux" (to activate the 4 GB MMC on which I install Linux Debian 7) and the boot drive order.

I purchased these Atom NUC for embedded system (Asterisk server, Odoo Posbox...), so it is really a pain to be obliged to have a screen plugged in the NUC to make it boot.

Have you experienced the same problem ? Do you know a workaround ? Or a cheat in the BIOS configuration ?

Alexis

Dear all,

our issue is quite simple: the NUC often hangs and freezes if we want to reboot it.

Facts:

7 NUCs from three different Shops tested (three different S/N groups)

RAM: Kingston KVR16LS11S6/2 2GB DDR3L SO-DIMM

Storage: Internal MMC Flash

OS: we tried OpenELEC, ArchLinux, Fedora 20

BIOS: 0032, 0034, 0036

BIOS Settings: all different settings tried. Static settings were: Legacy boot enabled, eMMC enabled, OS Linux.

What's wrong in detail:

If we issue a reboot command on the box, it shuts down X-Server, shuts down all Task, etc. (Serial console debugging has finished too!) and when the kernel tries to reboot the box may hang.

Yesterday we had 3 NUCs in a loop-reboot (reboot every minute) during the night. All three boxes rebooted as they should. I then took one box, applied another BIOS settings => hang!

I removed that bios setting again => still hangs every time (although it was working the whole night... ).

We tried different BIOS versions and settings. We tried different linux reboot commands: even the most brutal force-reboot hangs

One of that seven boxes seem to definitely broken, as it refuses all BIOS updates, but all seven?

What can we exclude so far:

* different linux distros and kernels. We tried many! Kernels from 3.16.3 up to 3.17.2

* BIOS settings like EX Prevention Disable, Power settings

* BIOS versions

What really drives me crazy is that it seem only we got this issue, no other findings here or on Google.

Currently a coworker is trying to get different RAM modules (we only have 1,5V ones here and they definitely do not work), because this is my last "hope" as all seven NUCs uses the same RAM model.

Any ideas from the community?

Thanks in advance ;-)

PS: Yes, we also tried all the HowTos and Guides from the Intel support pages

Hi,

I'm having some trouble setting up the Intel NUC DE3815TYK with an EPOS receipt printer under Linux.

The first 40 - 60 characters get through to the printer, but the rest of the data is lost.  The printer / software has been proven to work fine on a more conventional desktop motherboard so i believe the issue to be in the setup / configuration of the serial port or underlying UART.  I'm guessing its a buffer issue, but I'm having difficulty diagnosing the problem without some further information.

In order that i might be able to further investigate a solution, could I get some details about the legacy serial hardware employed on the DE3815TYK:

• What type of UART is it? i.e. 8250, 16550A etc..
• What is the base address for the 2 serial ports?
• What IRQ's are assigned to the 2 serial ports?
• Are there any known issues with native Linux kernel drivers?

My Environment is:

• Linux Lite 2.0, NUC Edition
• Kernel version - 3.13.0-34-generic

The Linux Lite distribution is installed on the internal 4GB eMMC, with the stock vanilla kernel.  I haven't as yet looked into rolling a new

Thanks in advance.

Craig.

NUC5i5RYK + 8Gb (1.35V Corsair) + 480Gb SSD (Crucial M2)

Updated to latest BIOS, then installed Ubuntu 15.04

Seemed to work very well.

Suspended it last night (not first time) and this morning it wouldn't wake up (orange suspend LED just kept flashing). Tried 4-second button press, tried different mouse and keyboard, nothing. Eventually pulled the power cord, now it won't do anything - no boot at all.

What to do? I have seen older NUCs had issues with Ubuntu 14.02 - but this is latest BIOS and Ubuntu 15.04.

Hello, Intel,

This is a topic that's been discussed since Series 7: BIOS support for backwards compatibility with PCIe 1.0/1.0a is problematic on may Intel motherboards. This has been brought up many times in the forums, but the threads all die without resolution. Sylvia_Intel was involved in many of those discussions. If this isn't the place to direct this request, please point me in the right direction.

My company produces digital signage devices that use various capture cards designed around the SAA7160/NXP7160 audio/video bridge, which sports a PCIe 1.0a interface. We have such cards working with several Intel systems, including a Haswell reference design, but no 1.0a card can be detected by the NUC N54250WYKH Haswell design. The difference between the two Haswells is that the working system employs an AMI BIOS which allows to force PCIe bus speed to GEN1 (or AUTO with "Detect non-compliant device" as an option.) The NUC's Visual BIOS does not support such a setting, and apparently does not conform to the PCIe spec requiring backwards compatibility.

See: www.tbsdtv.com/forum/viewtopic.php?f=37&t=7521 for one manufacturer's comments concerning the problem.

This problem affects anyone who plans to use a NUC as an HTPC with video capture capability, since many capture cards are based on the 716x. My company plans to deploy hundreds of these units in FQ4, if we can get the capture cards to work with NUC!

So, my question is: Is anyone at Intel looking into this issue for the NUC BIOS?  It should be a simple fix, a write during initialization to the Root Complex Link Capabilities Register to limit link speed to GEN1 and width to x1, and maybe some compliance items.  I'd do it myself if I had source to the BIOS ;-)

PLEASE give us our GEN1 compatibility!.

Thx...

The mPCIe power-on, reset logic is not up to spec. The PCIE RSET is 185 MS before 3.3v is available. This reset should be after and not before power.

This is preventing from mPCIe cards from functioning correctly when power is first applied. the system function after reboot.

Intel should make a change to power on first, than reset.

BIOS version 0025 3/3/2014

i have attached the actual power on scope sequence showing the power comes on 185ms after the reset.

Please advise.

I am testing a NUC5CPYH with Windows 7 Professional 64bits and after install all drivers I noticed in Windows Device Manager that one driver was not recognized. The details of this driver showed the ACPI/MSFT0101 ID, and I found that this is a TXE driver. I try to reinstall the TXE driver but this driver remains unknown. I installed all the drivers, and before installing the TXE driver I installed the  KMDF update. Could anyone help me with it?

Details:

031 BIOS version

Jully Driver bundle

4GB PC12800 DDR3 SDRAM

32GB SSD Sata III

Basically, several times a day, YouTube locks up in the latest versions of Chrome (v43.0.2357.124m). It'll always play for a few minutes and then, despite plenty of bandwidth and cached content to continue playing, it'll just crash my Chrome tab unless I exit quickly. It'll show me the circular buffering icon right before it crashes. I use Chrome the most, but when switching to Firefox the issue goes away completely. There is no pattern with the type of YouTube video being played; long or short doesn't matter. It specific to Chrome and YouTube, all other embedded video works fine (Facebook, Bloomberg, Yahoo, etc.)

Here's my setup:

Intel NUC NUC5i5RYK

Samsung XP941 256GB PCIe 2.0 x4 M.2 SSD

G.SKILL Ripjaws Series 16GB 204-Pin DDR3 SO-DIMM DDR3L 1600

Windows 8.1 Enterprise clean install with all the latest updates as of today, June 10th.

Dual monitors using DP-to-miniDP cable and HDMI-to-mHDMI cable running to two Samsung monitors (SA850 and S27C750P LED monitors, respectively).

Latest BIOS and drivers are being used on all hardware, including a recent update of the Intel 6000 GPU to the May 20th 10.18.14.4206 beta drivers. I don't see a dump file created from the Chrome crash, but I probably don't know where to look. I thought it might be AV at first, so I disabled Trend OfficeScan but still had issues. Then I recently switched to Avast Premier 2015 and disabled it, and still had video crashing in YouTube. Note; no issues playing movies with VLC Media player, just browser video, so far just YouTube.

My system also has issue waking up my Samsung SA850 27-inch monitor running at 2560x1440 at 59Hz; I'll get artifacts and odd jitteryness until I power the monitor off and back on again. I'm also disappointed that Intel's Update Manager utility incorrectly lists older drivers to update when I run that utility, forcing me to manually check for updates line-by-line on their web site like it's 2001 as if I'm running Windows XP or something. For example, their update utility said I needed to update my Bluetooth driver to an older 17.1.1411.01 when I had the new v.17.1.1450.0402 already. This shouldn't be that hard to get right.

My DE3815TYKE was recently updated to v44 :TY0044.BIO

md5=efbfc3fb5d6a6bacff51f717533eeb30

http://downloadmirror.intel.com/25040/eng/TY0044.BIO

http://downloadmirror.intel.com/25040/eng/TY_0044_ReleaseNotes.pdf

Same file in  TYBYT10H.86A.0044.BI.ZIP http://downloadmirror.intel.com/25040/eng/TYBYT10H.86A.0044.BI.ZIP

http://downloadmirror.intel.com/25040/eng/TYBYT10H.86A.0044.BI.ZIP

And It boots fine, VisualBios displays : "Ver: 0ACCT014"

*But* then fail to load my GNU/Linux OS (Ethernet and keyboard not working) ...

More details on demand

I reported the problem at :

https://servicerequestmgmt.intel.com/webticketui/emailpage.aspx?servicetcktnumber=8001222045&pagetype=st

(normaly you should not be able to view it, but in case of I shared the reference)

I havent downgraded yet but wait for confirmation first ...

Because DE3815TYKHE reported serious issues :

Re: DE3815TYKE - not turning on , after bios downgrade

Tell me if it's safe to downgrade to v24 to support headless usage :

https://communities.intel.com/message/285968#285968

Questions :

Which BIOS version to install on #DE3815TYKHE ?

Does the BIOS download feature used to work on that model too ?

Do you know other black magic procedures for NUC ?

Other hints :

From https://communities.intel.com/inbox?objectType=2&objectID=218772 "Try unplugging the NUC from the power outlet approx. 5 minutes, then power it back, then press the power bottom for 10seconds."

https://communities.intel.com/message/318723#318723

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

More to come in this thread or maybe I should create a knowledge base's article somewhere ?

Draft ... contact me if you want to edit it too

rzr@gna.org

== BIOS ==

v30

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

² Notes for the Intel® NUC Kit DE3815TYKHE and Intel® NUC Board DE3815TYBE:

Update this Intel NUC model to BIOS version 0030 or later before installing any Intel processor I/O controller drivers.

v43

TY0043.BIO 2a45c5412e94c50185ce0cfdad7489024c61f977ca7edb011a111b070ca9d4cd

https://communities.intel.com/message/318925#318925

v44 :

Re: Feedback about DE3815TYKE BIOS upgrade to TY0044.BIO ?

Problem on headless boot :

https://communities.intel.com/inbox?objectType=2&objectID=262437

Hi, I have the D54250WYK with Windows 8.1 and after leaving it on at the desktop doing nothing for a while, I'll get a low memory error.

My setup is:

Memory is Crucial Ballistix Sport 16GB BLS2K8G3N169ES4.

Clean install with Windows 8.  Upgraded to Windows 8.1.

Latest BIOS and Intel drivers installed.  All Windows Update installed.

Enabled "Let me choose one scaling level for all my displays."

Disabled Sleep.

Restarted computer.  Left on desktop and do nothing overnight.  In morning, turn on monitor and there's a low memory error on screen.  Task manager shows more than 14GB of ram free.  I can reproduce this consistently.  Reinstalling windows did not fix the issue.

I am not running any full screen applications or games (simply left on the desktop with no applications running) so I'm not sure if it's the same issue others are having.