Setting up an Intel NUC DN2820FYKH as a HTPC

Intel_NUC_4th_GenI recently did exactly this with an Intel NUC DN2820FYKH. This was a bit of a gamble because I wasn’t entirely sure the spec of the NUC was up to scratch for a home theatre PC.

Turns out, it actually is – with a couple of caveats which I’ll go into in a moment. You’ll need to add RAM (I went with 8G on mine) and a laptop drive. SSD will perform better, but it performs well on a standard 5400 RPM. The CeleronĀ DN2820FYKH performs quite admirably – I suspect the Core i3, i5 and i7 versions would do everything you need – albeit with a slightly bigger power footprint.

Firstly, I didn’t use Windows. I don’t even like Windows, so that was never an option. I used XBMCBuntu – a fairly lightweight version of Ubuntu with XBMC pre-packaged. I then add the ‘mythbuntu-control-center’ package to add MythTV backend and set up MythBuntu components for Live TV. You can do this the other way around too – install MythBuntu and then add XBMC packages. I just prefer the XBMCBuntu startup splash screens for my HTPC so I do it the other way around šŸ™‚

Then, find yourself a Sony PlayTV USB Tuner (if you want Live Terrestrial TV). The NUC has no space for adding TV tuner cards so you’ll need a USB tuner. The PlayTV has worked flawlessly for me and I highly recommend them. I picked mine up from EB Games in Melbourne, but you can get them on eBay too. Sadly they don’t appear to be made any more, which is a shame as they’re the cheapest and most reliable way of getting Live TV on your MythTV setup on Linux.

xbmcbootingOnce you install XBMCBuntu and add the Myth components you’ll need to make a couple of tweaks to make it run a little more smoothly and use less power. If using less power was possible. The things runs at about 6W idle, which was why I went with this – I got sick of the power crazed standard HTPC. Firstly, go into the XBMC settings and switch off the RSS feed scroller – that alone drops the XBMC process usage from around 35% constantly to about 10%. Also, if you’re using the Hybrid skin, turn off the background raindrop effect – for another significant processor drop.

Switching between screens on Hybrid skin isn’t silky smooth, but it isn’t far off. Watching TV, movies, listening to music etc is all perfectly smooth. And with built in Infrared, in a 4 inch footprint that costs around 6 watts of energy, this is a highly recommended setup for a Home Theatre PC and requires no active cooling and can sit outside of a cabinet just alongside the TV without looking out of place. And as HTPC’s go, the price is pretty good too. It’ll cost you around $350 all up, less if you only need 4G of RAM.

More Information:

Get MythBuntu
Intel NUCs on eBay
Sony PlayTV on eBay
EB Games pre-owned gear

Installing Bugzilla on a CentOS cPanel VPS

This article is designed to hopefully assist someone not have to go over the same troubles as I experienced installing the latest stable Bugzilla onto my cPanel server. To say it gave me a headache is an understatement.

To begin with everything went smoothly. It was all good. I followed the instructions for the Bugzilla installation, and ran the various perl scripts, which said I needed to install some additional modules to make Bugzilla work. That was no problem, so I thought, because I had CPAN installed and set up.

Most of the modules went on OK, and everything looked good. But then I started receiving e-mails from users of another site written in perl that resides on the server. They were getting Internal Server Errors galore. Premature end of script headers. Oh joy.

So I went on the hunt for what could be going on. I ran the perl script manually for the site that was complaining. It borked with some file or other that couldn’t be found in the @INC path. That’s odd, because it was working before I tried installing the JSON::RPC module from CPAN. I ran the Bugzilla ‘’ script again and now that borked with files missing from @INC.

What the?

I tried using CPAN to install the missing modules that the script was now complaining about. One went on, then CPAN itself stopped working! Now I was really confused.

I did some googling around, discovered some fairly useful information to put things back and got CPAN up and running again. I can’t give specifics of this because it really depends on what you did prior to getting here as to what you’ll need to look for. Hopefully though you read this BEFORE you bork your CPAN install šŸ™‚

Long story short, I have two Perl binaries on my system, compiled with different @INC paths.


I discovered it quite by accident. One was in /usr/bin/perl – the other was /usr/local/bin/perl. Running from the command line was using /usr/local/bin/perl, but web scripts (and the script) were coded to use /usr/bin/perl.

At this point in time I have renamed the /usr/bin/perl version to /usr/bin/perl.sav and softlinked to /usr/local/bin/perl since all my CPANing and tweaking was done with the /usr/local/bin/perl variant (which used a /usr/local/ prefix to its @INC path).

This seems to have fixed Bugzilla, and kept the other site happy too. I’ve yet to test whether it’s broken cPanel now though!

Centos 5 in VirtualBox – High CPU Usage FIXED

CentOS LogoLet me give some background to the problem. You’re running CentOS 5 under VirtualBox, perhaps on OSX Leopard Server or indeed possibly another host operating system. You’ve noticed that even when the guest is utterly idle, the processor on the host is hovering at 50% or above. Or maybe only 20% but really, when the guest is idle, why is VirtualBox using ANY host processor.

I noticed that I don’t have this issue with Ubuntu (can’t remember which version) so I figured it had to be a Linux kernel issue rather than a VirtualBox issue.

After much scouring of Google, and receiving some excellent, but highly convoluted answers such as recompile the guest kernel with CONFIG_NO_HZ=y and CONFIG_HIGH_RES_TIMERS=y (neither of which the kernel with Centos 5 understands) and so I went down the path of recompiling my own CentOS kernel.

But now I have found a very simple answer. Forget about recompiling your own CentOS kernel, you don’t need to. You can simply pass a boot time parameter into the kernel using the grub menu.lst


The problem comes because the CentOS kernel is compiled with theĀ CONFIG_HZ_1000=y andĀ CONFIG_HZ=1000 options. This (I’m told) basically means the kernel is trying to service interrupts at a rate of 1000 per second – which is fair and reasonable on normal hardware. But it makes a lot of extra work for a VM which is virtualising those interrupts. Setting the divider to 10 means you drop the amount of time spent generating interrupts and so the VM has less work to do – hence less processor use on the host.

The full line in /boot/grub/menu.lst for my running kernel now looks like this;

kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet divider=10

I’ve also found since making this change that the guest seems a LOT more responsive and snappy. Odd really since the 1000Hz kernels are meant to be snappier. Oh well, Virtualization is a strange art of its own rulemaking and I’m just a user!

Hope that helps someone else.