Information Technology - 8

The fact that the idea of free software is so contrary to the behavior of Microsoft is exactly reflected by how their respective representatives act in their talks. Here’s a quick video edited by myself from sources I found on YouTube:

It’s totally up to you who you trust.

I complained about my old notebook being too slow at image processing. As I now run a new machine, it’s time to measure the performance increase:

Old system: 1×1.6 GHz CPU, 1 GB RAM
New system: 8×2.67 GHz CPU (by threads), 6 GB RAM
Test file sizes: 11.2–12.5 MB

Task #1: Render 8 RAW images to PPM in multi-parallel
Command line:

Old system time: 1 min 41.1 sec
Old system mem usage: 1 GB (100%)

New system time: 0 min 04.6 sec
New system mem usage: 2 GB (33%)

→ 22× faster

Task #2: Render 8 RAW images to JPEG in multi-parallel
Command line:

Old system time: 5 min 0.0 sec
Old system mem usage: 1 GB (100%)

New system time: 0 min 18.2 sec
New system mem usage: 2.5 GB (42%)

→ 16.5× faster

Hell yeah!

Debian’s standard kernel 2.6.26 has a little drawback: The coretemp module doesn’t recognize Intel’s Core i7 processor. The sensor chip W83667HG of my Asus P6T Deluxe (LGA 1366 socket) is not yet supported as well. This is a typical symptom when using Linux on too recent hardware. However, if it’s enough for you to read an aggregated CPU temperature instead of eight individual core temperatures, you can force loading the w83627ehf module with

and tune the /etc/sensors3.conf to get rid of false alarms.

Luckily, for the current prerelease 2.6.29-rc6 there’s a very recent bunch of patches available that brings support for W83667HG into the w83627ehf module, whereas coretemp already finds the CPU. Follow this guide on how to compile and install a new kernel the Debian way. A drawback is that source modules from the official Debian repositories might not compile anymore, e.g. the MadWifi modules. You have to get them from the project directly (via SVN). You also need to build a current version of lm-sensors (via SVN) to correctly gather the values from w83627ehf. You could then visualize the values e.g. with gkrellm.

Now have fun stress-testing your system with MPrime.

Update 03/24: It appears that these patches didn’t make it into the final 2.6.29 release.

Update 04/09: The patches went into 2.6.30-rc1.

Because it’s a pain, a short reminder for myself on how to connect a Bluetooth capable cell phone with a Debian box:

1. Install bluez-utils.
2. Read this (German) guide and follow instructions, but ignore the obsolete stuff about the pin helper; today it’s just an entry like passkey “1337”;
3. For whatever reason, hcid doesn’t launch a passkey-agent automatically. For the very first connection, you have to do it by yourself:
1. Get both the passkey-agent.c.gz source and its Makefile from the bluez-utils examples directory and compile it; you’ll need libdbus-1-dev.
2. Launch it as /path/to/passkey-agent 1337 HA:RD:WA:RE:AD:DR and go to a different shell.
4. cat < /dev/rfcomm0 and enter the requested pin on your cell. If nothing special happens, you’re done.

In your cell’s Bluetooth settings you could now permanently authorize your PC. The next cat < /dev/rfcomm0 shouldn’t initiate a pin request anymore.

Two days ago I finished assembling my new workstation and set up a 64-bit Debian ‘lenny’ on it. When I decided to go for Intel Core i7 I wasn’t aware that due to Intel’s Hyperthreading technology each of the four cores is able to handle two threads at once, making it effectively an eight(!)-core system to the OS! Dig this:

I thought that the onboard Intel SATA-RAID controller provided a hardware RAID, but it’s just a software RAID in disguise, so I can well let Linux do the job. Then I had problems setting up WLAN with the Atheros card I built in, but thanks to the MadWifi project I got it running. What else? Yes, Memtest86 v3.5 didn’t boot on Core i7 and/or 6 GB RAM, but Memtest86+ v2.11 did.

I named the new system ‘davinci’, honoring the technological genius Leonardo da Vinci, what is consistent with the weapon-like appearance of the Cooler Master Storm Sniper case.

I proudly list the installed components here:

• CPU: Intel Core i7-920 4×2.67GHz
• RAM: OCZ Platinum 3×2GB DDR3-1600 SDRAM, CL7-7-7-24
• Mainboard: Asus P6T Deluxe, 6×DDR3-1333 slots
• GPU: Zotac GeForce GTX 260 AMP²! Edition, 896MB GDDR3, PCIe 2.0 ×16, 2×DVI
• Harddisks: 2× Western Digital RE3 1TB SATA II, RAID-1
• Optical drive: LG Electronics GH22LS30 SATA, 22×/8×/12× DVD±R/+RW/-RAM
• WLAN: D-Link AirPlusXtremeG DWL-G520, 108Mbit, PCI
• Case: Cooler Master CM Storm Sniper
• Power supply: Cooler Master Silent Pro 700W
• Monitor: Samsung SyncMaster 2693HM 26″ TFT-LCD, 1920×1200, DVI, HDMI, speakers, USB
• Input devices: Logitech Cordless Desktop Wave

Currently I just use Intel’s boxed CPU cooler, so I haven’t done any overclocking yet. I’m having an eye on the Cooler Master V10 that’ll be available by April. With this I aim to overclock the cores to 3.2 GHz for the first time, what I might increase to a maximum of 3.8 GHz one day.

Processing images with my current notebook (1.6 GHz CPU, 1 GB RAM) finally is a real pain in the ass. Having the RAW converter render some JPEGs while the HDR software performs tonemapping, it becomes impossible to do image editing or even browse the web at the same time, as the mouse pointer only moves stutteringly like in those “good old days”. In addition, my 160 GB disk is almost full. My computer usage history documents the years where I got a PC (for the use as a workstation, not counting those few boxes for my server and firewalling experiments): 1995, 1998 and 2001; the notebook’s from 2004. So, it’s about time for an upgrade.

When I first thought about whether it should be a notebook again, I noticed that I don’t use my current notebook “on the road” anyway. And notebooks don’t have the computing power of dedicated desktop machines.

Nerds who buy a new PC every year are probably surprised that a Linux geek like me gets along with that few hardware upgrades. Well, my strategy is more like: Buy rarely, but wisely. I don’t feel well when messing around on a productive machine that is supposed to work; just a matter of experience. Thus, I select the components for my new PC carefully and according to my demands: Fast, multi-core, RAM expandable, good disk size, RAID-1, average good GPU, and—very important—silent operation. The price for the box should traditionally be around EUR 1,500 (formerly ATS 20,000). These are now my considerations:

From: me
To: Disputo Support
Date: Wed, 03 Dec 2008 15:47
Subject: Zweimalig 25EUR verrechnet ohne Auftrag

Ich sehe auf meiner Kreditkarte zwei Positionen von „WP-FIRSTUSENET INT“ vom 01.12.2008 zu je 25 EUR, obwohl ich keinen Auftrag abgesetzt habe! Was hat es damit auf sich? Ich habe zuletzt am/vorm 24.09.2008 das Transferguthaben von 20GB um 25EUR aufgeladen und seither nichts mehr getätigt.

From: Disputo Support
To: me
Date: Wed, 3 Dec 2008 16:01

leider ist ein Problem in der Rechnungsverarbeitung aufgetreten, aufgrund dessen Ihr Account fehlerhaft berechnet wurde. Der Fehler wurde beseitigt und falsch abgebuchte Beiträge wurden am 02.12.2008 zurück erstattet. Wir bitten vielmals um Entschuldigung.

From: me
To: Disputo Support
Date: Fri, 05 Dec 2008 07:24

Bis jetzt sehe ich nur eine einmalige Rückerstattung von 25 EUR mit Datum 01.12.2008. Die zweiten 25 EUR sind noch nicht rückgebucht. Wurden beide Beträge rückerstattet?

About ¾ of a year later I did my next try with installing NVIDIA CUDA on Debian lenny, mainly because I wanted to try GpuCV, a GPU-accelerated computer vision library that’s partly compliant with OpenCV. Debian is still not officially supported by NVIDIA, but the finally upcoming release of lenny and NVIDIA’s support for the rather recent Ubuntu 8.04 (2008/04) have a very positive effect: CUDA 2.1 Beta works out of the box, and this with lenny’s GCC 4.3! The only thing I had to consider is to install libxmu-dev and libc6-dev-i386 (for my 64-bit CPU) to make CUDA’s examples compile. Also, in order to actually execute the examples, one has to rely on the NVIDIA driver version 180.06 that CUDA provides, whereas even NVIDIA’s version 180.22 fails to execute the OpenGL examples with the message

cudaSafeCall() Runtime API error in file <xxxxx.cpp>, line nnn : unknown error.

With CUDA working I could then think of compiling GpuCV from SVN. But the build relies on Premake 3.x, which is not available in Debian and has to be installed in advance. In addition, the package libglew1.5-dev is needed. Some more stumbling blocks were that I had to define the typedef unsigned long GLulong by myself. Also, and IIRC, the provided SugoiTools of GpuCV didn’t link, so I fetched and compiled them from SVN as well, and I replaced the .so-files in GpuCV’s resources directory. After that GpuCV finally compiled (except the GPUCVCamDemo, as I don’t have the cvcam lib installed). Including the lib/gnu/linux paths into the $LD_LIBRARY_PATH, the GPUCVConsole demo finally runs. The next step will be to actually use that lib.