I have got a Intel NUC i3-3217U, when its starts up my screen goes black after a few seconds. I see a second or three of the windows startup screen. After that noting. The system is not in a sleep or energiesaving modus. I tried different cables and monitors.. If a us a hdmi to vdi cable i don't have this problem.
I know that is a solution, but then i don't have sound.
Who has a solution?
René
Hello, recently purchased the NUC6i5SYH, and am trying to install Windows 7 Home Premium 64-bit. It is a modified ISO, as I've slimmed the heck out of it down to a final install size of just 3.5GB.
I've tried an OEM install as well from Microsoft and it gives same results.
The hardware: NUC6i5SYH, Kingston HyperX DDR4 2133MHz @ CL13, ZTC 128GB 2240 M.2 SATA3 SSD, and Corsair 256GB SSD of some sorts.
I'm connecting a USB 2.0 2GB flash drive to the NUC via internal header as Intel's tool did not work in my attempt to install Windows 7.
It has the latest BIOS. There is no option to select which OS within the BIOS.
Windows 7 install is automated, and have keyboard/mouse support when selecting a partition to install Windows 7 onto, but after everything is said and done, and boots to the desktop, there is no peripheral support for ANYTHING. USB external or internally connected, don't work. I cannot load drivers as every Intel driver for the NUC, Windows 7 thinks it's unsigned and cannot load before selecting the partition.
Tried installing drivers with RT 7 Lite, version 2.6, with the proper, updated USB 3 drivers.
I've followed this guide here, a guide from Intel, researched here, and here. Nothing seems to be working.
The reason Windows 7 is important to me is Windows 10 is dreadfully horrible. Among the reasons is Microsoft kindly eliminated nearly every aspect of user privacy control (which sort-of works), and their own bloatware creates easy backdoors, and possibly more malware created for Windows 10 now that it runs on so many various devices.
Any tips/guidance will be greatly appreciated, and I'll provide all the info I can to assist in solving this.
When trying the DISM GUI, it gives an error about the install.wim when trying to add the USB 3 drivers, but worked on the boot.wim..
I have a new NUC5i5MYHE. Seeing 2 Mini DP ports on the back, I assumed the machine could support dual monitors with extended desktop even without daisy-chaining or a DP hub.
Neither of my monitors has a DP socket, so I'm using 2 DP-->VGA adapters, with each monitor plugged into one Mini DP port on the NUC.
I get only duplicated monitors, with no option for extending the desktop.
My question: Is there something about this hardware setup that makes it absolutely impossible to extend my display over 2 monitors? (I.e., will the graphics card absolutely not drive 2 different VGA displays even if they're plugged into different sockets)?
Or is it a software problem?
The system is Manjaro Linux XFCE. I've been able to set up extended desktops using the same OS but with different hardware, so in this case I'm looking for the usual setup choices and finding them missing.
Any suggestions?
Hi,
I love the Intel NUC but I hate that it doesn't support HDMI CEC.
Does anyone know if the skylake gen intel nuc with the 540 graphics chip will support HDMI CEC?
//eNeLL
OS: Windows 10 64 bit
NUC5i5RYK
This RAM is on the supported memory matrix for this model NUC
The memory is set to automatic settings in the firmware. All firmware settings are "default".
The firmware is the latest version RYBDWi35.86A.0355.2016.0224.1501
2 X 8GB G.SKILL RIPJAWS
F3-1600C9S-8GRSL
DDR3L-1600 CL9-9-9-28 1.35v
PC3L-12800 8Gx1 SO-DIMM
It posts and boots just fine with EITHER module in SOCKET1
It posts and boots just fine with EITHER module in SOCKET2
It WILL NOT post with both modules installed.
No beeps.
No video from HDMI.
NUC6i5SYH starts up when I shut down PHILIPS TV (46PFL9706T) with remote (IR). Where can I disable IR in the NUC or change IR-codes so it will not respond to my TV-remote?
I am using NUC5CPYH with Windows 8.1 and the latest Intel graphic driver, but it cannot passthrough DTS-HD and Dolby TrueHD audio via HDMI to my AV receiver on any programs.
So, are there any ways to get NUC5CPYH passthrough DTS-HD, Dolby TrueHD Audio?
This thread's initial OP appears below this Workaround Alert. Since folks afflicted by Intel's 'Linux Suspend > Dead NUC' intermittent defect can no doubt benefit most from learning how to avoid getting their NUCs bricked by it, it seems wise to present these bricking avoidance techniques at the top of this thread; and of course you're at liberty to read the whole conversation below, from which they derive.
Workaround Alert
or 'How To Avoid Getting Your NUC Bricked by Linux Suspend'
TL;DR – use wake-on-USB to wake with an input peripheral (eg: keyboard, mouse, trackpad, etc.) or wake-on-LAN from a smartphone app.
Many reports in these forums, dating back to August 2014, show that the Intel NUC is afflicted by an as yet unfixed design flaw: when run under several different distros of Linux (Ubuntu, Arch, Mint, Fedora, Debian), each use of the Linux Suspend function carries a small but real risk of initiating a NUC-bricking incident. Susceptible NUC users are those who use a short press on the Power button to wake from suspend, because the first symptoms of an impending NUC-bricking incident are as follows.
NUC-Bricking: Symptoms #1
When Linux Suspend is used and works normally, the NUC goes into sleep mode, and the Power button LED winks amber. When the 'Linux Suspend > Dead NUC' problem occurs, these are the symptoms which afflict sleep mode:
See 'Bricking Avoidance Workaround' below for ways in which to successfully wake a NUC exhibiting these symptoms, rather than experience...
NUC-Bricking: Symptoms #2
Once a NUC is in the grip of symptoms #1, the only way to get the NUC to power off is by disconnecting the power cable. After the power cable is reconnected:
Unbricking Workaround: to get a thus bricked NUC to work again, you have to fully disassemble the NUC, disconnect and reconnect the CMOS battery from the far side of the motherboard, and reassemble the NUC. Such a drastic remedial action highlights the nature of this failure mode as a manufacturer design defect.
Bricking Avoidance Workaround
Two ways of avoiding the NUC-bricking consequence of symptoms #2 are known to be effective, and both involve alternate ways of waking a sleeping NUC: by input peripheral (wake-on-USB), and by mobile device (wake-on-LAN). They both take some setting up, which is described below.
BIOS Settings for Wake-on-USB and Wake-on-LAN
On booting up your NUC, press 'F2 to Enter Setup' on your keyboard to go into Intel Visual BIOS Settings. On the Power tab (Advanced pull-down menu > Power), set your Secondary Power Settings to match those illustrated below.
Photo credit: sylvia_intel
Press 'F10 - Save and exit' (and 'Y' to confirm) to save these settings and reboot your NUC.This may well be all you need to do, so test to see if you can now wake from suspend with the USB-connected input peripheral of your choice (eg: keyboard, mouse, trackpad, etc.); if it works OK, then you should also be able to use it after a Linux shutdown to boot up your NUC.
OS Settingsfor Logitech Wireless Input Devices
My Logitech wireless keyboard+trackpad and wireless trackpad didn't work straight away to wake from suspend, but community assistance soon got them working flawlessly – so if you too are using Logitech wireless input devices, please see the '2. OS Settings' section of post #39 below (» https://communities.intel.com/message/362981#362981 ) for additional set up instructions.
Wake-on-LAN Apps
To boot up and wake from suspend using wake-on-LAN, you can use a smartphone/tablet app – so just search your mobile device's app store for 'wake on LAN' to acquire an appropriate app. For instance, I've tested the free 'Wake On Lan' Android app by Mike Webb, available in the Google Play store, and it works perfectly. Similar apps are also available for Apple iOS devices.
Workaround Works – Fix is Pending
Once you've settled in to routinely using either wake-on-USB (ie: wake-on-keyboard, wake-on-trackpad, etc.) and/or wake-on-LAN, then even if symptoms #1 of the 'Linux Suspend > Dead NUC' defect should arise again, they'll most likely go unnoticed, since you'll no longer be using a power button short press to end a suspend – and a simple routine tap on an input device or mobile app will wake your NUC as usual.This workaround thankfully avoids the NUC-bricking effect of symptoms #2, but it does not eliminate the 'Linux Suspend > Dead NUC' defect – so we are still waiting on Intel and System76 to come up with a permanent fix for this defect; and that's why this thread remains tagged as 'This question is Not Answered'.
__________________________________________________________________
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:
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:
[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. After an email of complaints to System76 CEO Carl Richell, the 'chocolate teapot' tech (non-)support staffer has been replaced by a honest and helpful operations manager, and a possible fix has been encoded in a 'System76 Driver' update, so System76 are at least striving to address this defect; meanwhile Intel are asking for more time to investigate the problem (07 Jan 2016 update).
We have found that if a local monitor is not plugged in to the NUC 5i5 the remote KVM screen remains black( in Bios and windows).
However Keyboard and mouse clicks remain active, we can see this on windows when running remote admin screen.
If we plug in a local monitor or emulate a local monitor, the remote KVM screen works well as expected.
This is rather frustrating we assumed that the built in KVM would work headless, mainly because the NUC unit itself has been designed to run headless as stated in the manual.
The Nuc in general fantastic compact unit. Our current solution is to use a modified mini display port to VGA adapter, which is around 1/4 the size of the NUC pcb which is a real shame.
Does anyone out there have a better solution, or is there already some sort of a firmware solution out there already.
How do you get that piece of **** IR inside the NUC6 series to work?
I'm running windows 10 and under HID devices I got 6 entries, 4 HID compliant ones and ITECIR and microsoft ehome transceiver. These are all related to the IR receive because removing one of them removes all of them. The driver is installed by windows 10 automatically.
However running eventghost I don't see a single keystroke popping up. I tried my LG tv and WD live TV remotes. Both should be normal IR controllers.
I tried installing the ITE tech IR driver listed on the Intel download page for my device (nuc6i3) but that driver fails during install, outputting 0x80070103 in crappy English. Color me surprised, ****** chinese hard and software that isn't working.
So is there way to get this turd to work or should we all just accept that Intel is simply utter **** at delivering software (their own or somebody else s) that actually works? Any point in wasting more time on this or am I better off saving my time and frustrations and just spend a 100 bucks on a mce remote (yes those things are that expensive where I live)?
Hi,
I am living in Poland in Europe. If I buy a NUC from Amazon's third party seller in United States, what is the fastest and easiest way to RMA?
1) Send back to Amazon?
2) Send to Poland Intel Service?
3) Send to US Intel Service?
4) Other way?
Thanks in advance.
I have a NUC6i5SYH with Bios 42
Linux Mint 17.3 with 3.19.0-32-generic (the one includes with the distro)
I have not wifi, not bluetooth, and the graphics performing not so good.
ILOGICAL PROCEDURE TO MAKE THE NUC6i5SYH working under MINT 17.3:
sudo apt-get update
sudo apt-get install linux-headers-generic build-essential
wget https://www.kernel.org/pub/linux/kernel/projects/backports/2015/11/20/backports-20151120.tar.gz
tar -zxvf backports-20151120.tar.gz
cd backports-20151120
make defconfig-iwlwifi
make
sudo make install
cd /lib/firmware
sudo cp iwlwifi-7265D-13.ucode iwlwifi-3165-9.ucode
sudo cp iwlwifi-7265-13.ucode iwlwifi-3165-13.ucode
sudo reboot
sudo dpkg -i linux-*.deb
sudo reboot
sudo apt-get remove linux-image-4.6.0
sudo apt-get remove linux-headers-4.6.0
sudo update-grub
sudo reboot
But please I buy this device for the promise of Linux support, but not drivers or solutions is found on the official pages.
I'm worried because:
Hi,
i have in my organitazion 150 Nuc With OS 7 Enterprise 64bit
when i disconected the cable hdmi the nuc its crush with blue screen
Can anybody help ??
Thanks
Best regards
Hi Guys,
I am using my Nuc6i5syh since february - without a few minor issues probably driver ones (Soundcard, VideoCard) - they may caused some headache, but the overall picture was not so bad - like at the WHEA uncorrectable "fans". I can tell that the from mid March till today - no serious event was happened, no hardware incompatibility before. (2x 4 GBCorsair Value Select CMSO16GX4M2A2133C15, 1x 128 GB NVMe SAMSUNG MZVPV128 and Samsung SSD 850 EVO 500GB)
Today morning I realized FIRST time, that my NUC is not responding, power cable out - plugged back and start - second attempt was OK, and system was built up.
Checked the Eventlog, and I saw a tons of WHEA Logger - Event 19 and 47 errors written there in every seconds. (CPU and Memory related "corrected" hw issue)
I do not know since when this kind NUC writing this errors, there were tons - last one is yesterday 19:50
So it is not showing the reason what may trigger this event, or what happened during the freeze - getting or not the WHEA crash page - I do not know.
Now system is running correctly but the eventlog is continuously "under writing attack" with this event 19.
My BIOS is still 28, and it is not the evergreen everblue uncorrectable WHEA one, but can you please advise what can I do with this error?
I will update to 42 soon today, but is it solving that issue or I can only join to the glorious "WHEA" fanclub - then RMA?
Thanx
Attila
I've had this happen to me multiple times now. I'm fairly confident that there's a bug in intel's LAN driver for my NUC 5i5RYK. I have currently have version 20.7 for windows 10 64 bit. I use OpenVPN on occasion (with my LAN) and sometimes after disconnecting from the VPN server I no longer can access anything on the internet through the LAN. I just get cannot resolve DNS messages. Rebooting doesn't fix it. I can however connect to the internet through WLAN while it won't work on the LAN. Uninstalling and reinstalling the LAN fixes the issue every time. Has anybody else seen this bug? It's awful annoying. Anyone know a fix?
Hello,
I had an issue with heating on my NUC5i5RYH board's power intake. I believe one of the SMD resistors is missing, likely fallen off due to liquified solder.
I would like to replace it, but need to know what the resistor was rated at so that i can secure an appropriate replacement part.
Can you please provide the schematic of the board to illustrate the resistor's rating?
Is it currently possible to daisy chain 2 40" 4K monitors to run at 3840x2160@60hz with any of the NUC6i models?
OK, I am not real good at this stuff and thought it would be easy, Bought NEW SSD DRIVE and Installed in INTEL NUC5PGYH Mini Computer, Used the Acronis Downloaded Software to MIGRATE the NEW DRIVE. Did NOT WORK, Did not Recognize the Drive But was there to select as the TARGET DRIVE. Now what Do I do. If the software they send with the NEW DRIVE does not work.
Also There are no WINDOWS 10 OPERATING DISK's came with the Little Cube Unit. It was already loaded on a 3Gb eSSD drive in the unit. How do you get a Start up or Recovery disk in case something goes bad. How do you RESTORE the Unit to Factory if the Drive is messed up or corrupted.
Need a lot of help, being 66 and all this stuff is Supposed to be PLUG AND PLAY and it is all PLUG and DELAY in my book.
Thanks for any help.
Dave Huellewig
I have been trying for a week now to update my Windows 7 ISO with USB 3.0 drivers, to allow me to install this O/S onto my NUC. Unfortunately, none of Intel's workarounds have worked (including the ones listed here: https://downloadmirror.intel.com/25476/eng/Install-Win7-to-USB3.0-Computers-Readme.pdf).
I am now going to try using the onboard USB 2.0 ports.
However, I can't be sure of the exact cable I need. I've bought a couple but neither has fitted. I have also read differing views from people. Some say 1.25mm pitch is required, others say 2mm pitch.
Could someone at Intel please post a link to the correct cable for this particular model (NUC6i5SYH)? I'm in the UK so would prefer a UK supplier.
Once I get the correct cable, is it simply a case of connecting them (i.e. are the ports live or do they need to be enabled within BIOS)?
Thanks
I have a NUC 5i7RYH. After my first unit was replaced under warranty, my second unit was running beautifully, dual-booting Unbuntu 15.10 and Windows 10 (almost never). I have been very pleased with the unit. First sign of emerging problems (while still running 15.10) occurred last week, when the NUC started to refuse to suspend. It would enter suspend mode, then spontaneously awaken itself after two or three seconds.
Yesterday, I installed Ubuntu 16.04 LTS. The system went to sleep last night as usual. This morning the system would not respond/awaken to keyboard input. The power button was slowly flashing orange and was completely unresponsive. I unplugged the power and plugged it back in . . . you all know the drill by now . . . no response at all. So I took it apart and unplugged the CMOS battery [ if the gray and black wires disconnect for anyone else like they did for me, when you put it back together, the gray one reattaches on the side closest to the chassis ]. I was able to restart the system.
My BIOS is RYBDWi35.86A.0355.2016.0224.1501.
Now, since Ubuntu 15.10 wasn't sleeping/suspending properly, I don't see any good reason to roll back from 16.04 to 15.10. But what is the best way for me to proceed. Are there recommended bios settings or any other action that I can take to minimize this problem going forward?
---
Update. I went to the power settings and tested my ability to recover from Suspend with the USB S4/S5 both checked and unchecked. While 15.10 would wakeup the system (while that setting as NOT checked), 16.04 will not wake the system up at all. So far, I have been able to awaken the system with the power button when the tests have failed. Wake On LAN is enabled and I downloaded and configured a mobile app. It does not wake the system. Although, interesting, the screen does flicker for a fraction of a second. For Wake On LAN usage, does anyone know how to configure/the NUC and the APP? I am running Wireless and I only see the ability to set the adapter to Wake On LAN from a magic packet on the wired adapter address. Will Wake on LAN work with the wireless adapter? If so, how do you configure it in Ubuntu?
