Last year I bought a fit-PC in order to replace my old router (which was a desktop PC). This year I bought a fit-PC2 to replace my home server (which was a big fat computer).
Requirements
This time my needs were a bit different than the ones for my router. I was looking for a low power consumption device with at least 512 MB of RAM, fast enough to read videos (I may use it as a HTPC in the future), fan-less and of course, it must work with Linux.
fit-PC2 specifications
So I end up with Compulab’s fit-PC2. Here are the official specs:
- CPU: Intel Atom Z530 1.6 GHz
- RAM: 1 GB DDR2-533
- HDD: 160 GB SATA 2.5”
- 1 Gigabit ethernet port
- 4 USB 2.0 ports
- 2 mini-USB 2.0 ports
- 1 mini-SD socket
- 1 IR receiver (infra-red, for remote control)
- DVI output (using a HDMI connector, HDMI to DVI cable provided)
- Power consumption: 6 W idle, 7 W reading H.264 videos, 8 W at full load
- Shipped with Ubuntu
Several flavors are available (with WiFi, without hard drive, with an Atom Z510 CPU…).
Pictures
Usage
I tried the pre-installed Ubuntu but it’s an old version (8.04). Anyway, it was working quite fine. For video playback only MPlayer was using hardware acceleration provided in fit-PC2. I played Sita Sings The Blues on it, it works wonderfully (the movie is a Full HD (1920*1080), 4.12 GB file (I was hardly able to read it on my MacBook)).
But I don’t really want to use Ubuntu. If I want a *buntu linux I would install Kubuntu instead, anyway I installed Debian. Here is the beginning of my troubles.
First, I’m using Debian’s “testing” version, which proved to be quite stable so far. Except with the new 2.6.30 Linux kernel which froze my VIA C7 powered Dedibox and is behaving weirdly on the fit-pc2. I don’t know if the problem is in linux kernel, gcc, debian but installing 2.6.30 kernel was not a good thing on my debian boxes. I’m using the fit-pc2 remotely (ssh, music streaming, time machine backups ) and from time to time it stops to respond, but if I hit a key on the keyboard, network operations resume very weird. A problem in power saving code? a deadlock which resolved itself when a new interruption is raised? No idea, I’m clearly not competent in that domain. Easy solution: revert to 2.6.26 kernel.
Second problem: drivers. The graphic chipset used is an Intel GMA500. Even if Intel recently helped the Open Source community by giving specifications of its chipsets, they didn’t for that one (because it’s not really an Intel one, it was developed by PowerVR (and they are much less cooperative)). Somehow Compulab/DeLL/Ubuntu managed to get a partly open source driver with hardware acceleration (that part is still proprietary), but according to various websites, the driver is crappy and not well maintained (but it looks like some people are trying to make that better). So, for now, hardware acceleration does not work easily on Debian. I hope it will work soon.
Power consumption
- Off: 0.3 W
- Idle: 9 W
- H.264 playback: <10 W
- Full load: <11 W
It seems that it consume a bit more than expected (my watt-meter is a cheap one, I’m not sure how reliable it is), or maybe figures on fit-pc2 website were given for an Atom Z510.
Note: the case can be very hot.
Conclusion
fit-PC2 is a nice bit of hardware, but if you are going to install an alternative BSD/Linux operating system, you have to know that you may get some troubles with video drivers (if you need nice graphical interface).











