Henry's Blog

TeXstudio-2.2 on Slackware64

2011-09-22T19:51:00.001+07:00

Today, I have upgraded TeXstudio (formerly TexMakerX) from 2.1 to 2.2 release version (released on 2011-07-20). I need this LaTeX Editor for writing my dissertation report. For the new features, release notes, screenshots, etc., please refer to its website. I downloaded the source code from this link. It needs Qt (at least 4.3), libpoppler, and TeX packages (don't worry, they can be found in l (or deps for Qt if you are using Eric's KDE compilation packages) and t directory for Slackware/64) for compilation.

The compilation process is very easy:

extract the source files from tarball
enter to texstudio source directory
# qmake texstudio.pro
# vim Makefile.Release (or, use your favorite text editor to edit Makefile.Release)
make sure /usr/lib64 is written on LIBS (see Figure 1)
# make
# make install

Figure 1: Makefile.Release

It should be no problem in compilation. Enjoy your TeXstudio!

Screenshot:

Figure 2: TeXstudio-2.2 is running on Slackware64

Installing e-Sword under wine on Slackware64

2011-08-30T10:58:00.000+07:00

Finally, I can install e-Sword, a Bible study software for windows, under wine on Slackware64 after trying it for a whole day. I decided to use e-Sword because it has abundant, almost complete modules; everything that I need mostly can be downloaded or purchased on the internet.

Before installing e-Sword, you have to prepare the wine environment. For Slackware users, you can download the slackbuild scripts from SlackBuild.org and the source files, then build the slackware packages, in order, webcore-fonts, fontforge, wine, winetricks, and cabextracts. Strictly for Slackware64 users, you have to install Eric's multilib packages in order to compiling and running the wine. After these wine's packages are installed, do these following steps (you have to connect to internet):
   $ export WINEARCH=win32   <-- just for Slackware64
   $ winetricks mfc42   <-- installing mfc42.dll
   $ winetricks msls31   <-- installing msls31.dll

Now, you're ready to install e-Sword. Download the latest version then install it:
   $ wine [path-to]/setupXXX.exe   <-- the "XXX" is the version number of e-Sword

After that, you need to set up wine environment again:

   $ cp ~/.wine/drive_c/Program Files/e-Sword/riched20.dll ~/.wine/drive_c/windows/system32

   $ winecfg

In winecfg, set riched20.dll to native and oleaut32.dll to native,builtin (see picture below).

Finally, run e-Sword by clicking the icon on your desktop/menu (if any) or typing this command on terminal:

   $ wine "C:/Program Files/e-Sword/e-Sword.exe"

Installing eSword9Converter
If you have the old modules (before version 9) for e-Sword, you need to convert it before using it. You will need eSword9Converter to do that. Please download it from this site. Before installing it, you have to install .NET Framework 3.5 by typing this command on terminal (you have to connect to internet):

   $ winetricks dotnet35

Then you can install eSword9Converter:
$ wine [path-to]/setup-X.X.X.exe <--- the "X.X.X" is the version number of eSword9Converter
After finishing installation, you can run eSword9Converter by clicking the icon on your desktop/menu (if any) or typing this command on terminal:

   $ wine "C:/Program Files/eSword9Converter/eSword9Converter.exe"

That's all.

References:

http://ubuntuforums.org/showthread.php?t=404042
http://forum.sabayon.org/viewtopic.php?t=22775#p127929

ATI Catalyst on Linux Kernel 3.0.3

2011-08-26T19:53:00.003+07:00

Yesterday, I found that the kernel and ATI Catalyst driver have been updated since August 17, so that, I decided to spend my time for testing them, then use them if there is no problem. Since a few hours ago, the new kernel 3.0.3 and ATI Catalyst has been running smoothly on my laptop. I have tested 2 versions of ATI Catalyst, those are, 10.12 and 11.8.

ATI Catalyst 11.8 (without patch)
This version has been installed without problem and without any single line's patch. My suggestion, use xorg.conf from aticonfig --initial for avoiding any problem (see my previous post), especially if you want to use Desktop Effects.

ATI Catalyst 10.12 (with patch)
I have tried this version on kernel 3.0.3 and it has been running smoothly without problem, however, it need to be patched. For patching ATI Catalyst 10.12, please read my previous post. You can find the link for downloading the patch on that post.

That's all.

Note: for my other posts about ATI Catalyst, go to this link. You may need to read it.

Linux Kernel 3.0.1 & ATI Catalyst

2011-08-09T11:51:00.020+07:00

Since yesterday, I have tried to run the Linux kernel 3.0.1 on my laptop; everything is good, no problem so far. Next step, I tested the ATI Catalyst 11.7, without patching. After installation, everything is running well including fglrx kernel module and the driver for x server. However, I still have the "old" problem that always occurs when I install ATI Catalyst 11.x, that is, I cannot activate OpenGLOverlay so that the Desktop Effects (compiz) cannot be launched. Therefore, any version of 11.x can be installed as long as the OpenGLOverlay is disabled (see the option below).

Section "Device"
        [...]
        Option      "OpenGLOverlay" "off"
        [...]
EndSection

Now, I am using ATI Catalyst 10.12 with OpenGLOverlay enabled (see the option below) so that I can activate the Desktop Effects since this version does not have problem with OpenGLOverlay. Of course, I have to patch it first. I use the patch that I have written about two months ago (here). So far so good, I can activate the Desktop Effects again.

Section "Device"
        [...]
        Option      "OpenGLOverlay" "on"
        [...]
EndSection

Linux Kernel 3.0.1 and ATI Catalyst 10.12:

My note: Although I have problem with Desktop Effects when I use ATI Catalyst 11.7, My colleague, Widya Walesa, can activate the Desktop Effects when using 11.7; you can read it on his blog. I still don't know what the cause of my problem is.

Note: for my other posts about ATI Catalyst, go to this link. You may need to read it.

Disabling Nepomuk and Akonadi

2011-08-04T12:36:00.002+07:00

After upgrading to KDE-4.7.0, I feel that Nepomuk and Akonadi are very annoying. I always get notification about Nepomuk and some messages about Akonadi when I quit from KDE. Since I don't use Desktop Search and KMail anymore, I have decided to turn Nepomuk and Akonadi off.

Disabling Nepomuk
I follow these steps to disable Nepomuk:

Go to System Settings --> Workspace Appearance and Behavior --> Desktop Search
Untick "Enable Strigi Desktop File Indexer" and "Enable Nepomuk Semantic Desktop" under Basic Setting Tab
Choose "Ignore all removable media" on Removable media handling and also make sure all folders are left unticked in "Customize index folders ..." under Desktop Query Tab
Select "Disable Automatic Backups" on Backup frequency under Backup Tab
Go to System Settings --> Common Appearance and Behavior --> Application and System Notifications --> Manage Notifications
Under Applications Tab, select "Desktop Search" on Event source and make sure all states are empty
Do the same for "Nepomuk file watch service" and "Semantic Desktop" on Event source
Quit System Settings

Disabling Akonadi
For disabling Akonadi, open the terminal then enter the directory ~/.config/akonadi/akonadiserverrc and set the value of "StartServer" on [QMYSQL] to false.

[QMYSQL] 
... 
StartServer=false

After finishing all steps described above, restart the KDE. Nepomuk and Akonadi have been disabled.

Note: I configure my System Settings to Classic Tree View (see picture below).

Oxygen KDE: A Firefox Theme

2011-07-21T12:05:00.002+07:00

This morning, I got information from Deddy through Google+ about Oxygen KDE. I give it a try ... awesome ... I like it so much! So far, there is no problem after installing it. For KDE users that use firefox as web browser, I suggest you to try this theme.

kdeutils-4.6.5 for Slackware after patching

2011-07-19T12:41:00.000+07:00

I have patched the source of kdeutils-4.6.5 since there are problems on KCalc (see this link and this link). You can download the slackbuild script, patches, and the source of kdeutils-4.6.5 from this link. Before compiling yourself, make sure you have upgraded your KDE to KDE-4.6.5 using Eric's packages. Next, uncompress kdeutils-4.6.5_SlackBuild.tar.gz and run the KDE.SlackBuild as root. This slackbuild script will compile kdeutils-4.6.5 then upgrade your previous one.

For Slackware64 users, you don't need to compile; just download the binary package from this link, then do upgradepkg.

ATI Catalyst Proprietary Display Driver & kernel-2.6.39.x

2011-06-13T14:27:00.011+07:00

Updated: I have renewed all links for the patch. If you still have problem with the link, do not hesitate to contact me. Thank you for all you that have informed me about this link problem.

Again, we need to patch the source code of fglrx kernel module, part of ATI Catalyst (you will find it on /lib/modules/fglrx after installation), for kernel 2.6.39.x since there are some changes on the kernel. On this post, I will show how to patch ATI Catalyst 11.x (tested on 11.5) and 10.10 - 10.12 (tested on 10.12) so that it works on 2.6.39.x (tested on 2.6.39.1).

ATI Catalyst 11.x
First, download 2 files: 2.6.39_bkl.patch and no_bkl.patch (Thank's to https://aur.archlinux.org/packages.php?ID=41040 and http://www.mindwerks.net/2011/04/ubuntu-11-04-natty-with-fglrx-and-2-6-39). Copy those files to /lib/modules/fglrx/build_mod then run these commands:

patch -p1 &lt; 2.6.39_bkl.patch

patch -p1 &lt; no_bkl.patch

Next step, execute ./make.sh and if there is no error, change directory to /lib/modules/fglrx then execute ./make_install.sh

ATI Catalyst 10.10 - 10.12
You have to download this patch: fglrx_10.10-12_with_2.6.39.x.patch. Copy this file to /lib/modules/fglrx/build_mod then execute:
patch -p1 < fglrx_10.10-12_with_2.6.39.x.patch
After that, execute ./make.sh and if there is no error, change current working directory to /lib/modules/fglrx then execute ./make_install.sh

Happy patching!

Note: for my other posts about ATI Catalyst, go to this link. You may need to read it.

Xilinx ISE WebPack on Slackware64

2011-04-30T02:30:00.006+07:00

(breaking news) Slackware64-13.37 has been released! Thank's to Pat, Eric, and other maintainers for making this version available.

For a long time, I have struggled with errors on the installation of Xilinx ISE WebPack on Slackware64 because I want make Slackware64 not only for doing my "office work", but also as the environment for all development software related to my work. So far, I can make design and draw PCB artwork on Slackware64 using gEDA and pcb. Also, I am able to compile and use gcc cross-compilers for AVR and ARM-based embedded systems. However, if I want to develop "some hardware" on FPGA using Verilog HDL, I must switch to other OS that I really don't like it. Finally, I can install Xilinx ISE WebPack on Slackware64. Thank's to Philip Pemberton that has written the solution on Ubuntu 64-bit version.

The installation problem occurs only when you try to install it on 64-bit version of Linux. I have tried it on Slackware64 and Ubuntu 64-bit version, all trials are failed. The solution is just install 32-bit version of Xilinx ISE on Slackware64. By Philip's reference, here is the step of installation:

Download the Xilinx ISE (any latest Linux version or complete version) and extract the installer.
Enter the installer directory.
Install it with this command (must be root): linux32 ./xsetup
Follow the instructions.
Enter the installation directory (if you don't change the default, it should be /opt/Xilinx/[ISE_version]
Create a script: startise.sh (if you use vim, just type: vim startise.sh)
Put a few lines below on the script (in my case, I install Xilinx ISE 13.1. If you use different release number, just change the "13.1" to the correct one):

#!/bin/bash
source /opt/Xilinx/13.1/ISE_DS/settings32.sh /opt/Xilinx/13.1/ISE_DS/
ise
Don't forget to make it executable: chmod +x startise.sh
Execute the script to start Xilinx ISE.

Here is the screenshot of Xilinx ISE on Slackware64 inside my laptop:

myPhone @ES6192

2011-04-21T03:34:00.004+07:00

"myPhone @ES6192" is my final assignment on ES6192 course (Embedded Operating Systems). I worked on this assignment together with my partner, Rahmady. This assignment simulates a phone dialer. We had to develop device drivers and application software that could be performed on ARM-based Embedded System with Linux as its operating system.

We developed device drivers for simple I/O on the board: 4 LEDs, 7's Segment LED displays, and 4x4 keyboard. For LCD screen, we use framebuffer driver that has already built on the kernel. The keyboard driver can handle interrupt, also, use tasklet, work queue, and FIFO circular buffer to manage the data.

The application software is multithreaded; it has 6 threads (excluding main thread) for handling all processes such as manipulating I/O devices (4 threads), updating clock (1 thread), and controlling whole system by setting the operating modes based on user’s input (1 thread). For managing shared data, we use semaphores.

Modes on “myPhone @ES6192”:

display clock mode or cancel key on phone dialer and off-hook mode by pressing “C” key
adjust clock mode by pressing “D” key
phone dialer mode by pressing “E” key
off-/on-hook by pressing “F” key (toggled)
backspace key on adjust clock and phone dialer mode by pressing “A” key

Structure of "myPhone @ES6192":

Video demo:

How to make touchpad/clickpad temporarily disable when typing?

2011-03-25T00:07:00.004+07:00

Since my laptop has clickpad that has larger area and more sensitive than common touchpad, I get an annoying behavior of my clickpad; when I type and my thumb or palm accidentally touches or near the clickpad, the cursor will be moved to the position that is pointed by mouse pointer, so that, I will continue to type in the wrong position! I hate this behavior! I have to disable my clickpad when I am typing. There are two methods:

Method 1, I disable my clickpad permanently. I run this script to toggle on/off my clickpad:

#!/bin/bash
#Toggle touchpad
SYNSTATE=$(synclient -l | grep TouchpadOff | awk '{ print $3}')
# change state
if [ $SYNSTATE = 0 ]; then
synclient touchpadoff=1
elif [ $SYNSTATE = 1 ]; then
synclient touchpadoff=0
fi

Method 2, I use /usr/bin/syndaemon to disable my clickpad only when I am typing. The steps:

Make ~/.xprofile
#!/bin/sh
# Customize X environment
#
# Activate syndaemon for monitoring keyboard activity and disabling # the touchpad when the keyboard is being used.
/usr/bin/syndaemon -td
Add these lines on the top of /usr/bin/startkde (if you use KDE as the default desktop manager) in order to make X server executes ~/.xprofile when it starts.
if [ -r /etc/xprofile ]; then
source /etc/xprofile
fi
if [ -r $HOME/.xprofile ]; then
source $HOME/.xprofile
fi
Restart X server.

Currently, I use method 2 because I only disable my clickpad temporarily when syndaemon detects keyboard action and resume my clickpad function within 2 seconds after the last key pressed. For more information about syndaemon, type: man syndaemon on your console.

Synaptics-1.4.0 patch for activating right-click function on clickpad

2011-03-24T23:33:00.000+07:00

Last month, I have written about how to activate right-click function on clickpad by patching synaptics-1.3.0. In this page, I will show you how to patch synaptics-1.4.0 so that you can use right-click function (also, middle-click). The patch is patch for synaptics-1.3.0 with a few changes. For the modified patch, you can download it from here (gzip compressed). You can follow the instructions from my last note; just change the step 3 with this: copy this file to path-to/x11/patch/ (in my case, copy it to /home/henry/rsync/x11/patch/). The rest will be same. I also put my clickpad.conf on google docs so that you can download it and place it in /etc/X11/xorg.conf.d/ then restart the X server.

ATI Catalyst Proprietary Display Driver 10.12 & kernel-2.6.38

2011-03-22T16:10:00.001+07:00

If you want to use ATI Catalyst Proprietary Display Driver 10.12 on your PC/Laptop that running kernel 2.6.38, you will get error because the installer cannot create fglrx kernel module. You need to patch ATI Catalyst kernel module before you compile it manually. Here is the patch:

--- ./firegl_public.c   2010-12-02 22:28:43.000000000 +0100
+++ ./firegl_public.c.new       2011-01-09 17:40:22.000000000 +0100
@@ -320,7 +320,7 @@
     return firegl_release((KCL_IO_FILE_Handle)filp);
 }

-int ip_firegl_ioctl(struct inode* inode, struct file* filp, unsigned int cmd, unsigned long arg)
+int ip_firegl_ioctl(struct file* filp, unsigned int cmd, unsigned long arg)
 {
     return firegl_ioctl((KCL_IO_FILE_Handle)filp, cmd, arg);
 }
@@ -407,7 +407,7 @@
 #endif
     open:    ip_firegl_open,
     release: ip_firegl_release,
-    ioctl:   ip_firegl_ioctl,
+    unlocked_ioctl:   ip_firegl_ioctl,
     mmap:    ip_firegl_mmap,

     write:   ip_firegl_write,
@@ -840,7 +840,12 @@ static int fglrx_pci_suspend(struct pci_
      * happen much less frequent then without this workaround.
      */
     if (state == PM_EVENT_SUSPEND)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+        console_lock();
+#else
         acquire_console_sem();
+#endif
+

     if (firegl_cail_powerdown(privdev, state))
         ret = -EIO;
@@ -862,7 +867,11 @@ static int fglrx_pci_suspend(struct pci_
     }

     if (state == PM_EVENT_SUSPEND)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+        console_unlock();
+#else
         release_console_sem();
+#endif

     KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, ret, NULL);  
     
@@ -886,7 +895,11 @@ static int fglrx_pci_resume(struct pci_d
     if (PMSG_EVENT(pdev->dev.power.power_state) == 0) return 0;

     if (PMSG_EVENT(pdev->dev.power.power_state) == PM_EVENT_SUSPEND)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+        console_lock();
+#else
         acquire_console_sem();
+#endif

 #ifdef FIREGL_USWC_SUPPORT
     // Restore the PAT after resuming from S3 or S4.
@@ -911,7 +924,11 @@ static int fglrx_pci_resume(struct pci_d
     firegl_cail_powerup(privdev);

     if (PMSG_EVENT(pdev->dev.power.power_state) == PM_EVENT_SUSPEND)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)
+        console_unlock();
+#else
         release_console_sem();
+#endif

     PMSG_EVENT(pdev->dev.power.power_state) = 0;
     KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, 0, NULL);  

@@ -5107,7 +5107,7 @@
 unsigned int ATI_API_CALL KAS_Mutex_Initialize(void* hMutex)
 {
     kasMutex_t* mutex_obj = (kasMutex_t*)hMutex;
-    init_MUTEX(&(mutex_obj->mutex));
+    sema_init(&(mutex_obj->mutex),1);
     return 1;
 }

--- ./kcl_ioctl.c       2010-12-02 22:28:43.000000000 +0100
+++ ./kcl_ioctl.c.new   2011-01-09 17:40:22.000000000 +0100
@@ -193,7 +193,7 @@
  */
 void* ATI_API_CALL KCL_IOCTL_AllocUserSpace32(long size)
 {
-    void __user *ret = COMPAT_ALLOC_USER_SPACE(size);
+    void __user *ret = arch_compat_alloc_user_space(size);

     /* prevent stack overflow */
     if (!access_ok(VERIFY_WRITE, ret, size))

Save this patch to file and follow the instructions that I have written on http://henryhermawan.blogspot.com/2011/02/problem-when-using-ati-catalyst.html.

Reference: http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/3b716dfe326fef23?pli=1

dmesg: operation not permitted as user

2011-03-12T20:52:00.003+07:00

After upgrading to Slackware64 13.37, I cannot access the kernel syslog (dmesg) as user. This problem is caused by kernel (2.6.37.3) setting in Slackware (see pictures below).

There are 2 solutions, you are freely to choose one of them.

Solution 1: add these lines on your rc.local:

if [ -r /proc/sys/kernel/dmesg_restrict ]; then
    if [ $(cat /proc/sys/kernel/dmesg_restrict) = 1 ]; then
        echo 0 > /proc/sys/kernel/dmesg_restrict
    fi
fi

Solution 2: change the correspond kernel setting (restrict unprivileged access to the kernel syslog) to "N" then recompile the kernel.

Bigger buffer log (dmesg) size

2011-02-27T01:58:00.000+07:00

Someone asked me: how to make dmesg output is not truncated. The answer is make the buffer log size bigger. How? As far as I know, there are two ways to raise the buffer log size:

Pass the parameter of log_buf_len=n to kernel, where n is a power of two number (n = 2^x). The default for slackware is 2^15 or 32768 (32k). You can change n to 65536 (2^16) or 131072 (2^17). In this way, you don't need to recompile your current kernel.
Compile or recompile your kernel. Before you compile the kernel yourself or recompile it yourself, you have to change the kernel parameter in General Setup > Kernel log buffer size (see figure) to 16 (65536) or 17 (131072). After compilation, don't forget to copy kernel image, config, and System.map into /boot directory and set up your bootloader (lilo/grub) properly.

Choose one of them then you will get full dmesg output on your screen. It will be very long message log.

Problem when using ATI Catalyst Proprietary Display Driver 11.x

2011-02-26T14:52:00.003+07:00

When I monitored ATI Catalyst driver website for Linux, the last driver version is 11.2 (15 Feb 2011). However, when I tried to install it on my laptop (ATI Mobility Radeon HD5400 series, my own compilation of kernel 2.6.37.2, & Xorg-server 1.9.4 from slackware64-current), the x server crashed. This happened also when I tried to install 11.1 version. Therefore, I have to draw back to the 10.12 version and it runs smoothly on my laptop. Since this version is very stable, I suggest, it's better if you stay on 10.12 version until AMD releases the new version.

Note: If you want to install the 10.12 version, you will need to patch the kernel module of ATI Catalyst using this patch for 2.6.37.x or this patch for 2.6.36.x. You don't need to this patch if you are using 2.6.35.x. Also, the 11.x version of ATI Catalyst doesn't need this patch.

How to install & patch:

Download the 10.12 version from here.
From console (run in text mode, make sure to this as root and the installer are executable), enter the directory where the installer is then run: ./ati-driver-installer-10-12-x86.x86_64.run --install
Follow the instructions.
When done, enter to /lib/modules/fglrx/build_mod/
copy the patch to this directory then run: patch -p0 < fglrx_10.10-12_with_2.6.XX.x.diff (note that XX is 36 or 37, depends on your kernel version).
run: ./make.sh
if there is no error, go up to one level (/lib/modules/fglrx/) then do: ./make_install.sh
reboot your system
use aticonfig --initial to create /etc/X11/xorg.conf then make necessary changes on it. My suggestion, it's better if you move and rename that xorg.conf to /etc/X11/xorg.conf.d/fglrx.conf
start your x server

Test your display, activate desktop effect, or whatever you want.

How to activate right-click function on clickpad?

2011-02-03T23:18:00.008+07:00

Finally, I can use the right-click of the clickpad on my laptop (HP Pavilion dv3-4036TX). Clickpad is differ from touchpad, those are, it is larger than touchpad and it doesn't have physical buttons for left- and right-click (see picture below and click here for more detail).

Because of this construction, if we use common driver (synaptics) on linux, you cannot use right-click function, in other word, when you click on both left and right bottom side of clickpad, you will get left-click function only.

If you want to activate right-click function, you have to patch the xf86-input-synaptics driver. You can download the patch from this site. How to patch? Follow the steps below:

Download the source of x11 (the whole directory tree) from Slackware site. It's better if you use rsync command for downloading it. In my case, I use: rsync -avP rsync.osuosl.org::slackware/slackware64-current/source/x/x11 /home/henry/rsync/
Copy the patch to path-to/x11/patch/xf86-input-synaptics/. In my case, I copy it to /home/henry/rsync/x11/patch/xf86-input-synaptics/.
Add this line: patch -p1 < $CWD/patch/xf86-input-synaptics/synaptics-clickpad-support.patch --verbose || { touch ${SLACK_X_BUILD_DIR}/${PKGNAME}.failed ; continue ; } to path-to/x11/patch/xf86-input-synaptics.patch then save it. In my case, I add that line to /home/henry/rsync/x11/patch/xf86-input-synaptics.patch file.
Run the slackbuild script exactly like this: ./x11.slackbuild driver xf86-input-synaptics
You will get new slackware package of xf86-input-synaptics for your clickpad. Afterward, upgrade the existing xf86-input-synaptics with the new one using upgradepkg.
Make new file (you can name it freely) in /etc/X11/xorg.conf.d/ (in my case: /etc/X11/xorg.conf.d/clickpad.conf), then write these lines in the file then save it:

Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
          Option "TapButton1" "1"
          Option "TapButton2" "2"
          Option "TapButton3" "3"
EndSection

Restart X server, then enjoy your "right-click function" of clickpad if you click the right bottom area of clickpad. In addition, if you click the middle bottom area of clickpad, you will get "middle-button function".

Converting wma to mp3

2011-01-29T17:39:00.004+07:00

Hi Readers,

This week, I got a bunch of wma files from my friend and I want to convert all into mp3 format for a reason (if you are linux user, you have known what my reason is). After I search on internet, I found a simple script from Linux Questions that can be used for converting wma format to mp3 format. For making this script works in your system, you need mplayer (already in slackware package) and lame (you can find slackbuild scripts for lame on http://slackbuilds.org). In order to make me comfortable when using this script, I make a little modification on this script, that is:

#!/bin/bash

current_directory=$( pwd )

#remove spaces
for i in *.wma; do mv "$i" `echo $i | tr ' ' '_'`; done

#Rip with Mplayer / encode with LAME
for i in *.wma ; do mplayer -vo null -vc dummy -af resample=44100 -ao pcm:waveheader $i && lame -m s audiodump.wav -o $i; done

#convert file names
for i in *.wma; do mv "$i" "`basename "$i" .wma`.mp3"; done

#add spaces as origins (if there are spaces)
for i in *.mp3; do mv "$i" "`echo "$i" | tr '_' ' '`"; done

rm audiodump.wav

Just put this script on the same directory of your wma files then run it. All of your wma files will be converted to mp3 files.
I hope this script and my little modifications can help you converting your wma files to mp3 files.

Bug on KDE-4.5.2

2010-11-04T01:24:00.006+07:00

At least, there is a bug on KDE-4.5.2, that is, if the time is set back, for instance, a few hours or 1 day before, the KDE will be crashed. I had this experience last week, so that, I downgraded to KDE-4.5.1, then on the next few days (when I have passed the day that the setting made KDE crashed), I upgraded to KDE-4.5.2 again. Now, KDE-4.5.2 is running smoothly on my laptop.

A good news, if you get this problem, you don't need to do exactly what I have done. Simply, just clear the KDE cache on your home directory --please follow the guideline that has been suggested by Fabrizio Montesi on his blog-- or upgrade the KDE-4.5.2 to KDE-4.5.3 (see announcement) that has been released on Nov 3, 2010. For detail information about the bug, please refer to this KDE Bug Tracking System.

How to fix Windows 7 Boot Manager when failed to start?

2010-10-26T14:37:00.000+07:00

After I repartitioned and installed Slackware64 on my laptop, the Windows 7 failed to start. The error status is 0xC0000225 and the error message is "the boot selection failed because a required device is inaccessible". This problem is easy to be fixed as long as you have a Windows 7 Recovery Disk. You just boot your PC/laptop using this disk and follow the instruction for repairing the Windows. After repair is finished, the disk will restart your PC/Laptop, then, you will get back the Windows 7.

Please note that you have to use the same version of recovery disk, I mean, if you have Windows 7 32-bit on your PC/Laptop, you have to use Windows 7 32-bit Recovery Disk, vice versa. You can create your own Recovery Disk from your existing Windows 7. For further information about creating Recovery Disk, please consult to Microsoft website.

How to fix my silent laptop?

2010-10-25T22:47:00.002+07:00

I have some problems with my new laptop: HP Pavilion dv3-4036TX. The first problem is the laptop was silent --it was no sound on the speaker-- after I installed Slackware64. However, if I plugged my headset to the headset plug-in port, I can hear the sound clearly. The simple steps for fixing this problem:

turn off the alsa using /etc/rc.d/rc.alsa stop
run alsaconf then follow the instructions

Please note that you have to run the steps above as root.
Now, I can hear my favorite songs from the speaker.

The first problem is solved. There are another problems that still need to be solved. I will share to you after I find out the solutions.

My First Day on Academic Activities at NTU

2010-08-30T11:21:00.007+07:00

Hi Readers,

Today (30/08/2010) is the first day of my MSc in Embedded System Program at Nanyang Technological University (NTU), as well, first day of all academic activities after Youth Olympic Games 2010. Moreover, it is my first time to enter Lee Wee Nam (LWN) Library, the library for Engineering and Science at NTU. All of those is very impressive and exciting for me.

First, I have had a discussion with A/Prof Suhaib about the topic of my dissertation project. I enjoyed the discussion and I have selected one topic from him for my dissertation. Tomorrow, I will register that topic to the School of Computer Engineering (SCE) System before I start to work on my dissertation.

Second, in LWN Library, there are so many journal that are "out of reached" by me when I was in Indonesia, most of them are IEEE society journal, on printed books, such as journal from Computational Intelligence Society, Computer Society, Robotics and Automation Society, Circuit and System Society, Education Society, Signal Processing Society, Systems, Man, and Cybernetics Society, and so on. In addition, there are some magazines that I am interested in, such as, Scientific American, Scientific American Minds, Discover Magazine, etc. It is awesome for me. From now, I can "waste" my time in LWN Library to read fascinating topics on those journals and magazines, especially those are related to my dissertation.

In conclusion, I really enjoy my activities today.

That's all that I can share with you. Thank's for being my readers.

PROLiNK PML501: Nano Wireless 2.4GHz Laser Mouse with 5-Button

2010-08-16T20:22:00.004+07:00

Hari ini (16/08/2010), saya membeli sebuah mouse PROLiNK PML501 untuk menggantikan mouse saya yang lama. Saya memilih produk ini karena beberapa alasan utama, yaitu: USB ~~bluetooth~~ WiFi receiver adapter yang kecil (karena itu nama produk ini ada kata "Nano"), dapat digunakan pada berbagai tempat karena sensornya menggunakan laser, ergonomis, hemat daya (menurut spesifikasinya, dapat digunakan sampai 6 bulan hanya dengan 1 baterai ukuran AA), dan tertulis bahwa produk ini dapat dioperasikan pada sistem operasi Linux. Mouse ini beroperasi pada frekuensi WiFi 2.4GHz dengan modulasi GFSK dan mempunyai resolusi max 1600 cpi. Untuk tombolnya, mouse ini mempunyai 5 tombol, yaitu: left-click, right-click, middle-click (scroll wheel), dan 2 tombol untuk prev - next (letaknya di samping kiri, dioperasikan dengan ibu jari tangan kanan untuk right-handed person). Uniknya, scroll wheel pada mouse ini dapat digunakan untuk vertical scroll dan horizontal scroll (biasanya, scroll wheel mouse hanya untuk vertical scroll saja), sehingga pengguna dapat dengan mudah melihat dokumen atau halaman web yang membutuhkan geser atas-bawah dan kanan-kiri. Untuk geser ke kanan-kiri, pengguna tinggal "bend" scroll wheel tersebut ke kanan atau ke kiri. Sangat mengasyikkan. Selain itu, ada tombol untuk memilih resolusi mouse; apakah 800 cpi atau 1600cpi. Pada bagian bawah mouse, ada switch untuk ON/OFF, serta tempat untuk menyimpan USB ~~bluetooth~~ WiFi receiver adapter saat tidak digunakan. Ada bonusnya, yaitu pouch untuk menyimpan mouse.

Sewaktu dicoba pada laptop saya dengan Slackware64 13.1 -current, mouse ini dapat terdeteksi tanpa ada masalah. Kelima tombol berfungsi dengan baik, bahkan tombol untuk memilih resolusi juga dapat berfungsi (saya yakin pasti dapat juga digunakan dengan baik pada Slackware 13.1). Vertical scroll dan horizontal scroll juga berfungsi dengan mulus. Amat menyenangkan. Sekarang, jika saya ingin melakukan PREV ataupun NEXT pada firefox, saya cukup menekan tombol prev - next yang ada pada mouse ini. Juga, ketika saya ingin melakukan geser horisontal ke kanan atau ke kiri, saya tinggal membengkokkan (bend) scroll wheel dari mouse ini ke kanan atau ke kiri.

Summary:
Today (16/08/2010), I have just bought a wireless laser mouse, i.e., PROLiNK PML501, that is a nano wireless 2.4GHz laser mouse with 5-buttons manufactured by PROLiNK. I chose this product because it has a small USB ~~bluetooth~~ WiFi receiver adapter on frequency of 2.4GHz using GFSK modulation, it is a laser mouse, ergonomic, low power consumption (based on its specification, 1 AA-battery can power it for 6 months), and, the important thing, it can be operated in Linux Operating System. This mouse has resolution up to 1600 cpi and there is a button for changing resolution from 800 cpi to 1600 cpi, vice versa. The 5 buttons are left-click, right-click, middle-click (scroll wheel), and 2 buttons for selecting PREV or NEXT on the browser. For scroll wheel, it can handle vertical scroll, as usual, and the new function: horizontal scroll, so that, if we want to scroll the document or browser horizontally, just bend the scroll wheel to the left or right. Awesome! On the bottom of the mouse, there are an ON/OFF switch and a place for keeping USB ~~bluetooth~~ WiFi receiver adapter when it is not used. The last, there is a bonus: a pouch for keeping the mouse when we are on travelling.

When I tried the mouse on my laptop with Slackware64 13.1 -current, the USB ~~bluetooth~~ WiFi receiver adapter can be detected perfectly (see picture above) so that the mouse can be used smoothly (I am sure it can also be used smoothly on Slackware 13.1). All of buttons are functionally working. Very nice. Therefore, if I want to go PREV or NEXT on firefox browser, I just click the prev or next button on my mouse. Also, I can make horizontally scroll easily from my mouse by bending the scroll wheel to the left or right.

I'm now in Singapore

2010-08-16T18:41:00.001+07:00

Dear Readers,

From the date of 12 August 2010, I will live in Singapore for 1 year (I hope and try to make it true) in order to take my Master of Science in Embedded System at Dept. of Computer Engineering, Nanyang Technological University (NTU). I will always write that I think it is valuable to be shared to all my readers.

Thank you for being my readers.

Genius iSlim 310 Webcam

2010-06-26T04:06:00.010+07:00

Beberapa waktu yang lalu, saya membeli webcam Genius iSlim 310 yang murah (sekitar Rp. 145.000,00) untuk memperlengkapi laptop saya yang belum ada built-in webcam.Fitur dari webcam ini adalah sebagai berikut:

300k pixel, resolusi VGA
up to 30fps
ada mikrofon
dapat diatur posisinya untuk desktop maupun laptop
frame format: PJPG (tetapi di website tertulis JPEG/WMV; mungkin karena menggunakan driver untuk jendela)
fokus manual
USB 1.1
Windows & Mac Support

Saya penasaran dengan pernyataan yang tertulis pada website Genius, bahwa webcam ini hanya disupport untuk penggunaan di Windows & Mac. Apakah di Linux, webcam ini tidak dapat digunakan?

Setelah saya coba untuk pasang ke laptop saya yang berisi Slackware64 13.1, ternyata hasilnya seperti gambar berikut ini:

Hanya mikrofonnya saja yang dikenali. Dari hasil lsusb, saya mendapatkan:

Lalu dengan VID 093Ah dan PID 2625h tersebut, saya search di internet, didapatkan, image chip yang digunakan adalah PAC7302, yang ternyata telah disupport oleh Linux Kernel dengan video driver gspca. Akan tetapi, jika diselidiki lebih lanjut, pada kernel source file pac7302.c yang terdapat pada /usr/src/linux/drivers/media/video/gspca maka tidak ada VID dan PID pada tabel usb_device_id (lihat tabel berikut ini), sehingga, walaupun driver telah ada, webcam tersebut tetap tidak dikenali.

/* -- module initialisation -- */
static const struct usb_device_id device_table[] __devinitconst = {
    {USB_DEVICE(0x06f8, 0x3009)},
    {USB_DEVICE(0x093a, 0x2620)},
    {USB_DEVICE(0x093a, 0x2621)},
    {USB_DEVICE(0x093a, 0x2622), .driver_info = FL_VFLIP},
    {USB_DEVICE(0x093a, 0x2624), .driver_info = FL_VFLIP},
    {USB_DEVICE(0x093a, 0x2626)},
    {USB_DEVICE(0x093a, 0x2628)},
    {USB_DEVICE(0x093a, 0x2629), .driver_info = FL_VFLIP},
    {USB_DEVICE(0x093a, 0x262a)},
    {USB_DEVICE(0x093a, 0x262c)},
    {}
};
MODULE_DEVICE_TABLE(usb, device_table);

Dari website https://patchwork.kernel.org/patch/106041/, telah tersedia patch untuk kernel sehingga webcam ini dikenali oleh sistem.

diff --git a/Documentation/video4linux/gspca.txt b/Documentation/video4linux/gspca.txt
index f13eb03..f9b9d32 100644
--- a/Documentation/video4linux/gspca.txt
+++ b/Documentation/video4linux/gspca.txt
@@ -253,6 +253,7 @@ pac7302  093a:2620 Apollo AC-905
 pac7302  093a:2621 PAC731x
 pac7302  093a:2622 Genius Eye 312
 pac7302  093a:2624 PAC7302
+pac7302  093a:2625 Genius iSlim 310
 pac7302  093a:2626 Labtec 2200
 pac7302  093a:2628 Genius iLook 300
 pac7302  093a:2629 Genious iSlim 300
diff --git a/drivers/media/video/gspca/pac7302.c b/drivers/media/video/gspca/pac7302.c
index 2a68220..7c0f265 100644
--- a/drivers/media/video/gspca/pac7302.c
+++ b/drivers/media/video/gspca/pac7302.c
@@ -1200,6 +1200,7 @@ static const struct usb_device_id device_table[] __devinitconst = {
 {USB_DEVICE(0x093a, 0x2621)},
 {USB_DEVICE(0x093a, 0x2622), .driver_info = FL_VFLIP},
 {USB_DEVICE(0x093a, 0x2624), .driver_info = FL_VFLIP},
+ {USB_DEVICE(0x093a, 0x2625)},
 {USB_DEVICE(0x093a, 0x2626)},
 {USB_DEVICE(0x093a, 0x2628)},
 {USB_DEVICE(0x093a, 0x2629), .driver_info = FL_VFLIP},

Patch tersebut dicopy dari website tersebut, lalu disimpan pada suatu file yang diberi nama, misalnya: patch-genius-islim-310, dan diletakkan dalam directory /usr/src. Selanjutnya, saya mendownload kernel source 2.6.34 dan extract ke /usr/src. Sebagai catatan, versi kernel yang digunakan tidak harus versi 2.6.34, asalkan, versi kernel yang digunakan telah mensupport PAC7302 (saya tidak tahu mulai versi berapa). Beberapa langkah selanjutnya (root mode) pada Slackware64 atau Slackware 13.1 adalah sebagai berikut:

pada terminal: ln -s /usr/src/linux/linux-2.6.34 /usr/src/linux
pada terminal: cd /usr/src/linux
pada terminal: patch -p1 -i ../patch-genius-islim-310
pada terminal: cp /boot/config-huge-2.6.33.4 /usr/src/linux/.config
pada terminal: make oldconfig
pada terminal: make xconfig atau make menuconfig (jika ingin mengganti konfigurasi)
pada terminal: make bzImage
pada terminal: cp arch/boot/x86/bzImage /boot/vmlinuz-2.6.34
pada terminal: make modules
pada terminal: make modules_install
pada terminal: cp System.map /boot/System.map-2.6.34
pada terminal: cp .config /boot/config-2.6.34
edit lilo.conf jika diperlukan atau buat symlink dari vmlinuz-2.6.34, System.map-2.6.34, config-2.6.34 ke vmlinuz, System.map, dan config
pada terminal: lilo
restart untuk menggunakan kernel hasil patch

Untuk versi kernel atau distro Linux yang berbeda, silakan dikonversi sendiri. Hasilnya:

Webcam telah dikenali, baik video maupun audio (mikrofon). Hasil test dengan qv4l2:

Selanjutnya, saya mencoba untuk menggunakan webcam ini dengan skype, tidak ada masalah. Masalah baru muncul ketika saya mencoba untuk membuat program sederhana menggunakan OpenCV, ternyata, OpenCV tidak mengenali format PJPG, error message:

HIGHGUI ERROR: V4L2: Pixel format of incoming image is unsupported by OpenCV

Sebagai catatan, saya menggunakan OpenCV 2.0.0. Versi terbaru dari OpenCV adalah 2.1.0. Mungkin saja, pada versi 2.1.0, format PJPG telah disupport oleh OpenCV ... belum dicoba ... Jika Anda telah mencobanya sebelum saya mencoba, mohon diinformasikan ke saya. Summary: I have bought a cheap webcam from Genius, that is, Genius iSlim 310 for my laptop that is not equipped with built-in webcam. For the features and specification of this webcam, please check this website. Unfortunately, when I connected to my laptop with Slackware64 13.1, only the audio (microphone) has been recognized (see second picture). Result of lsusb indicated that VID and PID of this webcam are 093Ah and 2625h, respectively (see third picture). The VID and PID of this webcam give the information that image chip of this webcam is PAC7302 that has been supported by current kernel but the VID and PID are not listed on usb_device_id table in pac7302.c. From https://patchwork.kernel.org/patch/106041/, I found that there is a patch for kernel to modify /usr/src/linux/drivers/media/video/gspca/pac7302.c so that the kernel can recognized the webcam when it is connected to system. The steps of patching and compiling the kernel in Slackware or Slackware64 13.1 (root mode) are:

copy the newest version of kernel or the version that has supported PAC7302, then extract to /usr/src. I use kernel version of 2.6.34. The last kernel version of Slackware 13.1 is 2.6.33.4
make symlink: ln -s /usr/src/linux/linux-2.6.34 /usr/src/linux
save the patch from that website as a file, for instance, patch-genius-islim-310, then save that file in /usr/src directory
in terminal: cd /usr/src/linux
in terminal: patch -p1 -i ../patch-genius-islim-310
in terminal: cp /boot/config-huge-2.6.33.4 /usr/src/linux/.config
in terminal: make oldconfig
in terminal: make xconfig or make menuconfig (if needed)
in terminal: make bzImage
in terminal: cp arch/boot/x86/bzImage /boot/vmlinuz-2.6.34
in terminal: make modules
in terminal: make modules_install
in terminal: cp System.map /boot/System.map-2.6.34
in terminal: cp .config /boot/config-2.6.34
edit lilo.conf if needed or make symlink from vmlinuz-2.6.34, System.map-2.6.34, and config-2.6.34 to vmlinuz, System.map, and config respectively
in terminal: lilo
restart system for activating patched kernel

Note that if you use different Linux distribution, different kernel version, and/or different boot loader, please convert yourself the steps above. The result of patched kernel is the system can recognized this webcam (see fourth picture). I have tested on qv4l2 (see fifth and sixth pictures)and skype, so far so good. However, when I tried to access the webcam from my own program that use OpenCV Library v.2.0.0, there was an error message that told if the PJPG is unsupported by OpenCV:

HIGHGUI ERROR: V4L2: Pixel format of incoming image is unsupported by OpenCV

I have not tried for OpenCV 2.1.0 yet. I will try it later if I have a chance. Please tell me if you have tried it.

OpenOffice.org 3.2.1 for Slackware64

2010-06-17T14:33:00.004+07:00

Bagi pengguna Slackware64, kita dapat menggunakan OpenOffice versi 64-bit yang telah tersedia. Caranya amat sangat mudah. Anda hanya perlu mengerjakan beberapa langkah berikut ini:

Download OpenOffice.org 3.2.1 versi 64-bit di sini.
Download SlackBuild script di sini.
Extract compressed SlackBuild script openoffice.org.tar.gz (tar -xvzf openoffice.org.tar.gz) maka akan muncul directory openoffice.org
Copy atau move file OOo_3.2.1_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz ke dalam directory tersebut pada langkah 3.
Dengan working directory openoffice.org dan user root, jalankan script openoffice.org.SlackBuild (./openoffice.org.SlackBuild).
Jika tidak ada error, maka Anda akan mendapatkan file /tmp/openoffice.org-3.2.1_en_US-x86_64-1_SBo.tgz
Jalankan upgradepkg --install-new /tmp/openoffice.org-3.2.1_en_US-x86_64-1_SBo.tgz (berlaku untuk install baru maupun upgrade).
Done.

Sangat mudah bukan?

Summary:
For anyone that use Slackware64, you can install and use OpenOffice.org 3.2.1 64-bit version that has been ready to be used very easily. You only have to do following steps:

Download OpenOffice.org 3.2.1 64-bit version here.
Download SlackBuild script here.
Extract compressed SlackBuild script openoffice.org.tar.gz (tar -xvzf openoffice.org.tar.gz) then you will see openoffice.org directory
Copy or move OOo_3.2.1_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz into that directory.
Make sure the working directory is openoffice.org and as root user, run the script openoffice.org.SlackBuild using this command: ./openoffice.org.SlackBuild
If no error found, then you will get /tmp/openoffice.org-3.2.1_en_US-x86_64-1_SBo.tgz
Run upgradepkg --install-new /tmp/openoffice.org-3.2.1_en_US-x86_64-1_SBo.tgz for installing or upgrading OpenOffice.org to your system.
Done.

Piece a cake, isn't it?

Slack-ID Magazine

2010-04-08T15:57:00.000+07:00

Sebenarnya sudah terlambat untuk menuliskan ini, tetapi, karena di mailing list id-slackware masih ada yang bertanya, lebih baik saya tuliskan saja di blog saya supaya yang membaca blog saya memperoleh informasi ini.

Pada bulan Desember 2009 yang lalu, telah diterbitkan edisi perdana dari majalah elektronik "Slack-ID", suatu majalah tentang Slackware dalam bahasa Indonesia yang ditulis oleh komunitas id-slackware. Tujuan dari majalah ini adalah untuk memberikan informasi tentang slackware kepada komunitas slackware di Indonesia, sebagai wadah untuk saling berbagi ilmu. Majalah ini tidak gratis. Hanya saja, untuk edisi perdana, diedarkan gratis; Anda bisa mendownload dari http://daunsalam.net/slackid.htm. Untuk edisi selanjutnya, Anda dapat memperolehnya dengan berkontribusi dana sebesar Rp. 10.000,00 per edisi. Seluruh dana yang diperoleh tidak dipakai untuk redaksi majalah ini, tetapi akan disumbangkan untuk membantu kelangsungan proyek resmi Slackware yang dipimpin oleh Patrick Volkerding.

Summary:
On December 2009, there are new release of Indonesian Slackware Magazine, "Slack-ID", an Indonesian magazine that talk about Slackware written by Indonesian Slackware Community. The aim of this magazine is to share information about Slackware for Indonesian Slackware community. For first edition, this magazine is free, you can download it from http://daunsalam.net/slackid.htm. However, for next editions, you have to pay the cost of Ro. 10.000,00 before you can download it. All of money earned from you will be sent to official Slackware Maintainer, Patrick Volkerding, for supporting him to maintain Slackware Project.

New Project: Digital Music Studio on Slackware

2009-11-28T20:22:00.002+07:00

Sebenarnya, sejak tahun lalu, saya ingin memulai projek ini, tetapi, karena kesibukan dan belum terlalu diperlukan, akhirnya, saya tunda. Namun, pada pertengahan bulan November ini, karena kebutuhan untuk aransemen lagu-lagu untuk acara perayaan Natal di gereja --kebetulan lagunya berjibun banyaknya dan aransemennya sangat kompleks, bahkan ada 5 lagu dengan beda rhythm style, tempo, dan nada dasar (variasi overtone dan undertone) yang dimainkan medley, sehingga susah jika mengandalkan hafalan karena waktu latihan terbatas-- mau tidak mau akhirnya saya mulai saja projek ini. Sebenarnya juga ... :) ... bisa pakai distro yang khusus untuk digital studio seperti 64Studio turunan debian, Ubuntu Studio, dan lainnya, tapi, karena saya cinta Slackware ... :) ... maka saya berusaha membuat Slackware ready untuk Digital Studio. Langkahnya cukup panjang, tapi sekarang ini Slackware64 di Laptop saya mulai menjadi digital studio saya, walaupun, masih ada yang belum saya eksplore; misalnya: waktu saya coba hubungkan RD-700SX ke Laptop via USB (Midi), masih belum lancar, dll. Yang sudah OK adalah penggunaan hydrogen untuk drum programming. Ada lagu yang sudah pakai hydrogen, untuk membantu pemain drum di grup saya dan untuk "mempercantik" lagu, yang kebetulan cenderung Ballad.

Itu dulu yang bisa saya ceritakan ... Semoga akhir Desember nanti saya bisa cerita lebih banyak, mulai dari patching kernel, instalasi software, sampai pada aplikasinya di gereja.

Summary:
Since last year, I wanted to start this project, unfortunately, I had a lot of job to do so that I decided to postpone the project. However, in the mid of this month (November), I needed to write and analyze my song arrangements that I have been worked for this Christmas in the church. The arrangements are very complex; many songs have to play and there are 5 songs that have to play in medley with different rhythm styles, pitch, and tempo. Actually, nowadays, there are some distros that are built for digital studio such as 64Studio, Ubuntu Studio, etc. But, I love Slackware ... :) ... so that I will try to make Slackware64 on my Laptop to accommodate ideal system resources for digital studio. Today, I can use my Laptop, with Slackware64 running on it, as digital studio, but I have not explored all features and still get some problems such as connection problem between RD-700SX and Laptop via USB (Midi). I have used hydrogen, a drum programming software, for helping my drummer playing in a ballad style's song.

That's all that I can share now ... I hope, I can share more details from patching the kernel, software compilation and installation, until the application of digital studio in the church.

Opini: Menggunakan Linux dan Open Source Software adalah suatu pilihan

2009-10-29T10:03:00.007+07:00

-- For English readers, please apologize me ... I wrote this article in Indonesian only --

Artikel ini merupakan opini saya tentang penggunaan Linux dan Open Source Software (OSS) yang adalah pilihan bagi masing-masing individu. Diawali dengan 5 butir pemikiran pribadi berdasarkan pengalaman pribadi saya, saya menyimpulkan bahwa pilihan untuk menggunakan Linux dan OSS tidak dapat dipaksakan, tetapi, walaupun begitu, bagi komunitas pengguna Linux dan OSS, jika kita tidak mengenalkan Linux dan OSS pada komunitas bukan pengguna Linux dan OSS, bagaimana mereka bisa memilih untuk menggunakan Linux dan OSS? Tidak kenal Linux dan OSS, pasti tidak akan memilih Linux dan OSS.

Beberapa waktu yang lalu, saya pernah didebat oleh beberapa rekan kerja saya tentang keuntungan penggunaan Linux dan OSS seperti OpenOffice.org, Blender, Gimp, dll, dalam aplikasi sehari-hari. Mereka beropini, menggunakan Linux dan OSS itu sedikit untungnya tetapi banyak susahnya. Mereka mencontohkan jika mereka ingin menginstall program harus selalu memperhatikan dependencies dari program tersebut; belum lagi masalah konfigurasi yang "njlimet". Selain itu, upgrade programnya juga terlalu sering, sehingga cukup merepotkan. Lalu, mereka membandingkan dengan penggunaan sebuah propriatery operating system dan propriatery software-software lain yang sangat terkenal dan banyak digunakan. Menurut mereka, banyak sekali kemudahan-kemudahan yang dialami seperti instalasi program baru yang sangat mudah dan upgrade yang sangat jarang. Salah satu statement mereka adalah "Hidup kok dibuat susah ... yang gampang-gampang saja ... ngapain susah-susah pakai Linux dan OSS padahal ada yang gampang ..."

Didebat seperti itu, saya, yang sejak akhir tahun 2003 telah secara total menggunakan Linux dan OSS, tidak langsung mendebat keras, tetapi, saya mulai menjelaskan, paling tidak, pemikiran dan opini saya tentang Linux dan OSS, sebenarnya apa sih alasan saya menggunakan Linux dan OSS ...

Pertama, dan juga tidak bisa ditawar-tawar lagi, masalah lisensi. Sebagian besar propriatery operating system dan software dijual dalam harga yang relatif mahal, terutama buat saya. Bisa-bisa, gaji saya sebulan habis untuk beli software ... itupun cuma dapat beberapa software ... Kalau membajak, sudah pasti, melanggar UU HAKI. Nah, solusi bagi siapa saja yang tidak berduit banyak dan ingin tidak melanggar UU HAKI, hanya satu: menggunakan Linux dan OSS. Dengan biaya yang relatif tidak mahal, kita bisa menggunakan Linux dan OSS dengan bebas, dalam koridor lisensi OSS seperti GPL, dsb.

Kedua, berdasarkan pengalaman saya, penggunaan Linux dan OSS membuat penghematan kapasitas hard disk yang sangat luar biasa. Sewaktu masih menggunakan propriatery operating system dan software, saya membutuhkan kapasitas hard disk minimal 20GB, dan itu sangat cepat "habis" jika banyak program yang diinstall. Bahkan, saya pernah mendengar keluh-kesah teman saya, kalau hard disk yang 160GB saja sekarang ini sudah tidak "layak" digunakan lagi karena propriatery operating system dan software yang baru sudah sangat "boros". Ketika saya beralih ke Linux dan OSS, kapasitas hard disk yang saya gunakan untuk operating system dan software tidak lebih dari 12 GB; itu sudah super sangat banyak OSS yang saya install pada Laptop saya. Sisanya, bisa "foya-foya" untuk data.

Ketiga, Linux dan OSS relatif "ringan", relatif tidak banyak menyedot resources PC/Laptop. Propriatery software dan operating system yang baru rata-rata mensyaratkan spesifikasi hardware yang sangat tinggi, entah itu prosesornya atau kapasitas RAM; sekarang ini, sebagian besar mensyaratkan penggunaan minimal prosesor sekelas Pentium 4 dan RAM 1GB, itupun dengan konfigurasi hardware minimal, sangat terasa "lemot"-nya (lemot = lambat). Untuk Linux dan OSS, spesifikasi hardware yang dibutuhkan lebih rendah dari itu; bisa saja prosesor sekelas Pentium II atau III, RAM cuma 512MB (itu jika menggunakan KDE atau Gnome). Bahkan, Linux dan OSS, beberapa masih bisa jalan pada komputer tua; tentu saja jangan menggunakan KDE atau Gnome :) ... Dari penjelasan tersebut, PC/Laptop yang berspesifikasi tinggi --jika menggunakan propriatery operating system dan software ternyata performance-nya biasa-biasa saja-- pasti akan terasa cepat, dengan kata lain, performance-nya akan "sip" jika menggunakan Linux dan OSS, untuk mengerjakan pekerjaan yang levelnya sama, dengan hasil yang sama pula ... so pasti ... hemat waktu mengerjakan dan tidak perlu jengkel menunggu loading software :) ...

Keempat, juga berdasarkan pengalaman saya, penggunaan Linux dan OSS akan membuat penggunanya semakin mengerti proses yang terjadi saat booting, eksekusi program, cara kerja operating system, cara kerja driver, konsep networking, konsep multi user, bahkan, jika pengguna mempunyai skill programming yang baik dan mencoba untuk mengeksplorasi source code dari OSS maka pengguna tersebut akan mendapatkan banyak sekali pengetahuan yang tidak ternilai harganya untuk pengembangan diri. Saya, sebagai seorang dosen, sering mendapatkan hal-hal baru yang dulunya belum pernah saya ketahui, dan pengetahuan baru itu dapat memperkaya saya saat saya mengajar. berdiskusi, serta membimbing mahasiswa-mahasiswa saya dalam hal Arsitektur Komputer, Programming, Networking, dan Embedded System. Hal inilah yang terus-menerus memacu saya untuk mengoprek Linux dan OSS.

Kelima, yang ini akan terasa sangat idealis, penggunaan Linux dan OSS tidak membuat saya terikat pada suatu perusahaan atau sekelompok orang yang eksklusif, tertutup, dan berorientasi total pada profit. Memang, dalam dunia industri dan perdagangan, profit itu yang terutama dan pasti ada usaha-usaha khusus untuk "mengamankan" profit, misalnya, dengan cara meng-"close" akses-akses yang dapat mengurangi peningkatan profit seperti menutup source code, memasang dongle hardware, dsb. Itu wajar. Akan tetapi, sebagai anggota suatu komunitas sosial, apa salahnya jika share kepada orang lain yang memang membutuhkan tetapi mengalami keterbatasan untuk mendapatkan. Pemikiran saya, misalnya, suatu perusahaan pengembang software membebaskan penggunaan software untuk kalangan pelajar dan organisasi sosial, perusahaan tersebut masih tetap dapat memperoleh profit pada beberapa waktu yang akan datang; karena pelajar yang terbiasa menggunakan software tersebut, saat bekerja di suatu perusahaan lain, pasti akan menyarankan atasannya untuk menggunakan software tersebut, sehingga perusahaan tersebut akan membeli lisensi penggunaan software dari perusahaan pengembang software itu --> ini kan menghasilkan profit! Contoh lain, karena pelajar tersebut telah menyarankan penggunaan software tersebut, perusahaan tempat pelajar tersebut bekerja bisa membeli jasa technical support dari perusahaan pengembang --> profit lagi! Jadi, perusahaan-perusahaan pengembang software yang tidak sekedar mengutamakan profit, kelihatannya rugi di awal-awal, tetapi, setelah beberapa waktu lamanya, mereka akan menuai profit yang besar. Konsep inilah yang diterapkan oleh perusahaan-perusahaan pengembang OSS dan free software seperti Trolltech (kelihatannya sekarang telah diakuisisi oleh Nokia) dengan Qt-nya, RedHat dengan RHEL, Fedora-nya, Novell dengan SUSE Enterprise-nya, Sun dengan Java, Open Solaris, OpenOffice.org, Virtual Box-nya, dsb. Perusahaan-perusahaan tersebut tidak bangkrut gara-gara share dengan komunitas, malahan, mereka semakin unjuk gigi sehingga perusahaan pengembang propriatery software perlu mewaspadai mereka dalam persaingan industri software.

Nah ... berdasarkan kelima pemikiran/opini saya itu, saya menyimpulkan bahwa sebenarnya penggunaan Linux dan OSS itu merupakan pilihan individu, tidak dapat dipaksakan, karena tiap individu mempunyai pemikiran sendiri-sendiri tentang apa yang dianggap baik dan bermanfaat. Bagi yang suka menggunakan propriatery software, silakan saja, asal tidak melanggar hukum. Bagi pengguna OSS, silakan menggunakan dengan bebas dalam koridor lisensi yang biasanya disebutkan pada dokumen license.txt.

Logikanya, bagaimana mereka bisa memilih menggunakan OSS jika mereka tidak mengenal OSS?

Akhir kata, bagi saya dan pengguna OSS, dalam mempopulerkan OSS, kita perlu mengenalkan OSS kepada semua pengguna propriatery software, minimal, beri kesempatan kepada mereka untuk "mencicipi" OSS, selanjutnya terserah mereka ... Logikanya, bagaimana mereka bisa memilih menggunakan OSS jika mereka tidak mengenal OSS? Hal ini yang saya lakukan di laboratorium. Mahasiswa semester dua saya kenalkan dengan Linux dan OSS; mereka menggunakannya dalam waktu satu semester. Selanjutnya ... terserah mereka. Berdasarkan pengalaman saya, paling tidak sekitar 30% - 40% dari mereka, tertarik untuk mencoba Linux dan OSS lebih dalam. Langkah saya juga diikuti oleh dosen-dosen dari jurusan, fakultas, dan departemen lain yang juga mengenalkan OSS untuk kegiatan perkuliahan dan laboratorium, seperti penggunaan R untuk statistik, Maxima serta wxMaxima untuk matematika, OpenOffice.org untuk dokumentasi laporan mahasiswa, NetKit dan ns-2 untuk networking, dan Scilab untuk aplikasi signal processing.

3-in-1 USB Converter

2009-10-28T09:03:00.002+07:00

Berawal dari permasalahan yang dialami oleh 2 mahasiswa saya, yang pada saat itu membutuhkan suatu ARM Bootloader yang bisa digunakan pada Laptop --ARM Bootloader yang tersedia adalah ARM Bootloader yang menggunakan Serial Port (COM Port), padahal port ini sudah tidak ada lagi pada Laptop--, saya mulai mendesain suatu ARM Bootloader yang menggunakan USB Port menggunakan IC FT232RL keluaran FTDI Limited. Dalam pengembangan desain, saya mulai berpikir untuk mengakomodasi beberapa kebutuhan dasar mahasiswa saya yang lain dan juga dosen-dosen yang lain, yang mana mereka membutuhkan suatu converter dari USB ke UART untuk sistem minimum berbasis mikrokontroler atau mikroprosesor serta converter dari USB ke ZigBee untuk aplikasi image processing pada mobile robot yang dikendalikan dari Laptop secara wireless. Akhirnya, jadilah suatu alat yang saya beri nama 3-in-1 USB Converter, yang seharusnya dapat digunakan pada semua platform (sudah dites dan dapat digunakan pada platform Linux dan Windows). Untuk diketahui bahwa dalam mendesain converter ini, saya secara total menggunakan Open Source Software yang berjalan pada sistem operasi Linux, seperti: gEDA, pcb, minicom, Code::Blocks, wxWidgets, dan libftdi. Hal ini membuktikan bahwa Open Source Software sudah berkembang dengan pesat dan dapat diandalkan dalam aplikasi sehari-hari, mulai dari aplikasi level designer, developer, sampai dengan aplikasi level end-user.

Skema rangkaian dari 3-in-1 USB Converter dapat dilihat pada gambar berikut. Sebagai catatan, hanya gunakan 1 fungsi untuk 1 penggunaan, maksudnya, jika converter ini digunakan sebagai USB to UART Converter, sebaiknya jangan digunakan sebagai USB to ZigBee Converter atau ARM Bootloader. Hal ini dikarenakan jalur komunikasi pada IC FT232RL digunakan secara shared pada ketiga fungsi ini; converter ini hanya menggunakan 1 IC FT232RL dan IC ini hanya mempunyai 1 channel jalur komunikasi. Ada 3 jumper yang digunakan untuk konfigurasi seperti tegangan supply dari I/O --J2-- (+5V atau +3.3V), asal tegangan supply --J1-- (USB-powered atau self-powered), dan aktivasi ARM Bootloader --J3--.

Desain menggunakan gEDA dan pcb:

Hasil akhir dari 3-in-1 USB Converter ini dapat dilihat pada gambar berikut:

Pesan dmesg saat 3-in-1 USB Converter dihubungkan pada Laptop:

Setting minicom dan tampilan pada minicom saat ujicoba:

Program ujicoba yang di-develop menggunakan Code::Blocks dan library wxWidgets dan libftdi:

Jika Anda tertarik untuk memperoleh 3-in-1 USB Converter yang siap pakai, silakan menghubungi saya via e-mail untuk informasi lebih lanjut. Alamat e-mail saya dapat dilihat pada Profile saya.

Referensi:

FT232R Datasheet.

Summary:
When I see that 2 of my students had difficulty in their undergraduate final project since there was no USB ARM Bootloader that could be used, I decided to develop USB ARM Bootloader using IC FT232RL, manufactured by FTDI Limited. In next step of development, I tried to accomodate the needs of my other students and my colleagues that need USB to UART converter for serial communication between PC/Laptop and microprocessor- or microcontroller-based minimum system and USB to ZigBee converter for image processing applied to mobile robot system that is controlled by PC/Laptop wirelessly. Please note that I totally used Open Source Software, such as gEDA, pcb, minicom, Code::Blocks, wxWidgets, dan libftdi, in phase of development and testing of the 3-in-1 USB Converter.

There are some notes:

You cannot use all functions in one time, because FT232RL has only one channel. I shared this channel for all functions.
There are 3 jumpers for configuration: J1 for USB-powered or self-powered I/O selector, J2 for selecting +5V or +3.3V supply of I/O, and J3 for activating ARM Bootloader function.

You can look all of pictures above for schematics, the product, etc. For more information about this product, please do not hesitate to contact me via e-mail (see my profile).

Slackbuild script untuk AVR Development Software

2009-10-15T09:48:00.001+07:00

Bagi pengguna Linux dan ingin bereksperimen dengan mikrokontroler AVR, sekarang ini Anda sudah dapat bereksperimen secara penuh pada platform Linux. Beberapa development software yang dibutuhkan adalah kelompok avr-binutils, avr-gcc, avr-gdb, avr-libc, dan avrdude. Sebagai firmware downloader, Anda dapat menggunakan USBasp yang didesain oleh Thomas Fischl, yang juga sudah saya bahas pada blog saya ini. Untuk para Slackers yang ingin mencoba mikrokontroler AVR, Anda dapat menginstall semua development software dari mikrokontroler AVR dengan Slackbuild script. Anda tinggal mendownload script dan source file lalu jalankan script-nya.

Yang telah saya kerjakan dengan Slackbuild script, setelah selesai mendownload semuanya, saya mencari versi terbaru pada saat itu. Ternyata, hanya Slackbuild script untuk gcc saja yang perlu diedit karena saya memutuskan menggunakan gcc versi 4.4.1 daripada gcc versi 4.3.4. Jadi, saya edit baris ini dari avr-gcc.SlackBuild:

VERSION=${VERSION:-4.3.4}

menjadi:

VERSION=${VERSION:-4.4.1}

Untuk semua Slackbuild script, karena saya menggunakan Slackware64 13.0, maka baris ini:

ARCH=${ARCH:-i486}

saya edit menjadi:

ARCH=${ARCH:-x86_64}

Catatan: jika Anda menggunakan Slackware 13.0, Anda tidak perlu mengedit baris tersebut.

Setelah selesai menjalankan semua Slackbuild scripts, saya mendapatkan paket-paket berikut ini:

avr-binutils-2.19.1-x86_64-1_SBo.tgz
avr-gcc-4.4.1-x86_64-1_SBo.tgz
avr-gdb-6.8-x86_64-1_SBo.tgz
avr-libc-1.6.7-x86_64-2_SBo.tgz
avrdude-5.8-x86_64-1_SBo.tgz

yang selanjutnya saya install menggunakan command installpkg.

Referensi:

http://slackbuilds.org/result/?search=avr&sv=13.0

Summary:
For Slackers that want to make experiments on AVR microcontrollers, now, you have all of AVR Development Software running in your Slackware. You can use Slackbuild scripts to build installer packages of these: avr-binutils, avr-gcc, avr-gdb, avr-libc, and avrdude. The only script that you have to edit if you want to build newer version is avr-gcc.SlackBuild, please edit the following line:

VERSION=${VERSION:-4.3.4}

become this:

VERSION=${VERSION:-4.4.1}

For Slackware64 users, as usual, you have to change the following line:

ARCH=${ARCH:-i486}

to be like this line:

ARCH=${ARCH:-x86_64}

The packages that I have been built using Slackbuild scripts:

avr-binutils-2.19.1-x86_64-1_SBo.tgz
avr-gcc-4.4.1-x86_64-1_SBo.tgz
avr-gdb-6.8-x86_64-1_SBo.tgz
avr-libc-1.6.7-x86_64-2_SBo.tgz
avrdude-5.8-x86_64-1_SBo.tgz

then I installed them using installpkg command.

USBasp

2009-10-14T23:00:00.005+07:00

USBasp adalah sebuah USB In-circuit programmer untuk mikrokontroler AVR yang didesain oleh Thomas Fischl. Penggunaannya cukup mudah dan dapat dijalankan pada platform Linux, Mac OS X, maupun Windows. USBasp dapat men-download firmware ke internal flash dari mikrokontroler AVR yang menjadi targetnya dengan kecepatan maksimal 5 kB/s dan tersedia jumper untuk men-set USBasp agar support mikrokontroler AVR target yang mempunyai low clock speed (< 1.5MHz); biasanya, jika kita membeli mikrokontroler AVR yang baru, by default, kebanyakan AVR tersebut di-set menggunakan internal clock frekuensi 1MHz (untuk mengubah setting clock ini, Anda harus memprogram LFUSE, HFUSE, dan/atau EFUSE; silakan lihat datasheet dari mikrokontroler AVR yang digunakan untuk lebih rincinya).

Berdasarkan skema rangkaian dari Thomas Fischl, saya membuat artwork PCB untuk USBasp yang nantinya saya, beserta Laboratorium Otomasi dan Sistem Embedded, Jurusan Teknik Elektro, Universitas Surabaya, gunakan untuk men-download firmware ke internal flash dari mikrokontroler AVR, seperti untuk praktikum mata kuliah Mikrokontroler dan proyek pembuatan intelligent robot. (hardware robot yang digunakan pada Ubaya Robosoccer Competition 2009 dikembangkan menggunakan mikrokontroler AVR). Program yang saya gunakan untuk menggambar ulang skema rangkaian serta membuat artwork PCB-nya adalah gEDA dan pcb, suatu GPL'ed Electronic Design Automation Suite yang sangat layak diandalkan, dan terlebih lagi (dan yang paling penting), program ini berjalan di atas platform Linux. Gambar berikut ini menunjukkan tampilan gEDA dan pcb untuk pembuatan USBasp.

Setelah dicetak dan disolder seluruh komponennya, serta, firmware USBasp telah di-download-kan ke ATmega8 yang digunakan pada USBasp ini, maka hasil akhirnya dapat dilihat pada gambar berikut ini:

USBasp in action menggunakan AVRDude sebagai ISP Software:

Jika Anda tertarik untuk memperoleh USBasp yang siap pakai atau masih dalam bentuk belum disolder, silakan menghubungi saya via e-mail untuk informasi lebih lanjut. Alamat e-mail saya dapat dilihat pada Profile saya.

Solusi jika USBasp tidak dapat digunakan oleh user biasa di Linux
Jika pada saat Anda menggunakan USBasp sebagai user biasa di Linux, ternyata USBasp Anda tidak dapat digunakan, tetapi saat Anda sebagai root atau superuser, ternyata USBasp tersebut dapat digunakan, berarti Anda sebagai user biasa tidak mempunyai hak akses ke USBasp. Solusi untuk masalah ini cukup mudah. Anda harus membuat file baru dengan nama 99-usbasp-rules pada direktori /lib/udev/rules.d yang isinya sebagai berikut:

# allow users to claim the device

ACTION=="add" SUBSYSTEM=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", MODE="0664", GROUP="plugdev"

untuk idVendor dan idProduct dapat Anda ketahui melalui command: lsusb (dengan catatan Anda sebagai root atau superuser dan USBasp Anda terhubung ke PC/Laptop). Setelah file tersebut di-save, re-plug USBasp Anda dan Anda akan mempunyai hak akses ke USBasp. Jangan lupa, pastikan user biasa tersebut telah menjadi group member dari plugdev.

Referensi:

Summary:
This article shows USBasp, a USB in-circuit programmer for Atmel AVR Controllers, designed by Thomas Fischl. I have created PCB artwork for USBasp using gEDA and pcb, a GPL'ed Electronic Design Automation Suite that is running on Linux, then have applied it to all activities/projects related to AVR microcontroller in my laboratory, such as laboratory session for my students and intelligent robot developments.

If your USBasp cannot be used by user, but it can be detected and used by root, you have to add an udev rule in directory /lib/udev/rules.d through these steps (as a superuser or root):

create new file: 99-usbasp-rules
add these lines below to the file (you can obtain idVendor and idProduct by lsusb command as root and make sure your USBasp connected to your PC/laptop):

ACTION=="add" SUBSYSTEM=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", MODE="0664", GROUP="plugdev"

save the file
copy it to /lib/udev/rules.d (note: you must be a root to do this)
re-plug your USBasp

Now, you can use your USBasp in user mode.

Kompilasi dan Instalasi OpenCV 2.0.0 pada Linux -- Compiling & Installing OpenCV 2.0.0 on Linux --

2009-10-12T14:25:00.003+07:00

Seperti yang telah saya janjikan pada tulisan sebelumnya, sekarang saya ingin membagikan pengalaman saya saat melakukan kompilasi dan instalasi OpenCV 2.0.0 di laptop saya. Distro Linux yang saya gunakan adalah Slackware64 13.0, tapi, menurut saya, pengalaman saya ini merupakan pengalaman untuk Linux secara umum, tidak tergantung distro. OK, kita mulai ...

Langkah pertama, sudah pasti, kita harus memastikan semua dependencies dari OpenCV 2.0.0 telah terinstall dengan baik pada PC/Laptop kita. Biasanya, untuk OpenCV, saya inginnya yang lengkap. Ada beberapa program yang merupakan dependencies dari OpenCV 2.0.0 yang "harus ada" (menurut kebutuhan dan mau saya), antara lain: xinelib, ffmpeg, libdc1394, v4l, swig, python, libjpeg, zlib, libpng, libtiff, libjasper. Untuk Slackware/Slackware64 13.0, beberapa dependencies seperti xinelib, swig, python, libjpeg, zlib, libpng, libtiff, dan libjasper telah terinstall; saya hanya perlu menambahkan ffmpeg, libdc1394, dan v4l. Mengenai cara mencari dan menambahkan dependencies, silakan dibaca pada manual distro masing-masing.

Setelah semua dependencies sudah terinstall, langkah kedua adalah kompilasi OpenCV 2.0.0. Untuk versi 2.0.0 ini, ada 2 cara kompilasi, yang pertama, cara klasik, menggunakan configure dan make; cara yang kedua adalah menggunakan cmake dan make. Saya telah mencoba kedua cara tersebut. Untuk yang menggunakan cmake, sebenarnya cara ini lebih mudah dan user-friendly (sejauh yang saya rasakan) tapi saat saya coba, setelah 85% proses kompilasi, muncul error.

# cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -D BUILD_PYTHON_SUPPORT=ON -D BUILD_LATEX_DOCS=ON ..

Jika tidak ada error, lalu: 

# make 

Error yang muncul:

...
Linking CXX shared library ../../lib/libcvaux.so
[ 84%] Built target cvaux
Scanning dependencies of target cvhaartraining
[ 84%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvboost.o
[ 84%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvcommon.o
[ 85%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvhaarclassifier.o
[ 85%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvhaartraining.o
[ 85%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvsamples.o
Linking CXX static library ../../lib/libcvhaartraining.a
[ 85%] Built target cvhaartraining
Scanning dependencies of target createsamples
[ 85%] Building CXX object apps/haartraining/CMakeFiles/createsamples.dir/createsamples.o
Linking CXX executable ../../bin/opencv_createsamples
../../lib/libhighgui.so.2.0.0: undefined reference to `cvCreateCameraCapture_V4L(int)'
collect2: ld returned 1 exit status
make[2]: *** [bin/opencv_createsamples] Error 1
make[1]: *** [apps/haartraining/CMakeFiles/createsamples.dir/all] Error 2
make: *** [all] Error 2

Sampai sekarang, saya masih belum tahu sebabnya. Saya telah menanyakan ke forum OpenCV, belum ada jawaban, mungkin tidak ada yang mengalaminya, karena jika saya amati dari respon anggota forum, mayoritas bukan pengguna Linux.
Akhirnya, saya pakai cara klasik:

$ ./configure --with-xine --with-ffmpeg --with-1394libs --with-v4l --with-gtk --without-quicktime --enable-sse --with-swig --with-python --with-gthread

Jika tidak ada error, lalu:

$ make

Kompilasi sukses.

Langkah ketiga, install hasil kompilasi tersebut menggunakan make install. Pastikan Anda telah menjadi root user atau superuser saat menginstall:

# make install

Langkah terakhir adalah mencoba OpenCV 2.0.0. Kebetulan, 2 tahun lalu, saya pernah menulis di blog ini tentang cara membuat program dengan library OpenCV pada Linux. Program-program tersebut saya coba untuk di-compile ulang menggunakan library OpenCV versi 2.0.0 dan hasil kompilasinya dapat berjalan mulus pada laptop saya. Sekedar mengingatkan, cara kompilasi menggunakan library OpenCV adalah sebagai berikut:

$ g++ -Wall [nama_file].cpp -o [nama_file_output] `pkg-config opencv --cflags --libs`

Contoh:

$ g++ -Wall trial1.cpp -o trial1 `pkg-config opencv --cflags --libs`

Referensi:

http://opencv.willowgarage.com/wiki/InstallGuide

Summary:
This article describes about compiling and installing OpenCV on Linux in general, not depending on Linux distros. All writings of this article are based on reference at OpenCV wiki site that you can find the link on Referensi. There are 4 steps that I've been worked that I will discuss.

First, make sure all dependencies of OpenCV have been installed properly. By my experience, I need xinelib, ffmpeg, libdc1394, v4l, swig, python, libjpeg, zlib, libpng, libtiff, and libjasper. For how to add dependencies, please consult to each distro's manual.

Second, compiling OpenCV. There are 2 methods, classical method (configure then make) and cmake method. When I tried cmake method using this command:

# cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -D BUILD_PYTHON_SUPPORT=ON -D BUILD_LATEX_DOCS=ON .. 

I found an error when the process has been 85% finished.

...
Linking CXX shared library ../../lib/libcvaux.so
[ 84%] Built target cvaux
Scanning dependencies of target cvhaartraining
[ 84%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvboost.o
[ 84%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvcommon.o
[ 85%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvhaarclassifier.o
[ 85%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvhaartraining.o
[ 85%] Building CXX object apps/haartraining/CMakeFiles/cvhaartraining.dir/cvsamples.o
Linking CXX static library ../../lib/libcvhaartraining.a
[ 85%] Built target cvhaartraining
Scanning dependencies of target createsamples
[ 85%] Building CXX object apps/haartraining/CMakeFiles/createsamples.dir/createsamples.o
Linking CXX executable ../../bin/opencv_createsamples
../../lib/libhighgui.so.2.0.0: undefined reference to `cvCreateCameraCapture_V4L(int)'
collect2: ld returned 1 exit status
make[2]: *** [bin/opencv_createsamples] Error 1
make[1]: *** [apps/haartraining/CMakeFiles/createsamples.dir/all] Error 2
make: *** [all] Error 2

Until now, I still don't know how to solve it. There is no response from OpenCV forum, perhaps, nobody got this error when compiling OpenCV 2.0.0.

I switched the method using classical method:

$ ./configure --with-xine --with-ffmpeg --with-1394libs --with-v4l --with-gtk --without-quicktime --enable-sse --with-swig --with-python --with-gthread

If no error, lalu:

$ make

I found no error until compilation finished.

Third, install the compiled OpenCV using (note: make sure you have been a root user or superuser when execute this command):

# make install

The last step is try to make a simple program that needs OpenCV library then compile it using:

$ g++ -Wall [input_file].cpp -o [output_file] `pkg-config opencv --cflags --libs`

OpenCV 2.0.0 telah dirilis

2009-10-08T07:19:00.008+07:00

-- Sorry, I wrote this article in Indonesian only. For information related to OpenCV 2.0.0 in English, please go to the OpenCV Wiki Site (see Referensi for the link) --

OpenCV merupakan suatu library kumpulan fungsi-fungsi pemrograman yang khusus ditujukan untuk real-time computer vision. Aplikasinya cukup luas, antara lain: Human-Computer Interaction (HCI), Object Identification, Segmentation and Recognition, Face Recognition, Gesture Recognition, Motion Tracking, Ego Motion, Motion Understanding, Structure From Motion (SFM), Stereo and Multi-Camera Calibration and Depth Computation, Mobile Robotics.

Bagi yang berkecimpung dalam bidang computer vision, terutama real-time computer vision, ada kabar yang menggembirakan, yaitu, pada tanggal 30 Sept. 2009, telah dirilis OpenCV versi 2.0.0. Beberapa penambahan fitur pada versi 2.0.0 ini bila dibandingkan dengan OpenCV 1.1pre1 antara lain:

bug fixed.
The brand-new C++ interface untuk sebagian besar fungsi pada OpenCV (cxcore, cv, highgui).
Build system menggunakan CMake.
Perbaikan pada fungsi-fungsi aljabar linier.
Support bicubic and Lanczos interpolation.
Support stereo camera (Linux).
Image dapat dikompress dan di-dekompress langsung pada buffer memory
Beberapa fungsi dasar dan operasi image processing (seperti operasi aritmatika, geometric image transformations, filtering, dll) telah mempunyai optimasi SSE2 sehingga fungsi-fungsi tersebut akan bekerja beberapa kali lebih cepat daripada versi sebelumnya.
dll.

Untuk lebih detilnya, silakan menuju ke link yang tercantum pada bagian referensi.

Instalasi OpenCV 2.0.0 for Linux dengan cara meng-compile sendiri dari source akan saya bahas kemudian. So ... be patient! :))

Referensi:

Menambahkan Multilib pada Slackware64 -- Enabling multilib on Slackware64 --

2009-10-02T22:46:00.006+07:00

Seperti yang telah kita ketahui, Slackware 13.0 yang dirilis pada akhir Agustus 2009 lalu mempunyai 2 versi, yaitu: versi 32-bit dan versi 64-bit, sehingga sekarang ini, sudah ada 3 official port untuk slackware, yaitu: 32-bit port, 64-bit port, dan ARM-port. Slackware yang ARM port ditujukan untuk mesin yang dijalankan dengan prosesor berarsitektur ARM. Untuk 32-bit port, bisa dikatakan versi ini adalah versi normal release dari Slackware selama ini untuk komputasi 32-bit. Official port terbaru dari Slackware adalah 64-bit port, diberi nama Slackware64. Versi ini ditujukan untuk komputasi 64-bit yang sekarang ini sudah di-support oleh prosesor-prosesor keluaran Intel dan AMD yang terbaru. Untuk mengetahui apakah prosesor pada PC/laptop kita telah support komputasi 64-bit, silakan Anda membaca artikel tentang “Penggunaan cpuinfo untuk mengetahui apakah prosesor kita support komputasi 64-bit”.

Pada tutorial kali ini, akan dibahas mengenai penambahan multilib pada Slackware64 karena Slackware64 hanya menyediakan library untuk komputasi 64-bit sehingga Slackware64 tidak dapat menjalankan program-program yang hanya support komputasi 32-bit, seperti wine, skype, adobe reader, dan grub, serta tidak dapat meng-compile source code untuk komputasi 32-bit. Jadi, dengan kata lain, jika kita menghendaki Slackware64 yang terinstall pada PC/laptop kita dapat meng-compile dan menjalankan program-program untuk komputasi 32-bit, maka kita harus menyediakan library 32-bit yang dibutuhkan oleh program-program tersebut. Penambahan library 32-bit ini akan membuat Slackware64 kita mempunyai 2 jenis library, 32-bit dan 64-bit, oleh karena itu, kondisi ini disebut multilib, bentuk singkat dari multi-library. Untuk membuat Slackware64 kita menjadi multilib, caranya sangat mudah karena pada dasarnya, Slackware64 sudah multilib-ready, kita hanya tinggal meng-install-kan 32-bit libraries yang dibutuhkan. Eric Hameleers, sebagai pembuat dan maintainer Slackware64, telah menuliskan caranya pada http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib . Tutorial ini akan membahas langkah-langkah yang telah dilakukan penulis untuk me-multilib-kan Slackware64 berdasarkan panduan dari Eric.

Pertama kali, Anda harus men-download paket-paket gcc dan glibc yang versi multilib serta compat32-tools dari website Eric (http://connie.slackware.com/~alien/multilib/). Paket-paket tersebut, pada saat tutorial ini ditulis, adalah sebagai berikut:

gcc-4.3.3_multilib-x86_64-4alien.txz
gcc-g++-4.3.3_multilib-x86_64-4alien.txz
gcc-gfortran-4.3.3_multilib-x86_64-4alien.txz
gcc-gnat-4.3.3_multilib-x86_64-4alien.txz
gcc-java-4.3.3_multilib-x86_64-4alien.txz
gcc-objc-4.3.3_multilib-x86_64-4alien.txz
glibc-2.9_multilib-x86_64-3alien.txz
glibc-i18n-2.9_multilib-x86_64-3alien.txz
glibc-profile-2.9_multilib-x86_64-3alien.txz
glibc-solibs-2.9_multilib-x86_64-3alien.txz
glibc-zoneinfo-2.9_multilib-noarch-3alien.txz
compat32-tools-1.0-noarch-12alien.tgz

File-file tersebut disimpan dalam satu directory, lalu jalankan command berikut:

# upgradepkg --reinstall --install-new *.t?z

Selanjutnya, Anda dapat men-download paket-paket compat32 dari website Eric (http://connie.slackware.com/~alien/multilib/slackware64-compat32/), dari directori a-compat32, ap-compat32, d-compat32, l-compat32, n-compat32, dan x-compat32. File-file tersebut merupakan paket slackware 32-bit yang sudah dikonversi menggunakan script yang ada pada compat32-tools, totalnya sekitar 60MB. Tentang cara konversi, bisa dibaca pada website Eric yang tertulis pada bagian referensi di akhir tutorial ini. Kemudian, jalankan command berikut untuk menginstall semua paket tersebut:

# installpkg *-compat32/*.t?z

Sebagai catatan, waktu penulis melakukan instalasi paket-paket ini, muncul pesan error saat instalasi pango-compat32, yaitu:

Executing install script for pango-compat32-1.22.4-x86_64-4.txz.

/usr/bin/pango-querymodules-32: error while loading shared libraries: libXft.so.2: cannot open shared object file: No such file or directory

Jika Anda mengalami error ini, biarkan saja, nanti setelah semua paket terinstall, Anda hanya perlu mengulangi installasi pango-compat32:

# upgradepkg --reinstall pango-compat32-1.22.4-x86_64-4.txz

That's it all. Slackware64 Anda telah benar-benar multilib. Anda bisa menjalankan aplikasi 32-bit dan meng-compile source yang hanya dapat dijalankan pada slackware 32-bit. Gambar-gambar berikut menunjukkan bahwa aplikasi 32-bit seperti Adobe Reader 9.1.2 dan Skype 2.0.0.72 for Linux dapat dijalankan dengan mulus pada Slackware64 di laptop penulis serta pada saat booting, Anda akan melihat beberapa baris tambahan.

Catatan khusus bagi yang ingin meng-compile aplikasi 32-bit dari source, misalnya meng-compile wine, Anda harus mengkonfigurasi shell environment dengan menjalankan command berikut ini (lengkap dengan titiknya):

# . /etc/profile.d/32dev.sh

Cukup sekian tutorial multilib ini. Informasi lebih detil dapat Anda baca pada website Eric Hamaleers yang tercantum pada bagian referensi.

Referensi:

Summary:
This article shows how to enable multilib on Slackware64 in Indonesian based on Eric's work (see referensi). If you want to know more about enabling multilib on Slackware64 in English, I encourage you to read yourself at Eric's writing that is more detail than mine.

Instalasi digiKam 1.0.0-beta4 pada Slackware -- digiKam 1.0.0-beta4 Installation on Slackware --

2009-09-29T16:20:00.005+07:00

digiKam adalah suatu program aplikasi yang dikhususkan untuk memanajemen foto-foto digital. Program ini menyediakan suatu user interface (tampilan) yang sederhana tetapi mempunyai fungsi yang banyak dan handal, seperti import-export (download-upload) foto digital, mengenali lebih dari 1000 kamera digital yang telah beredar di pasaran, mengatur foto-foto digital kita yang sangat banyak dalam directory-directory sesuai dengan keinginan kita, membaca exif data dari foto digital, editing, dan sebagainya. File foto digital yang di-support cukup banyak, seperti RAW format dari berbagai vendor kamera digital, JPEG, TIFF, PNG, still image compression, dan moving image format (video). Program digiKam yang akan dibahas kali ini adalah digiKam 1.0.0-beta4 yang sudah dapat didownload sejak 31 Agustus 2009.

Instalasi digiKam pada Slackware/Slackware64 13.0 cukup mudah, Anda hanya membutuhkan tambahan 1 dependency, yaitu lensfun, sedangkan dependencies yang lain sudah tersedia pada Slackware/Slackware64 13.0. Untuk lensfun -saat tutorial ini dibuat, lensfun sudah versi 0.2.3-, Anda bisa men-download source file-nya, yaitu lensfun-0.2.3.tar.bz2, dari website projeknya, http://lensfun.berlios.de, sedangkan slackbuild script dari lensfun (lensfun.tar.gz) dapat Anda peroleh dari slackbuild.org. Setelah source file dan slackbuild script untuk lensfun telah Anda download, langkah selanjutnya adalah Anda ekstrak slackbuild script (lensfun.tar.gz) lalu source file lensfun-0.2.3.tar.bz2 Anda letakkan pada directory yang sama dengan lensfun.SlackBuild. Sebagai catatan kecil, jika Anda menggunakan slackware64 13.0, kita harus meng-edit file lensfun.SlackBuild pada bagian ARCH=${ARCH:-i486} menjadi ARCH=${ARCH:-x86_64}. Selanjutnya, jalankan script lensfun.SlackBuild pada mode root atau superuser (su) karena slackbuild script membutuhkan akses ke directory /tmp. Jika tidak ada error -seharusnya tidak ada ... :)-, maka Anda akan menemukan file lensfun-0.2.3-i486-1_SBo.tgz (atau lensfun-0.2.3-x86_64-1_SBo.tgz untuk slackware64) pada directory /tmp lalu installpkg. Urutan langkah instalasi lensfun dapat disimpulkan sebagai berikut:

$ tar -xvzf lensfun.tar.gz $ cd lensfun $ cp path-to/lensfun-0.2.3.tar.bz2 ./ $ su # ./lensfun.SlackBuild # installpkg /tmp/lensfun-0.2.3-i486-1_SBo.tgz

That's all for lensfun. Anda bisa copy file /tmp/lensfun-0.2.3-i486-1_SBo.tgz ke directory yang Anda kehendaki sebagai arsip dan hapus file hasil proses slackbuild script dari /tmp/SBo.

Langkah selanjutnya adalah instalasi digiKam 1.0.0-beta4. Source file, digikam-1.0.0-beta4.tar.bz2, dapat di-download dari website http://www.digikam.org. Untuk slackbuild script dari digiKam, tidak tersedia, tetapi Eric Hameleers (alienBOB) menyediakan slackbuild script untuk digiKam versi 0.10.0 yang dapat didownload dari http://connie.slackware.com/~alien/slackbuilds/digikam. Untuk proses kompilasi dan instalasi digiKam, penulis memilih proses kompilasi dan instalasi dari source file. Cara cukup mudah, terutama bagi para slackers ... betul khan ... :). Pertama kali, tentu saja, ekstrak file digikam-1.0.0-beta4.tar.bz2, lalu masuk ke directory hasil ekstrak tersebut (biasanya digikam-1.0.0-beta4). Selanjutnya cmake ., make, dan make install (dalam mode root atau superuser) jika tidak ada error -seharusnya tidak ada ... :)-, digiKam sudah siap pada PC/laptop Anda. Urutan langkah kompilasi dan instalasi digiKam dapat disimpulkan sebagai berikut:

$ tar -xvjf digikam-1.0.0-beta4.tar.bz2 $ cd digikam-1.0.0-beta4 $ cmake . $ make $ su # make install

That's all for digiKam. So easy, isn't it?

Beberapa gambar tampilan digiKam 1.0.0-beta4 pada laptop saya dapat dilihat di bawah ini.

Referensi:
http://www.digikam.org
http://lensfun.berlios.de
http://slackbuild.org

Summary:
digiKam is an advanced, KDE Digital Photo Management Application with support for Digital Cameras. It needs some dependencies software, but, we only add lensfun on Slackware/Slackware64 13.0. First, download the source of lensfun-0.2.3.tar.bz2 then download the SlackBuild script (lensfun.tar.gz) from slackbuild.org. Next, follow the steps below:

Please note that you have to change path-to to correct directory and if you use Slackware64, please change the line ARCH=${ARCH:-i486} to ARCH=${ARCH:-x86_64} before executing lensfun.SlackBuild.

$ tar -xvzf lensfun.tar.gz
$ cd lensfun
$ cp path-to/lensfun-0.2.3.tar.bz2 ./
$ su
# ./lensfun.SlackBuild
# installpkg /tmp/lensfun-0.2.3-i486-1_SBo.tgz

That's all for lensfun.

Now, the main job, compiling digiKam from source and install it. Download the source of digiKam-1.0.0-beta4.tar.bz2, then follow these steps:

$ tar -xvjf digikam-1.0.0-beta4.tar.bz2
$ cd digikam-1.0.0-beta4
$ cmake .
$ make
$ su
# make install

Now, you can run digiKam from your Slackware. That's all for digiKam. So easy, isn't it?

Prosesor Anda 32-bit atau 64-bit? -- What is your processor? 32-bit or 64-bit? --

2009-09-29T16:09:00.003+07:00

Beberapa waktu lalu, pada milis id-slackware, ada yang menanyakan pada saya tentang prosesor yang terpasang pada PC Desktopnya, apakah prosesor 32-bit atau 64-bit? Pertanyaan ini berkaitan dengan dirilisnya Slackware64, yang dikhususkan untuk PC/laptop yang memakai prosesor berarsitektur 64-bit atau berarsitektur yang support komputasi 64-bit. Ternyata, cara untuk mengetahui apakah prosesor kita sudah mensupport komputasi 64-bit sangat mudah. Kita ketikkan saja pada console/terminal:

$ cat /proc/cpuinfo | grep flags

maka akan muncul hasilnya seperti gambar berikut ini:

Lalu, kita cari flag lm. Jika kita temukan flag ini, maka prosesor PC/laptop kita sudah support komputasi 64-bit, sehingga kita bisa menginstall sistem operasi 64-bit.

Catatan: lm singkatan dari Long Mode (64-bit mode)

Referensi:

http://www.cyberciti.biz/faq/linux-how-to-find-if-processor-is-64-bit-or-not/
http://www.unixtutorial.org/2009/05/how-to-confirm-if-your-cpu-is-32bit-or-64bit/
http://www.cyberciti.biz/tips/how-do-i-find-out-if-my-server-cpu-can-run-a-64-bit-kernel-version-apps-or-not.html

Summary:
In id-slackware mailing-list, someone asked me about kind of processor he had, 32-bit or 64-bit. The answer is we can know it from cpuinfo by typing this command at console/terminal:

$ cat /proc/cpuinfo | grep flags

If you find lm flag (Long Mode) in the result, you have a 64-bit capable processor so that you can use 64-bit operating system.

My New-look Slackware

2009-09-29T16:04:00.001+07:00

It was more than 3 years I have been waiting for 64-bit official port of Slackware (since I bought laptop with AMD Turion64 processor). Finally, in the end of August 2009, the good news has been coming when Pat and Eric announced release version of Slackware64 13.0. After I heard that news, I installed Slackware64 13.0 as soon as possible. I didn't any difficulty because I have used Slamd64, an 64-bit unofficial port of Slackware, created and maintained by Fred Emmott for 3 years; although Eric built Slackware64 by his own work, it has similarity to Slamd64 because Eric has learnt Fred's work in Slamd64. CMIIW.

The new-look slackware on my laptop can be seen at the picture below.

Thank's to Eric for realizing the 64-bit official port of Slackware. It is so nice. Great job.
Also, I would like to thank abundantly to Fred Emmott that has been created and maintained Slamd64 very well so that I still could use my favorite Linux distro, Slackware.

2009-09-29T08:40:00.006+07:00

Hello everyone...
It has been long time not to see you in this blog ... :( in 2 years, I didn't write anything ...

I hope, I can write regularly since today. Many things I'd like to share ...
Perhaps, from today, I will write mostly in Indonesian, but don't worry if your language is not Indonesian because I will give a summary in English at the end of my posts if I write them in Indonesian. If you wanna to contact me for some questions after read the English summary, please do not hesitate to e-mail me ...

How to Set Extra Keys on Laptop

2007-09-24T15:08:00.002+07:00

Laptop usually has some extra keys for particular purposes such as volume control, brightness control, sleep button, etc. If you are lucky, you will get all extra keys are working nicely. On my laptop, only brightness control can working.
From Arman Idris' blog, I got an explanation in Indonesian about how to set extra keys on laptop that have Slackware installed and KDE as desktop manager. I think all Linux distros can adopt it if they are using KDE as desktop manager. If you use GNOME, I'm sorry ... I do not know how to set ... please googling :)

The software that we need to activate the extra keys are xmodmap and xbindkeys. Xmodmap are commonly used in X system, so that, we do not need to install it. Xbindkey usually does not included. We need to install it. Get it from http://hocwp.free.fr/xbindkeys/xbindkeys.html then compile and install it. After finishing install xbindkeys, there are some steps to follow:

First, we have to know the keycode of extra keys that we want to activate. From console, type xev then press the desired extra key. On screen we will see some texts like this:

    KeyPress event, serial 32, synthetic NO, window 0x2a00001,
root 0x66, subw 0x0, time 335922971, (1083,351), root:(1093,377),
state 0x0, keycode 160 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

Pay attention on the bold texts. That is the keycode for extra key that we just pressed, on my laptop, that is extra key for muting volume. Using the same procedure, on my laptop, I found keycode 174 and 176 for volume down and volume up, respectively.

Second, we write 2 configuration files: .xmodmaprc and .xbindkeysrc, place them in the home directory. Here is my .xmodmaprc:
keycode 160 = F14
keycode 174 = F15
keycode 176 = F16
The name of F14, F15, and F16 are alias names of extra keys that have keycode of respectively 160, 174, and 176. For standard naming in xmodmap, please refer to xmodmap manual.
My .xbindkeysrc can be found here:
#Volume Mute
"/usr/local/bin/mute.sh"
F14
#Volume decrease
"dcop kmix Mixer0 decreaseVolume 0"
F15
#Volume increase
"dcop kmix Mixer0 increaseVolume 0"
F16
Note that dcop can be found only in KDE.
Since we do not have script file mute.sh, we have to write it then place it to /usr/local/bin. Do not forget to change file permission using: chmod 0755 /usr/local/bin/mute.sh -- of course, you must have root permission to execute this command --
Here is the script of mute.sh:
#/bin/bash
MUTE=`dcop kmix Mixer0 mute 0`
if $MUTE -eq "true" ; then
dcop kmix Mixer0 setMute 0 off
else
dcop kmix Mixer0 setMute 0 on
fi
This script will toggle the mute status when we press the mute key. For instance, if the last status is "mute", the status will change to "unmute" when we press the mute key.

Third, we edit the .xinitrc (you can found it in your home directory) to run configuration files that have been written. Here is my .xinitrc:
#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.xmodmaprc
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi

/usr/local/bin/xbindkeys -f $HOME/.xbindkeysrc

# Start the window manager:
startkde

The bold lines are the lines that have been added by me.

Last step, restart X, then enjoy your extra keys :)

Reference:

Extra Key on Laptop, Arman Idris, http://hocwp.free.fr/xbindkeys/xbindkeys.html

Capturing Frames from a USB Camera using OpenCV on Linux

2007-09-19T15:36:00.001+07:00

Next step after loading image and manipulating it, I try to access a Linux-USB-registered USB Camera using a simple camera capture framework written in C with OpenCV Library. Here is the code:

/////////////////////////////////////////////////////
// trialcam1a.cpp
// A Simple Camera Capture Framework
// This program will connect to a camera then
// show the frames in a window
/////////////////////////////////////////////////////
#include <stdio.h>
#include <cv.h>
#include <highgui.h>

int main()
{
IplImage *frame = NULL; //Preparing frame pointer
int key;

//Allocates and initializes cvCapture structure
// for reading a video stream from the camera.
//Index of camera is -1 since only one camera
// connected to the computer or it does not
// matter what camera to use.
CvCapture *input_camera = cvCaptureFromCAM(-1);

//Grabs and returns a frame from camera
frame = cvQueryFrame(input_camera);

//Creates window for displaying the frames
//Flag is reset (0) --> change window size
// manually
cvNamedWindow("Capturing Image ...", 0);

//Change to the appropriate size. In GTK, the
// inappropriate size will return a segmentation
// fault. I don't know why ...
//Gets the appropriate size using cvGetCaptureProperty
// with CV_CAP_PROP_FRAME_HEIGHT and CV_CAP_PROP_FRAME_WIDTH
// as property_id
cvResizeWindow("Capturing Image ...",
(int) cvGetCaptureProperty(input_camera, CV_CAP_PROP_FRAME_HEIGHT),
(int) cvGetCaptureProperty(input_camera, CV_CAP_PROP_FRAME_WIDTH));

while(frame != NULL)
{
//Shows a frame
cvShowImage("Capturing Image ...", frame);

//Checks if ESC is pressed and gives a delay
// so that the frame can be displayed properly
key = cvWaitKey(10);
if(key == 27)
break;
//Grabs and returns the next frame
frame = cvQueryFrame(input_camera);
}

//Release cvCapture structure
cvReleaseCapture(&input_camera);

//Destroy the window
cvDestroyWindow("Capturing Image ...");

return 0;
}

Compiling (in the working directory):
$ g++ -Wall trialcam1a.cpp -o trialcam1a `pkg-config --cflags --libs opencv`

Running (in the working directory):
$ ./trialcam1a

Screenshot:

dmesg when I plugged USB Camera:
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
pwc: Philips webcam module version 10.0.13 loaded.
pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
pwc: Logitech QuickCam 4000 Pro USB webcam detected.
pwc: Registered as /dev/video0.
usbcore: registered new interface driver Philips webcam
usbcore: registered new interface driver snd-usb-audio

Camera driver: pwc.
Camera interface: v4l (Video for Linux).

References:

OpenCV wiki (http://opencvlibrary.sourceforge.net)
Introduction to programming with OpenCV, by Gady Agam (http://www.cs.iit.edu/~agam/cs512/lect-notes/opencv-intro/opencv-intro.html)
Linux-uvc-devel mailing list, January 2007 archieve, e-mail posting by Jose Luis Landabaso

Compiling OpenCV Program on Linux

2007-09-17T15:22:00.001+07:00

After OpenCV installation, I try to make a simple OpenCV program that loads an image from file, clones it, inverts it, and displays it at monitor, then, compile it on Linux. Here is the code:

//////////////////////////////////////////////////////////////////
//
// trial1a.cpp
//
// This is a simple, introductory OpenCV Program. The program will
// read an image from a file, clone it, invert it, and display the
// result.
//
//////////////////////////////////////////////////////////////////
#include <stdlib.h>
#include <stdio.h>
#include <math.h>
#include <cv.h>
#include <highgui.h>

int main(int argc, char *argv[])
{
IplImage* img = 0;
IplImage* img1 = 0;
int height,width,step,channels;
uchar *data;
int i,j,k;

if(argc<2)
{
printf("Usage: main \n\7");
exit(0);
}

//load an image
img1=cvLoadImage(argv[1]);
if(!img1)
{
printf("Could not load image file: %s\n",argv[1]);
exit(0);
}

//clonning the image before processing
img=cvCloneImage(img1);

//get the image data
height=img->height;
width=img->width;
step=img->widthStep;
channels=img->nChannels;
data=(uchar *)img->imageData;
printf("Processing a %dx%d image with %d channels\n",height,width,channels);

//create a window
cvNamedWindow("Image Window",CV_WINDOW_AUTOSIZE);
cvMoveWindow("Image Window",0,0);

//show the original image
cvShowImage("Image Window",img1);
//wait for input any key
cvWaitKey(0);

//invert the image
for(i=0;i<height;i++)
for(j=0;j<width;j++)
for(k=0;k<channels;k++)
*(data+(i*step+j*channels+k))=255-*(data+(i*step+j*channels+k));

//create another window
cvNamedWindow("Invert Image Window",CV_WINDOW_AUTOSIZE);
cvMoveWindow("Invert Image Window",500,0);

//show the inverted image
cvShowImage("Invert Image Window",img);
//wait for input any key
cvWaitKey(0);

//release the image
cvReleaseImage(&img1);
cvReleaseImage(&img);
return 0;
}

After typing and saving it using Kate Editor, I compile using gcc with command (in the working directory):
$ g++ -Wall trial1a.cpp -o trial1a `pkg-config --cflags --libs opencv`
Note that the option `pkg-config --cflags --libs opencv` will inserts -I/usr/local/include/opencv -L/usr/local/lib -lcxcore -lcv -lhighgui -lcvaux -lml automatically to the command. If that is not working, you can try this:
$ g++ -Wall trial1a.cpp -o trial1a -I/usr/local/include/opencv -L/usr/local/lib -lcxcore -lcv -lhighgui -lcvaux -lml

Next, if there are no errors, I type (in the working directory):
$ ./trial1a foto.jpg
Then ... (see screenshots)

References:

OpenCV wiki (http://opencvlibrary.sourceforge.net)
Introduction to programming with OpenCV, by Gady Agam (http://www.cs.iit.edu/~agam/cs512/lect-notes/opencv-intro/opencv-intro.html)

Installing OpenCV from source, especially on x86_64 Linux system that has multilib support

2007-09-17T13:00:00.001+07:00

Yesterday, I spent many hours to find out why I could not use OpenCV in Slamd64 after compiling and installing from the source. Finally, I found the problem: something related to multilib support in Slamd64, especially when I configured OpenCV to use GTK+-2.0. In Slamd64 system that has multilib support, it has two version of GTK+-2.0, i.e. 32-bit version and 64-bit version. Until now, I don't understand, when in the configuring process of OpenCV source, why that process "choose" the 32-bit version of GTK+-2.0 instead of 64-bit version, so that, I got error in compiling process and if didn't get error, ld could not link the OpenCV library to my program when I run gcc. I will check later if I have time :)

How to Compile OpenCV from source, especially on x86_64 Linux system that has multilib support
Note for user that doesn't use x86_64 Linux OS: after first step, you can skip the second.
First, make sure ffmpeg has been installed. Read the INSTALL documentation in OpenCV source tree. Other libraries that may be needed such as xine-lib, ieee1394 library (libraw1394 and libdc1394), video for linux (usually already included in kernel), libjpeg, zlib, libpng, libtiff, libjasper, libIlmImf are optional. Make sure to install those libraries before configuring/compiling OpenCV if it's necessary.
Second, to make sure the configuring process of OpenCV source "choose" the 64-bit version of GTK+-2.0, you have to edit 2 lines from the configure file in OpenCV source tree because you cannot add them as options when you type ./configure on bash prompt :(

For GTK_LIBS:

find this line: GTK_LIBS=`$PKG_CONFIG --libs ""gtk+-2.0 gdk-pixbuf-2.0""`
change to this (NOTE THAT THE CODE MAY VARY IN YOUR SYSTEM!): GTK_LIBS="-L/usr/lib64 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0"

How to get "-L/usr/lib64 ..."?
$ pkg-config --libs ""gtk+-2.0 gdk-pixbuf-2.0""
You will get: -L/usr/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
Copy that line to configure file and change /usr/lib to /usr/lib64.

For GTK_CFLAGS:

find this line: GTK_CFLAGS=`$PKG_CONFIG --cflags ""gtk+-2.0 gdk-pixbuf-2.0""`
change to this (NOTE THAT THE CODE MAY VARY IN YOUR SYSTEM!): GTK_CFLAGS="-DPNG_NO_MMX_CODE -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12"

How to get "-DPNG_NO_MMX_CODE -I/usr/include/gtk-2.0 ..."?
$ pkg-config --cflags ""gtk+-2.0 gdk-pixbuf-2.0""
You will get: -DPNG_NO_MMX_CODE -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12
Copy that line to configure file and change /usr/lib/gtk-2.0/include to /usr/lib64/gtk-2.0/include

For GTHREAD_LIBS:

find this line: GTHREAD_LIBS=`$PKG_CONFIG --libs ""gthread-2.0""`
change to this: GTHREAD_LIBS="-L/usr/lib64 "`$PKG_CONFIG --libs ""gthread-2.0""`

Third,
$ ./configure --with-xine --with-ffmpeg --with-1394libs --with-v4l --with-gtk --without-quicktime
It indicates that OpenCV uses xine, ffmpeg, ieee1394, video for linux, and GTK+-2.0 libraries but disables quicktime library. OpenCV will be installed in default prefix (/usr/local) For detailed options, type ./configure --help
Here is some results of the configure in my laptop:
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
...
...
...
checking Carbon/Carbon.h usability... no
checking Carbon/Carbon.h presence... no
checking for Carbon/Carbon.h... no
checking for pkg-config... /usr/bin/pkg-config
checking for "gtk+-2.0 gdk-pixbuf-2.0"... yes
checking GTK_CFLAGS... -DPNG_NO_MMX_CODE -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12
checking GTK_LIBS... -L/usr/lib64 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
checking for "gthread-2.0"... yes
checking GTHREAD_CFLAGS... -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
checking GTHREAD_LIBS... -L/usr/lib64 -pthread -lgthread-2.0 -lglib-2.0
checking xine.h usability... yes
checking xine.h presence... yes
checking for xine.h... yes
checking for xine_init in -lxine... yes
checking ffmpeg/avcodec.h usability... yes
checking ffmpeg/avcodec.h presence... yes
checking for ffmpeg/avcodec.h... yes
checking for avcodec_decode_video in -lavcodec... yes
checking for av_open_input_file in -lavformat... yes
checking libraw1394/raw1394.h usability... yes
checking libraw1394/raw1394.h presence... yes
checking for libraw1394/raw1394.h... yes
checking for raw1394_new_handle in -lraw1394... yes
checking libdc1394/dc1394_control.h usability... yes
checking libdc1394/dc1394_control.h presence... yes
checking for libdc1394/dc1394_control.h... yes
checking for dc1394_camera_on in -ldc1394_control... yes
checking linux/videodev.h usability... yes
checking linux/videodev.h presence... yes
checking for linux/videodev.h... yes
checking for linux/videodev2.h... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking for jpeg_destroy_decompress in -ljpeg... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for gzopen in -lz... yes
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking libpng/png.h usability... yes
checking libpng/png.h presence... yes
checking for libpng/png.h... yes
checking for png_read_image in -lpng12... yes
checking for png_get_valid... yes
checking for png_set_tRNS_to_alpha... yes
checking tiff.h usability... yes
checking tiff.h presence... yes
checking for tiff.h... yes
checking for TIFFReadRGBAStrip in -ltiff... yes
checking jasper/jasper.h usability... yes
checking jasper/jasper.h presence... yes
checking for jasper/jasper.h... yes
checking for jas_image_readcmpt in -ljasper... yes
checking ImfCRgbaFile.h usability... no
checking ImfCRgbaFile.h presence... no
checking for ImfCRgbaFile.h... no
configure: Checking for necessary tools to build python wrappers
checking for python... /usr/bin/python
checking for python version... 2.5
checking for python platform... linux2
checking for python script directory... ${prefix}/lib64/python2.5/site-packages
checking for python extension module directory... ${exec_prefix}/lib64/python2.5/site-packages
configure: PYTHON_CSPEC=-fPIC -I/usr/include/python2.5
configure: PYTHON_LSPEC= -L/usr/lib64/python2.5/config -lm -lpthread -ldl -lutil -lpython2.5 -Xlinker -export-dynamic
checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating opencv.pc
config.status: creating opencv.spec
config.status: creating docs/Makefile
config.status: creating data/Makefile
config.status: creating cxcore/Makefile
config.status: creating cxcore/include/Makefile
config.status: creating cxcore/src/Makefile
config.status: creating cv/Makefile
config.status: creating cv/include/Makefile
config.status: creating cv/src/Makefile
config.status: creating cvaux/Makefile
config.status: creating cvaux/include/Makefile
config.status: creating cvaux/src/Makefile
config.status: creating ml/Makefile
config.status: creating ml/include/Makefile
config.status: creating ml/src/Makefile
config.status: creating otherlibs/Makefile
config.status: creating otherlibs/highgui/Makefile
config.status: creating apps/Makefile
config.status: creating apps/haartraining/Makefile
config.status: creating apps/haartraining/include/Makefile
config.status: creating apps/haartraining/src/Makefile
config.status: creating interfaces/Makefile
config.status: creating interfaces/swig/Makefile
config.status: creating interfaces/swig/filtered/Makefile
config.status: creating interfaces/swig/general/Makefile
config.status: creating interfaces/swig/python/Makefile
config.status: creating tests/Makefile
config.status: creating tests/python/Makefile
config.status: creating tests/cv/Makefile
config.status: creating tests/cv/src/Makefile
config.status: creating tests/cxts/Makefile
config.status: creating tests/cxcore/Makefile
config.status: creating tests/cxcore/src/Makefile
config.status: creating utils/Makefile
config.status: creating samples/Makefile
config.status: creating samples/c/Makefile
config.status: creating samples/python/Makefile
config.status: creating cvconfig.h
config.status: cvconfig.h is unchanged
config.status: executing depfiles commands

General configuration ================================================
Compiler: g++
CXXFLAGS: -Wall -fno-rtti -pipe -O3 -fomit-frame-pointer

Install path: /usr/local

HighGUI configuration ================================================

Windowing system --------------
Use Carbon / Mac OS X: no
Use gtk+ 2.x: yes
Use gthread: yes

Image I/O ---------------------
Use libjpeg: yes
Use zlib: yes
Use libpng: yes
Use libtiff: yes
Use libjasper: yes
Use libIlmImf: no

Video I/O ---------------------
Use QuickTime / Mac OS X: no
Use xine: yes
Use ffmpeg: yes
Use dc1394 & raw1394: yes
Use v4l: yes
Use v4l2: yes

Wrappers for other languages =========================================
SWIG
Python yes

Additional build settings ============================================
Build demo apps yes

Now run make ...

configure:
ATTENTION: highgui will be built with xine support,
thus it will be a subject to GNU Public License

Fourth and next ..., if there are no errors, then
$ make
# make install
Make sure you have root privilege to run make install.

Installing digikam from source on Slamd64/Slackware

2007-09-12T15:31:00.001+07:00

Last year, I bought digital camera, Canon Powershot A430, but, I never used my camera (read: download the images to PC) in Linux because Slamd64/Slackware could not detect it automatically. Today, finally .... the camera can be detected automatically so that I can download the images from that camera to PC using digikam. The software, digikam, and its dependencies has been installed by compiling them from source. I don't use Slackware's tgz because my system is x86_64 and, also, I prefer to install from source rather than install using any package management.

First step, I downloaded all sources that I needed:

exiv2-0.15
jasper-1.900.1
libgphoto2-2.4.0
libkdcraw-0.1.1
libkipi-0.1.5
libkexiv2-0.1.5
sqlite-3.4.2
digikam-0.9.2

Second step, I compiled and installed them one by one with the order same as that of I downloaded. There're some notes:

I added the option "--enable-shared" (the default is static). If not being added, digikam could not detect libjasper.
people can use specific driver when compiling libgphoto2 using option "--with-driver= ...." in configure. The default is all. I chose same as the default.
I used the option "--with-tcl=/usr/lib64" in configure before compiling sqlite. Without that option, the configure script could not find tcl in my system.

After installing digikam, I got a problem that the digikam could not detect my camera. There is an answer from denic's blog (http://makassar-slackers.org/node/74) that I have to edit file /etc/udev/rules.d/50-udev.rules in section # libusb device access; add , MODE="0666" after the text SUBSYSTEM=="usb_device", PROGRAM="/bin/sh -c 'X=%k X=$${X#usbdev}; B=$${X%%%%.*}; D=$${X#*.}; echo bus/usb/$$B/$$D'", SYMLINK+="%c"
Next step, I stopped HAL, messagebus, and udev services, then, I started those service again.

After all step ... digikam can detect my camera and download the images easily in PTP mode.

Note that, by default, Slackware/slamd64 is not activating HAL service. If you activate HAL service, you will see the window below:

I fall in love with Slackware

2007-09-06T15:53:00.001+07:00

That is true ... I fall in love with Slackware. First time I used Linux in the end of 2003, I installed Mandrake 9.1 (now Mandriva) on my PC, but, in the third month after installed, I was boring with that distro. I wanted something that gave me a big challenge. Then, I chose Slackware 9.1 in the beginning of 2004. First time using Slackware ... very stressful ... but ... I didn't give up ... then ... I was surprised, I became know about many processes related to how to operating system works ... and the most important thing ... I got "my own desktop" so that I can said "what do you see on screen is me" :) Thank's to Patrick Volkerding and the Slackware team for the BEST Linux distribution (your mileage may vary).

In October 2006, I bought my first laptop (thank's to Ubaya and Mr. Yohanes G. Yusuf that help me financially to buy that laptop), a local trademark laptop: Relion TW12KM (AMD Turion64 1.8GHz, 1GB RAM, 60GB HDD, DVD-RW, 12.1" XGA TFT). When I was going to install Linux, I rather disappointed cause Slackware didn't have a x86_64 version (Until now, AFAIK, Pat don't have plan to release x86_64 version) ... oh .. no ... Did I had to "divorce" with Slackware? In the next few days, I got a good news from internet after searching using Google (thank's to Google for a wonderful search engine), there was a unofficial port of Slackware for x86_64 machine, that is, Slamd64 (www.slamd64.org). Thank's to Fred Emmott for this project, so that, until now, I can "live" with Slackware.

Here is the screenshot of Slamd64-current that running in my laptop:

I have changed the default icons using nuvoX 0.4. Also, I use Plastik as KDE Manager. The color of the desktop is contrast with the white case of my laptop.

First Posting

2007-08-27T13:11:00.000+07:00

Hi ...
This is my first posting in my blog. I've never use blog, so, this is also the first time for me to write blog. I hope, I can share something to all of my reader's blog regularly :)