Planet Slackware Indonesia

Willy Sudiarto Raharjo: Adding More Protection Layer on PHP

noreply@blogger.com (Willy Sudiarto Raharjo) — Sun, 05 Feb 2012 02:21:00 +0000

PHP is a well known and popular programming language that has been considered mature for years. It has a big community behind the stage and it's been used in most websites due to it's nature of being an open source project and widely supported by many Linux distributions.

Unfortunately, lately, they have been struggling to work with their security problems and even with Stefan Esser's help to improve the project, their ego was too high, so they ignored some of his proposal to improve PHP's security core. At the end, Stefan released Suhosin project to help users to get the better PHP service from the security point of view.

I always installed Suhosin on my servers since lately, PHP has changed it's way of rolling releases and it's not as often as it used to be. Some critical fixes are in pending for months until it's rolled out to users and sometimes, it's kinda late to prevent exploits coming around.

There are two ways of installing Suhosin. The first one comes as a PHP patch which will be used against PHP source code prior compilation and the second option come as an extension. If you plan to compile your first PHP and release it as a bundle, it's better for you to pick the first option as it will patch PHP directly into the source. However, sometimes you have your PHP up and running and you want to add additional security layer on top of it and that's when the second option is preferred.

Here's how you compile and install Suhosin on top of running PHP

Download the latest release of Suhosin Extension
Extract the package (tar -xzvf suhosin-0.9.33.tgz)
Change to suhosin directory (cd suhosin-0.9.33)
Ran the magic command (phpize; ./configure; make;)
Install the package using root account (make install)
Add this line into your php.ini file (extension=suhosin.so)
Add the appropriate location of the module in extension_dir variable in php.ini
Restart your Apache (/etc/rc.d/rc.httpd restart)
Confirm your PHP is protected by Suhosin (php -v)

If you ran the phpinfo() function, you will get something like this

Widya Walesa: Slackware Current Using Kernel 3.2.2

Fri, 03 Feb 2012 07:22:17 +0000

Still remember my poll about what kernel version should be used by the next slackware-current? So for you who have choosen the linux kernel 3.2.2, now you can have a nice drink . Yes, slackware-current now shipped with kernel 3.2.2 as it's default kernel. But not only that. You'll be surprised if you read the full ChangeLog.txt for complete update information. Trust me on that. Or, you can read Willy's blog for the update summary. So now, I'm going to write about how to upgrade my slackware-current to the latest release.

Willy Sudiarto Raharjo: GSB 3.2.2 Maintenance Patches

noreply@blogger.com (Willy Sudiarto Raharjo) — Fri, 03 Feb 2012 00:23:00 +0000

People working in GSB project has updated their repositories to add GNOME 3.2.2 maintenance patches. I actually missed this update because i didn't use GSB on my systems. I found out this update when running rsync script on my server. Here's the latest changelog:

Mon Jan 30 18:34:44 GMT 2012
  GNOME 3.2.2 maintenance patches.
patches/avahi-0.6.30-i486-2gsb.txz: Patched.
  Fix a potential problem where avahi could replace the /etc/HOSTNAME with
  incorrect information.  Thanks to Robby Workman for pointing out the problem
  and sending a patch.
patches/clutter-1.8.4-i486-1gsb.txz: Upgraded.
patches/packages/gjs-1.30.1-i486-1gsb.txz: Upgraded.
patches/packages/evolution-data-server-3.2.3-i486-1gsb.txz: Upgraded.
patches/packages/gnome-icon-theme-symbolic-3.2.2-i486-1gsb.txz: Upgraded.
patches/packages/gtkhtml-4.2.3-i486-1gsb.txz: Upgraded.
patches/packages/evolution-3.2.3-i486-1gsb.txz: Upgraded.
  Fixes numerous crashes.  For more information, see:
     http://download.gnome.org/sources/evolution/3.2/evolution-3.2.3.changes.
patches/packages/evolution-exchange-3.2.3-i486-1gsb.txz: Upgraded.
patches/packages/evolution-groupwise-3.2.3-i486-1gsb.txz: Upgraded.
patches/packages/gedit-3.2.6-i486-1gsb.txz: Upgraded.
patches/packages/gnome-nettool-3.0.1-i486-1gsb.txz: Upgraded.
patches/packages/mutter-3.2.2-i486-1gsb.txz: Upgraded.
  Fixes a major memory leak with gnome-shell.  For more information, see:
    https://bugzilla.gnome.org/show_bug.cgi?id=642652
patches/packages/clutter-gst-1.4.6-i486-1gsb.txz: Upgraded.
patches/packages/libgee-0.6.4-i486-1gsb.txz: Upgraded.
patches/packages/gnome-shell-3.2.2.1-i486-1gsb.txz: Upgraded.
  Fixes numerous crashes and brings improvements for the message tray.  For
  more information, see: 
    https://bugzilla.gnome.org/show_bug.cgi?id=663815
    https://bugzilla.gnome.org/show_bug.cgi?id=664138
    https://bugzilla.gnome.org/show_bug.cgi?id=648450
    https://bugzilla.gnome.org/show_bug.cgi?id=667652
    https://bugzilla.gnome.org/show_bug.cgi?id=668048
patches/packages/heimdal-libraries-1.5.2-i486-1gsb.txz: Upgraded.
  This contains two security fixes for the libtelnet library and for libkrb5
  checksums (2012-01-11, 2012-01-10). For more information, see:
    http://www.l5l.org/advisories.html?show=2012-01-10
    http://www.l5l.org/advisories.html?show=2012-01-11
  (* Security fix *)
testing/gnote-0.8.2-i486-1gsb.txz: Added.
testing/tdb-1.2.9-i486-1gsb.txz: Added.
  An upgraded tdb package is needed by rhythmbox;  this version of the library
  will conflict with the tdb in the samba package.  
testing/rhythmbox-2.95-i486-1gsb.txz: Added.

Willy Sudiarto Raharjo: Kernel-firmware Updated and Firefox 11 Beta 1

noreply@blogger.com (Willy Sudiarto Raharjo) — Fri, 03 Feb 2012 00:13:00 +0000

Ysterday's update had some glitch in which one of the file had a FAILED checksums and that belongs to the kernel-firmware package. The checksums of the package is good, but the .asc file that is being used to verify it's not, so it's not really a serious problem, but Pat decided to fix this problem by building a fresh kernel-firmware package taken from the git source.

A new beta build of Firefox is also added on testing/. It surely follows the tradition of adding Firefox's beta builds on testing/ that has been executed in the last round of development cycle.

Willy Sudiarto Raharjo: Updated Multilib and Qt

noreply@blogger.com (Willy Sudiarto Raharjo) — Fri, 03 Feb 2012 00:03:00 +0000

AlienBOB has updated his multilib packages to sync with the latest update in -Current that happened yesterday. People running multilib system won't be able to launch several applications if they don't upgrade their multilib packages since the application on -Current are built based on other version of GCC and GLIBC, so it must be re-adjusted once they are upgraded.

Another update from AlienBOB is the updated Qt package which fixed a security vulnerability (CVE-2011-3922) and should solve the path problem in several places, and this should fix the missing startup sound notification we all experienced soon after we upgraded to KDE 4.8.0. With this update, my previous article is no longer needed as it has been fixed by upstream.

Hadi Sumarsono: Nikmati ber-Zekr di Slackware 13.37

Thu, 02 Feb 2012 04:06:00 +0000

Bismillah.

Aplikasi Zekr bermanfaat bagi muslimin untuk mencari dan membaca ayat-ayat Al-Quran di komputer. Zekr nampaknya belum bisa digantikan aplikasi lainnya karena stabil dan jarang sekali bermasalah. Nah, sayangnya bila Zekr diinstalkan di Slackware 13.37 akan konflik dengan aplikasi Seamonkey bawaan. Zekr akan bekerja baik bila Seamonkey di-downgrade ke versi 1.1.17 bawaan Slackware-13.0 (sayang sekali, versi lama).

(more)

Willy Sudiarto Raharjo: Current Moving On

noreply@blogger.com (Willy Sudiarto Raharjo) — Thu, 02 Feb 2012 03:55:00 +0000

After a while, Pat has finally updated the public repository with a massive (as expected) updates with a great quote from the fortune package and everything looks shinny and interesting to see.

So, in general, this is what you will get with the latest -Current:

Linux Kernel 3.2.2 (fixed the mempodipper bug)
Coreutil 8.15 (brings improvement for ext4)
Cups 1.4.8 (brings fixes for LibreOffice printing problems, and have a chance to be backported to 13.37 as a patch)
Glibc 2.14.1(latest stable version being rebuilt with new GCC)
GCC 4.6.2 (also latest stable, with support of Go language from Google)
Emacs 23.4 (surprisingly newer than in the original website)
Mozilla Firefox/Thunderbird 10 (just released few days ago)
Seamonkey 2.7 (along with GCC updates to have it working for ARM architecture, thanks to AlienBOB's work)
OpenSSL 0.9.8t (still no 1.0 release yet, but it's 0.9.x still well maintained upstream)
ca-certificates-20111211: removed untrusted certificates
Some library and standard updates

More packages will come soon enough, so start your engine and bandwidth for the whole new excitement of Slackware-Current.

I will start by syncing with the latest update on Slackware-Current in UKDW Repository

Widya Walesa: KDE 4.8.0 Dan Perbaikan Fitur Suspend di AMD Catalyst

Wed, 01 Feb 2012 03:54:23 +0000

Selamat pagi! Apa kabar semuanya? Sudah pakai KDE 4.8.0?

Willy Sudiarto Raharjo: Merging into /usr

noreply@blogger.com (Willy Sudiarto Raharjo) — Sun, 29 Jan 2012 06:26:00 +0000

There has been a plan for some Linux distribution (started by Fedora) to follow what Solaris has been doing for the last 15 years (and fully completed with the release of Solaris 11) and that is the /usr merge process. In short, all directories containing binaries files should go to /usr and not being scattered in many places like what we had right now, such as /bin, /sbin, /lib, and many others. With this, /usr/bin and /bin will be the same position thus all binaries should be located on this directory.

So far, systemd is probably working on this process and it's being documented on this wiki page. I assume many other will follow once this concensus has been reached. As an addition, please have a look on this article as well: Understanding the bin, sbin, usr/bin , usr/sbin split.

What about Slackware? Well, it's kinda difficult to predict what will happen in Slackware since all the final decision is made by Patrick himself along with other Slackware team members, but as long as it's beneficial to Slackware Project and it doesn't give too much burden to the team or Pat himself to do this changes, i think it's still possible to have it on Slackware. Basically this applies to all kinds of technology/features, not just spesifically the /usr merge process.

This is just my personal opinion as a Slackware users. It doesn't reflect Pat or any other Slackware Team Member's opinion.

Willy Sudiarto Raharjo: Google Earth 6.0.3 on Slackware

noreply@blogger.com (Willy Sudiarto Raharjo) — Sat, 28 Jan 2012 11:55:00 +0000

It's just a few minutes after my previous post about a broken Google Earth 6.0.3 on Slackware and now i have found the solution for that kind of problem, so here's the solution to install the latest Google Earth on Linux (tested here on Slackware Linux):

./GoogleEarthLinux.bin --target /tmp/ge --noexec
cd /tmp/ge/setup.data/bin/Linux/x86/
cd /tmp/ge/setup.data/bin/Linux/x86_64/ (64-bit)
mv setup.gtk setup.gtk2
cd /tmp/ge
./setup.sh (it can be installed using root or normal account)

If for some reason you failed to launch the Google Earth, make sure you have created a symlink to comply with LSB that Google requires by running this as root:

ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

Here's a screenshot to a working Google Earth installation on my desktop:

Willy Sudiarto Raharjo: Updated Google Earth Stucked at LSB 4.0

noreply@blogger.com (Willy Sudiarto Raharjo) — Sat, 28 Jan 2012 11:28:00 +0000

There's a new Google Earth release and it's now 6.2. Unfortunately, the same version is not available in Linux and the latest one in Linux is at 6.0.3.2197. I once covered on how to install Google Earth on Slackware and it's working fine up to Version 6.0.2.2074.

Today, i downloaded the latest version and i saw an update there : 6.0.3.2197. I tried to reproduce the same steps i have been using to perform the installation of Google Earth in Linux, but this time, it failed me.

/GoogleEarthLinux.bin --target /tmp/ge
Creating directory /tmp/ge
Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 6.0.3.2197.............................................................................................
This version of Google Earth requires LSB 4.0 support which you
do not seem to have.
./setup.sh: line 285: [: missing `]'
Unknown id: yum install redhat-lsb
I/O error : No such file or directory
setup.data/setup.xml:1: parser error : Document is empty

^
setup.data/setup.xml:1: parser error : Start tag expected, '<' not found

^
./setup.sh: line 158: 28089 Segmentation fault      "$setup" "$@"

I'm really sure that it was working in the previous version, but unfortunately, it's likely that Google changed it's requirement to have LSB 4.0 as the base

Willy Sudiarto Raharjo: Updated digiKam SlackBuild

noreply@blogger.com (Willy Sudiarto Raharjo) — Fri, 27 Jan 2012 03:38:00 +0000

digiKam is one of my favorite application in KDE since i can use it to export my photos to Facebook directly and it has a lot of interesting features. Unfortunately, this package is not yet part of Slackware default packages, but it's still available on SlackBuilds project.

Another problem is that the maintainer hasn't updated the SlackBuild script to the latest version (2.5.0) and stuck at 1.9.0 up to now.

For those who wanted to try the new digiKam, you can download the original SlackBuild for digiKam from SBo package and replace the .SlackBuild script with the modified SlackBuild from my Box.net account and also a patch file to make it compilable. Put them in the digikam directory and start your engine to compile.

Please read the requirements for the new digiKam package as it adds more dependencies in the process.

Willy Sudiarto Raharjo: VMWare Workstation 8.0.2 and Linux Kernel 3.2 Patch

noreply@blogger.com (Willy Sudiarto Raharjo) — Fri, 27 Jan 2012 00:00:00 +0000

Jérôme posted a comment on my post about VMWare and Linux Kernel patch, saying that the patch i mentioned is not working with VMWare Workstation 8.0.2, the latest VMWare released by the vendor. When a stable kernel is released, normally, the patch should work normally, but in this case, i was wrong (at least my assumption), since the changes in the kernel affected the patch.

So i started a discussion at the patcher's blog and finally the author of the patch confirmed that there's a change in kernel source code which applies to his patch. He fixed the patch and submit it again into his blog post.

Unfortunately, the script still failed on me if i tried to use his script, but Ted, another people confirmed that it's working on his system but instead of using the bash script to do the job, he patched it manually, so i tried and it worked.

So here's the solution:

Get the patch from the author's blog or from my Box account
Extract it (assume in /home/willysr)
Go to /usr/lib/vmware/modules/source
Extract the source file (tar xvf vmnet.tar)
Patch the source file (patch -p1 < /home/willysr/vmware3.2.0.patch)
Create a new source file (tar cvf vmnet.tar vmnet-only/)
Recompile VMWare again (vmware-modconfig --console --install-all)
Voila.... everything works normally again

This patch should also be working for future Linux Kernel 3.3, so you probably don't need to search for more patch when Linux Kernel 3.3 released by Linus.

Willy Sudiarto Raharjo: Fixing Amarok Bug: Stop on Every Track

noreply@blogger.com (Willy Sudiarto Raharjo) — Thu, 26 Jan 2012 16:49:00 +0000

I didn't remember when i started to have this problem, but it's very annoying bug. Amarok will stop playing after it completed playing one track even though there are still a lot of files in the playlist. I assume it's another bug due to transition from previous release of Amarok that might caused this problem to surface.

Thanks to UbuntuForums, i found the solution and i tried it on my desktop and yes, it worked like charm. It seems my predictions was right and the solution is very simple, which is to remove the old configuration of Amarok by doing this steps (you might loose all your Amarok configuration):

mkdir ~/.kde/share/config/backup
mv ~/.kde/share/config/amarok* ~/.kde/share/config/backup/

Restart your Amarok and voila.... it will start playing all the playlist tracks

Willy Sudiarto Raharjo: Fixing Sound Startup on KDE

noreply@blogger.com (Willy Sudiarto Raharjo) — Thu, 26 Jan 2012 15:44:00 +0000

For those who have been playing with KDE 4.8.0 that was released yesterday, you might noticed that your KDE will not ring any sound when you logged in anymore. I noticed this earlier, but i thought that there was some backend problem and i haven't had time to find the solutions for this.

AJ Field commented on Eric's blog post about KDE 4.8.0 and pointed a thread at ArchLinux Forum which should solve the problem. I tried to use the solution written there and it really work like a charm.

The problem only lies in the directory reading on Notification settings (System Settings -> Applications and System Notifications). Previously, you mentioned only the filename, but in KDE 4.8.0, i guess it should have been a complete path, so the solution is simple, just browse the file and pick the same file and it will give you the full path.

I'll show you before and after i changed the path using these two screenshots below. The first screenshot is the original condition:

This is what i got after i browse the file and pick the same filename.

I only need to save the changes and it will be back to normal again once you logged out and logged in again.

Hadi Sumarsono: Refleksi Kemerdekaan SO & Aplikasi -Jelang Maulid Nabi- ala slackycml

Thu, 26 Jan 2012 08:26:00 +0000

BismilLahirrohmanirohim.

Ini tulisan "agak serius" dan "non slackware", yang lahir dari keprihatinan diri selaku putra negeri ini. Baiklah ... jelang peringatan Maulid Nabi Muhammad shollalLohu 'alayhi wa sallam, sebenarnya ada kesempatan kita -selaku muslim- untuk bercermin diri. Tentu saja yang akan ana bicarakan adalah sisi Sistem Operasi (SO) di komputer kita, bukan hari kemarin yang telah berlalu... tapi hari ini dan hari esok. Ya, mencoba meneropongnya lebih dalam dengan kejujuran seorang muslim.

Dan jujur saja, tulisan di bawah ini akan menyarankan Anda selaku pembaca untuk menggunakan SO dan aplikasi GNU/Linux yang merdeka, dan meninggalkan SO yang tidak pernah kita -satu kali pun- membeli lisensi penggunaannya. Jadi kalau Anda "membenci" tema seperti ini, berhentilah membaca dan berpindahlah ke judul lainnya, oke?

(more)

Willy Sudiarto Raharjo: First Impression on KDE 4.8.0

noreply@blogger.com (Willy Sudiarto Raharjo) — Wed, 25 Jan 2012 23:11:00 +0000

I have just finished upgrading my desktop to use KDE 4.8.0, which was just released by KDE team few hours ago while i was sleeping. Thanks to Eric Hameleers, i could get the early release of KDE packages and downloaded this packages as i slept last night. When i woke up this morning, all i have to do is to make sure everything is already up to date by running the rsync script once again.

Next on, performed the command written on the README and performed the upgrade. Don't forget to have a complete look on the README as there has been a renamed packages. After i rebooted my machine, KDE started to be loaded and there was a new splash screen called Air and Ariya Splash Screen which is very minimalistic, but it does look more professionals.

If you have been using KDE 4.7, you won't get too much drastic changes, as it's based on previous releases. According to the announcement, there are a lot of areas which has been improved on this release:

I do feel that KDE 4.8.0 is faster than previous release, probably due to updated Qt which is now bumped to 4.8.0 to sync with KDE release version. You can also have better performance when you enabled desktop effects as there has been a lot of improvements on this area as well.

I used Kate a lot and on this release, Kate also got several new features and one of the new feature i like a lot is the new Line Modification Indicators. It really helps for developers to work in collaboration.

Another nice improvement from KDE is the Power Management System Settings which has been redesigned for simplification. It really helps for users carrying portable devices, such as laptop or netbooks.

KSecretService is taking it's debut on this release to provide new framework for sharing saved passwords and other credentials between a wider range of applications.

So far, i have no problems with this release, but even if there is a problem, it will soon be sorted out in the next monthly release which should be out in February and months following.

For now, i'll enjoy Slackware and KDE 4.8.0

Willy Sudiarto Raharjo: KDE 4.8.0 For Slackware

noreply@blogger.com (Willy Sudiarto Raharjo) — Wed, 25 Jan 2012 21:22:00 +0000

KDE has been proven to be stable enough ever since they released the controversial 4.0 version few years ago. Since then, KDE has matured and i can say it's stable enough to be used in production machines (i used it on my desktop, laptop, and workstation). The previous current version was 4.7.4 and it was released on December 2011. This version was meant to be the last version of KDE 4.7.x series according to KDE

KDE communities never stop improving KDE and as the results, we could see KDE 4.8.0 by now and it's spreading to mirror sites around the world and most distribution vendors has started up to update KDE to the latest version to be included to the distribution packages.

Slackware at this point is still on hibernate status and there hasn't been any big changes on the public repository (-Current tree). Many people has feared that Pat will stop maintaining Slackware, but that's not true. We all know that Pat is very proud of Slackware and i'm sure he will try to maintain it as long as he can, but for now, he need to focus on other things besides Slackware and that results in the lack of updates in -Current. Hopefully that will change in the near future.

Meanwhile, Eric has continued to keep maintaining KDE packages for Slackware. He has done it for several releases back from KDE 4.0 up to 4.7.4 and now, he continues his tradition to provide KDE packages and this time, it's KDE 4.8.0, the latest version from KDE.

This new version of KDE has more packages then the previous version, thanks to the modularization made by the KDE release team. In total, Eric counted there are 90 tarball sources for this release, exploded from 71 sources from KDE 4.7. This gives more burden to the packagers, but it gives more flexibility to the users as they can pick which packages should be installed on their systems.

As always, KDE has been known to work without HAL and that will also likely to happen in Slackware, so try to stop depending to HAL for the time being until it's removed completely from Slackware which will be likely to be in the next release of Slackware since KDE and XFCE will be HAL-free for their next major release (KDE 4.8.0 and XFCE 4.8.0).

Eric mentioned that newer KDE needs mesa-7.10 or newer, and his KDE packages are built for -Current users, not for Slackware 13.37. The reason is simple. There has been a toolchain upgrade in -Current which affects the KDE packages shipped by Eric being incompatible with Slackware-13.37.

Due to a lot of changes in the package naming, it's suggested that you do exactly what's written on the README to perform this upgrade:

On Slackware 32-bit:
  # upgradepkg --reinstall --install-new x86/deps/*.t?z
  # upgradepkg --reinstall --install-new x86/kde/*.t?z
  # removepkg polkit-kde-1
  # removepkg kdeaccessibility
  # removepkg kdebase
  # removepkg kdebase-runtime
  # removepkg kdebase-workspace
  # removepkg kdebindings
  # removepkg kdeedu

# removepkg kdegraphics
  # removepkg kdeutils
  # removepkg konq-plugins

  On Slackware 64-bit:
  # upgradepkg --reinstall --install-new x86_64/deps/*.t?z
  # upgradepkg --reinstall --install-new x86_64/kde/*.t?z
  # removepkg polkit-kde-1
  # removepkg kdeaccessibility
  # removepkg kdebase
  # removepkg kdebase-runtime
  # removepkg kdebase-workspace
  # removepkg kdebindings
  # removepkg kdeedu

# removepkg kdegraphics
  # removepkg kdeutils
  # removepkg konq-plugins

You can remove the unneeded packages later on once it's proven to be running well.

If you upgrade from his previous packages (KDE 4.6 or 4.7), then please the end of the note about a change in the package's name:
* oxygen-gtk was renamed to oxygen-gtk2
* mobipocket was renamed to kdegraphics-mobipocket

In the end, credit should all go to Eric for his hard work of maintaining KDE packages for Slackware. I am only helping to distribute his work to Indonesian areas and for those who reads this blog.

If you need to keep KDE 4.7.4 on your system, please use the main repository (http://alien.slackbook.org/ktown/) or put an "exclude" command on your rsync script to prevent them to be deleted since in other mirror sites, KDE 4.7.4 has been deleted.

This set of KDE 4.8.0 packages is now available at UKDW Repository as well. Enjoy KDE 4.8.0 for Slackware.

Richi Hariyanto: gnome-3.2

Tue, 24 Jan 2012 04:50:35 +0000

ternyata tidak diperlukan perjuangan yang payah untuk memasang Gnome 3.2 pada Slackware 13.37. ini diakibatkan adanya dokumentasi pada blog pak Widya Walesa. setelah installasi berhasil, saya memasang libffi yang tidak ditemukan. kemudian membangun ulang gjs. lalu mengcompile ulang mesa untuk mengaktifkan gallium. saya iseng memanfaatkan mesa 7.10.2 yang tersedia pada directory testing. kompilasi berjalan lancar jaya tanpa mengganti libdrm versi 2.3.23. berikut konfigurasi yang saya kutip :

 gjs.SlackBuild
..
sed -i 's/mozilla-js/seamonkey-js/g' configure.ac
autoconf -i -f
..

 Mesa.SlackBuild
..
  --enable-gallium-i915 \
  --enable-gallium-i965 \
  --enable-gallium-radeon \
  --enable-gallium-r600 \
  --enable-gles1 \
  --enable-gles2 \
  --enable-shared-dricore \
  --with-driver=dri \
  --with-state-trackers=dri,glx,egl
..

hasilnya, lumayan

referensi :
http://www.walecha.net/content/gallium-berhasil-tundukkan-gnome-shell-di-ati-radeon
http://www.walecha.net/content/mencoba-gsb-32-di-slackware-current

Widya Walesa: ATI Catalyst Gagal Suspend di Kernel 3.2.1

Sun, 22 Jan 2012 13:11:12 +0000

Sekitar 3 hari yang lalu saya dibuat terkejut dengan sebuah kegagalan fungsi suspend di notebook saya. Saat itu saya sedang memindahkan notebook yang sedang saya gunakan ke ruang lain dengan sebelumnya saya atur agar fitur suspend di Slackware saya menjadi aktif.