tag:blogger.com,1999:blog-924870795881527292024-03-14T10:00:28.220+07:00Henry's BlogSharing something to you ...Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.comBlogger56125tag:blogger.com,1999:blog-92487079588152729.post-18369575433031469402014-12-28T14:17:00.000+07:002014-12-28T14:17:19.147+07:00AMD Catalyst Omega 14.501.1003 (14.12) for kernel 3.18.xFinally, I had time to upgrade my laptop to the latest of slackware64-current, kernel 3.18.1, and <a href="http://support.amd.com/en-us/kb-articles/Pages/AMDCatalystOmegaLINReleaseNotes.aspx" target="_blank">AMD Catalyst Omega 14.501.1003</a> 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, <a href="https://aur.archlinux.org/packages/catalyst/" target="_blank">Arch User Repository (AUR)</a> for the patch. I modified the patch so that only one patch file is needed. You can download <a href="https://drive.google.com/file/d/0B4VfWnVnFzi4TGQ1LWU2MVdiM0E/view?usp=sharing" target="_blank">the patch from my Google Drive</a>. You can follow the guidelines below to patch the fglrx module:<br />
<div>
<ul>
<li>change directory to the path where the installer is</li>
<li>run the installer as root (superuser):<br /><span style="font-family: Courier New, Courier, monospace;"># ./amd-driver-installer-14.501.1003-x86.x86_64.run</span></li>
<li>follow the instructions, at the end of installation process you will get notice that there are some errors.</li>
<li>exit the installer</li>
<li>at console, copy the patch file (<span style="font-family: Courier New, Courier, monospace;"><a href="https://drive.google.com/file/d/0B4VfWnVnFzi4TGQ1LWU2MVdiM0E/view?usp=sharing" target="_blank">fglrx-14.12_kernel-3.18.x.patch</a></span>) to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>change directory to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>patch the fglrx source:<br /><span style="font-family: Courier New, Courier, monospace;"># patch -p0 < fglrx-14.12_kernel-3.18.x.patch</span></li>
<li>compile the fglrx modules:<br /><span style="font-family: Courier New, Courier, monospace;"># ./make.sh<br /># cd ..<br /># ./make_install.sh</span></li>
<li>reboot.</li>
</ul>
</div>
Enjoy your AMD Catalyst-14.501.1003 or 14.12 running on linux kernel 3.18.x.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com15tag:blogger.com,1999:blog-92487079588152729.post-83725212565534388262014-02-13T15:41:00.000+07:002014-02-13T15:41:01.009+07:00AMD Catalyst Patch for kernel-3.13.xYesterday, I decided to upgrade the kernel from kernel tree of 3.12.x to 3.13.x and AMD Catalyst from 13.8-beta1 to 13.12. When I upgraded the AMD Catalyst, I got error message on compiling fglrx kernel module. As usual, I checked to <a href="https://aur.archlinux.org/packages/catalyst/">Arch Linux</a> for the patch and I found it. I used the information from it to modify the patch into one file only. You can <a href="https://drive.google.com/file/d/0B4VfWnVnFzi4ZEJMd0wtdFFNbEk/edit?usp=sharing">download the modified patch from my Google Drive</a>. Using this patch file, you can patch the fglrx module (of course, you have to install AMD Catalyst 13.12 first) as below (in case of using kernel-3.13.2. Just edit the number "3.13.2" for other kernel version):<br />
<div>
<ul>
<li>change directory to the path where the installer is</li>
<li>run the installer as root (superuser):<br /><span style="font-family: Courier New, Courier, monospace;"># ./amd-catalyst-13.12-linux-x86.x86_64.run</span></li>
<li>follow the instructions, at the end of installation process you will get notice that there are some errors.</li>
<li>exit the installer</li>
<li>at console, copy the patch file (<span style="font-family: Courier New, Courier, monospace;"><a href="https://drive.google.com/file/d/0B4VfWnVnFzi4ZEJMd0wtdFFNbEk/edit?usp=sharing">fglrx-13.12_kernel-3.13.x.patch</a></span>) to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>change directory to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>patch the fglrx source:<br /><span style="font-family: Courier New, Courier, monospace;"># patch -p0 < fglrx-13.12_kernel-3.13.x.patch</span></li>
<li>compile the fglrx modules:<br /><span style="font-family: Courier New, Courier, monospace;"># ./make.sh<br /># cd ..<br /># ./make_install.sh</span></li>
<li>reboot.</li>
</ul>
</div>
Enjoy your AMD Catalyst-13.12 running on linux kernel 3.13.x.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com0tag:blogger.com,1999:blog-92487079588152729.post-52903426428178293832013-03-07T19:03:00.001+07:002013-03-07T19:12:50.018+07:00AMD Catalyst Patch for Kernel 3.8.xKernel 3.7.x is EOL now, replaced by 3.8.x as the latest stable kernel version. Because of this, I upgraded the kernel running on my laptop to 3.8.x (on the day I wrote this post, the newest version is 3.8.2). Of course, upgrading the kernel means recompiling the fglrx module. It means, this module need to be re-patched so that can work on kernel-3.8.x. As usual, I searched the patch from <a href="https://aur.archlinux.org/packages/catalyst/">Arch Linux</a> then used the information on that site to patch the fglrx module. You can download <a href="https://docs.google.com/file/d/0B4VfWnVnFzi4YS1xM2ItSXVfbXM/edit?usp=sharing">the complete patch from my Google Drive</a>. Using this patch file, you can patch the fglrx module (by installing AMD Catalyst 13.1 first) as below (in case of using kernel-3.8.2. Just edit the number "3.8.2" for other kernel version):<br />
<ul>
<li>change directory to the path where the installer is</li>
<li>run the installer as root (superuser): </li>
<di><span style="font-family: Courier New, Courier, monospace;"># ./amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run</span></di>
<li>follow the instructions, at the end of installation process you will get notice that there are some errors.</li>
<li>exit the installer</li>
<li>at console, copy the patch file (<span style="font-family: Courier New, Courier, monospace;"><a href="https://docs.google.com/file/d/0B4VfWnVnFzi4YS1xM2ItSXVfbXM/edit?usp=sharing">fglrx-3.8.patch</a></span>) to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>(<i>optional, if you don't find </i><span style="font-family: Courier New, Courier, monospace;">version.h</span><i> in <span style="font-family: Courier New, Courier, monospace;">/</span></i><span style="font-family: Courier New, Courier, monospace;">lib/modules/3.8.2/build/include/linux</span>) Make symlink of <span style="font-family: Courier New, Courier, monospace;">version.h</span>: </li>
<di><span style="font-family: Courier New, Courier, monospace;"># ln -s /lib/modules/3.8.2/build/include/generated/uapi/linux/version.h /lib/modules/3.8.2/build/include/linux/version.h</span></di>
<li>change directory to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>patch the fglrx source:</li>
<di><span style="font-family: Courier New, Courier, monospace;"># patch -p0 < fglrx-3.8.patch</span></di>
<li>compile the fglrx modules:</li>
<di><span style="font-family: Courier New, Courier, monospace;"># ./make.sh<br /># cd ..<br /># ./make_install.sh</span><br />
<li>reboot.</li>
</di></ul>
Enjoy your AMD Catalyst-13.1 running on linux kernel 3.8.x.
<br />
<br />Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com14tag:blogger.com,1999:blog-92487079588152729.post-31759004331767533382012-12-31T16:14:00.001+07:002012-12-31T16:47:58.213+07:00AMD Catalyst Patch for kernel-3.7.xIt has been 5 months! I didn't upgrade the AMD Catalyst driver and also the kernel (I sticked with kernel 3.4.x). This week, I got time for upgrading the kernel to 3.7.x and also trying to install AMD Catalyst 12.10. As usual, the fglrx module of AMD Catalyst 12.10 could not be compiled smoothly because of incompatibilities between kernel 3.7.x and this fglrx module. Fortunately, I found the patch from arch linux (<i>also as usual ...</i> :) ... <i>my favorite place for searching any patches</i>) from <a href="http://catalyst.apocalypsus.net/files/arch-fglrx-3.7.patch">this link</a> then I make a little bit modification. You can download it from my <a href="https://docs.google.com/open?id=0B4VfWnVnFzi4a3R6N2xnOC1TWlU">google docs link</a>.<br />
<div>
<br /></div>
<div>
<b>How to patch?</b></div>
<div>
<div>
I used the following steps to install AMD Catalyst-12.10 for kernel 3.7.1 (of course, you just change the kernel directory on these steps if your kernel version is not 3.7.1) and patch the fglrx module:</div>
<div>
<ul>
<li>change directory to the path where the installer is</li>
<li>run the installer as root (superuser): </li>
<di><span style="font-family: Courier New, Courier, monospace;"># ./amd-driver-installer-catalyst-12.10-x86.x86_64.run</span></di>
<li>follow the instructions, at the end of installation process you will get notice that there are some errors.</li>
<li>exit the installer</li>
<li>at console, copy the patch file (<span style="font-family: Courier New, Courier, monospace;"><a href="https://docs.google.com/open?id=0B4VfWnVnFzi4a3R6N2xnOC1TWlU">fglrx-3.7.patch</a></span>) to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>(<i>optional, if you don't find </i><span style="font-family: Courier New, Courier, monospace; font-size: x-small;">version.h</span><i> in <span style="font-family: Courier New, Courier, monospace;">/</span></i><span style="font-family: Courier New, Courier, monospace;">lib/modules/3.7.1/build/include/linux</span>) Make symlink of <span style="font-family: Courier New, Courier, monospace;">version.h</span>: </li>
<di><span style="font-family: Courier New, Courier, monospace;"># ln -s /lib/modules/3.7.1/build/include/generated/uapi/linux/version.h /lib/modules/3.7.1/build/include/linux/version.h</span></di>
<li>change directory to <span style="font-family: Courier New, Courier, monospace;">/lib/modules/fglrx/build_mod/</span></li>
<li>patch the fglrx source:</li>
<di><span style="font-family: Courier New, Courier, monospace;"># patch -p0 < fglrx-3.7.patch</span></di>
<li>compile the fglrx modules:</li>
<di><span style="font-family: Courier New, Courier, monospace;"># ./make.sh<br />
# cd ..<br />
# ./make_install.sh</span><br />
<li>reboot.</li>
</di></ul>
</div>
<div>
Enjoy your AMD Catalyst-12.10 running on linux kernel 3.7.x.<br />
<br /></div>
</div>
Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com11tag:blogger.com,1999:blog-92487079588152729.post-28495582102701939892012-07-09T14:00:00.000+07:002012-07-09T14:05:02.888+07:00Left-, Right-, and Middle-click on Clickpad<span style="background-color: white;">Last time, I have shared to you about <a href="http://henryhermawan.blogspot.com/2011/03/synaptics-140-patch-for-activating.html">how to activate right-click on clickpad by patching and recompiling the source of synaptics, at that time, synaptics version 1.4.0</a>. Pat has upgraded the synaptics in Slackware- or Slackware64-current to version of 1.6.2. When I read the source of </span><span style="background-color: white; font-family: inherit;">synaptics-1.6.2</span><span style="background-color: white;">, I found that the click function of clickpad can be performed by clicking the clickpad using one, two, and three finger(s). I set the clickpad configuration for X-server, saved in <span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">/etc/X11/xorg.conf.d/clickpad.conf</span>, as below:</span><br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">Section "InputClass"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Identifier "touchpad"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Driver "synaptics"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> MatchDevicePath "/dev/input/event*"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> MatchIsTouchpad "on"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Option "TapButton1" "1"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Option "TapButton2" "2"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Option "TapButton3" "3"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Option "VertTwoFingerScroll" "on"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Option "HorizTwoFingerScroll" "on"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Option "VertEdgeScroll" "on"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Option "HorizEdgeScroll" "on"</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">EndSection</span><br />
<br />
By this configuration, I activate the behavior of click functions, vertical- and horizontal-scroll using two fingers, and also vertical-edge- and horizontal-edge-scroll that are very convinient for me. Click functions on my laptop can be performed such like this:<br />
<br />
<ul>
<li><span style="background-color: white;">left-click: one-finger's click</span></li>
<li><span style="background-color: white;">right-click: two-finger's click</span></li>
<li><span style="background-color: white;">middle-click: three-finger's click</span></li>
</ul>
<br />
<br />Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com2tag:blogger.com,1999:blog-92487079588152729.post-83522991927981722152012-07-02T12:04:00.000+07:002012-07-02T14:40:37.076+07:00Official Release of AMD Catalyst 12.6Finally, <a href="http://www2.ati.com/drivers/linux/amd-driver-installer-12-6-x86.x86_64.run">AMD Catalyst 12.6</a> 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. <a href="http://wiki.cchtml.com/index.php/Hardware">This unofficial AMD Catalyst's wiki</a> may help you to decide which version you want to install on your computer.<br />
<br />
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: "<a href="http://henryhermawan.blogspot.com/2012/06/amd-catalyst-patch-for-kernel-34x.html">AMD Catalyst Patch for kernel-3.4.x</a>". 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.<br />
<br />
<i>Updated (02-JUL-2012):</i><br />
<ul>
<li><a href="http://www2.ati.com/drivers/linux/amd-driver-installer-12-6-x86.x86_64.run">This Catalyst driver</a> and <a href="http://henryhermawan.blogspot.com/2012/06/amd-catalyst-patch-for-kernel-34x.html">the patch</a> are working very well on kernel-3.4.4</li>
<li>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 <a href="http://support.amd.com/us/kbarticles/Pages/Catalystbetadriver1.aspx">this link</a>. However, this beta version is not for linux ... :( </li>
</ul>Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com0tag:blogger.com,1999:blog-92487079588152729.post-54144199514402705112012-06-14T12:06:00.001+07:002012-06-14T12:11:14.528+07:00AMD Catalyst-12.6 Beta and xorg-server-1.12.1After 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, <a href="http://support.amd.com/us/kbarticles/Pages/AMDCatalyst126beta.aspx">AMD Catalyst-12.6 Beta</a>. 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.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com1tag:blogger.com,1999:blog-92487079588152729.post-47975077890954242252012-06-14T11:46:00.000+07:002012-06-14T11:48:36.769+07:00AMD Catalyst Patch for kernel-3.4.xAfter the kernel-3.3.x has been terminated (EOL), I decided to move to kernel-3.4.x. Unfortunately, this moving was not so easy since fglrx module could not be compiled for the kernel-3.4.x, in other words, this module needs to be patched. Referring to two references that I have written below, I have got the patch and have successfully patched fglrx module of <a href="http://www2.ati.com/drivers/linux/amd-driver-installer-12-4-x86.x86_64.run">AMD Catalyst-12.4</a> and <a href="http://support.amd.com/us/kbarticles/Pages/AMDCatalyst126beta.aspx">AMD Catalyst-12.6Beta</a>. You can download the patch from <a href="https://docs.google.com/open?id=0B4VfWnVnFzi4Q2lGeW9pYW5UWjQ">this link</a> or just copy-paste a few lines below to your favorite text editor and saving it to a file:<br />
<br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">--- lib/modules/fglrx/build_mod/firegl_public.c</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+++ lib/modules/fglrx/build_mod/firegl_public.c.new</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">@@ -4181,7 +4184,11 @@ static int kasInitExecutionLevels(unsigned long level_init)</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> {</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> unsigned int p;</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> KCL_DEBUG5(FN_FIREGL_KAS, "%d\n", level_init);</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,4,0)</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+ for_each_possible_cpu(p)</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+#else</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> for_each_cpu_mask(p, cpu_possible_map)</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+#endif</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> {</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> KCL_DEBUG1(FN_FIREGL_KAS,"Setting initial execution level for CPU # %d\n", p);</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> preempt_disable();</span><br style="font-family: "Courier New",Courier,monospace;" /><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">--- lib/modules/fglrx/build_mod/kcl_ioctl.c</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+++ lib/modules/fglrx/build_mod/kcl_ioctl.c.new</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">@@ -217,6 +217,10 @@</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> * \param size [in] Number of bytes to allocate</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> * \return Pointer to allocated memory</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> */</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,4,0)</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+DEFINE_PER_CPU(unsigned long, old_rsp);</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+#endif</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;">+</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> void* ATI_API_CALL KCL_IOCTL_AllocUserSpace32(long size)</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> {</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> void __user *ret = COMPAT_ALLOC_USER_SPACE(size);</span></span><br />
<br />
I used the following steps to install AMD Catalyst-12.4 or 12.6 Beta and patch the fglrx module:<br />
<ul>
<li>change directory to the path where the installer is</li>
<li>run the installer as root (superuser): </li>
<di><span style="font-family: "Courier New",Courier,monospace;"># ./amd-driver-installer-12-4-x86.x86_64.run
</span><br />(change to <span style="font-family: "Courier New",Courier,monospace;">./amd-driver-installer-8.98-x86.x86_64.run</span> for AMD Catalyst-12.6 Beta)</di>
<li>follow the instructions, at the end of installation process you will get notice that there are some errors.</li>
<li>exit the installer</li>
<li>at console, copy the patch file (<span style="font-family: "Courier New",Courier,monospace;">fglrx_kernel_3.4.0.patch</span>) to <span style="font-family: "Courier New",Courier,monospace;">/lib/modules/fglrx</span></li>
<li>change directory to <span style="font-family: "Courier New",Courier,monospace;">/lib/modules/fglrx</span></li>
<li>patch the fglrx source: </li>
<di style="font-family: "Courier New",Courier,monospace;"># patch -p3 < fglrx_kernel_3.4.0.patch </di>
<li>compile the fglrx modules:</li>
<di style="font-family: "Courier New",Courier,monospace;"># cd build_mod<br /># ./make.sh<br /># cd ..<br /># ./make_install.sh</di>
<li>reboot.</li>
</ul>
Enjoy your AMD Catalyst-12.4 or AMD Catalyst-12.6 Beta!<br />
<br />
References:<br />
<ul>
<li><a href="http://cvs.rpmfusion.org/viewvc/rpms/catalyst-kmod/F-16/fglrx_kernel_3.4.0.patch?revision=1.3&root=nonfree&view=markup">http://cvs.rpmfusion.org/viewvc/rpms/catalyst-kmod/F-16/fglrx_kernel_3.4.0.patch?revision=1.3&root=nonfree&view=markup</a></li>
<li><a href="http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/475575-warning-kernel-3-4-amd-catalyst-12-4-not-compatible.html#post2466327">http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/475575-warning-kernel-3-4-amd-catalyst-12-4-not-compatible.html#post2466327</a></li>
</ul>Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com13tag:blogger.com,1999:blog-92487079588152729.post-183761871350516512012-04-10T15:58:00.000+07:002012-04-10T15:59:35.193+07:00Beware when compiling using -jN optionWhen I compiled lilypond-2.15.36, I found this error:
<source></source><br />
<blockquote class="tr_bq" style="font-family: "Courier New",Courier,monospace;">
<span style="font-size: x-small;">cat out/feta-braces-a.otf-table out/feta-braces-b.otf-table out/feta-braces-c.otf-table out/feta-braces-d.otf-table out/feta-braces-e.otf-table out/feta-braces-f.otf-table out/feta-braces-g.otf-table out/feta-braces-h.otf-table out/feta-braces-i.otf-table > out/emmentaler-brace.otf-table<br />echo '(design_size . 20)' > out/emmentaler-brace.otf-gtable<br />echo feta-braces-d feta-braces-c feta-braces-i feta-braces-e feta-braces-h feta-braces-a feta-braces-g feta-braces-f feta-braces-b > out/emmentaler-brace.subfonts<br />printf 'emmentaler-brace' > out/emmentaler-brace.fontname<br />cd ./out && /usr/bin/fontforge -script emmentaler-11.pe<br />Copyright (c) 2000-2011 by George Williams.<br /> Executable based on sources from 13:48 GMT 22-Feb-2011-ML-TtfDb.<br /> Library based on sources from 13:48 GMT 22-Feb-2011.<br />Cannot open /usr/local/src/Music/lilypond-2.15.36/build/mf/out/feta11.pfb<br />The requested file, feta11.pfb, does not exist<br />MergeFonts: Can't find font: feta11.pfb<br />Called from...<br /> emmentaler-11.pe: line 17<br />make[1]: *** [out/emmentaler-11.svg] Error 1<br />make[1]: *** Waiting for unfinished jobs..... </span></blockquote>
<br />
This error is caused by the use of -jN option when compiling lilypond (I used this instruction: make -j4 all). I used that option in order to maximize CPU cores utilization, however, this option can lead the compilation process into race condition. In the case of lilypond compilation, feta11.pfb is needed by one of compilation thread/stream before other thread/stream compiles it. When I omitted the -jN option, the compilation was successful.<br />
<br />
In conclusion, be careful when we use the -jN option. This option can make the compilation process faster because the compilation process uses more than one CPU core, however, the race condition can occur in some cases.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com1tag:blogger.com,1999:blog-92487079588152729.post-28245799259042342102012-04-05T14:39:00.001+07:002012-04-05T14:39:16.913+07:00Linux Kernel 3.3.1 & AMD CatalystI just upgraded the kernel to 3.3.1 (my own compilation) then tried to recompile the fglrx modules for this new kernel. No problem in compilation, as well as in use. I have tried AMD Catalyst 12.2 and 12.3, both are no problem on my system with kernel 3.3.1. If you want to upgrade your kernel to 3.3.1 and AMD Catalyst 12.2 or 12.3, you can upgrade them ... without problem, hopefully.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com3tag:blogger.com,1999:blog-92487079588152729.post-14922785194950453212011-09-22T19:51:00.001+07:002011-09-22T22:27:30.855+07:00TeXstudio-2.2 on Slackware64Today, I have upgraded <a href="http://texstudio.sourceforge.net/">TeXstudio</a> (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 <a href="http://texstudio.sourceforge.net/">its website</a>. I downloaded the source code from <a href="http://sourceforge.net/projects/texstudio/files/texstudio/TeXstudio%202.2/texstudio-2.2.tar.gz/download">this link</a>. It needs Qt (at least 4.3), libpoppler, and TeX packages (don't worry, they can be found in <span style="font-family: "Courier New",Courier,monospace;">l</span> (or <span style="font-family: "Courier New",Courier,monospace;">deps</span> for Qt if you are using <a href="http://taper.alienbase.nl/mirrors/alien-kde/">Eric's KDE compilation packages</a>) and <span style="font-family: "Courier New",Courier,monospace;">t</span> directory for Slackware/64) for compilation.<br />
<br />
The compilation process is very easy:<br />
<ul>
<li>extract the source files from tarball</li>
<li>enter to texstudio source directory</li>
<li style="font-family: "Courier New",Courier,monospace;"># qmake texstudio.pro</li>
<li> <span style="font-family: "Courier New",Courier,monospace;"># vim Makefile.Release</span> (or, use your favorite text editor to edit <span style="font-family: "Courier New",Courier,monospace;">Makefile.Release</span>)</li>
<li>make sure <span style="font-family: "Courier New",Courier,monospace;">/usr/lib64</span> is written on <span style="font-family: "Courier New",Courier,monospace;">LIBS</span> (see Figure 1)</li>
<li style="font-family: "Courier New",Courier,monospace;"># make</li>
<li style="font-family: "Courier New",Courier,monospace;"># make install</li>
</ul>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9G7Gj1Z3JKYiFMv9ejVIrWxH6MbcdSBlYt2Ao_0GUY-6teSFiYxjvH2zZ72i08Hfx_ENqKNU2PhP792LgQ2HZo75hL51FR9nc-WKAvhDHc5bYBByFr2T3Kk6rCSCW9sRvLlXXc_t29zk/s1600/texstudio_Makefile_edited.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="83" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9G7Gj1Z3JKYiFMv9ejVIrWxH6MbcdSBlYt2Ao_0GUY-6teSFiYxjvH2zZ72i08Hfx_ENqKNU2PhP792LgQ2HZo75hL51FR9nc-WKAvhDHc5bYBByFr2T3Kk6rCSCW9sRvLlXXc_t29zk/s320/texstudio_Makefile_edited.png" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Figure 1: Makefile.Release</td></tr>
</tbody></table>
<br />
It should be no problem in compilation. Enjoy your TeXstudio!<br />
<br />
Screenshot:<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgj-mm3i8Jdp0FCzCLbk1suHW6pGSka2kfXtbBO50emoebMVcPWV1QU3DshPgeACtGOV7o6RwxzIz3KYC4r55bYk0voyScfcayutWb7sJ2Rt37h5SZ_TQUzn7b523JhBo9zZDlD6JfqQdg/s1600/texstudio_screenshot.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="173" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgj-mm3i8Jdp0FCzCLbk1suHW6pGSka2kfXtbBO50emoebMVcPWV1QU3DshPgeACtGOV7o6RwxzIz3KYC4r55bYk0voyScfcayutWb7sJ2Rt37h5SZ_TQUzn7b523JhBo9zZDlD6JfqQdg/s320/texstudio_screenshot.png" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Figure 2: TeXstudio-2.2 is running on Slackware64</td></tr>
</tbody></table>
<br />
<ul>
</ul>
Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com0tag:blogger.com,1999:blog-92487079588152729.post-69599375782843268952011-08-30T10:58:00.000+07:002011-08-30T13:29:07.097+07:00Installing e-Sword under wine on Slackware64Finally, I can install <a href="http://www.e-sword.net/index.html">e-Sword</a>, a Bible study software for windows, under <a href="http://www.winehq.org/">wine</a> on <a href="http://www.slackware.com/">Slackware64</a> 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.<br />
<br />
Before installing e-Sword, you have to prepare the wine environment. For Slackware users, you can download the slackbuild scripts from <a href="http://slackbuild.org/">SlackBuild.org</a> and the source files, then build the slackware packages, in order, webcore-fonts, fontforge, wine, winetricks, and cabextracts. <u>Strictly for Slackware64 users</u>, you have to install <a href="http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib">Eric's multilib packages</a> 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):<br />
<span style="font-family: "Courier New",Courier,monospace;"> $ export WINEARCH=win32</span> <span style="color: red;"><-- just for Slackware64</span><br />
<span style="font-family: "Courier New",Courier,monospace;"> $ winetricks mfc42</span> <span style="color: red;"><-- installing </span><span style="color: red; font-family: "Courier New",Courier,monospace;">mfc42.dll</span><br />
<span style="font-family: "Courier New",Courier,monospace;"> $ winetricks msls31</span> <span style="color: red;"><-- installing </span><span style="color: red; font-family: "Courier New",Courier,monospace;">msls31.dll</span><br />
<br />
Now, you're ready to install e-Sword. Download the latest version then install it:<br />
<span style="font-family: "Courier New",Courier,monospace;"> $ wine [path-to]/setupXXX.exe</span> <span style="color: red;"><-- the "XXX" is the version number of e-Sword</span><br />
<br />
After that, you need to set up wine environment again:<br />
<div style="font-family: "Courier New",Courier,monospace;">
$ cp ~/.wine/drive_c/Program Files/e-Sword/riched20.dll ~/.wine/drive_c/windows/system32</div>
<div style="font-family: "Courier New",Courier,monospace;">
$ winecfg</div>
<br />
In winecfg, set <span style="font-family: "Courier New",Courier,monospace;">riched20.dll</span> to native and <span style="font-family: "Courier New",Courier,monospace;">oleaut32.dll</span> to native,builtin (see picture below).<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEin0Vr3Z5jx3pV5qiWMaIbv890KDFZxgfcaMalkqeHJHjBo1T-2WgghLhwrdz0Gen72tbb-krg-XE3I2zkjISakXbSKv166vrnGm9TzRPcbyIcC3xkI2PdjInEVlg8x-IRLgcxivtbS7v4/s1600/e-Sword+-+winecfg.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEin0Vr3Z5jx3pV5qiWMaIbv890KDFZxgfcaMalkqeHJHjBo1T-2WgghLhwrdz0Gen72tbb-krg-XE3I2zkjISakXbSKv166vrnGm9TzRPcbyIcC3xkI2PdjInEVlg8x-IRLgcxivtbS7v4/s400/e-Sword+-+winecfg.png" width="357" /></a></div>
Finally, run e-Sword by clicking the icon on your desktop/menu (if any) or typing this command on terminal:<br />
<div style="font-family: "Courier New",Courier,monospace;">
$ wine "C:/Program Files/e-Sword/e-Sword.exe"</div>
<br />
<u>Installing eSword9Converter</u><br />
If you have the old modules (before version 9) for e-Sword, you need to convert it before using it. You will need <a href="http://goodolclint.com/e-sword">eSword9Converter</a> to do that. Please download it from <a href="http://goodolclint.com/e-sword">this site</a>. Before installing it, you have to install .NET Framework 3.5 by typing this command on terminal (you have to connect to internet):<br />
<div style="font-family: "Courier New",Courier,monospace;">
$ winetricks dotnet35</div>
Then you can install eSword9Converter:<br />
<span style="font-family: "Courier New",Courier,monospace;"> $ wine [path-to]/setup-X.X.X.exe</span> <span style="color: red;"><--- the "X.X.X" is the version number of eSword9Converter</span><br />
After finishing installation, you can run eSword9Converter by clicking the icon on your desktop/menu (if any) or typing this command on terminal:<br />
<div style="font-family: "Courier New",Courier,monospace;">
$ wine "C:/Program Files/eSword9Converter/eSword9Converter.exe"</div>
<br />
That's all.<br />
<br />
<u>References:</u><br />
<ul>
<li>http://ubuntuforums.org/showthread.php?t=404042</li>
<li>http://forum.sabayon.org/viewtopic.php?t=22775#p127929</li>
</ul>
<br />
<br />Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com1tag:blogger.com,1999:blog-92487079588152729.post-44460624809164133122011-08-26T19:53:00.003+07:002011-08-26T19:56:02.609+07:00ATI Catalyst on Linux Kernel 3.0.3Yesterday, 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.<br />
<br />
<u>ATI Catalyst 11.8 (without patch)</u><br />
This version has been installed without problem and without any single line's patch. My suggestion, use <span style="font-family: "Courier New",Courier,monospace;">xorg.conf</span> from <span style="font-family: "Courier New",Courier,monospace;">aticonfig --initial</span> for avoiding any problem (see <a href="http://henryhermawan.blogspot.com/2011/08/linux-kernel-301-ati-catalyst.html">my previous post</a>), especially if you want to use Desktop Effects.<br />
<br />
<u>ATI Catalyst 10.12 (with patch)</u><br />
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 <a href="http://henryhermawan.blogspot.com/2011/06/ati-catalyst-proprietary-display-driver.html">my previous post</a>. You can find the link for downloading the patch on that post.<br />
<br />
That's all.<br />
<br />
<i><u>Note:</u></i> for my other posts about ATI Catalyst, go to <a href="http://henryhermawan.blogspot.com/search/label/ati-radeon">this link</a>. You may need to read it.
Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com2tag:blogger.com,1999:blog-92487079588152729.post-36143148691623144242011-08-09T11:51:00.020+07:002011-08-11T10:37:47.745+07:00Linux Kernel 3.0.1 & ATI CatalystSince 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).<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
<span style="font-size: x-small;">Section "Device"</span><br />
<span style="font-size: x-small;"> [...]</span><br />
<span style="font-size: x-small;"> Option "OpenGLOverlay" "off"</span><br />
<span style="font-size: x-small;"> [...]</span><br />
<span style="font-size: x-small;">EndSection</span></blockquote>
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 (<a href="http://henryhermawan.blogspot.com/2011/06/ati-catalyst-proprietary-display-driver.html">here</a>). So far so good, I can activate the Desktop Effects again.<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
<span style="font-size: x-small;">Section "Device"</span><br />
<span style="font-size: x-small;"> [...]</span><br />
<span style="font-size: x-small;"> Option "OpenGLOverlay" "on"</span><br />
<span style="font-size: x-small;"> [...]</span><br />
<span style="font-size: x-small;">EndSection</span></blockquote>
<br />
Linux Kernel 3.0.1 and ATI Catalyst 10.12:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhFzG6AM0kYQUuAZv-Lowu1jNkWqK9heEpY3k_kQlLlGYp9iZ-CjwTIdvVBerTtp2OS6cs09wu1lpPYkY7hnp8j4Rsfv6fUh-sbS4WYIL-jwx26OGZzesjl2oT0zXhVPpHNIu7abTDkCYY/s1600/kernel-3.0.1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="28" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhFzG6AM0kYQUuAZv-Lowu1jNkWqK9heEpY3k_kQlLlGYp9iZ-CjwTIdvVBerTtp2OS6cs09wu1lpPYkY7hnp8j4Rsfv6fUh-sbS4WYIL-jwx26OGZzesjl2oT0zXhVPpHNIu7abTDkCYY/s400/kernel-3.0.1.png" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiT8B13rOS8LgRPVil85It7XmAjaUmq7GSpEMYhDFM067mMuJZWsxhNzAb7lvHi2WvVJDOcNIeQKsillCdmQd6FsfyqlO8YGsptcNAwZ8y6G1IXFt4SoadgwbSv6Q1WpJwqGsASVQ5zDvY/s1600/ATI_Catalyst_10.12_3.0.1-atisysinfo.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="25" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiT8B13rOS8LgRPVil85It7XmAjaUmq7GSpEMYhDFM067mMuJZWsxhNzAb7lvHi2WvVJDOcNIeQKsillCdmQd6FsfyqlO8YGsptcNAwZ8y6G1IXFt4SoadgwbSv6Q1WpJwqGsASVQ5zDvY/s200/ATI_Catalyst_10.12_3.0.1-atisysinfo.png" width="200" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh4LcvBtEW6QkeTrAj_ZHOFp3IMv57vhi0tTpuHxFgevPE7EQZxE_JX9VvrE2Y87Bgv0B2hzjAnLUfbDfbsgMEuSumO7fIazHCI-7HQpaX5ONYagsu8LkBcj5itT12lPi5k_uNuirV4O68/s1600/ATI_Catalyst_10.12_3.0.1-XorgLog.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="90" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh4LcvBtEW6QkeTrAj_ZHOFp3IMv57vhi0tTpuHxFgevPE7EQZxE_JX9VvrE2Y87Bgv0B2hzjAnLUfbDfbsgMEuSumO7fIazHCI-7HQpaX5ONYagsu8LkBcj5itT12lPi5k_uNuirV4O68/s320/ATI_Catalyst_10.12_3.0.1-XorgLog.png" width="320" /></a></div>
<br />
<i><u>My note:</u></i> 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 <a href="http://www.walecha.net/content/ati-catalyst-linux-kernel-301?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+slackwall+%28Slackware+%7C+walecha+[at]+f0x%29">his blog</a>. I still don't know what the cause of my problem is.<br />
<br />
<i><u>Note:</u></i> for my other posts about ATI Catalyst, go to <a href="http://henryhermawan.blogspot.com/search/label/ati-radeon">this link</a>. You may need to read it.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com0tag:blogger.com,1999:blog-92487079588152729.post-81294252185475655272011-08-04T12:36:00.002+07:002011-08-04T14:54:44.530+07:00Disabling Nepomuk and AkonadiAfter 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.<br />
<br />
<u>Disabling Nepomuk</u><br />
I follow these steps to disable Nepomuk:<br />
<ul>
<li>Go to System Settings --> Workspace Appearance and Behavior --> Desktop Search</li>
<li>Untick "Enable Strigi Desktop File Indexer" and "Enable Nepomuk Semantic Desktop" under Basic Setting Tab</li>
<li>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</li>
<li>Select "Disable Automatic Backups" on Backup frequency under Backup Tab</li>
<li>Go to System Settings --> Common Appearance and Behavior --> Application and System Notifications --> Manage Notifications</li>
<li>Under Applications Tab, select "Desktop Search" on Event source and make sure all states are empty</li>
<li>Do the same for "Nepomuk file watch service" and "Semantic Desktop" on Event source</li>
<li>Quit System Settings </li>
</ul>
<br />
<u>Disabling Akonadi</u><br />
For disabling Akonadi, open the terminal then enter the directory <b style="font-weight: normal;"><span style="font-family: "Courier New",Courier,monospace;">~/.config/akonadi/akonadiserverrc</span> and set the value of "<span style="font-family: "Courier New",Courier,monospace;">StartServer</span>" on <span style="font-family: "Courier New",Courier,monospace;">[QMYSQL]</span> to <span style="font-family: "Courier New",Courier,monospace;">false</span>.</b><br />
<blockquote>
<div class="wp_syntax">
<div class="code">
<pre class="bash" style="font-family: monospace;">[QMYSQL]
...
StartServer=false</pre>
</div>
</div>
</blockquote>
<br />
After finishing all steps described above, restart the KDE. Nepomuk and Akonadi have been disabled.<br />
<br />
Note: I configure my System Settings to Classic Tree View (see picture below).<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDpEXt6F11Zb2JrVPDHlCLVK55A5nzf-_WJun4QgZvla8wzME_xnqFcr_Bfr3w7KoHQgO5Zo5XCBit53r84F6AOfjgdlPTRA02wdOvS9tVSBb0Q181kn7JFPjhpVHWE8tB6BfXfaBhKF8/s1600/nepomuk.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="173" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDpEXt6F11Zb2JrVPDHlCLVK55A5nzf-_WJun4QgZvla8wzME_xnqFcr_Bfr3w7KoHQgO5Zo5XCBit53r84F6AOfjgdlPTRA02wdOvS9tVSBb0Q181kn7JFPjhpVHWE8tB6BfXfaBhKF8/s320/nepomuk.png" width="320" /></a></div>
<br />Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com6tag:blogger.com,1999:blog-92487079588152729.post-20068339986313716332011-07-21T12:05:00.002+07:002011-07-21T12:20:03.958+07:00Oxygen KDE: A Firefox ThemeThis morning, I got information from Deddy through Google+ about <a href="http://kde-look.org/content/show.php/Oxygen+KDE+%28Firefox+Theme%29?content=117962">Oxygen KDE</a>. 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.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com1tag:blogger.com,1999:blog-92487079588152729.post-72493648603733109342011-07-19T12:41:00.000+07:002011-07-19T12:41:51.229+07:00kdeutils-4.6.5 for Slackware after patchingI have patched the source of kdeutils-4.6.5 since there are problems on KCalc (see <a href="https://bugs.kde.org/show_bug.cgi?id=277020">this link</a> and <a href="http://bugs.kde.org/show_bug.cgi?id=276568">this link</a>). You can download the slackbuild script, patches, and the source of kdeutils-4.6.5 from <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4YTZjMzhkNGEtNzM4MS00MzkxLWFjNzMtYzBiY2RlMzc0NjAy&hl=en_US">this link</a>. Before compiling yourself, make sure you have upgraded your KDE to KDE-4.6.5 using <a href="http://alien.slackbook.org/blog/kde-software-compilation-4-6-5/">Eric's packages</a>. Next, uncompress <span style="font-family: "Courier New",Courier,monospace;">kdeutils-4.6.5_SlackBuild.tar.gz</span> and run the <span style="font-family: "Courier New",Courier,monospace;">KDE.SlackBuild</span> as <span style="font-family: "Courier New",Courier,monospace;">root</span>. This slackbuild script will compile kdeutils-4.6.5 then upgrade your previous one. <br />
<br />
For Slackware64 users, you don't need to compile; just download the binary package from <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4ZDA4MDRlMTMtZjU3NS00YWMxLTk1NWQtOWQ3NDEyMTRhYTMz&hl=en_US">this link</a>, then do <span style="font-family: "Courier New",Courier,monospace;">upgradepkg</span>.<br />
<br />Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com0tag:blogger.com,1999:blog-92487079588152729.post-58433561117924829352011-06-13T14:27:00.011+07:002011-08-11T10:37:30.678+07:00ATI Catalyst Proprietary Display Driver & kernel-2.6.39.x<blockquote>
<i>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.</i></blockquote>
<br />
Again, we need to patch the source code of fglrx kernel module, part of ATI Catalyst (you will find it on <span style="font-family: "Courier New",Courier,monospace;">/lib/modules/fglrx</span> 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).<br />
<br />
<u>ATI Catalyst 11.x </u><br />
First, download 2 files: <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4ZjUyZmQyODktYTM2Yi00Mjg0LWIzMWItZTk5ZjY5YjcwMjZk&hl=en_US&authkey=CL3ew70E">2.6.39_bkl.patch</a> and <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4OGNhNzY2YWQtMjA2Ni00YzkzLWEzOTYtZDQ0YWEzOWU5Yjk2&hl=en_US&authkey=CKmhnMoO">no_bkl.patch</a> (Thank's to <a href="https://aur.archlinux.org/packages.php?ID=41040">https://aur.archlinux.org/packages.php?ID=41040</a> and <a href="http://www.mindwerks.net/2011/04/ubuntu-11-04-natty-with-fglrx-and-2-6-39">http://www.mindwerks.net/2011/04/ubuntu-11-04-natty-with-fglrx-and-2-6-39</a>). Copy those files to <span style="font-family: "Courier New",Courier,monospace;">/lib/modules/fglrx/build_mod</span> then run these commands:<br />
<div style="font-family: "Courier New",Courier,monospace;">
patch -p1 &lt; 2.6.39_bkl.patch</div>
<div style="font-family: "Courier New",Courier,monospace;">
patch -p1 &lt; no_bkl.patch</div>
Next step, execute <span style="font-family: "Courier New",Courier,monospace;">./make.sh</span> and if there is no error, change directory to <span style="font-family: "Courier New",Courier,monospace;">/lib/modules/fglrx</span> then execute <span style="font-family: "Courier New",Courier,monospace;">./make_install.sh</span><br />
<br />
<u>ATI Catalyst 10.10 - 10.12</u><br />
You have to download this patch: <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4OWZjMzAzMGMtYjQzZi00YTBkLTlhZDMtZWE1YjI2Njc0ZTc5&hl=en_US&authkey=CI6Mlr8E">fglrx_10.10-12_with_2.6.39.x.patch</a>. Copy this file to <span style="font-family: "Courier New",Courier,monospace;">/lib/modules/fglrx/build_mod</span> then execute:<br />
<span style="font-family: "Courier New",Courier,monospace;">patch -p1 &lt; fglrx_10.10-12_with_2.6.39.x.patch</span><br />
After that, execute <span style="font-family: "Courier New",Courier,monospace;">./make.sh</span> and if there is no error, change current working directory to <span style="font-family: "Courier New",Courier,monospace;">/lib/modules/fglrx</span> then execute <span style="font-family: "Courier New",Courier,monospace;">./make_install.sh</span><br />
<br />
Happy patching!<br />
<br />
<u><i>Note:</i></u> for my other posts about ATI Catalyst, go to <a href="http://henryhermawan.blogspot.com/search/label/ati-radeon">this link</a>. You may need to read it.<br />
<br />Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com2tag:blogger.com,1999:blog-92487079588152729.post-44390632310223745802011-04-30T02:30:00.006+07:002011-04-30T02:45:07.767+07:00Xilinx ISE WebPack on Slackware64<blockquote><i>(breaking news)</i> <a href="http://www.slackware.com/">Slackware64-13.37</a> has been released! Thank's to Pat, Eric, and other maintainers for making this version available.</blockquote><br />
For a long time, I have struggled with errors on the installation of <a href="http://www.xilinx.com/products/design-tools/ise-design-suite/">Xilinx ISE WebPack</a> 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 <a href="http://www.gpleda.org/">gEDA</a> and <a href="http://pcb.gpleda.org/index.html">pcb</a>. 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 <a href="http://www.xilinx.com/products/design-tools/ise-design-suite/">Xilinx ISE WebPack</a> on Slackware64. Thank's to <a href="http://www.philpem.me.uk/elec/fpga/ise12ubuntu/">Philip Pemberton that has written the solution on Ubuntu 64-bit version</a>.<br />
<br />
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 <a href="http://www.philpem.me.uk/elec/fpga/ise12ubuntu/">Philip's reference</a>, here is the step of installation:<br />
<ul><li>Download the <a href="http://www.xilinx.com/products/design-tools/ise-design-suite/">Xilinx ISE</a> (any latest Linux version or complete version) and extract the installer.</li>
<li>Enter the installer directory.</li>
<li>Install it with this command (must be root): <span style="font-family: "Courier New",Courier,monospace;">linux32 ./xsetup</span></li>
<li>Follow the instructions.</li>
<li>Enter the installation directory (if you don't change the default, it should be /opt/Xilinx/[ISE_version] </li>
<li>Create a script: startise.sh (if you use vim, just type: vim startise.sh)</li>
<li>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):<br />
<br />
<span style="font-family: "Courier New",Courier,monospace;">#!/bin/bash</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> source /opt/Xilinx/13.1/ISE_DS/settings32.sh /opt/Xilinx/13.1/ISE_DS/</span><br style="font-family: "Courier New",Courier,monospace;" /><span style="font-family: "Courier New",Courier,monospace;"> ise</span> <br />
<br />
</li>
<li>Don't forget to make it executable: <span style="font-family: "Courier New",Courier,monospace;">chmod +x startise.sh</span></li>
<li>Execute the script to start Xilinx ISE.</li>
</ul><br />
Here is the screenshot of Xilinx ISE on Slackware64 inside my laptop: <br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgML5ITs28o7J5dG-EA5kNEhu37croRCP-nf4DskkQwRyVzp2948NL2Rw_70f5cj5dSHyqt6dNtGdM0nt5gorJLkphhnHmNgieFPaUpBATI0w4NXf7SyHTmHtQ2SUV9B1yu7KlqNSabJ5I/s1600/Xilinx_ISE.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="223" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgML5ITs28o7J5dG-EA5kNEhu37croRCP-nf4DskkQwRyVzp2948NL2Rw_70f5cj5dSHyqt6dNtGdM0nt5gorJLkphhnHmNgieFPaUpBATI0w4NXf7SyHTmHtQ2SUV9B1yu7KlqNSabJ5I/s400/Xilinx_ISE.png" width="400" /></a></div><br />
<br />
<br />
<ul></ul>Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com2tag:blogger.com,1999:blog-92487079588152729.post-37804402980312777022011-04-21T03:34:00.004+07:002011-04-21T11:00:30.688+07:00myPhone @ES6192<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjSywhgKJ8WBcmUqAcPbCO8tpfahB4WIZAYTHF_dwZlTvy7LXbsQGchogcWSr2bsXc5OhTjnGNCYY_5Hg6YLHESSaYJWGG0BwTF3yDyV7ODCXzcpwSJefGZANk2mZroLFdTPePVDLhB84I/s1600/IMAG0076.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="241" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjSywhgKJ8WBcmUqAcPbCO8tpfahB4WIZAYTHF_dwZlTvy7LXbsQGchogcWSr2bsXc5OhTjnGNCYY_5Hg6YLHESSaYJWGG0BwTF3yDyV7ODCXzcpwSJefGZANk2mZroLFdTPePVDLhB84I/s320/IMAG0076.jpg" width="320" /> </a></div><div class="separator" style="clear: both; text-align: center;"><br />
</div><div align="JUSTIFY" style="font-family: inherit; margin-bottom: 0cm;">"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.<span style="font-size: small;"> We had to develop device drivers and application software that could be performed on ARM-based Embedded System with Linux as its operating system.</span></div><div align="JUSTIFY" style="font-family: inherit; margin-bottom: 0cm;"><br />
</div><div align="JUSTIFY" style="font-family: inherit; margin-bottom: 0cm;"><span style="font-size: small;">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.</span></div><div align="JUSTIFY" style="font-family: inherit; margin-bottom: 0cm;"><br />
</div><div align="JUSTIFY" style="font-family: inherit; margin-bottom: 0cm;"><span style="font-size: small;">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. </span></div><div class="separator" style="clear: both; text-align: left;"><span style="font-size: small;"><span style="font-family: inherit;"> </span></span></div><div align="JUSTIFY" style="font-family: inherit; margin-bottom: 0cm;"><span style="font-size: small;"><br />
</span> </div><span style="font-size: small;"><span style="font-family: inherit;"> </span></span><br />
<div align="JUSTIFY" style="font-family: inherit; margin-bottom: 0cm;"><span style="font-size: small;">Modes on “myPhone @ES6192”:</span></div><span style="font-size: small;"><span style="font-family: inherit;"> </span></span><br />
<ul style="font-family: inherit;"><li><div align="JUSTIFY" style="margin-bottom: 0cm;"><span style="font-size: small;">display clock mode or cancel key on phone dialer and off-hook mode by pressing “C” key</span></div></li>
<li><div align="JUSTIFY" style="margin-bottom: 0cm;"><span style="font-size: small;">adjust clock mode by pressing “D” key</span></div></li>
<li><div align="JUSTIFY" style="margin-bottom: 0cm;"><span style="font-size: small;">phone dialer mode by pressing “E” key</span></div></li>
<li><div align="JUSTIFY" style="margin-bottom: 0cm;"><span style="font-size: small;">off-/on-hook by pressing “F” key (toggled)</span></div></li>
<li><div align="JUSTIFY" style="margin-bottom: 0cm;"><span style="font-size: small;">backspace key on adjust clock and phone dialer mode by pressing “A” key</span></div></li>
</ul><span style="font-size: small;"><span style="font-family: inherit;"> </span></span> <br />
<div style="font-family: inherit;"><span style="font-size: small;">Structure of "myPhone @ES6192":</span></div><div class="separator" style="clear: both; text-align: center;"></div><div style="font-family: inherit;"><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijL3kI8nkcjUQqXtArPPXmrOwNQDSEfVD_eiOeRjwq8VxIlhBK-dZkjvluGu-50S_l36N46kMGu6oK7LhpLeok4MM8KzDBoRfGVQ-p48SZpuFKbLMkmwRhorAEnL5dXLARjxwDqrK2HJw/s1600/myPhone.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="204" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijL3kI8nkcjUQqXtArPPXmrOwNQDSEfVD_eiOeRjwq8VxIlhBK-dZkjvluGu-50S_l36N46kMGu6oK7LhpLeok4MM8KzDBoRfGVQ-p48SZpuFKbLMkmwRhorAEnL5dXLARjxwDqrK2HJw/s320/myPhone.png" width="320" /></a></div><span style="font-size: small;"><br />
</span></div><div style="font-family: inherit;"><span style="font-size: small;"><br />
</span></div>Video demo:<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><iframe allowfullscreen='allowfullscreen' webkitallowfullscreen='webkitallowfullscreen' mozallowfullscreen='mozallowfullscreen' width='320' height='266' src='https://www.youtube.com/embed/SciYRQBvnH0?feature=player_embedded' frameborder='0'></iframe></div>Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com1tag:blogger.com,1999:blog-92487079588152729.post-31218317433617687912011-03-25T00:07:00.004+07:002011-03-25T00:29:02.532+07:00How to make touchpad/clickpad temporarily disable when typing?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:<br />
<br />
<b>Method 1</b>, I disable my clickpad permanently. I run this script to toggle on/off my clickpad:<br />
<blockquote><div style="font-family: "Courier New",Courier,monospace;"><span style="font-size: x-small;">#!/bin/bash<br />
#Toggle touchpad<br />
SYNSTATE=$(synclient -l | grep TouchpadOff | awk '{ print $3}')<br />
# change state<br />
if [ $SYNSTATE = 0 ]; then<br />
synclient touchpadoff=1<br />
elif [ $SYNSTATE = 1 ]; then<br />
synclient touchpadoff=0<br />
fi</span></div></blockquote><br />
<b>Method 2</b>, I use <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">/usr/bin/syndaemon</span></span> to disable my clickpad <u><b>only</b></u> when I am typing. The steps:<br />
<ol><li>Make <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">~/.xprofile</span></span><br />
<blockquote><span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">#!/bin/sh</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;"># Customize X environment</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">#</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;"># Activate syndaemon for monitoring keyboard activity and disabling # the touchpad when the keyboard is being used.</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">/usr/bin/syndaemon -td</span></span></blockquote></li>
<li>Add these lines on the top of <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">/usr/bin/startkde</span></span> (if you use KDE as the default desktop manager) in order to make X server executes <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">~/.xprofile</span></span> when it starts.<br />
<blockquote><span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">if [ -r /etc/xprofile ]; then</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;"> source /etc/xprofile</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">fi</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">if [ -r $HOME/.xprofile ]; then</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;"> source $HOME/.xprofile</span></span><br />
<span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">fi</span></span></blockquote></li>
<li>Restart X server.</li>
</ol>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 <span style="font-family: Arial,Helvetica,sans-serif; font-size: small;">syndaemon</span>, type: <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">man syndaemon</span></span> on your console.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com1tag:blogger.com,1999:blog-92487079588152729.post-11507142213766361762011-03-24T23:33:00.000+07:002011-03-24T23:33:51.372+07:00Synaptics-1.4.0 patch for activating right-click function on clickpadLast month, I have written about <a href="http://henryhermawan.blogspot.com/2011/02/how-to-activate-right-click-on-clickpad.html">how to activate right-click function on clickpad by patching synaptics-1.3.0</a>. 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 <a href="https://patchwork.kernel.org/patch/93837/">patch for synaptics-1.3.0</a> with a few changes. For the modified patch, you can download it from <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4Zjk3M2E0YjAtYjZiYy00MmYxLWIxMGEtMDA4ZGMyM2EzMzI4&hl=en&authkey=COqmhZkH">here</a> (gzip compressed). You can follow the instructions from <a href="http://henryhermawan.blogspot.com/2011/02/how-to-activate-right-click-on-clickpad.html">my last note</a>; just change the step 3 with this: copy <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4NzYyOTU1ZGUtNzkxMy00OWEzLThmYWUtZTMzZTk4NWM4YWIz&hl=en&authkey=CMCBrf4G">this file</a> to <i>path-to</i>/x11/patch/ (in my case, copy it to <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">/home/henry/rsync/x11/patch/</span></span>). The rest will be same. I also put <a href="https://docs.google.com/leaf?id=0B4VfWnVnFzi4ZTRlYWY1NDAtNTY4Ny00NGNmLWI1N2QtYmVlMDdiNTc0ZWI0&hl=en&authkey=CN_J6agG">my clickpad.conf on google docs</a> so that you can download it and place it in /etc/X11/xorg.conf.d/ then restart the X server.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com12tag:blogger.com,1999:blog-92487079588152729.post-30616465210613426112011-03-22T16:10:00.001+07:002011-03-22T16:15:24.573+07:00ATI Catalyst Proprietary Display Driver 10.12 & kernel-2.6.38If 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 <b>fglrx</b> kernel module. You need to patch ATI Catalyst kernel module before you compile it manually. Here is the patch:<br />
<br />
<div style="font-family: "Courier New",Courier,monospace;"><span style="font-size: x-small;">--- ./firegl_public.c 2010-12-02 22:28:43.000000000 +0100<br />
+++ ./firegl_public.c.new 2011-01-09 17:40:22.000000000 +0100<br />
@@ -320,7 +320,7 @@<br />
return firegl_release((KCL_IO_FILE_Handle)filp);<br />
}<br />
<br />
-int ip_firegl_ioctl(struct inode* inode, struct file* filp, unsigned int cmd, unsigned long arg)<br />
+int ip_firegl_ioctl(struct file* filp, unsigned int cmd, unsigned long arg)<br />
{<br />
return firegl_ioctl((KCL_IO_FILE_Handle)filp, cmd, arg);<br />
}<br />
@@ -407,7 +407,7 @@<br />
#endif<br />
open: ip_firegl_open,<br />
release: ip_firegl_release,<br />
- ioctl: ip_firegl_ioctl,<br />
+ unlocked_ioctl: ip_firegl_ioctl,<br />
mmap: ip_firegl_mmap,<br />
<br />
write: ip_firegl_write,<br />
@@ -840,7 +840,12 @@ static int fglrx_pci_suspend(struct pci_<br />
* happen much less frequent then without this workaround.<br />
*/<br />
if (state == PM_EVENT_SUSPEND)<br />
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)<br />
+ console_lock();<br />
+#else<br />
acquire_console_sem();<br />
+#endif<br />
+<br />
<br />
if (firegl_cail_powerdown(privdev, state))<br />
ret = -EIO;<br />
@@ -862,7 +867,11 @@ static int fglrx_pci_suspend(struct pci_<br />
}<br />
<br />
if (state == PM_EVENT_SUSPEND)<br />
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)<br />
+ console_unlock();<br />
+#else<br />
release_console_sem();<br />
+#endif<br />
<br />
KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, ret, NULL); <br />
<br />
@@ -886,7 +895,11 @@ static int fglrx_pci_resume(struct pci_d<br />
if (PMSG_EVENT(pdev->dev.power.power_state) == 0) return 0;<br />
<br />
if (PMSG_EVENT(pdev->dev.power.power_state) == PM_EVENT_SUSPEND)<br />
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)<br />
+ console_lock();<br />
+#else<br />
acquire_console_sem();<br />
+#endif<br />
<br />
#ifdef FIREGL_USWC_SUPPORT<br />
// Restore the PAT after resuming from S3 or S4.<br />
@@ -911,7 +924,11 @@ static int fglrx_pci_resume(struct pci_d<br />
firegl_cail_powerup(privdev);<br />
<br />
if (PMSG_EVENT(pdev->dev.power.power_state) == PM_EVENT_SUSPEND)<br />
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,38)<br />
+ console_unlock();<br />
+#else<br />
release_console_sem();<br />
+#endif<br />
<br />
PMSG_EVENT(pdev->dev.power.power_state) = 0;<br />
KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, 0, NULL); <br />
<br />
@@ -5107,7 +5107,7 @@<br />
unsigned int ATI_API_CALL KAS_Mutex_Initialize(void* hMutex)<br />
{<br />
kasMutex_t* mutex_obj = (kasMutex_t*)hMutex;<br />
- init_MUTEX(&(mutex_obj->mutex));<br />
+ sema_init(&(mutex_obj->mutex),1);<br />
return 1;<br />
}<br />
<br />
--- ./kcl_ioctl.c 2010-12-02 22:28:43.000000000 +0100<br />
+++ ./kcl_ioctl.c.new 2011-01-09 17:40:22.000000000 +0100<br />
@@ -193,7 +193,7 @@<br />
*/<br />
void* ATI_API_CALL KCL_IOCTL_AllocUserSpace32(long size)<br />
{<br />
- void __user *ret = COMPAT_ALLOC_USER_SPACE(size);<br />
+ void __user *ret = arch_compat_alloc_user_space(size);<br />
<br />
/* prevent stack overflow */<br />
if (!access_ok(VERIFY_WRITE, ret, size))</span></div><br />
Save this patch to file and follow the instructions that I have written on <a href="http://henryhermawan.blogspot.com/2011/02/problem-when-using-ati-catalyst.html">http://henryhermawan.blogspot.com/2011/02/problem-when-using-ati-catalyst.html</a>.<br />
<br />
<b>Reference:</b> <a href="http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/3b716dfe326fef23?pli=1">http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/3b716dfe326fef23?pli=1</a>Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com0tag:blogger.com,1999:blog-92487079588152729.post-17337521715207081312011-03-12T20:52:00.003+07:002011-03-12T23:54:07.461+07:00dmesg: operation not permitted as user<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPArY0opaZuf3Paq0XyLNGps1WxuYBwBzw8NfrhYQydm7wzCWGl8JdFr-SGfHQgQp0oc-fErHh3XVBLJ4L-vGA59_Sb79RNkLKMn25JFMS2H2t2NYvNjs8bXpAHTLxjr4aGGyLFT2BmFI/s1600/dmesg_access-1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPArY0opaZuf3Paq0XyLNGps1WxuYBwBzw8NfrhYQydm7wzCWGl8JdFr-SGfHQgQp0oc-fErHh3XVBLJ4L-vGA59_Sb79RNkLKMn25JFMS2H2t2NYvNjs8bXpAHTLxjr4aGGyLFT2BmFI/s1600/dmesg_access-1.png" /></a></div><br />
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).<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU9VcDhJtXOnO6OIQwfFlMW0qLRi5YmCUj9IRBVGd_vAT48pPfb9jMh-9CfXKrrW_aldpfU6j6muIhgEQHm8qMHDHrwopGbZNS68p1AaXjdi7BZrvo21Il2f-bV1FFOtmLDoI4n5pLCgo/s1600/dmesg_access-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="57" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU9VcDhJtXOnO6OIQwfFlMW0qLRi5YmCUj9IRBVGd_vAT48pPfb9jMh-9CfXKrrW_aldpfU6j6muIhgEQHm8qMHDHrwopGbZNS68p1AaXjdi7BZrvo21Il2f-bV1FFOtmLDoI4n5pLCgo/s320/dmesg_access-2.png" width="320" /></a></div><br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjZx6nUx2CFjCA0qhH7ikIBZQmwPAmPvoaZ28U16cbY3HriRlIGSjzMWpHuEWiUKpfN2d5KRWB8kAOv9xnIUzrjGeo7sD7MhByTaJ65YmOROZeRNA77t7HljU62JYRnwOWbsIuuZXAGY50/s1600/dmesg_access-3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="144" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjZx6nUx2CFjCA0qhH7ikIBZQmwPAmPvoaZ28U16cbY3HriRlIGSjzMWpHuEWiUKpfN2d5KRWB8kAOv9xnIUzrjGeo7sD7MhByTaJ65YmOROZeRNA77t7HljU62JYRnwOWbsIuuZXAGY50/s320/dmesg_access-3.png" width="320" /></a></div><br />
There are 2 solutions, you are freely to choose one of them.<br />
<br />
<u>Solution 1:</u> add these lines on your rc.local:<br />
<div style="font-family: "Courier New",Courier,monospace;"><span style="font-size: x-small;">if [ -r /proc/sys/kernel/dmesg_restrict ]; then<br />
if [ $(cat /proc/sys/kernel/dmesg_restrict) = 1 ]; then<br />
echo 0 > /proc/sys/kernel/dmesg_restrict<br />
fi<br />
fi</span></div><br />
<u>Solution 2:</u> change the correspond kernel setting (<b>restrict unprivileged access to the kernel syslog</b>) to "N" then recompile the kernel.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com2tag:blogger.com,1999:blog-92487079588152729.post-15073497109353262062011-02-27T01:58:00.000+07:002011-02-27T01:58:02.121+07:00Bigger buffer log (dmesg) sizeSomeone 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:<br />
<ol><li>Pass the parameter of <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">log_buf_len=n</span></span> to kernel, where <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">n</span></span> is a power of two number (n = 2^x). The default for slackware is 2^15 or 32768 (32k). You can change <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">n</span></span> to 65536 (2^16) or 131072 (2^17). In this way, you don't need to recompile your current kernel.</li>
<li>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 <span style="font-size: x-small;"><span style="font-family: "Courier New",Courier,monospace;">/boot</span></span> directory and set up your bootloader (lilo/grub) properly.</li>
</ol><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilZuSMy9EyERehCzNiebyypczo4mR2HzOjRv7ggzQQVRvQ0N2a5Xsh3840KqggwyefZwgXdCuQ6I7rg7OyLhMu2zSWK8mcihNFIlrU9rTtFwZywCTaOSLAFU2snz5L-G4NFatTm8NVNFw/s1600/log_buf_dmesg.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="34" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilZuSMy9EyERehCzNiebyypczo4mR2HzOjRv7ggzQQVRvQ0N2a5Xsh3840KqggwyefZwgXdCuQ6I7rg7OyLhMu2zSWK8mcihNFIlrU9rTtFwZywCTaOSLAFU2snz5L-G4NFatTm8NVNFw/s320/log_buf_dmesg.png" width="320" /></a></div><br />
<br />
Choose one of them then you will get full dmesg output on your screen. It will be very long message log.Anonymoushttp://www.blogger.com/profile/06722395114968657299noreply@blogger.com0