depends what you define as multitouch, I guess.

please attach the evtest output from the device file and your Xorg.log file, that should get us started.

Created attachment 35747 [details]
X.org log

> depends what you define as multitouch, I guess.
Support handling more than touching of one finger. Two fingers scroll for example.

> please attach the evtest output from the device file
# evtest /dev/input/event11
Input driver version is 1.0.0
Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1
Input device name: "SynPS/2 Synaptics TouchPad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 274 (MiddleBtn)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value      1
      Min     1472
      Max     5472
    Event code 1 (Y)
      Value   5855
      Min     1408
      Max     4448
    Event code 24 (Pressure)
      Value      0
      Min        0
      Max      255
    Event code 28 (Tool Width)
      Value      0
      Min        0
      Max        0

> and your Xorg.log file, that should get us started.
Attached.

> > please attach the evtest output from the device file
> # evtest /dev/input/event11
> Input driver version is 1.0.0
> Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1
> Input device name: "SynPS/2 Synaptics TouchPad"
> Supported events:
>   Event type 0 (Sync)
>   Event type 1 (Key)
>     Event code 272 (LeftBtn)
>     Event code 273 (RightBtn)
>     Event code 274 (MiddleBtn)
>     Event code 325 (ToolFinger)
>     Event code 330 (Touch)

sorry, your touchpad doesn't support multi-touch. there should be a Tool
Doubletap and Tool Tripletap for two or three fingers respectively in this
list.

Now, if the hardware claims that multi-touch is supported then this is a
kernel driver issue that needs to be resolved first.

Yes, it's driver issue, because multi-touch work in Windows with original driver.

What information I can provide to help solve this driver issue?

please file a kernel bug for this, it's not something we can solve in the Xorg stack.