Official Kodi Wiki - User contributions [en]

Archive:Intel NUC

2015-03-24T18:47:04Z

Jolan: /* Known issues */

[[File:Intel NUC 4th Gen.jpg|300px|right]][[File:NUC.jpg|300px|right]]
{{mininav|[[Devices]]|[[x86 hardware]] }}
<section begin="intro" />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.<section end="intro" />

== Installing Kodi on an Intel NUC ==
{{See also|HOW-TO:Install KODI on an Intel NUC}}
Installing {{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.

== 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.

{{collapse top|Click "Expand" to show full specs -->}}
=== Atom-based ===
There is one NUC model based on an Atom processor: DE3815TYKHE.

{| class="prettytable"
|-
| width="100" | Model Number
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-de3815tykhe.html DE3815TYKHE]
|-
| CPU
| align="center" | [http://ark.intel.com/sv/products/78476/Intel-Atom-Processor-E3815-1M-Cache-1_46-GHz Intel® Atom(TM) E3815] w/ HD Graphics (4 EUs)
|-
| RAM
| align="center" | DDR3L SO-DIMM 1.35V, 1333/1600 MHz (down clocked to 1066 MHz) 1x SO-DIMMs, 8 GB total max.
|-
| Display
| align="center" | 1x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI 1.4a], full-size 1x Embedded DisplayPort* (eDP) 1.3 (2 lanes with backlight and adjustable voltage/timings) 1x VGA
|-
| Mass Storage
| align="center" | 4-GB eMMC storage device built in Internal support for 2.5-inch HDD or SSD (up to 9.5mm thickness)
|-
| Ethernet
| align="center" | 1x RJ45, 10/100/1000 Mbps
|-
| WiFi
| align="center" | Half-length PCIe* mini-card slot and wireless antennas pre-assembled
|-
| Audio
| align="center" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via HDMI Back panel headphone/microphone jack
|-
| USB 2.0 Ports
| align="center" | 2x rear, 3x via internal pin header
|-
| USB 3.0 Ports
| align="center" | 1x front
|-
| Consumer IR Port
| align="center" | None
|-
| MiniPCIe Slots
| align="center" | 1x half-length
|-
| Included in-box
| align="center" | 12V, 36W wall-mount AC-DC power adapter (12-19V DC back panel power connector) Multi-country plugs (IEC types A/C/G/I) Vertical stand VESA mount bracket (75 x 75mm and 100 x 100mm compatible)

|-
| Chassis / Enclosure
| align="center" | Passive/fanless design Metallic gray plastic ring with black sides (190mm x 116mm x 40mm)
|-
| AC Power Cord
| align="center" | Not included
|-
| Manufacturer Links
| style="text-align: center;" |[http://www.intel.com/p/en_US/support/category/dsktpboards/dk-de3815tykhe/doc_guide Technical Documentation]
|}

Even with limited GPU power, this Atom-based Intel NUC works well with XBMC. There are few formats this device can't properly decode. This is a great fanless replacement of the [[Raspberry Pi]]. Compared to the other NUC models this ends up much cheaper (no additional harddrive is required because of the internal 4GB mSATA drive which without problems holds GNU/Linux with XBMC) and passive (totally silent) at the cost of CPU/GPU power.

A more comprehensive test can be found here: http://nucblog.net/2014/05/part-2-bay-trail-atom-nuc-as-htpc-de3815tykhe/

Demonstation with OpenELEC: http://www.youtube.com/watch?v=UXIYZjlrFic

=== Celeron-based ===
There are two NUC's based on a Celeron processor: the first-generation DCCP847DYE and the third-generation DN2820FYKH.

{| style="float: right; border: 1px solid #BBB; margin: .46em .2em;"
|- style="font-size: 86%;"
| valign="top" |[[File:DCCP847DYE.png|200px]] Intel Celeron-based NUC, DCCP847DYE
|-
|-
|- style="float: right; border: 1px solid #BBB; margin: .46em .2em;"
|- style="font-size: 86%;"
| valign="top" |[[File:DN2820FYKH.png|200px]] Intel Baytrail Celeron-based NUC, DN2820FYKH
|}

{| class="prettytable"
|-
| width="100" | Model Number
| width="250" align="center" | [http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-kit-dccp847dye.html DCCP847DYE]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-board-dn2820fykh.html DN2820FYKH]
|-
| CPU
| align="center" | [http://ark.intel.com/products/56056/ Celeron 847] w/ HD Graphics (6 EUs)
| align="center" | [http://ark.intel.com/products/79052/Intel-Celeron-Processor-N2820-1M-Cache-up-to-2_39-GHz?wapkw=intel%C2%AE+celeron%C2%AE+processor+n2820 Celeron N2820] w/ HD Graphics (756 MHz)
|-
| RAM
| align="center" | Dual-channel DDR3 1333 MHz 2x SO-DIMMs, 16 GB total max.
| align="center" | Single-channel DDR3L 1066 MHz 1x SO-DIMMs, 8 GB total max.
|-
| Chipset
| align="center" | [http://www.intel.com/content/www/us/en/chipsets/performance-chipsets/mobile-chipset-qs77.html Intel QS77]
| align="center" | N/A; [http://software.intel.com/en-us/articles/an-introduction-to-the-intel-4th-generation-core-processor CPU is an SoC]
|-
| Display
| align="center" | 2x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI 1.4a], full-size
| align="center" | 1x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI 1.4a], full-size
|-
| Mass Storage
| align="center" | mSATA SSD support via 1x full-length MiniPCIe slot
| align="center" | 2.5" SSD or HDD w/ 9.5mm max height SATA data and power connectors provided
|-
| Ethernet
| colspan="2" style="text-align: center;" | 1x RJ45, 10/100/1000 Mbps
|-
| WiFi
| align="center" | 2x dual-band WiFi antennas embedded in enclosure
| align="center" | [http://www.intel.com/content/www/us/en/wireless-products/dual-band-wireless-n-7260-bluetooth-brief.html Intel Wireless-N 7260BN] w/ BT 4.0 preinstalled 2x dual-band WiFi antennas embedded in enclosure
|-
| Audio
| align="center" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via HDMI
| align="center" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via HDMI Rear-panel 3.5mm headset jack
|-
| USB 2.0 Ports
| align="center" | 2x rear, 1x front, 2x via internal pin header
| align="center" | 2x rear
|-
| USB 3.0 Ports
| align="center" | None
| align="center" | 1x front
|-
| Consumer IR Port
| align="center" | None
| align="center" | Front Panel
|-
| MiniPCIe Slots
| align="center" | 1x full-length, 1x half-length
| align="center" | 1x half-length, used by WiFi card
|-
| Included in-box
| align="center" | Fan/heatsink, 19VDC 65W AC adapter, VESA mount
| align="center" | Fan/heatsink, 12VDC 36W wall-mount AC adapter w/ 4x multi-country plugs, VESA mount
|-
| Chassis / Enclosure
| align="center" | Plastic & aluminum, 4.59” × 4.41” × 1.55” (116.6mm × 112.0mm × 39.0mm)
| align="center" | Plastic & aluminum, 4.59” × 4.41” × 2.03” (116.6mm × 112.0mm × 51.5mm)
|-
| AC Power Cord
| align="center" | Not included
| align="center" | NA; AC adapter is wall-mount
|-
| Manufacturer Links
| style="text-align: center;" |[http://www.intel.com/p/en_US/support/category/dsktpboards/dk-dccp847dye/doc_guide?format-type=Technical+Documents Technical Documentation] 
[http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+DCCP847DYE Latest BIOS and Drivers] 
[http://www.intel.com/content/www/us/en/desktops/desktop-kit-dccp847dye-interactive-layout-demo-video.html Interactive Product Layout]
| style="text-align: center;" |[http://www.intel.com/p/en_US/support/category/dsktpboards/dk-dn2820fyk/doc_guide?format-type=Technical+Documents Technical Documentation] 
[http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=3782 Latest BIOS and Drivers]
|}

* 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!

The Celeron-based NUC can play everything XBMC can including 1080p SBS 3D. It will struggle with full frame packed 3D. Boot up time direct into XBMC is less than 10 seconds. It is entirely possible to create a system with an 32GB mSATA SSD and 4GB RAM, which will be overkill when you want to run OpenELEC but might be interesting in case you are considering a Windows build. For a cheap alternative with upgrade potential, you could use the internal USB headers to run the entire system from a USB stick. If you read the [http://forum.xbmc.org/showthread.php?tid=140534 NUC thread], there are screen caps of prices to help you compare to today's prices.

Skinswise, Confluence, Ace or Bello are wonderful to use and very fluid. Once you start using the heavier skins that utilise many addons, such as Aeon Nox, MQ3, MQ4 you will notice they run smooth but not as fluid as what can be enjoyed on the i3 & i5 models.

=== Core i3-based ===
There are six different NUCs equipped with Core i3 processors. The table below shows the similarities and differences:
{| class="prettytable"
|-
| width="100" | Model Number
| width="250" align="center" | [http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-kit-dc3217by.html DC3217BY]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-kit-dc3217iye.html DC3217IYE]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-d34010wyk.html D34010WYK]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-d34010wykh.html D34010WYKH]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i3ryk.html NUC5I3RYK]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i3ryh.html NUC5I3RYH]
|-
| CPU
| colspan="2" style="text-align: center;" | [http://ark.intel.com/products/65697/ i3-3217U] w/ HD Graphics 4000
| colspan="2" style="text-align: center;" | [http://ark.intel.com/products/75107/ i3-4010U] w/ HD Graphics 4400
| colspan="2" style="text-align: center;" | [http://ark.intel.com/products/75107/ i3-5010U] w/ HD Graphics 5500
|-
| RAM
| colspan="2" style="text-align: center;" | Dual-channel DDR3 1333/1600 MHz 2x SO-DIMMs, 16 GB total max.
| colspan="4" style="text-align: center;" | Dual-channel 1.35V DDR3L 1333/1600 MHz 2x SO-DIMMs, 16 GB total max.
|-
| Chipset
| colspan="2" style="text-align: center;" | [http://www.intel.com/content/www/us/en/chipsets/performance-chipsets/mobile-chipset-qs77.html Intel QS77]
| colspan="2" style="text-align: center;" | N/A; [http://software.intel.com/en-us/articles/an-introduction-to-the-intel-4th-generation-core-processor CPU is an SoC]
| colspan="2" style="text-align: center;" | N/A; CPU is an SoC
|-
| Display
| style="text-align: center;" | 1x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI 1.4a], full-size 1x [http://en.wikipedia.org/wiki/Thunderbolt_(interface) Thunderbolt] / [http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort 1.1a]
| style="text-align: center;" | 2x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI 1.4a], full-size
| colspan="4" style="text-align: center;" | 1x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 MiniHDMI 1.4a] 1x [http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort 1.2]
|-
| width="100" | Mass storage
| width="250" align="center" | mSATA SSD support via 1x full-length MiniPCIe slot
| width="250" align="center" | mSATA SSD support via 1x full-length MiniPCIe slot
| width="250" align="center" | mSATA SSD support via 1x full-length MiniPCIe slot
| width="250" align="center" | 2.5" SSD or HDD w/ 9.5mm max height SATA data and power connectors provided and mSATA SSD support via 1x full-length MiniPCIe slot
| width="250" align="center" | M.2 SSD
| width="250" align="center" | M.2 SSD and 2.5" SSD or HDD w/ 9.5mm max height SATA data and power connectors provided
|-
| Ethernet
| style="text-align: center;" | None
| colspan="5" style="text-align: center;" | 1x RJ45, 10/100/1000 Mbps
|-
| Consumer IR Receiver
| colspan="2" align="center" | None
| colspan="4" align="center" | Front panel
|-
| WiFi Antennae
| colspan="4" style="text-align: center;" | 2x dual-band, embedded in enclosure
| colspan="4" style="text-align: center;" | Bluetooth 4.0
|-
| Audio
| style="text-align: center;" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI] and
[http://en.wikipedia.org/wiki/Thunderbolt_(interface) Thunderbolt]/[http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort]
| style="text-align: center;" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI]
| colspan="4" style="text-align: center;" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI] and [http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort] Front-panel 3.5mm headset jack
|-
| USB 2.0 Ports
| style="text-align: center;" | 2x rear, 1x front
| style="text-align: center;" | 2x rear, 1x front 2x via internal pin header
| colspan="4" style="text-align: center;" | 2x via internal pin header
|-
| USB 3.0 Ports
| style="text-align: center;" | None
| style="text-align: center;" | None
| colspan="4" style="text-align: center;" | 2x rear, 2x front
|-
| MiniPCIe Slots
| colspan="4" style="text-align: center;" | 1x full-length w/ [http://en.wikipedia.org/wiki/Serial_ATA#Mini-SATA_.28mSATA.29 mSATA] support, 1x half-length
| colspan="2" style="text-align: center;" | 1x M.2 slot with PCIe X4 lanes

|-
| Included in-box
| colspan="6" style="text-align: center;" | Fan/heatsink, 19VDC 65W AC adapter, VESA mount
|-
| Chassis / Enclosure
| colspan="2" align="center" | Plastic & aluminum, 4.59” × 4.41” × 1.55” (116.6mm × 112.0mm × 39.0mm)
| align="center" | Plastic & aluminum, 4.59" x 4.41" x 1.36" (116.6mm x 112.0mm x 34.5mm)
| align="center" | Plastic & aluminum, 4.59" x 4.41" x 1.95" (116.6mm x 112.0mm x 49.5mm)
| colspan="2" align="center" | Plastic & aluminum, 4.52" x 4.37" x 1.36" (115mm × 111mm × 34.5mm)

|-
| AC Power Cord
| colspan="2" align="center" | Not included
| colspan="4" align="center" | Included in some SKUs
|-
| Manufacturer Links
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/dk-dc3217by/doc_guide?format-type=Technical+Documents Technical Documentation] [http://www.intel.com/p/en_US/support/highlights/dsktpboards/dk-dc3217by Latest BIOS and Drivers] [http://www.intel.com/content/www/us/en/desktops/desktop-kit-dc3217by-interactive-layout-demo-video.html Interactive Product Layout]
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/dk-dc3217iye/doc_guide?format-type=Technical+Documents Technical Documentation] [http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+DC3217IYE Latest BIOS and Drivers] [http://www.intel.com/content/www/us/en/desktops/desktop-board-dc3217iye-interactive-layout-demo-video.html Interactive Product Layout]
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/dk-d34010wyk/doc_guide Technical Documentation] [http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+D34010WYK Latest BIOS and Drivers] [http://www.intel.com/content/www/us/en/nuc/nuc-kit-d34010wyk-interactive-layout-demo-video.html Interactive Product Layout]
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/dk-d34010wyk/doc_guide Technical Documentation] [http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+D34010WYK Latest BIOS and Drivers] [http://www.intel.com/content/www/us/en/nuc/nuc-kit-D34010WYKH-interactive-layout-demo-video.html Interactive Product Layout]
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/nuc5i3ryh/doc_guide Technical Documentation] [https://downloadcenter.intel.com/SearchResult.aspx?ProdId=3851 Latest BIOS and Drivers]
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/nuc5i3ryk/doc_guide Technical Documentation] [https://downloadcenter.intel.com/SearchResult.aspx?ProdId=3852 Latest BIOS and Drivers]
|}

Can software decode most formats if needed. Does everything the Celeron can do and full frame packed 3D. Good for an HTPC that also needs light gaming and maybe some more heavy Windows applications. If you don't need those things, then you might want to stick with the Celeron to save some money.

{| border: 1px solid #BBB; margin: .46em .2em;"
|- style="font-size: 86%;"
| valign="top" align="center" |[[File:DC3217BY.png|200px]] Intel NUC based on the 3rd-Gen Core i3 DC3217BY
| valign="top" align="center" |[[File:DC3217IYE.png|200px]] Intel NUC based on the 3rd-Gen Core i3 DC3217IYE
| valign="top" align="center" |[[File:D34010WYK.png|200px]] Intel NUC based on the 4th-Gen Core i3 D34010WYK
| valign="top" align="center" |[[File:D34010WYKH.png|200px]] Intel NUC based on the 4th-Gen Core i3 D34010WYKH
|}

=== Core i5-based ===
There are three NUCs models with Core i5 processors. The table below shows the similarities and differences:
{| class="prettytable"
|-
| width="100" | Model Number
| width="250" align="center" | [http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-kit-dc53427hye.html DC53427HYE]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-d54250wyk.html D54250WYK]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-d54250wykh.html D54250WYKH]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i5myhe-board-nuc5i5mybe.html NUC5I5MYHE]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i5ryh.html NUC5I5RYH]
| width="250" align="center" | [http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i5ryk.html NUC5I5RYK]
|-
| CPU
| style="text-align: center;" | [http://ark.intel.com/products/64903/ i5-3427U] [http://www.intel.com/content/www/us/en/architecture-and-technology/vpro/vpro-technology-general.html vPro] w/ HD Graphics 4000
| colspan="2" style="text-align: center;" | [http://ark.intel.com/products/75028/ i5-4250U] w/ HD Graphics 5000
| colspan="3" style="text-align: center;" | [http://ark.intel.com/products/75107/ i3-5010U] w/ HD Graphics 5500
|-
| RAM
| style="text-align: center;" | Dual-channel DDR3 1333/1600 MHz 2x SO-DIMMs, 16 GB total max.
| colspan="2" style="text-align: center;" | Dual-channel 1.35V DDR3L 1333/1600 MHz 2x SO-DIMMs, 16 GB total max.
|-
| Chipset
| style="text-align: center;" | [http://www.intel.com/content/www/us/en/chipsets/performance-chipsets/mobile-chipset-qs77.html Intel QS77]
| colspan="2" style="text-align: center;" | N/A; [http://software.intel.com/en-us/articles/an-introduction-to-the-intel-4th-generation-core-processor CPU is an SoC]
|-
| Display
| style="text-align: center;" | 1x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI 1.4a], full-size 2x [http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort 1.1a]
| colspan="2" style="text-align: center;" | 1x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 MiniHDMI 1.4a] 1x [http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort 1.2]
|-
| Ethernet
| colspan="3" style="text-align: center;" | 1x RJ45, 10/100/1000 Mbps
|-
| Consumer IR Receiver
| align="center" | None
| colspan="2" align="center" | Front panel
|-
| WiFi Antennae
| colspan="3" style="text-align: center;" | 2x dual-band, embedded in enclosure
|-
| Audio
| style="text-align: center;" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI] and [http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort]
| colspan="2" style="text-align: center;" | [http://www.intel.com/content/www/us/en/chipsets/high-definition-audio.html Intel HD Audio]; 7.1 digital audio via [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI], [http://en.wikipedia.org/wiki/MiniDP Mini DisplayPort] and front-panel 3.5mm headset jack
|-
| USB 2.0 Ports
| style="text-align: center;" | 2x rear, 2x via internal pin header
| colspan="2" style="text-align: center;" | 2x via internal pin header
|-
| USB 3.0 Ports
| style="text-align: center;" | 1x front
| colspan="2" style="text-align: center;" | 2x rear, 2x front
|-
| MiniPCIe Slots
| colspan="3" style="text-align: center;" | 1x full-length w/ [http://en.wikipedia.org/wiki/Serial_ATA#Mini-SATA_.28mSATA.29 mSATA] support, 1x half-length
|-
| Included in-box
| colspan="3" style="text-align: center;" | Fan/heatsink, 19VDC 65W AC adapter, VESA mount
|-
| Chassis / Enclosure
| align="center" | Plastic & aluminum, 4.59” × 4.41” × 1.55” (116.6mm × 112.0mm × 39.0mm)
| align="center" | Plastic & aluminum, 4.59" x 4.41" x 1.36" (116.6mm x 112.0mm x 34.5mm)
| align="center" | Plastic & aluminum, 4.59" x 4.41" x 1.95" (116.6mm x 112.0mm x 49.5mm)
|-
| AC Power Cord
| align="center" | Not included
| colspan="2" align="center" | Included in some SKUs
|-
| Manufacturer Links
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/dk-dc53427hye/doc_guide Technical Documentation] [http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+DC53427HYE Latest BIOS and Drivers] [http://www.intel.com/content/www/us/en/nuc/dc53427hye-interactive-layout-demo-video.html Interactive Product Layout]
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/dk-d54250wyk/doc_guide Technical Documentation] [http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+D54250WYK Latest BIOS and Drivers] [http://www.intel.com/content/www/us/en/nuc/nuc-kit-d54250wyk-interactive-layout-demo-video.html Interactive Product Layout]
| style="text-align: center;" | [http://www.intel.com/p/en_US/support/category/dsktpboards/dk-d54250wyk/doc_guide Technical Documentation] [http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+D54250WYK Latest BIOS and Drivers] [http://www.intel.com/content/www/us/en/nuc/nuc-kit-d54250wykh-interactive-layout-demo-video.html Interactive Product Layout]
|}

{| border: 1px solid #BBB; margin: .46em .2em;"
|- style="font-size: 86%;"
| valign="top" align="center" |[[File:DC53427HYE.png|200px]] Intel NUC based on the 3rd-Gen Core i5 DC53427HYE
| valign="top" align="center" |[[File:D54250WYK.png|200px]] Intel NUC based on the 4th-Gen Core i5 D54250WYK
| valign="top" align="center" |[[File:D54250WYKH.png|200px]] Intel NUC based on the 4th-Gen Core i5 D54250WYKH
|}
{{collapse bottom}}

== Known issues ==
=== Windows ===
* Having graphical UI corruption with a NUC that uses Intel HD4000 graphics? Try these beta graphics drivers: [http://downloadmirror.intel.com/22938/a08/Win32_1533b.zip 32-bit] • [http://downloadmirror.intel.com/22935/a08/Win64_1533b.zip 64-bit]. [http://www.techblo.gg/?p=231]

* 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!

=== Hi10P / 10bit ===
{{Main|Hi10P}}
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 [https://www.youtube.com/watch?v=myvNa9Sk0Y4 here] ). Frames might start dropping at around 18Mbps, but common anime releases seem to have no significant issues. For more info, see [http://forum.xbmc.org/showthread.php?tid=171981 this thread] on the XBMC forum.

=== Unreliable Wireless Devices attached to USB 3.0 ports ===
* Use a USB extension cable to move the device as far away from the USB port as possible. USB 3.0 can cause wireless interference. [http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html Intel has released a whitepaper documenting the issue.]

== Mods ==
Here are some mods the community has done.
=== 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 [http://lightdims.com LightDims], which worked fantastically.

=== Fanless cases ===
There are several fanless cases available for the NUC:

Logic Supply offers a fanless case, the [http://www.logicsupply.com/components/cases/fanless/ml300/ ML300], compatible with the following Intel NUC motherboards: [http://www.logicsupply.com/components/motherboards/intel-core/dcp847ske/ DCP847SKE], [http://www.logicsupply.com/components/motherboards/intel-core/d33217gke/ D33217GKE], and [http://www.logicsupply.com/components/motherboards/intel-core/d53427rke/ D53427RKE]. The fully configured system is also available, the [http://www.logicsupply.com/computers/processor/intel-core/core-ml300/ Core-ML300].

The Haswell version, the [http://www.logicsupply.com/components/cases/fanless/ml320/ ML320] is in production available to pre-order as well as the fully configured system version, the [http://www.logicsupply.com/computers/processor/intel-core/core-ml320/ 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/

== Other tips, tricks, and advice ==
=== Linux ===
==== 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:

<code>$ sudo gdisk -l /dev/sda</code>

GPT fdisk (gdisk) version 0.8.7
<poem>
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.
</poem>

==== 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 [https://communities.intel.com/message/233970#233970]. So first update to Linux 3.15, if required.

For Ubuntu the kernel packages are available at [http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/ 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:
<pre>$ 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</pre>
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
<pre>$ uname -r
3.15.0-031500rc8-generic</pre>

The same [https://communities.intel.com/message/231175#2311750 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:
<pre>#! /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</pre>

Make the new file executable using:
<pre>$ chmod +x /etc/rc2.d/S18fix-cir</pre>

The system log should show something similar to these lines after rebooting:
<pre>$ 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</pre>

Next install lirc:
<pre>$ apt-get install lirc</pre>
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):
<pre>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"
</pre>
(the other settings are not important)

Now the CIR device should be supported by lirc. Time to [[HOW-TO:Setup Lirc|configure your remote]]

== Links ==
* http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/nuc.html - Intel's NUC product page
* [[Wikipedia:Next Unit of Computing]] - Wikipedia page on the NUC
* http://forum.xbmc.org/showthread.php?tid=140534 - XBMC NUC resource thread
* http://www.impactics.com/d1nu1-b/ - impactics fanless NUC case
* http://forum.xbmc.org/showthread.php?tid=166886 - Celeron NUC with mods
* http://www.simerec.com - install IR on/off capabilities (NUC can sleep/wake without mods)
* http://www.intel.com/content/dam/www/public/us/en/documents/guides/nuc-i3-home-theater-solution-guide.pdf - Intel's NUC + XBMC setup guide
* http://www.logicsupply.com/components/cases/nuc/ - Logic Supply NUC Cases
* http://www.logicsupply.com/computers/feature/nuc/ - Logic Supply NUC Computers

== Random notes ==
{{large|''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.''}}

*

[[Category:HTPC]]
[[Category:Manual]]
[[Category:X86]]

Archive:Chromebox

2015-03-24T18:45:06Z

Jolan: /* Troubleshooting, Known Issues, Fixes/Workarounds */

{{Infobox information appliance
| name = Chromebox
| image = [[File:Asus_chromebox.jpg|300px]]
| releasedate = 2014-03-14 (US)
| os = ChromeOS
| cpu = Intel® Celeron 2955U/2957U Intel® Core i3-4010U/4030U Intel® Core i7-4600U
| graphics = Intel® HD Graphics/GT1 (Celeron) Intel® HD Graphics 4400/GT2 (i3/i7)
| storage = 16GB internal SSD (M.2 SATA)
| memory = 2GB/4GB/8GB standard, 16GB max Dual Channel DDR3L-12800
| connectivity = HDMI 1.4a DisplayPort 1.2a Bluetooth 4.0 USB 3.0 (4x) 802.11 abgn/AC wifi 10/100/1000 Ethernet 2 -in-1 Card Reader 3.5mm headphone plug
| dimensions = 4.88 x 4.88 x 1.65 inch (WxDxH)
}}
[[File:Asus_chromebox_ports.jpg|right|300px|Asus Chromebox Rear Ports|thumb]]
[[File:Asus_chromebox_ports_2.jpg|right|300px|Asus Chromebox Side/Front Ports|thumb]]
{{mininav|[[Devices]]|[[x86 hardware]]}}

{{note|This page was originally written for the ASUS ChromeBox, but all of the information is valid for the HP, Acer, and Dell Chromeboxes as well. The hardware is virtually identical: the Acer has a slightly different form factor; the HP model has only 1 dimm slot (vs the 2 the others have); the fan of the HP is also a bit louder than the others (with the Asus being the most quiet); the Dell models have an 802.11 AC wifi module, whereas the others only have 802.11 abgn.
 
}}

== ChromeBox Overview ==

The Haswell Celeron-based Chromebox is small, lightweight x86-64 PC that natively runs ChromeOS, but with a few simple tweaks, has the capability to run any Linux-based OS. It features HDMI and DisplayPort video outputs (which can be used simultaneously), 4x USB 3.0 ports, gigabit Ethernet, an SD card slot, and built-in 802.11a/b/g/n wireless and Bluetooth 4.0.

Capability wise, the ChromeBox fully supports hardware accelerated H.264/MPEG-2/VC-1 video playback at up to 2160p24/p30 (4K), proper 24p output, and full 7.1/HD audio bitstream output (Linux only). 3D playback is supported (HSBS/HTAB), though the decoding of MVC streams (as used in 3D Blu-ray ISOs) is not supported under Linux at this time; the hardware itself is capable. Hi10 H.264 1080p playback is software decoded, but works well with few exceptions. 2160p60 is available only via DisplayPort (and only for UI/desktop functionality - the Celeron GPU doesn't have the horsepower for 2160p60 video playback), as HDMI 1.4a is limited to 2160p30. H.265/HEVC is software (CPU) decoded, so playback is limited to 1080p and low/moderate bit-rates. From a purely Kodi/media playback standpoint, there's no advantage to the Core i3/i7 models over the Celeron model (outside of 2160p60 video playback, which the i3/i7's HD4400 GPU can handle), or to upgrading the RAM or SSD.

The ChromeBox uses customized open-source firmware components (mainly [http://www.coreboot.org coreboot]) to boot ChromeOS in a secure/verified manner. By putting it in developer mode, we disable the verified boot restriction, and allow the ChromeBox to boot in "legacy mode" (via a legacy boot payload, [http://www.seabios.org SeaBIOS]), which enables other operating systems (eg: OpenELEC, Ubuntu/Kodibuntu) to be installed / dual booted. If ChromeOS isn't needed, then custom firmware can be installed to directly boot the legacy BIOS. A simplified overview of the ChromeBox boot process is shown here (click for full-size):
 
[[File:ChromeBox_boot_process.png|400px]]
 
This wiki page will guide you through the steps necessary to put the ChromeBox into developer mode and set it up in either a dual boot or standalone (non-ChromeOS) configuration. The majority of the process has been automated via the ChromeBox EZ Setup Script, making it safe and easy to run Linux/Kodi on your ChromeBox.

== Device Preparation ==

=== Disable Firmware Write Protect ===

Disabling the firmware write protect will allow us to shorten the timeout on the developer boot screen (from 30s to ~1s) in a dual boot configuration, and optionally boot directly in "legacy mode" (and into Ubuntu or OpenELEC). Disabling the write protect is also necessary for standalone setups so that the stock firmware can be replaced with a custom version.

With the device powered off and unplugged:

# Remove (4) rubber feet from bottom of unit
# Remove (4) screws under rubber feet
# Separate two halves of unit. Tip: partially insert the screw removed from the notched end, but do not re-thread it. Use it to help separate the two halves.
# Remove write-protect screw circled below:
#::Asus/HP/Dell: [[File:Inside-chrome1.jpg|300px]]
#::Acer: [[File:Acer wp screw.png|400px]]
#:: Note: the write-protect screw on the Acer model is under the heat pipe, which needs to be removed to access it. Be sure to smooth out the heatsink grease/pad before reinstallation of the heat sink / heat pipe.
# Reassemble in reverse order

'''Important:''' The write-protect screw should be left out permanently.
 
 

=== Put in Developer Mode ===

Putting the ChromeBox in developer mode will disable verified boot mode, and allow you to access the underlying Linux operating system features necessary for installing/running Kodi (via OpenELEC/Ubuntu).

'''WARNING''': This will erase all user data on the device.
 
 
With the device powered off:
# Insert a paperclip into the hole left of the SD card slot and press the recovery button
#: [[File:Recoverybutton.png|200px]]
# Power on the device, then remove the paper clip
# When greeted with the recovery screen, press [CTRL-D] to enter developer mode
# Press the recovery button (with paperclip) to confirm.
 
After confirming, the device will reboot and wipe any existing user data - this will take ~5 minutes. Afterwards, the ChromeBox will be in developer mode (vs verified boot mode), and the developer boot screen (shown below) will be displayed at each boot.
 
 

[[File:ChromeBox_dev_boot.jpg|400px]]

The developer boot screen has a warning about OS verification being off. '''Do not hit [SPACE]''', as it will return the device to verified boot mode. The ChromeBox must remain in developer mode, else you will potentially have to redo the setup from the beginning. The developer mode boot screen has a ~30s timeout, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.
 
 

=== Perform a Factory Reset ===

A factory reset is not needed for a standalone setup, but must be performed prior to any dual-boot (re)install.

# Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or use the [https://chrome.google.com/webstore/detail/chromebook-recovery-utili/jndclpdbaamdhonoechobihbbiimdgai?hl=en ChromeBook Recovery Utility from the Chrome web store].

Note: Google's recovery tool can be picky about what kind/size of USB/SD media you use. If one USB stick doesn't work, try another.

# With the device powered off, use a paperclip to press the Recovery button and power on the device
# Insert the recovery media (USB or SD) when prompted
 
Note that this will re-partition the internal hard drive and restore the original copy of ChromeOS, erasing anything else on the drive. The ChromeBox will still be left in developer mode, and if you changed the Boot Options they will still be set - so be sure to reset them back to the 'ChromeOS + 30s default' option '''before''' performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery.
 
 
If you're having trouble creating the recovery media using Google's recovery tool above, you can manually download the recovery image and write it to a USB stick:
:*Download Recovery image:
:*:Asus: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6158.76.0_panther_recovery_stable-channel_mp.bin.zip
:*: HP: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6158.76.0_zako_recovery_stable-channel_mp-v2.bin.zip
:*:Acer: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6158.76.0_mccloud_recovery_stable-channel_mp.bin.zip
:*:Dell: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6158.76.0_tricky_recovery_stable-channel_mp.bin.zip
:* Download Win32 Disk Imager: http://sourceforge.net/projects/win32diskimager/
:* Unzip the recovery image; the file should be ~1.5 GB
:* Rename the recovery image extension from .bin to .img
:* Write the image to your USB media using Win32 Disk Imager
 
 

== Installation, Configuration, and Updating ==

=== OS and Kodi Installation ===
Kodi can be installed on the ChromeBox in a variety of ways. The two most common are via OpenELEC or Ubuntu+Kodi, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run (at least initially) from ChromeOS.
 
The EZ setup script will facilitate everything needed to install either a dual boot setup, or install a custom firmware which allows the installation of any Linux-based OS in standalone mode.
 
To run the ChromeBox E-Z Setup script, perform the following steps:

# Power on and boot to ChromeOS. Do not log in, but ensure a network connection is established.
# Hit CTRL-ALT-F2 to open command prompt
# Login with user chronos (no password required)
# Download and run the ChromeBox setup script using the following two commands (hit enter after typing each command):
#: <nowiki>curl -L -O http://goo.gl/3Tfu5W</nowiki>
#: <nowiki>sudo bash 3Tfu5W </nowiki>

Full instructions and a detailed explanation of the script's functions and usage can be found at the following forum thread: http://forum.kodi.tv/showthread.php?tid=194362
 
 
'''Note:''' If installing a Linux-based OS other than OpenELEC (eg, Ubuntu/Kodibuntu), you will most likely need to manually update the kernel for optimal operation. Kernel version 3.18.4 is the minimum recommended, as it has a fix for an Intel GPU bug that can cause hanging during video playback. Updating the kernel is OS-specific and beyond the scope of this wiki, but instructions are easily found by googling.
 
 

=== Dual Boot OS Selection ===
When dual booting with ChromeOS and OpenELEC/Ubuntu, due to the ChromeBox's firmware setup, there is no conventional boot menu. Instead, the OS selection is made via keyboard shortcuts on the developer mode boot screen (shown above): [CTRL-D] boots directly ChromeOS; [CTRL-L] boots the legacy BIOS (and whatever secondary OS is installed). The default OS and boot timeout are set using the 'Set Boot Options' feature of the EZ Setup Script.
 
 

=== Updating Kodi ===

==== OpenELEC ====

The Chromebox is, at its core, a standard x86_64 Intel system (albeit, like the NUC, with an ultra low power processor). The standard OpenELEC builds - labeled 'Generic x86_64' - work perfectly well, and it is recommended to use OpenELEC's auto-update feature (System --> OpenELEC --> System --> Automatic Updates: auto). If that doesn't work for some reason, or you want to update to a nightly/beta/RC build, you can manually update using the instructions on the [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC OpenELEC wiki].
 
 

=== Recommended Settings ===

==== Kodi General ====

* System-->Settings-->System: Settings Level:'''Expert'''
* System-->Settings-->System-->Video Output: Vertical blank sync:'''Enabled during video playback''' (or just 'Enabled' if you experience UI tearing)
* System-->Settings-->System-->Power Saving: Shutdown function:'''Suspend''' (sets IR power toggle to suspend)
* System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:'''20%'''
* System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:'''Selected''' (de-select if you have interlaced VC-1 content)
* System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:'''Selected'''
 
Also see the video playback settings as shown in the screenshots below. Change as needed, then hit 'Set as default for all videos' to save.
 
 
==== OpenELEC Specific ====

* System-->OpenELEC-->System: Automatic Updates:'''Auto'''
* System-->OpenELEC-->Network: Wait for network before starting Kodi:'''Selected''' (if using a external mysql database)
* System-->OpenELEC-->Services: Enable Bluetooth:'''Selected''' (if using Bluetooth)
* System-->Settings-->Videos-->Acceleration: Use SW Filter for VAAPI:'''Selected''' (OE 4.x only)
 
 

<gallery>
File:chromebox_video_accel_settings_1.png|ChromeBox Settings: Video/Acceleration
File:chromebox_video_playback_settings_1.png|ChromeBox Video Playback Settings (1/2)
File:chromebox_video_playback_settings_2.png|ChromeBox Video Playback Settings (2/2)
</gallery>

=== Switching between Standalone and Dual Boot configurations ===

If you have a dual boot setup and wish to switch to a standalone setup, the steps are no different than installing on a "fresh" system, though you can obviously skip the steps you have already performed (removing the write-protect screw, putting the box in developer mode). If you have an OpenELEC dual boot setup and are switching to an OpenELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and restore after performing the standalone setup.

If you have a standalone setup and wish to switch to a dual boot setup, you need to first [[Chromebox#Restoring_the_Stock_Firmware|restore the stock firmware]], then [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], after which you can continue with the dual boot setup.
 
 

== Recommended Accessories / Hardware Upgrades ==
 
For most users, there's no need to upgrade the ChromeBox's RAM or HDD; OpenELEC uses minimal RAM and disk space, and there's no benefit to upgrading. However, users who opt for a full Ubuntu/Kodibuntu setup, and plan on running lots of background processes etc, may find it beneficial to install additional RAM or upgrade to a larger SSD.
 
 
'''RAM:'''
: The ChromeBox has two (2) 204-Pin SODIMM slots (HP models only have one), which accept 1.35V DDR3-1600 (PC3-12800) modules. Known working modules include:
:* Crucial CT25664BF160B (2GB, 1.35v/1.5v)
:* Crucial CT2CP51264BF160B (8GB [4GB x2] 1.35v/1.5v)
:* Crucial CT2KIT102464BF160B (16GB [8GB x2] 1.35v/1.5v)
:* Hynix HMT351S6CFR8C-PB (2GB, OEM)
:* HP H6Y75AA (4GB, 1.35v)
: 
: Crucial also has a list of 1.35v-only compatible modules here: http://www.crucial.com/usa/en/compatible-memory-for/ASUS/chromebox
 
'''SDD:'''
: The ChromeBox uses a single 2242 M.2 SATA SSD (22mm x 42mm); stock is a 16GB unit (usually Sandisk or Kensington). Any M.2 SATA 2242 replacement drive should work without issue.
 
'''Remote Controls:'''
: The ChromeBox does not have a built-in IR sensor, and must therefore use a USB IR receiver (or a Bluetooth remote). In general, any remote/receiver listed on the Kodi wiki as fully working under Linux should be fine, though some have issues when connected to USB3 ports. A Microsoft eHome compatible remote/receiver is one of the most compatible, subject to the limitations listed in the 'Known Issues' section above. Specific models tested as working include:
:* [http://flirc.tv/ Flirc]
:*: Flirc users need to set the "sleep detection" bit and program a wake key when setting it up, otherwise absolutely any IR signal will wake up your box from sleep.
:* HP IR receiver model 5188-1667 (MCE/eHome)
:* HP IR receiver model 5187-4593 (MCE/eHome)
:* Microsoft IR receiver model 1040 (MCE/eHome)
:* Sony IR receiver model PCVA-IR8U (MCE/eHome)
:* HP IR remote/receiver kit [http://www.amazon.com/dp/B00AYE6JDO/ OVU400102/71] (MCE/eHome, includes 5187-4593 receiver)
:* Ortek IR remote/receiver kit [http://www.amazon.com/dp/B00224ZDFY/ VRC-1100] (MCE clone, receiver also works well w/Logitech Harmony remotes)
:* Rosewill RHRC-11002 remote (MCE clone, includes receiver model IR605)
:* Rosewill WMC RRC-127 remote/receiver
:* Microsoft XBOX 360 IR remote (with MCE/eHome receiver or Flirc)
:* Microsoft XBOX One IR remote (with MCE/eHome receiver or Flirc)
:* Logitech Harmony remotes (programmed as Microsoft Media Center Extender - not as a keyboard - with MCE/eHome receiver; not recommended for use with a Flirc)
:* Sony Playstation 3 (PS3) Bluetooth remote (works with built-in BT receiver; press/hold START + ENTER to pair)
:* Logitech Harmony Smart Hub (via Bluetooth, works with built-in BT receiver, [http://forum.kodi.tv/showthread.php?tid=194362&pid=1843165#pid1843165 see forum post here])
:* Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
:* Amazon FireTV / Fire Stick remotes (Bluetooth)
:NOTE: If you need to re-map remote buttons, you can use the [[Add-on:Keymap Editor|Keymap Editor Add-on]] to do so.

:'''Currently non-working''':
:* HP IR receiver model 5070-2584 (MCE/eHome)
:* AVS Gear HA-IR01SV (MCE/eHome)
:* All Topseed manufactured MCE IR receivers
 
'''USB Audio Devices''':
:As the ChromeBox only has HDMI and analog audio outputs, if you need SPDIF, then either a converter or external/USB device must be used. The following devices have been tested/confirmed working:
:* [http://www.amazon.com/gp/product/B0036VO4X4/ Turtle Beach Audio Advantage Micro II ] (plug/play in both OpenELEC and Win8.1)
:* ASUS Xonar U3 USB (OpenELEC: requires un-muting the SPDIF line, see [http://openelec.tv/forum/41-supported-hardware/71023-asus-xonar-u3-usb-soundcard this forum post])
 
'''HDMI-CEC''':
:The ChromeBox does not support HDMI-CEC natively, but support can be added using an [http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx external USB CEC adapter] from Pulse-Eight. The USB CEC Adapter needs power to the USB port BEFORE there is any video out, or it simply will not pass through any video signal. There are several ways to work around this:

:* Either always leave your Chromebox on, or just put it into standby; never turn it off
:* Use an externally powered source (eg, USB hub, TV set) to power the adapter (rather than the ChromeBox itself), so it always has power
:* If you have a spare HDMI port, you actually can split video in and control in for one HDMI channel using two physical HDMI ports. The video will be connected to the main port, and that's the port you use in the HDMI config settings in XBMC, and then you simply connect the USB CEC adapter to a spare HDMI port, does not appear to matter which.
 
 

== Troubleshooting, Known Issues, Fixes/Workarounds ==

Installation, Dual Booting, USB booting:
:* Some keyboards seem to have issues working on the ChromeOS developer boot screen (before the OS is booted), and therefore cannot be used to setup/install Kodi on a ChromeBox, or to select between OSes in a dual boot setup. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working. Most Bluetooth keyboards '''will not work''' due to the fact that they require the OS to be loaded in order to reconnect to the ChromeBox.
:*: An effort is underway on the forums to catalog which keyboards work (and which do not); the thread (which is being updated regularly) can be found here: http://forum.kodi.tv/showthread.php?tid=211797
:* Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed.
:*:This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS is installed.
::* If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, [[Chromebox#Perform_a_Factory_Reset|as listed in the Device Prep section above]]. Simply perform the factory reset, then redo the dual boot setup using the script as before.
::* If you have a standalone setup:
::*: If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.
::*: If you '''don't''' see the 'Press ESC for boot menu' text, then the issue is with your boot media, so try using a different USB flash drive.
:* If the install media created by the script doesn't work (or you forget to create it before rebooting), then you can simply download the latest stable version (or beta/RC if you'd like) from [http://openelec.tv/get-openelec/download/viewcategory/8-generic-builds OpenELEC's website here]. The ChromeBox runs the 'Generic x86-64' version of OpenELEC, and it's recommended that you download the disk image version, and create the install media, as per the instructions [http://wiki.openelec.tv/index.php/HOW-TO:Installing_OpenELEC/Creating_The_Install_Key#tab=DiskImage on the OpenELEC wiki].
:* Some TVs/displays are not able to show the developer boot screen due to the resolution it uses (1024x768 @ 60Hz), in which case you'll need to use a different display to complete the initial setup steps.
:* Many TVs have overscan enabled by default, which will cut off the text display of the ChromeOS shell. Be sure to set your TV to a mode which does not overscan (varies by manufacturer - often called 'just scan', 'exact' 'pixel perfect').
:* Using a '''passive''' DisplayPort-->HDMI cable/adapter is often problematic, and can cause the video output drop out after booting. Use either a straight DP cable or straight HDMI/HDMI-->DVI cable; if you have to use a DisplayPort-->HDMI adapter, be sure it is the '''active''' type.

Color Range Selection:
:* This topic is a bit of a minefield, but [http://forum.kodi.tv/showthread.php?tid=176718&pid=1756704#pid1756704 this post on the forums is a good read]. It's for a NUC, but it applies to the ChromeBox as well. On some displays, the display and Intel video driver are not able to automatically sync up (in terms of which color space is being used), leading to incorrect black/white levels. You can download/play the following video clip to test: [https://dl.dropboxusercontent.com/u/98309225/1-Grayscale%20Ramp%20.mp4 Grayscale Ramp test] (file courtesy of avsforum.com). The correct output will show the grayscale ramp having a smooth transition (rather than stair steps) from 16-235, with solid black/white past the dots at the ends. See: [https://dl.dropboxusercontent.com/u/98309225/grayscale_ramp_good.png correct grayscale ramp].
:*: Solution: add the following line to the autostart script and reboot the device:
:*::<nowiki>xrandr --output HDMI1 --set "Broadcast RGB" "Full"</nowiki>
:*: Use 'DP1' instead of 'HDMI1' if connected via the DisplayPort output. See [http://wiki.openelec.tv/index.php?title=Autostart.sh the OpenELEC Autostart wiki page] for more info.
:*: You may also need to select the Kodi option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.
:*: '''Note:''' If you want to output Limited color range, you are required to do the following setting as well: Settings-->Video-->Acceleration-->Prefer VAAPI Rendering: disabled/de-selected.

No Audio and/or corrupted video on Wakeup from Suspend:
:* Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output and/or corrupted video output until the Chromebox is rebooted.
:*: Solution: If using a universal remote, such as a Harmony, ensure that you are turning off (suspending) the ChromeBox '''before''' your AVR/TV, and turning it on (resuming) '''after''' the AVR/TV.
:*: Solution: download/enable a script that will force the ChromeBox to reset the audio/video output on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/01-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 01-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox
:*: Note: If connected via the DisplayPort output, use a text editor (eg, nano) to edit the script and replace references to 'HDMI1' with 'DP1'.

Video Playback:
:* An Intel Linux video driver bug causes intermittent freezes where the video locks up but audio keeps playing.
:*: Solution: This issue is fixed as of OpenELEC 5.0.0; users running a different Linux distro should be sure to update their kernel to 3.18.4 or 3.19.0 (or newer).

Remote Controls:
:* Most MCE IR receivers work properly now when connected to USB3 ports under Linux with kernel 3.16+ (older kernels will require a patch/fix); OpenELEC 4.0+ is fully up to date. The version of Ubuntu installed by the ChromeBox EZ setup script in a dual boot setup also includes an up-to-date kernel. However, some buggy MCE receivers still do not work properly (at all), as noted below in the Hardware/Remotes section.

:: For standalone Ubuntu (or any other distro) installs, you will need to update to a 3.16 (or later) kernel.

Unreliable Wireless Devices attached to USB 3.0 ports:
:* Use a USB extension cable to move the device as far away from the USB port as possible. USB 3.0 can cause wireless interference. [http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html Intel has released a whitepaper documenting the issue.]

Power Management:
:* Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but works reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.
:* Note: WOL only works when the ChromeBox is suspended, not fully powered off, and requires the MAC address of the box to be set (eg, in YATSE)

Windows 8 (unsupported):
:* HDMI audio doesn't work, at all, even with the proper drivers loaded. Either use the analog audio output, an external USB sound card, or run Linux.
:* Bluray disc playback doesn't work, as PowerDVD and WinDVD report that the video drivers are not supported, even though they report the hardware is capable.
:* Update: now fixed in 2015/01/29 coreboot firmware. The CPU fan will shut down at boot and not come back on unless a utility like SpeedFan is used to start it.

Linux Video Tearing:
:* Some users may experience screen tearing under the Linux desktop, or when watching video (e.g., Netflix). The fix for this is [https://wiki.archlinux.org/index.php/Intel_Graphics#Tear-free_video documented on the Arch Wiki], and copied here for convenience.

:: from a terminal/shell prompt:
:::<nowiki>sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf</nowiki>

:: copy/paste the following:

:::<nowiki>Section "Device"</nowiki>
::::<nowiki>Identifier "Intel Graphics"</nowiki>
::::<nowiki>Driver "intel"</nowiki>
::::<nowiki>Option "TearFree" "true"</nowiki>
:::<nowiki>EndSection</nowiki>

:: then save, exit, and reboot.

High CPU at Idle:
:* When running a Linux setup, there is high idle CPU usage with some older kernels which do not fully support the Haswell platform; be sure to update to the latest kernel available (at '''least''' 3.18.4). On some (mostly dual boot) setups, it may also be necessary to add the following kernel boot parameters to disable the TPM: tpm_tis.force=1 tpm_tis.interrupts=0

OpenELEC Fails to boot:
:* If the OS isn't shutdown cleanly, sometimes a filesystem check (fsck) will be automatically performed. In some cases, the automatic repair is unsuccessful, and an error will show:
::<nowiki>***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***</nowiki> 
::<nowiki>### Starting debugging shell... type exit to quit ###</nowiki> 
::<nowiki>sh: can't access tty; job control turned off</nowiki> 
::<nowiki>#_</nowiki> 
 
In this case, simply run fsck manually as instructed, using the following commands, hitting [enter] after each: 
 
For a standalone setup:
:<nowiki>fsck /dev/sda1</nowiki> 
:<nowiki>fsck /dev/sda2</nowiki> 
 
For a dual-boot setup:
:<nowiki>fsck /dev/sda6</nowiki> 
:<nowiki>fsck /dev/sda7</nowiki> 
 
After the fsck is run, type 'reboot' then hit [enter] and the system should boot normally.
 
 

== Firmware/BIOS Updating ==

As depicted in the overview section above, the ChromeBox's firmware consists of two main parts: the main firmware (coreboot), and the Legacy BIOS payload (SeaBIOS). Users running a dual-boot configuration only need to update the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it contains an updated SeaBIOS payload (which can not be updated separately).

'''NOTE''': Under normal conditions, the ChromeBox's firmware does not need to be updated after the initial install/update via the EZ Setup Script. As the old saying goes: if it ain't broke, don't fix it. Only update if you are having an issue that is specifically noted in the changelog as being addressed by a newer version.

Dual-boot users should simply boot to ChromeOS and re-download/re-run the EZ Setup Script, choosing the '''Update Legacy BIOS''' option under the Dual Boot heading.

Standalone users should also re-download/re-run the setup script, but instead choosing the '''coreboot firmware install/update''' option under the Standalone heading. As of v3.0, the script can be run under any version of Linux with a full bash shell. As OpenELEC does not have a full bash shell, OE users will need to use the (separate) standalone firmware update script, as described near the end of [http://forum.kodi.tv/showthread.php?tid=194362 the EZ Setup Script forum post].
 
 

== Resetting to Stock ==

If you have a dual boot setup, simply [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], then hit [space] on the developer mode boot screen to revert to verified boot mode. Done.

If you have standalone setup, it is necessary to restore the stock firmware before performing a factory reset to reload ChromeOS.

In order to do this, we will create a bootable USB stick with ChromiumOS (the open-source version of ChromeOS) and use that to re-flash the stock firmware, which you backed up before flashing the Coreboot firmware. If you didn't make a backup, we can use a copy extracted from Google's recovery image, but an actual backup is preferred.
 
 

# Create ChromiumOS USB Stick
#:* Download the latest AMD64OS daily build from http://arnoldthebat.co.uk/wordpress/chromium-os/. Be sure it's the 64-bit (AMD64OS) version, and the image version (.img.7z) and not the virtual machine version (.vdi.7z). Example: Camd64OS-20140527010101.img.7z
#:* Follow the instructions at the link above to extract and copy the image onto a USB disk. You will need at least a 4GB drive, and the contents of it will be erased. Do '''NOT''' use the same USB stick that you used for your firmware backup
# Get a ChromiumOS Shell Prompt
#:* Connect the ChromiumOS USB stick to the ChromeBox, power on, and select the USB stick from the boot menu. Boot into ChromiumOS
#:* Open a shell the same way as in ChromeOS: [CTRL]-[ALT]-[F2] and login as user 'chronos' with password 'password'
# Copy firmware backup file
#:* If you have your firmware backup on USB, connect it now, then run the following commands from the shell prompt
#:*:<nowiki>mkdir /tmp/usb</nowiki>
#:*:<nowiki>sudo mount /dev/sdc /tmp/usb (If this fails, use /dev/sdc1 instead of /dev/sdc)</nowiki>
#:*:<nowiki>cp /tmp/usb/stock-firmware.rom ./</nowiki>
#:*:<nowiki>sudo umount /tmp/usb</nowiki>
#:* If you don't have a firmware backup, then run the following command to download one extracted from the recovery image
#:*:(Asus) <nowiki>curl -L -o stock-firmware.rom https://db.tt/sLQL9i1p</nowiki>
#:*:( HP ) <nowiki> curl -L -o stock-firmware.rom https://db.tt/8NmzlrZ6</nowiki>
#:*:(Acer) <nowiki> curl -L -o stock-firmware.rom https://db.tt/Nh5EeEti</nowiki>
#:*:(Dell) <nowiki> curl -L -o stock-firmware.rom https://db.tt/IXLtQ097</nowiki>
# Restore stock firmware
#:* After completing the above, then run the following commands from the shell prompt
#:*:<nowiki>sudo flashrom -w stock-firmware.rom</nowiki>
#:*Assuming it is successful, then:
#:*:<nowiki>sudo poweroff</nowiki>

You can now remove the ChromiumOS USB drive (and firmware backup USB drive). Proceed to [[ASUS_Chromebox#Perform_a_Factory_Reset|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
 
 

[[Category:Hardware]]
[[Category:HTPC]]
[[Category:x86]]

Raspberry Pi

2015-03-24T18:35:49Z

Jolan: /* Installing Kodi */

{{mininav|[[Devices]]}}

{{divbox|orange|| {{center| {{larger| Yes, Kodi works on the '''Raspberry Pi 2!''' }} }} }}

[[File:Single-board computer Raspberry Pi.jpg|320px|right]]

{{forum link2|1=For more info and help, check out the [http://forum.xbmc.org/forumdisplay.php?fid=166 XBMC Raspberry Pi support forum]}}
<section begin="intro" />The '''Raspberry Pi''' is an ARM powered, credit card sized computer developed in the UK by the Raspberry Pi Foundation for educational and hobbyist purposes. The low power computer is mass produced at very low prices and the high number of units sold gives it massive community support. As an XBMC HTPC, the Pi supports full 1080P video playback, supports most major codecs, most if not all XBMC add-ons, and a reasonably responsive GUI.<section end="intro" />

== Installing Kodi ==
{{Main|HOW-TO:Install Kodi on Raspberry Pi}}
<section begin="install"/>The easiest way to install Kodi on an R-Pi is to use one of these pre-made OS/Kodi packages:
* '''[[OpenELEC]] -''' [http://wiki.openelec.tv/index.php?title=Installing_OpenELEC_on_Raspberry_Pi Installing] • [http://wiki.openelec.tv/index.php?title=Raspberry_Pi_FAQ FAQ] • [http://openelec.tv/forum/124-raspberry-pi Help forum] • [[HOW-TO:Install XBMC on Raspberry Pi with USB drive|USB drive install]]
* '''[[OSMC]] -''' [https://osmc.tv/download/ Installing] • [https://osmc.tv/help/wiki FAQ] • [https://osmc.tv/help/ Help] • [https://discourse.osmc.tv Forum]
* '''[[XBian]] -''' [http://xbian.org/getxbian/ Installing] • [http://xbian.org/faq/ FAQ] • [http://xbian.org/getting-started/ Starters guide] • [http://forum.xbian.org/ Forum]
* '''Raspbian -''' http://michael.gorven.za.net/
* '''Arch Linux ARM -''' [http://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2 RPi2] • [http://archlinuxarm.org/platforms/armv6/raspberry-pi RPi1]
<section end="install"/>

== Frequently Asked Questions ==
{{see|Raspberry Pi FAQ}}

== Maximizing performance ==
<section begin="performance" />
* Use a lightweight skin such as the default Confluence, Amber, Quartz, Bellow, or xTV-SAF.

* Turn off RSS feeds and any scrolling text options for your skin.

* Use an SD card with good rewrite speeds. The class of the SD card doesn't always mean it will be faster, as that speed listing is for sustained reading and writing. For {{kodi}} random read/write speeds are more important. '''''[http://swag.raspberrypi.org/products/noobs-8gb-sd-card The class 4/6 Samsung SD cards sold on the Raspberry Pi Store] (the ones with NOOBS on them) typically have much better performance than most class 10 cards.''''' For more information about SD card speeds, check out this excellent thread on the R-Pi forum: ''' http://www.raspberrypi.org/forums/viewtopic.php?p=53159 '''

* You can also try to use a combination of SD and fast USB drive for your {{kodi}} install, but recent improvements to the software make it so that even just using a good SD card is about as fast as using a fast USB drive.

* Avoid using wifi. If you do use wifi, use a wifi adapter that contains two antenna (either internally or externally). Otherwise, stick to wired ethernet, local USB drives, or ethernet-over-power devices (like Homeplug, etc).

* If you are using wifi and it seems just on the edge of being fast enough, check out '''[[HOW-TO:Modify the video cache]]'''.

* Try using '''[[NFS]]''' file shares instead of SMB file shares.

* Try mounting network shares through OS rather than Kodi. This allows more tweaking of filesystem options, like chosing UDP and larger block sizes. See [http://forum.osmc.tv/showthread.php?tid=6825 This raspbmc thread for details]

* Overclock. Most Pi's can handle a significant overclock, as long as they have a good power supply. There is no universal setting that will work for everyone (except for the default speed that you get without overclocking). Try various overclocking settings and run {{kodi}} for a while and see if it's stable. If one group of overclocking settings causes crashes, try a group of settings that are lower than that. For more information about this check out this forum thread: ''' http://forum.xbmc.org/showthread.php?tid=199272 '''

* "Extract thumbnail and video information" from '''[[Settings/Video#File lists|file lists settings]]''' is disabled by default on the Pi as it improves browsing performance.

* For smoother video playback enable "Adjust display refresh rate to match video" from '''[[Settings/Video#Playback|playback settings]]'''

* When using dvdplayer "Sync playback to display" and "adjust PLL" for sync method are recommended. See '''[[Settings/Video#Playback|playback settings]]'''

* Make sure the video is using H.264 (up to High Profile. Hi10P will not work) or MPEG-4, or, if a codec was purchased and enabled, MPEG-2 or VC-1.

* Passthrough is recommended as it lowers CPU usage for DTS and AC3. Use '''[[Settings/System#Audio output|audio passthrough]]''' if your TV/receiver supports it.

* To determine which audio passthrough formats your HDMI-connected TV supports, you can log in to your chosen distribution, via SSH, and run this command: <code>/opt/vc/bin/tvservice a</code> (on OpenELEC: <code>tvservice -a</code>).

* Feeling adventurous? Check out the latest OpenELEC test builds, which often have even more speed improvements. Just remember that these builds can often be unstable: ''' http://forum.xbmc.org/showthread.php?tid=192380 '''

* Some additional advanced tips for speeding up boot times. {{editor note|Some of this can likely be broken up into individual bullet points for this list, but I haven't examined any of this in detail yet. I'm not sure which ones only improve boot time and which ones improve actual performance once already booted. If anyone wants to take a whack at this, please do.}} http://forum.xbmc.org/showthread.php?tid=201354

* For locally connected drives containing videos and music, the format of the drive can have an impact on read and write speeds. For example, NTFS tends to be much slower on any Linux-based system than the more native EXOFS formats (ext2, ext3, etc).

* If you use [[MySQL]] then you will want to make sure your images are pre-cached using the '''[[Texture Cache Maintenance utility]] tool'''. Local libraries typically don't need this as their images are cached when videos are scanned in. Using MySQL can improve performance as the database queries are handled by another machine.

* Organizing your movies in single folders for each movie, rather than all movies in one folder, is recommended. The individual folders reduce the time it takes for {{kodi}} to look for supporting media like external subtitles, making browsing, scanning and starting playback a little faster. You might also want to consider pre-scraping the meta data using a '''[[Library manager]]''' to reduce the time it takes to scan in both movies and TV shows.
<section end="performance" />

== Remote controls ==
[[File:gpioir.png|right|250px|thumb|Wiring instructions for a TSOP4838 GPIO IR sensor.]]
;GPIO IR receiver
:Don't have a CEC TV or a smartphone remote? For less than a dollar/euro, you can add an IR receiver to your Raspberry Pi that works with most MCE and Apple remotes (and a few others). Most {{kodi}} install options for the Pi should work with the GPIO IR out of the box, or by enabling a setting from within {{kodi}}. Go to a local electronics store or search on ebay for "<code>TSOP4838</code>" and use some simple jumper wires (or solder the pins directly, if you wish). ''(We need a link to a good, up to date GPIO IR guide. Most of the links I found are outdated and contain instructions for additional configurations that are no longer required. If you find a good link/guide, please add it to the wiki.)''

If you are using '''[[OpenELEC]]''' just add this to your config.txt file:
:<pre>device_tree_overlay=lirc-rpi</pre>

;[[CEC]]
:If your TV supports '''[[CEC]]''' then you should be able to use the remote control that came with your TV to control {{kodi}}. The remote control signals are sent over the HDMI cable and most often don't require any further settings or configuration.

;[[MCE remotes]]
:Various '''MCE''' USB receivers and remotes will work on the Pi.

;[[Keyboards]] and mice
:Any '''[[Keyboard]]''' such as wired, wireless, bluetooth. This includes remotes that are seen as keyboards, such as Rii remotes, the Mele F10-Pro remote, or the (very awesome) '''[[Flirc]]'''.

;[[Smartphone/tablet remotes]]
:Use your smartphone or tablet as a remote control.

;[[Web interface]]s
:Control {{kodi}} from anything that has a web browser.
{{-}}

== How good is it, really? ==
See for yourself: https://www.youtube.com/watch?v=ErWF2sYgJec 
{{youtube|ErWF2sYgJec}}

== Further reading ==
* [http://raspberrypi.org RaspberryPi.org]
* [http://elinux.org/RaspberryPiBoard Raspberry Pi Hub Wiki]
* [http://lea-linux.org/documentations/Raspberry_Pi Raspberry Pi French Wiki]
* [[Wikipedia:Raspberry Pi]]

==Random notes==
{{large|''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.''}}
*

{{Gotham updated}}

[[Category:Linux]]
[[Category:HTPC]]
[[Category:Raspberry Pi]]
[[Category:Broadcom]]
[[Category:ARM]]

Raspberry Pi

2015-03-24T18:33:15Z

Jolan: /* Installing Kodi */

{{mininav|[[Devices]]}}

{{divbox|orange|| {{center| {{larger| Yes, Kodi works on the '''Raspberry Pi 2!''' }} }} }}

[[File:Single-board computer Raspberry Pi.jpg|320px|right]]

{{forum link2|1=For more info and help, check out the [http://forum.xbmc.org/forumdisplay.php?fid=166 XBMC Raspberry Pi support forum]}}
<section begin="intro" />The '''Raspberry Pi''' is an ARM powered, credit card sized computer developed in the UK by the Raspberry Pi Foundation for educational and hobbyist purposes. The low power computer is mass produced at very low prices and the high number of units sold gives it massive community support. As an XBMC HTPC, the Pi supports full 1080P video playback, supports most major codecs, most if not all XBMC add-ons, and a reasonably responsive GUI.<section end="intro" />

== Installing Kodi ==
{{Main|HOW-TO:Install Kodi on Raspberry Pi}}
<section begin="install"/>The easiest way to install Kodi on an R-Pi is to use one of these pre-made OS/Kodi packages:
* '''[[OpenELEC]] -''' [http://wiki.openelec.tv/index.php?title=Installing_OpenELEC_on_Raspberry_Pi Installing] • [http://wiki.openelec.tv/index.php?title=Raspberry_Pi_FAQ FAQ] • [http://openelec.tv/forum/124-raspberry-pi Help forum] • [[HOW-TO:Install XBMC on Raspberry Pi with USB drive|USB drive install]]
* '''[[OSMC]] -''' [https://osmc.tv/download/ Installing] • [https://osmc.tv/help/wiki FAQ] • [https://osmc.tv/help/ Help] • [https://discourse.osmc.tv Forum]
* '''[[XBian]] -''' [http://xbian.org/getxbian/ Installing] • [http://xbian.org/faq/ FAQ] • [http://xbian.org/getting-started/ Starters guide] • [http://forum.xbian.org/ Forum]
* '''Raspbian -''' http://michael.gorven.za.net/
* '''Arch Linux ARM -''' [http://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2 Overview]
<section end="install"/>

== Frequently Asked Questions ==
{{see|Raspberry Pi FAQ}}

== Maximizing performance ==
<section begin="performance" />
* Use a lightweight skin such as the default Confluence, Amber, Quartz, Bellow, or xTV-SAF.

* Turn off RSS feeds and any scrolling text options for your skin.

* Use an SD card with good rewrite speeds. The class of the SD card doesn't always mean it will be faster, as that speed listing is for sustained reading and writing. For {{kodi}} random read/write speeds are more important. '''''[http://swag.raspberrypi.org/products/noobs-8gb-sd-card The class 4/6 Samsung SD cards sold on the Raspberry Pi Store] (the ones with NOOBS on them) typically have much better performance than most class 10 cards.''''' For more information about SD card speeds, check out this excellent thread on the R-Pi forum: ''' http://www.raspberrypi.org/forums/viewtopic.php?p=53159 '''

* You can also try to use a combination of SD and fast USB drive for your {{kodi}} install, but recent improvements to the software make it so that even just using a good SD card is about as fast as using a fast USB drive.

* Avoid using wifi. If you do use wifi, use a wifi adapter that contains two antenna (either internally or externally). Otherwise, stick to wired ethernet, local USB drives, or ethernet-over-power devices (like Homeplug, etc).

* If you are using wifi and it seems just on the edge of being fast enough, check out '''[[HOW-TO:Modify the video cache]]'''.

* Try using '''[[NFS]]''' file shares instead of SMB file shares.

* Try mounting network shares through OS rather than Kodi. This allows more tweaking of filesystem options, like chosing UDP and larger block sizes. See [http://forum.osmc.tv/showthread.php?tid=6825 This raspbmc thread for details]

* Overclock. Most Pi's can handle a significant overclock, as long as they have a good power supply. There is no universal setting that will work for everyone (except for the default speed that you get without overclocking). Try various overclocking settings and run {{kodi}} for a while and see if it's stable. If one group of overclocking settings causes crashes, try a group of settings that are lower than that. For more information about this check out this forum thread: ''' http://forum.xbmc.org/showthread.php?tid=199272 '''

* "Extract thumbnail and video information" from '''[[Settings/Video#File lists|file lists settings]]''' is disabled by default on the Pi as it improves browsing performance.

* For smoother video playback enable "Adjust display refresh rate to match video" from '''[[Settings/Video#Playback|playback settings]]'''

* When using dvdplayer "Sync playback to display" and "adjust PLL" for sync method are recommended. See '''[[Settings/Video#Playback|playback settings]]'''

* Make sure the video is using H.264 (up to High Profile. Hi10P will not work) or MPEG-4, or, if a codec was purchased and enabled, MPEG-2 or VC-1.

* Passthrough is recommended as it lowers CPU usage for DTS and AC3. Use '''[[Settings/System#Audio output|audio passthrough]]''' if your TV/receiver supports it.

* To determine which audio passthrough formats your HDMI-connected TV supports, you can log in to your chosen distribution, via SSH, and run this command: <code>/opt/vc/bin/tvservice a</code> (on OpenELEC: <code>tvservice -a</code>).

* Feeling adventurous? Check out the latest OpenELEC test builds, which often have even more speed improvements. Just remember that these builds can often be unstable: ''' http://forum.xbmc.org/showthread.php?tid=192380 '''

* Some additional advanced tips for speeding up boot times. {{editor note|Some of this can likely be broken up into individual bullet points for this list, but I haven't examined any of this in detail yet. I'm not sure which ones only improve boot time and which ones improve actual performance once already booted. If anyone wants to take a whack at this, please do.}} http://forum.xbmc.org/showthread.php?tid=201354

* For locally connected drives containing videos and music, the format of the drive can have an impact on read and write speeds. For example, NTFS tends to be much slower on any Linux-based system than the more native EXOFS formats (ext2, ext3, etc).

* If you use [[MySQL]] then you will want to make sure your images are pre-cached using the '''[[Texture Cache Maintenance utility]] tool'''. Local libraries typically don't need this as their images are cached when videos are scanned in. Using MySQL can improve performance as the database queries are handled by another machine.

* Organizing your movies in single folders for each movie, rather than all movies in one folder, is recommended. The individual folders reduce the time it takes for {{kodi}} to look for supporting media like external subtitles, making browsing, scanning and starting playback a little faster. You might also want to consider pre-scraping the meta data using a '''[[Library manager]]''' to reduce the time it takes to scan in both movies and TV shows.
<section end="performance" />

== Remote controls ==
[[File:gpioir.png|right|250px|thumb|Wiring instructions for a TSOP4838 GPIO IR sensor.]]
;GPIO IR receiver
:Don't have a CEC TV or a smartphone remote? For less than a dollar/euro, you can add an IR receiver to your Raspberry Pi that works with most MCE and Apple remotes (and a few others). Most {{kodi}} install options for the Pi should work with the GPIO IR out of the box, or by enabling a setting from within {{kodi}}. Go to a local electronics store or search on ebay for "<code>TSOP4838</code>" and use some simple jumper wires (or solder the pins directly, if you wish). ''(We need a link to a good, up to date GPIO IR guide. Most of the links I found are outdated and contain instructions for additional configurations that are no longer required. If you find a good link/guide, please add it to the wiki.)''

If you are using '''[[OpenELEC]]''' just add this to your config.txt file:
:<pre>device_tree_overlay=lirc-rpi</pre>

;[[CEC]]
:If your TV supports '''[[CEC]]''' then you should be able to use the remote control that came with your TV to control {{kodi}}. The remote control signals are sent over the HDMI cable and most often don't require any further settings or configuration.

;[[MCE remotes]]
:Various '''MCE''' USB receivers and remotes will work on the Pi.

;[[Keyboards]] and mice
:Any '''[[Keyboard]]''' such as wired, wireless, bluetooth. This includes remotes that are seen as keyboards, such as Rii remotes, the Mele F10-Pro remote, or the (very awesome) '''[[Flirc]]'''.

;[[Smartphone/tablet remotes]]
:Use your smartphone or tablet as a remote control.

;[[Web interface]]s
:Control {{kodi}} from anything that has a web browser.
{{-}}

== How good is it, really? ==
See for yourself: https://www.youtube.com/watch?v=ErWF2sYgJec 
{{youtube|ErWF2sYgJec}}

== Further reading ==
* [http://raspberrypi.org RaspberryPi.org]
* [http://elinux.org/RaspberryPiBoard Raspberry Pi Hub Wiki]
* [http://lea-linux.org/documentations/Raspberry_Pi Raspberry Pi French Wiki]
* [[Wikipedia:Raspberry Pi]]

==Random notes==
{{large|''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.''}}
*

{{Gotham updated}}

[[Category:Linux]]
[[Category:HTPC]]
[[Category:Raspberry Pi]]
[[Category:Broadcom]]
[[Category:ARM]]