Note for English Readers

If I write the articles in Indonesian, I will write a summary in English so that you can read my articles too. After you read the summary and you feel that you need more information about that, please do not hesitate to contact me via e-mail that can be found in my profile.

Thank you for reading my blogs.
Showing posts with label slackware64. Show all posts
Showing posts with label slackware64. Show all posts

Sunday, December 28, 2014

AMD Catalyst Omega 14.501.1003 (14.12) for kernel 3.18.x

Finally, I had time to upgrade my laptop to the latest of slackware64-current, kernel 3.18.1, and AMD Catalyst Omega 14.501.1003 or 14.12. When upgrading to the newest AMD Catalyst Omega, I have got error message after compiling fglrx module. As usual, I checked my favorite reference, that is, Arch User Repository (AUR) for the patch. I modified the patch so that only one patch file is needed. You can download the patch from my Google Drive. You can follow the guidelines below to patch the fglrx module:
  • change directory to the path where the installer is
  • run the installer as root (superuser):
    # ./amd-driver-installer-14.501.1003-x86.x86_64.run
  • follow the instructions, at the end of installation process you will get notice that there are some errors.
  • exit the installer
  • at console, copy the patch file (fglrx-14.12_kernel-3.18.x.patch) to /lib/modules/fglrx/build_mod/
  • change directory to /lib/modules/fglrx/build_mod/
  • patch the fglrx source:
    # patch -p0 < fglrx-14.12_kernel-3.18.x.patch
  • compile the fglrx modules:
    # ./make.sh
    # cd ..
    # ./make_install.sh
  • reboot.
Enjoy your AMD Catalyst-14.501.1003 or 14.12 running on linux kernel 3.18.x.

Monday, July 2, 2012

Official Release of AMD Catalyst 12.6

Finally, AMD Catalyst 12.6 has been released officially last Thursday (28-JUN-2012). Please note that this version only supports Radeon HD5000 series or newer as stated on AMD website. For HD4000 and older series, it is better if you stick on current driver that you are using now. This unofficial AMD Catalyst's wiki may help you to decide which version you want to install on your computer.

It has been working nicely on my laptop with kernel-3.4.2 and xorg-server-1.12.2 installed since yesterday. For anyone that uses linux kernel 3.4.x, please follow my step that I have written last time: "AMD Catalyst Patch for kernel-3.4.x". I still compile the kernel-3.4.4. This Catalyst driver should be able to work nicely too on it. I will update this post soon after I finish to set up my laptop with this new kernel.

Updated (02-JUL-2012):
  • This Catalyst driver and the patch are working very well on kernel-3.4.4
  • AMD also released the 12.7 beta version at the same day of 12.6 that will improve performance optimizations for the AMD Radeon HD 7900, AMD Radeon HD 7800, and AMD Radeon HD 7700 Series. You can checkout this link. However, this beta version is not for linux ... :(

Thursday, June 14, 2012

AMD Catalyst-12.6 Beta and xorg-server-1.12.1

After I postponed for more than a month because of incompatibility issue between xorg-server-1.12.1 and the latest AMD Catalyst driver (that is, 12.4), finally, I can use xorg-server-1.12.1 "normally" with the beta version of AMD Catalyst driver, that is, AMD Catalyst-12.6 Beta. I have tested this combination for two days and there is no problem so far. However, since the driver is beta version, there is such kind of logo at the bottom right of the display that give notice that the driver is for testing use only. As for me, it is OK since I believe that AMD will release the official release version soon.

Thursday, September 22, 2011

TeXstudio-2.2 on Slackware64

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

Tuesday, August 30, 2011

Installing e-Sword under wine on Slackware64

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


Saturday, April 30, 2011

Xilinx ISE WebPack on Slackware64

(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:




    Saturday, March 12, 2011

    dmesg: operation not permitted as user


    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.

    Monday, October 25, 2010

    How to fix my silent laptop?

    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.

    Thursday, June 17, 2010

    OpenOffice.org 3.2.1 for Slackware64

    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:
    1. Download OpenOffice.org 3.2.1 versi 64-bit di sini.
    2. Download SlackBuild script di sini.
    3. Extract compressed SlackBuild script openoffice.org.tar.gz (tar -xvzf openoffice.org.tar.gz) maka akan muncul directory openoffice.org
    4. 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.
    5. Dengan working directory openoffice.org dan user root, jalankan script openoffice.org.SlackBuild (./openoffice.org.SlackBuild).
    6. Jika tidak ada error, maka Anda akan mendapatkan file /tmp/openoffice.org-3.2.1_en_US-x86_64-1_SBo.tgz
    7. Jalankan upgradepkg --install-new /tmp/openoffice.org-3.2.1_en_US-x86_64-1_SBo.tgz (berlaku untuk install baru maupun upgrade).
    8. 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:
    1. Download OpenOffice.org 3.2.1 64-bit version here.
    2. Download SlackBuild script here.
    3. Extract compressed SlackBuild script openoffice.org.tar.gz (tar -xvzf openoffice.org.tar.gz) then you will see openoffice.org directory
    4. Copy or move OOo_3.2.1_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz into that directory.
    5. Make sure the working directory is openoffice.org and as root user, run the script openoffice.org.SlackBuild using this command: ./openoffice.org.SlackBuild
    6. If no error found, then you will get /tmp/openoffice.org-3.2.1_en_US-x86_64-1_SBo.tgz
    7. 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.
    8. Done.

    Piece a cake, isn't it?

    Thursday, October 15, 2009

    Slackbuild script untuk AVR Development Software

    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:


    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.

    Friday, October 2, 2009

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

    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.

    Tuesday, September 29, 2009

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

    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?

    My New-look Slackware

    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.