[blog...]
Currently the posts are filtered by: upgrade
Reset this filter to see all posts.
Tiny "fit-PC 2" Replacing Old Desktop PC
Recently I bought a "fit-PC 2" from CompuLab to replace my desktop PC at the Weltcafé reception. The predecessor was a Fujitsu Siemens computer from 2003 which replaced itself for a short time my VIA Epia EN1200.
I made a photo of these three computers and I measured approximatley the power consumption. And it's really estonishing: the tiny "fit-PC 2" is the fastest of it all and consumes only about 10 W even during watching youtube-videos.
Inside the metal box is working a single core Intel Atom Z530 with Hyper Threading at 1.6 GHz. It's equipped with 1 GB DDR2-RAM, a Samsung 250GB hard disk and even a RaLink RT3090 wireless card. There is only a HDMI-output but CompuLab includes a HDMI-DVI connector. With my DVI-VGA adaptors I cannot see any analog output but I don't need it at all.
The "fit-PC 2" comes preinstalled with Ubuntu 9.10. Of course, I tried to upgrade immediately to current Ubuntu 10.04 but afterwards the graphic output was slow and my special resolution (1440x900) failed :-(
Reason for this is the Intel Graphics inside: a GMA 500. For this you need the Intel Embedded Graphics Driver (iegd) for X.org. But this driver is closed source and it's not available yet for xorg-server 1.7 which is used in Ubuntu 10.04.
So, I had to reinstall Ubuntu 9.10 which was quite easy: download desktop ISO-image, write it with unetbootin on a USB-memory stick, boot and install. And now I'm waiting for Intel and follow the "fit-PC 2" forum for a release of Ubuntu 10.04 for "fit-PC 2".
I like this tiny device. It's sufficiant fast for my needs, it's silent (you only here the hard disk a little bit), has low power consumption and it's perfect small.
I bought my device from in Germany from SH EDV Vertrieb for 406 EUR including VAT and shipping to Germany.
Here is a /proc/cpuinfo for people like me googleing for it:
ab@ab-fit:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 28
model name : Intel(R) Atom(TM) CPU Z530 @ 1.60GHz
stepping : 2
cpu MHz : 800.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3
xtpr pdcm movbe lahf_lm tpr_shadow vnmi flexpriority
bogomips : 3191.90
clflush size : 64
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 28
model name : Intel(R) Atom(TM) CPU Z530 @ 1.60GHz
stepping : 2
cpu MHz : 800.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2
ssse3 xtpr pdcm movbe lahf_lm tpr_shadow vnmi flexpriority
bogomips : 3191.94
clflush size : 64
power management:
Upgrade linux.bigga.de to Typo3 4.3. Beta 2
Incompatiblity of tinyrte and t3blog?
Yesterday I was very brave and upgraded my Typo3 on linux.bigga.de from 4.2.10 (stable) to 4.3 Beta2. I thought, it's a good idea to work already on a non-production system with the future typo3-release.
4.3 seems to be much bigger than 4.2. Archive size increases from 7,8M to 12M. This is for sure due to some backports from Forge (Typo3v5) to enable the MVC-concept in extensions already in Typo3v4.
After going step by step through the upgrade wizard, everything seemed to be fine. But then I tried to add a post to the t3blog and I failed adding any content.
I was trying a while and removed finally tinyrte and reinstalled htmlarea RTE. Now, I can add contents again but have to use the very slow (!) RTE again :-(
Other uses already noticed this "bug". I just added some comments to the bugtracker: