ivoras’ FreeBSD blog Just another FreeBSD Developer’s weblog

January 9, 2008

fit-pc, part II

Filed under: FreeBSD — Tags: , , , , , , — ivoras @ 7:13 pm

Unfortunately, the FreeBSD boot loader doesn’t work on fit-pc, though apparently loaders of other BSD’s and Linux’s GRUB work withot problems. Yay for FreeBSD. I tried many things, including using GRUB (which boots the pre-installed Ubuntu), without luck. I agree with the diagnosis proposed by other similar users: something in the loader disables USB in the middle of booting. At the end, I took its drive to another machine, installed FreeBSD there and returned it.

FreeBSD is not exactly a good choice for fit-pc. There are no drivers for its USB 2 (USB1 works) controller, its audio controller and its built-in hardware crypto acceleration (AMD Geode AES). All of these things work on Linux. On the other hand, at least the network ports (Realtek chip) and other basic components (IDE controller, motherboard devices) work.


January 7, 2008

fit-pc, part I

Filed under: FreeBSD — ivoras @ 5:58 pm

NOTE: This post is about the original Fit-PC, with an AMD GEODE 500 MHz CPU
I got a fit-pc machine the other day :) The first impressions are not that good:

* While obviously the purchaser was in Europe, I got an American power cable (though the power transformer is luckily universal 110V-220V 50Hz-60Hz)
* There seems to be something loose in the transformer or the cord(s), since apparently it requires jiggling around to make it start. Will probably have to replace it all together.
* Installing Ubuntu with full graphical interface on this machine was a catastrophic waste of resources. The machine a) has only 256 MB of RAM and b) has an extremely slow CPU (500 MHz AMD Geode – this is way slower than what is in EEE PC). It swaps all the time while under GUI.


January 6, 2008

Encrypted iSCSI target

Filed under: FreeBSD — ivoras @ 12:50 am

Suppose you want to use a remote iSCSI device, but you don’t exactly trust either the storage or the network in between. Of course, there’s a way around it :)

The setup presented here is very simple and will behave like this:

[iSCSI server] -- encrypted data on the server and over the wire -- [iSCSI client]


Powered by WordPress