This how to probably will only work for ‘ET&T Technology TC4UM with device  ID 0664:0306 on Clevo TN120R running Ubuntu Hardy/Intrepid/Jaunty/Karmic.

• STEP 1: Download the driver from Magictouch website
• STEP 2: Copy Modules and other files

Extract the driver from magictouch website (Linux_USB_V2.20_ub904_090430[i386].tar.gz) and you will find these objects:

drwxr-xr-x 4 dedieko dedieko 4096 2009-04-29 10:19 .
drwxr-xr-x 3 dedieko dedieko 4096 2009-11-26 10:35 ..
drwx—— 2 dedieko dedieko 4096 2009-11-26 07:16 driver
-rwxrwxrwx 1 dedieko dedieko 4116 2009-04-28 14:18 install_Ubuntu9.04
-rwxrwxrwx 1 dedieko dedieko 2085 2009-04-28 14:28 uninstall_Ubuntu9.04
drwx—— 2 dedieko dedieko 4096 2009-11-26 07:16 utility

Instead of running Install_Ubuntu9.04, I wanted to know how things work, so we go with the manual way.
Go to driver folder and you will find 1 file:

-rwxr-xr-x 1 dedieko dedieko 75285 2009-04-29 10:05 etouch_drv.so

Copy this file to /usr/lib/xorg/modules/input
Go to utility folder and youwill find 3 files:

-rwxr-xr-x 1 dedieko dedieko 31706 2009-04-29 09:12 Calibration
-rwxr-xr-x 1 dedieko dedieko 14829 2008-12-10 14:33 Lift-off
-rwxr-xr-x 1 dedieko dedieko 29058 2009-04-28 15:57 Swap

Copy these files to /etc/etandt folder. Don’t forget to change the file ownership. Safest bet is to chmod 777

• STEP 3: Configure xorg.conf

If you use freshly installed Karmic, there is no xorg.conf, you could run this command to generate default Xorg.conf:

sudo dpkg-reconfigure -phigh xserver-xorg

Then edit the newly generated xorg.conf. Add ServerLayout Section and InputDevice Section
The hardest thing is probably to pinpoint the device location. Type this:

lshal | grep hiddev

Mine is look like this:

dedieko@dedieko-laptop:~$ lshal | grep hiddev
udi = ‘/org/freedesktop/Hal/devices/usb_device_664_306_noserial_if0_hiddev’
  hiddev.application_pages = {‘Unknown page 0xd0004′} (string list)
  hiddev.device = ‘/dev/usb/hiddev0‘  (string)
  hiddev.product = ‘ET&T Technology TC4UM’  (string)
  info.capabilities = {‘hiddev’} (string list)
  info.category = ‘hiddev’  (string)
  info.udi = ‘/org/freedesktop/Hal/devices/usb_device_664_306_noserial_if0_hiddev’  (string)
  linux.device_file = ‘/dev/usb/hiddev0′  (string)
  linux.sysfs_path = ‘/sys/devices/pci0000:00/0000:00:1d.2/usb7/7-1/7-1:1.0/usb/hiddev0′  (string)
dedieko@dedieko-laptop:~$

Pay attention to the red line, now write that or memorize it, then put it in the Xorg.conf below.
Mine is look like this:

Section “Monitor”
    Identifier    “Configured Monitor”
EndSection

Section “Screen”
    Identifier    “Default Screen”
    Monitor        “Configured Monitor”
    Device        “Configured Video Device”
    SubSection “Display”
        #Virtual    2560 1024
        Virtual    4096 4096
    EndSubSection
EndSection

Section “Device”
    Identifier    “Configured Video Device”
    Option “AccelMethod” “UXA”
    #Option “MigrationHeuristic” “Greedy”
EndSection

Section “ServerFlags”
    Option    “DontZap”    “False”
EndSection

Section “InputDevice”
    Identifier “ETouch”
    Driver “ETouch”
    Option “Device” “/dev/usb/hiddev0″
EndSection

Section “ServerLayout”
    Identifier “Layout01″
    InputDevice “ETouch” “SendCoreEvents”
EndSection

 sudo reboot -n

or simply by pressing

Ctrl+Alt+Del

When you got things right, your GUI will load, you touch screen will function, BUT… still not calibrated

• STEP 4: Calibration

sudo /etc/etandt/Calibration

If you dont use sudo, you will get Segmentation Fault
You’ll see white screen with small crossed circle. Press the center of it as precise as possible. You can cancel anytime by pressing Ctrl+C

You’re done.

References:
http://ubuntuforums.org/showthread.php?t=677833
http://magictouch.com/support_usb_xd.html
http://www.qbik.ch/usb/devices/showdescr.php?id=4460
http://forum.ubuntu-fr.org/viewtopic.php?pid=3073235 (in French)
http://widi-atmono.blogspot.com/2009/11/install-driver-touch-screen-m912m-di.html

After upgrading to Jaunty, in Compiz sometimes I get a lot of Gnome-Panel Freezes, hovering the mouse cursor over it won’t trigger any response.

This freezes usually triggered by pressing Alt-F2.

So, the gnome-panel has to be restarted with this command:

killall gnome-panel

nohup gnome-panel –replace &

References:

http://mylinuxnotebook.blogspot.com/2008/09/restart-gnome-panel.html

it’s been some times that everytime I did apt-get to install some stuff, I always found this line somewhere in the console output:

Processing triggers for menu …
/usr/share/menu/cairo-dock: 1: Syntax error: word unexpected (expecting “)”)
Execution of /usr/share/menu/cairo-dock generated no output or returned an error.

But, strangely, the cairo dock itself is running just fine, in my desktop
Kinda annoying though….

Finally, after some googling and trial-error, this is the latest setting:

[Dialer im3]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = AT+CGDCONT=1,”IP”,”indosatgprs”
Modem Type = USB Modem
ISDN = 0
New PPPD = yes
Phone = *99***1#
Modem = /dev/ttyUSB0
Username = gprs
Password = im3
Baud = 460800
Auto Reconnect = On
Stupid Mode = 1

Technorati Tags: ubuntu, usbmodem, wvdial

My Email Server is down….

I’ve been digging and foraging for infos about this one. The author of this ipcop great plugin, stated in the FAQ that it is possible to add custom rules for Update Accelerator, but can’t seem to find the guide anywhere.

Here are my findings so far :

Simply edit this file in your IPCOP box:

/usr/sbin/updxlrator

and you will find these lines :

while (<>) {

    $request=$_;

    @tmp=split(/ /,$request);
    chomp(@tmp);

    $source_url = $tmp[0];
    $hostaddr   = $tmp[1]; while ($hostaddr =~ /.*\/$/) { chop $hostaddr; }
    $username   = $tmp[2]; if ($username eq ”) { $username=’-'; };
    $method     = $tmp[3];

    $xlrator_url = $source_url;

    if (($method eq ‘GET’) || ($method eq ‘HEAD’))
    {

    # ———————————————————–
    #  Section: Windows Update / Windows Downloads
    # ———————————————————–

    if (
        (($source_url =~ m@^http://[^/]*\.microsoft\.com/.*\.(exe|psf|msi|msp|cab)$@i) ||
         ($source_url =~ m@^http://[^/]*\.windowsupdate\.com/.*\.(exe|psf|msi|msp|cab)$@i))
    &&   ($source_url !~ m@^http://[^/]*\.microsoft\.com/.*(/autoupd|selfupdate/).*\.cab@i)
    &&   ($source_url !~ m@\&@)
       )
    {
        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”Microsoft”,$unique);
    }

    # ———————————————————–
    #  Section: Adobe Downloads
    # ———————————————————–

    if (
        ($source_url =~ m@^http://(ar)?download\.adobe\.com/.*\.(exe|msi|bin|dmg|idx|gz)$@i) ||
        ($source_url =~ m@^http://swupdl\.adobe\.com/updates/.*\.(exe|msi|bin|dmg|idx|gz|[a-z][a-z]_[A-Z][A-Z])$@i) ||
        ($source_url =~ m@^http://swupmf\.adobe\.com/manifest/.*\.upd$@i)
       )
    {
        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”Adobe”,$unique);
    }

    # ———————————————————–
    #  Section: Linux Downloads
    # ———————————————————–

    if ($source_url =~ m@^[h|f]t?tp://[^?]+\.(deb|rpm)$@i)
    {
        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”Linux”,$mirror);
    }

    # ———————————————————–
    #  Section: Trend Micro Downloads
    # ———————————————————–

    if (
        ($source_url =~ m@^http://[^/]*\.trendmicro\.com/activeupdate/.*@i) &&
        ($source_url !~ m@.*/tmnotify\.dat$@i) &&
        ($source_url !~ m@.*/ini_xml\.zip$@i) &&
        ($source_url !~ m@.*/server\.ini$@i)
       )
    {
        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”TrendMicro”,$mirror);
    }

    # ———————————————————–
    #  Section: Symantec Downloads
    # ———————————————————–

    if ($source_url =~ m@^[h|f]tt?p://[^/]*\.symantec(liveupdate)?\.com/.*\.(exe|zip|vdb|xdb)$@i)
    {
        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”Symantec”,$unique);
    }

    # ———————————————————–
    #  Section: Apple Downloads
    # ———————————————————–

    if (
        (($source_url =~ m@^http://swcdn\.apple\.com/content/downloads/.*\.(tar)$@i) ||
         ($source_url =~ m@^http://appldnld\.apple\.com\.edgesuite\.net/.*\.(exe|dmg)$@i) ||
         ($source_url =~ m@^http://.*\.g.akamai.net/.*/3093/1/.*\.(tar|pkg|dmg|exe)$@i))
       )
    {
        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”Apple”,$unique);
    }

    # ———————————————————–
    #  Section: Avast Downloads
    # ———————————————————–

    if ($source_url =~ m@^http://download[\d]+\.avast\.com/.*\.(exe|vpu)$@i)
    {
        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”Avast”,$mirror);
    }
   

    # ———————————————————–

    }

Simply add these lines, just below the Avast section:

    # ———————————————————–

    #  Section: NOD Downloads

    # ———————————————————–

    if ($source_url =~ m@^[h|f]t?tp://[^?]+\.(nup|ver|)$@i)

    {

        $xlrator_url = &check_cache($source_url,$hostaddr,$username,”Other”,$mirror);

    }

I’m using the Linux section as the template, which is the easiest template compare to others. What do those line mean?

$source_url =~ m@^[h|f]t?tp://[^?]+\.(nup|ver|)$@i)

translate: UA should cache  nup and ver files…

$source_url =~ m@^[h|f]t?tp://[^?]+\.(nup|ver|)$@i)

translate: and the URLS could be anywhere…

$source_url =~ m@^[h|f]t?tp://[^?]+\.(nup|ver|)$@i)

translate: and it doesn’t matter whether it is http or ftp…

Pay attention to this:

$xlrator_url = &check_cache($source_url,$hostaddr,$username,”Other“,$mirror);

It’s vendorid flag, which indicated that these NUP and VER files should use Other flag in the UA web interface. If you want to mess around and add your own image/category, edit this file

/home/httpd/cgi-bin/updatexlrator.cgi

find these line :

print “\t\t ”;
            if ($vendorid =~ /^Adobe$/i)
            {
                print “ \n”;
            } elsif ($vendorid =~ /^Microsoft$/i)
            {
                print “ \n”;
            } elsif ($vendorid =~ /^Symantec$/i)
            {
                print “ \n”;
            } elsif ($vendorid =~ /^Linux$/i)
            {
                print “ \n”;
            } elsif ($vendorid =~ /^TrendMicro$/i)
            {
                print “ \n”;
            } elsif ($vendorid =~ /^Apple$/i)
            {
                print “ \n”;
            } elsif ($vendorid =~ /^Avast$/i)
            {
                print “ \n”;
            } else
            {
                if (-e “/home/httpd/html/images/updxl-src-” . $vendorid . “.gif”)
                {
                    print “ \n”;
                } else {
                    print “ \n”;
                }
            }

Maybe there are other files or lines that should be edited as well, I don’t know yet.
Technorati Tags: ipcop, update accelerator mod

Recently, I had to upgrade my hard disk from 120GB to 250GB, with the help of Gparted Live CD. As it turns out, that my new hard drive can’t boot from my laptop and give me this horror message:

So, with the help of “grub-install” tool, this is what I did:

1. Boot you system with any Ubuntu CD. In my case, I’m using Ubuntu 8.10 LiveCD.

2. Determine your hard disk device name. In my system, it’s /dev/sda

3. Determine your current boot type. In my system, my boot block is in MBR

4. Execute “grub-install” with the following syntax:

grub-install [OPTION] device name

in my system it would be like this:

sudo grub-install –recheck /dev/sda

Then reboot

Oh, forgot to mention, Week 39 and Week 40 are excluded, since we have
different modem and connection mode. Starting at week 41, I used Bridge
Mode in my ADSL modem, and a change from DHCP mode to PPPoE mode in pfSense’s WAN.

Hmmmm, what is this? Let’s bring the bandwidth usage, see if anything similar occur here:

It seem that the correlation is (almost) linear, the higher the bandwidth usage, the data rush definetely hammered the network ping replies

Let see the packet graph:

Yes, we did see the same correlation. The higher the packet count per second, the higher the ping result

CONCLUSION: There is a linear correlation between pfSense Network Quality , Bandwidth Usage and Packet Count.

I hope this result will bring some lights to my customers of how their ISP is doing.

Cheers.

This is just a routine check of speed.

Today, I received an email from My-Olympus mailing list, regarding a member with hot pixel problem in her Olympus E-500. Suddenly this topic began to interest me, since I also owned E-500 second hand.

Basicly, what is Hot Pixel really?

Wikipedia give me this :

Hot pixels are sensors on the CCD with higher than normal charge leakage. On long exposure, they can appear as bright pixels.

Sensors on the CCD that always appears as brighter pixels are called stuck pixels while sensors that only brighten up after long exposure are called hot pixels.

A very good source about hot pixel & how to see/reproduce them can be located here :
http://webpages.charter.net/bbiggers/DCExperiments/html/hot_pixel_facts.html
http://webpages.charter.net/bbiggers/DCExperiments/html/hot_pixels.html

Points taken.

Example of Hot Pixel :

From Olympus website:

In short, even a brand new digital camera will definitely suffers hot pixels, and they will develop hot pixel along the lifetime of the camera.

What Olympus has to say about this issue? (well, I owned Olympus, that’s the first thing I want to hear):

http://www.olympusamerica.com/crm/oneoffpages/crm_pixelmapping.asp

The more pixels your camera’s imaging sensor (CCD) is made of, the more likely some of them may fail. Think of the lights on a Christmas tree.When the string is smaller, the lights usually fire without incident. But the longer the set of lights, the higher the probability one or more individual lights will need repair. These “stuck,” “dead,” or “hot” pixels, as they are often called, can cause the quality of your images to be compromised. Nearly every digital camera, regardless of the manufacturer, includes a sensor that experiences this to some degree. The issue may not be severe enough to be noticed, but if you do notice this phenomenon to occur, look into Pixel Mapping.

Wait, what’s that? Pixel Mapping, sounds familiar, Aha, I’ve seen it on my E-500 menu, but I never used it, ’cause I don’t know what it is for (silly me).
Let’s carry on:

Oke, I’m on it. Luckily, My E-500 has this feature. But my old Kodax DX-6340 and Sony HCR-90 don’t seem to own this. Sigh, It’s okay, I’m cool