XBMC will be renamed to Kodi for v14. Read here for more details
Various pages on the wiki might contain old references to "XBMC", but will most often still apply to "Kodi". Find out how you can help here.

Intel NUC

From Kodi
Jump to: navigation, search
Intel NUC 4th Gen.jpg
NUC.jpg
Home icon grey.png   ▶ Devices ▶ x86 hardware ▶ Intel NUC

The Intel NUC is a series of small, awesome, x86-based PCs that works fantastically as an HTPC. Can run a full desktop OS if desired. Reasonable starting price considering size and power. Uses Celeron to Core i5 CPUs. Can run fanless with a replacement heatsink case.

Contents

1 Installing Kodi on an Intel NUC

Installing XBMC/Kodi on the NUC is pretty much just like installing it on any other PC. Since most NUCs come as barebone kits you will also need to install an OS. If all you are using the NUC for is Kodi then you might want to consider an all-in-one solution like OpenELEC, which has Kodi and OS and allows everything to be configured from within Kodi's interface.

2 About the Intel NUC

NUCs are available with either Celeron, Core i3 or Core i5 processors. You will need to purchase your own DDR3 SO-DIMM RAM, mSATA SSD, and if desired, MiniPCIe WiFi card. All current NUCs have 2x DDR3 SO-DIMM slots, allowing a maximum of 16GB of RAM (8 GB per slot). Newest models based on the 4th-Generation Core processor require DDR3L SO-DIMMs (1.35V). Although NUC boards will work with DC power ranging from 12VDC~19VDC, NUC kits come with a 19VDC 65W switching power adapter. However, not all SKUs have the AC power cord included. There are multiple SKUs of the latest NUC models, each of which has a different type of AC power cord, depending on the country/region/plug type.

All NUCs are x86 and x64 OS capable. You can install Windows 7, 8 or just XBMCbuntu or OpenELEC. It doesn't matter. But if you don't need Netflix, SkyGO, then stick with OpenELEC or XBMCbuntu. They even have the internal pin headers for extra USB ports, but also for power switch, LEDs etc. More on this later.

3 Known issues

3.1 Windows

  • Having graphical UI corruption with a NUC that uses Intel HD4000 graphics? Try these beta graphics drivers: 32-bit64-bit. [1]
  • The 2820 Baytrail will not bitstream HD Audio under Windows OS. This is a driver limitation as they don't support the PAP [Protected Audio Path] But under Linux, Ubuntu, openELEC. They work fine!

3.2 Hi10P / 10bit

The first stable version with Hi10P support is XBMC v12 (Frodo). Multi-core software decoding is essential on the Celeron NUC, which is available in normal OpenELEC builds and development builds for Windows.

The Celeron 847 NUC can play most 10bit anime near flawlessly (as shown here ). Frames might start dropping at around 18Mbps, but common anime releases seem to have no significant issues. For more info, see this thread on the XBMC forum.

4 Mods

Here are some mods the community has done.

4.1 IR mods

Here's one user's mod to add IR: http://forum.xbmc.org/showthread.php?tid=166886

He added http://www.simerec.com which is ON/OFF capability via remote, and added in IR from a Microsoft USB RC6 IR receiver. Plenty of pics and detailed description. Even the holes were covered with LightDims, which worked fantastically.

4.2 Fanless cases

There are several fanless cases available for the NUC:

Logic Supply offers a fanless case, the ML300, compatible with the following Intel NUC motherboards: DCP847SKE, D33217GKE, and D53427RKE. The fully configured system is also available, the Core-ML300.

The Haswell version, the ML320 is in production available to pre-order as well as the fully configured system version, the Core-ML320.

You can also buy fanless cases for these NUCs: http://www.impactics.com/d1nu1-b/

White model with RC6 USB receiver plugged into front of it: http://postimg.org/image/klk0h6yp3/

5 Other tips, tricks, and advice

5.1 Linux

5.1.1 Bootloader

info on what you choose when installing archboot when you do a UEFI install?

I used a GPT layout with GRUB as bootloader. Here's my partition info:

$ sudo gdisk -l /dev/sda

GPT fdisk (gdisk) version 0.8.7

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 125045424 sectors, 59.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 783A3002-626F-49A1-85D1-12225885803E
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 125045390
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
   1 2048 6143 2.0 MiB EF02 BIOS_GRUB
   2 8192 1056767 512.0 MiB EF00 UEFI_SYSTEM
   3 1056768 3153919 1024.0 MiB 8300 SWAP
   4 3153920 125045390 58.1 GiB 8300 BTRFS[/code]

The BIOS_GRUB partition is not really needed, I just added it in case I wanted to install to MBR and still use GPT. The UEFI_SYSTEM partition is mounted to /boot/efi. Look at the GRUB page in the Arch wiki, it has pretty good instructions.

5.1.2 Consumer IR

Enabling the build-in Consumer IR (CIR) is not (completely) straightforward and needs some editing in the configuration files. Most of the commands below must be run as root, or using `sudo`.

The Intel NUC CIR is supported by the nuvoton_cir kernel module. Some (required) updates to this module are added to Linux kernel 3.15 [2]. So first update to Linux 3.15, if required.

For Ubuntu the kernel packages are available at http://kernel.ubuntu.com/~kernel-ppa/mainline. Download either the amd64 or i386 version of the generic image and the all headers packages in a separate directory. Download and install using:

$ mkdir linux3.15
$ cd linux3.15
$ wget -O headers.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/linux-headers-3.15.0-031500_3.15.0-031500.201406131105_all.deb
$ wget -O image.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/linux-image-3.15.0-031500-generic_3.15.0-031500.201406131105_amd64.deb
$ dpkg -i *.deb

You will need to change the download URLs to match the correct version and processor type. Reboot and you should be running the Linux kernel 3.15, check with

$ uname -r
3.15.0-031500rc8-generic

The same Intel forum thread also shows the workaround to actually enable the novuton_cir driver for the CIR. Create a new file /etc/rc2.d/S18fix-cir using your favorite editor with this content:

#! /bin/sh
#
# Fix for Consumer IR device, see https://communities.intel.com/thread/46259
modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
modprobe nuvoton-cir

Make the new file executable using:

$ chmod +x /etc/rc2.d/S18fix-cir

The system log should show something similar to these lines after rebooting:

$ dmesg | grep -i Nuvoton
[    3.491310] nuvoton-cir 00:08: [io  0x0240-0x024f]
[    3.491326] nuvoton-cir 00:08: unable to assign resources
[    3.491330] nuvoton-cir 00:08: Could not activate PNP device!
# Note that at this point the S18fix-cir script kicks in, reloading the nuvoton_cir module with the 'fix'
[    4.147173] nuvoton-cir 00:08: [io  0x0240-0x024f]
[    4.147217] nuvoton-cir 00:08: [irq 3]
[    4.147223] nuvoton-cir 00:08: [io  0x0250-0x025f]
[    4.147862] nuvoton-cir 00:08: activated
[    4.174957] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:08/rc/rc0/input10
[    4.175091] rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:08/rc/rc0
[    4.203370] nuvoton_cir: driver has been successfully loaded
[    4.208858] input: MCE IR Keyboard/Mouse (nuvoton-cir) as /devices/virtual/input/input11
[    4.217123] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0

Next install lirc:

$ apt-get install lirc

It does not really matter what IR receiver is chosen as the required one is not available, so choose None for both the receiver and the transmitter.

Now open /etc/lirc/hardware.conf in you favorite editor and modify it, so it contains these settings (find the correct locations and modify them):

REMOTE="Nuvoton Transceivers/Remotes"
REMOTE_MODULES="lirc_dev nuvoton_cir"
REMOTE_DRIVER="default"
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""
START_LIRCD="true"
LOAD_MODULES="false"

(the other settings are not important)

Now the CIR device should be supported by lirc. Time to configure your remote

6 Links

7 Random notes

Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.

Personal tools
Namespaces

Variants
Actions
Navigation
Wiki help
Toolbox