Touchpad Vertical Scrolling does not work

**pi/roman** · January 10th, 2011

This is interesting here:

Originally Posted by WthIteh

Synaptics Capabilities (282): 0, 0, 0, 0, 0

Then from the synaptics manual:

Synaptics Capabilities
This read-only property expresses the physical capability of the touchpad, most
notably whether the touchpad hardware supports multi-finger tapping and scrolling.

8 bit (BOOL), 5 values (read-only), has left button, has middle button, has right
button, two-finger detection, three-finger detection.

My touchpad has every capabilty except the middle button. This is a read only property so that would mean that the kernel has to apply it.
also

NOTES
If either of Protocol "auto-dev" (default) or Protocol "event" is used, the driver initial‐
izes defaults based on the capabilities reported by the kernel driver. Acceleration, edges
and resolution are based on the dimensions reported by the kernel. If the kernel reports
multi-finger detection, two-finger vertical scrolling is enabled, horizontal two-finger
scrolling is disabled and edge scrolling is disabled. If no multi-finger capabilities are
reported, edge scrolling is enabled for both horizontal and vertical scrolling. Tapping is
disabled by default for touchpads with one or more physical buttons. To enable it you need
to map tap actions to buttons. See the "TapButton1", "TapButton2" and "TapButton3" options.

Button mapping for physical buttons is handled in the server. If the device is switched to
left-handed (an in-server mapping of physical buttons 1, 2, 3 to the logical buttons 3, 2,
1, respectively), both physical and TapButtons are affected. To counteract this, the TapBut‐
tons need to be set up in reverse order (TapButton1=3, TapButton2=1).

You tried the auto-dev protocol earlier and it didn't work, maybe try the event protocol.

It's strange that the device event didn't work but good call to find another method. It probably changed and you could look it up in hwinfo --mouse to see what it is now.

**WthIteh** · January 10th, 2011

Originally Posted by pi/roman

You tried the auto-dev protocol earlier and it didn't work, maybe try the event protocol.

It's strange that the device event didn't work but good call to find another method. It probably changed and you could look it up in hwinfo --mouse to see what it is now.

I tried "auto", "auto-dev", "event", "alps", and "xlps" protocols but only

Code:

    Option        "Protocol"    "alps"

could cause xinput to detect the Touchpad.

And there is no change in output of hwinfo --mouse as I could see:

Code:

> hal.1: read hal dataprocess 2432: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
36: PS/2 00.0: 10500 PS/2 Mouse                                 
  [Created at input.183]
  Unique ID: AH6Q.U5GX9Ignjc0
  Hardware Class: mouse
  Model: "PS/2 Generic Mouse"
  Vendor: 0x0002 
  Device: 0x0001 "PS/2 Generic Mouse"
  Compatible to: int 0x0210 0x0003
  Device File: /dev/input/mice (/dev/input/mouse0)
  Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event7, /dev/char/13:71, /dev/input/by-path/platform-i8042-serio-4-event-mouse, /dev/char/13:32, /dev/input/by-path/platform-i8042-serio-4-mouse, /dev/char/13:63
  Device Number: char 13:63 (char 13:32)
  Driver Info #0:
    Buttons: 3
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

**pi/roman** · January 11th, 2011

You can comment out the inputclass section so you don't have to worry about changing the protocol in both sections if you want to try a different one. It seems like the inputdevice section is needed for now though anyway to make it recognized.

I have some more things to try to get it working.

First thing to do is remove the synaptics driver package:

Code:

sudo apt-get remove --purge xserver-xorg-input-synaptics

Then run an update:

Code:

sudo apt-get update && sudo apt-get upgrade

Then reboot your computer and see if your touchpad is picked up by the mouse driver. The goal is not to run it off the mouse driver but to see if it will at least be picked up by it as it was before. If it is not operable try some of these commands:

Code:

sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=exps

Code:

sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=imps

Code:

sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=any

If it is operable, it should work about the same as it did before.
Then reinstall the synaptics driver:

Code:

sudo apt-get install xserver-xorg-input-synaptics

Then reboot the computer again and see if the touchpad is operable. If not, then modprobe the driver again with proto=imps or proto=exps which are the mouse drivers. Use proto=any to try to get it to take the synaptics driver.
If your touchpad is still not operable then install gpointing device settings:

Code:

 sudo apt-get install gpointing-device-settings

Check in the settings there to see if your touchpad will show up.

**WthIteh** · January 11th, 2011

Good and Bad News.....

First I removed driver and update by

Code:

sudo apt-get remove --purge xserver-xorg-input-synaptics
sudo apt-get update && sudo apt-get upgrade

While xorg.conf content was as:

Code:

Section "ServerLayout"
    Identifier    "Default Layout"
    InputDevice    "Touchpad"    "CorePointer"
EndSection

Section "InputDevice"
    Identifier    "Touchpad"
    Driver        "synaptics"
    Option        "Protocol"    "alps"
    Option        "Device"    "/dev/input/by-path/platform-i8042-serio-4-event-mouse"
    Option        "UpDownScrolling"    "1"
EndSection

After reboot, touchpad was operable completely (else of vertical scrolling) and was detected by xinput --list as PS/2 Generic Mouse device.
Here is output of cat /var/log/Xorg.0.log | grep -iE 'mouse|touchpad|pointer|synaptics' at that point:

Code:

[    54.729] (**) |-->Input Device "Touchpad"
[    54.765] (II) LoadModule: "synaptics"
[    54.766] (WW) Warning, couldn't open module synaptics
[    54.766] (II) UnloadModule: "synaptics"
[    54.766] (EE) Failed to load module "synaptics" (module does not exist, 0)
[    54.831] (==) intel(0): Silken mouse enabled
[    54.919] (II) LoadModule: "synaptics"
[    54.919] (WW) Warning, couldn't open module synaptics
[    54.919] (II) UnloadModule: "synaptics"
[    54.919] (EE) Failed to load module "synaptics" (module does not exist, 0)
[    54.919] (EE) No input driver matching `synaptics'
[    55.361] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event7)
[    55.361] (**) PS/2 Generic Mouse: Applying InputClass "evdev touchpad catchall"
[    55.361] (**) PS/2 Generic Mouse: always reports core events
[    55.361] (**) PS/2 Generic Mouse: Device: "/dev/input/event7"
[    55.441] (II) PS/2 Generic Mouse: Found 3 mouse buttons
[    55.441] (II) PS/2 Generic Mouse: Found relative axes
[    55.441] (II) PS/2 Generic Mouse: Found x and y relative axes
[    55.441] (II) PS/2 Generic Mouse: Configuring as mouse
[    55.441] (**) PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
[    55.441] (**) PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    55.441] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE)
[    55.441] (II) PS/2 Generic Mouse: initialized for relative axes.
[    55.441] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)

Then I installed driver by

Code:

sudo apt-get install xserver-xorg-input-synaptics

and after reboot, touchpad was NOT operable, but detected by xinput --list as Touchpad device.
So I try followings respectively to make it operable:

Code:

sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=exps
sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=imps
sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=any

But neither of three above protocols could not make touchpad operable.
Here is output of cat /var/log/Xorg.0.log | grep -iE 'mouse|touchpad|pointer|synaptics' at that point:

Code:

[    55.515] (**) |-->Input Device "Touchpad"
[    55.604] (II) LoadModule: "synaptics"
[    55.604] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[    55.604] (II) Module synaptics: vendor="X.Org Foundation"
[    55.670] (==) intel(0): Silken mouse enabled
[    55.749] (II) Synaptics touchpad driver version 1.2.2
[    55.749] (**) Option "Device" "/dev/input/by-path/platform-i8042-serio-4-event-mouse"
[    56.054] (**) Option "CorePointer"
[    56.054] (**) Touchpad: always reports core events
[    56.153] (II) XINPUT: Adding extended input device "Touchpad" (type: TOUCHPAD)
[    56.153] (**) Touchpad: (accel) keeping acceleration scheme 1
[    56.153] (**) Touchpad: (accel) acceleration profile 0
[    56.153] (**) Touchpad: (accel) acceleration factor: 2.000
[    56.153] (**) Touchpad: (accel) acceleration threshold: 4
[    56.791] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event7)
[    56.791] (**) PS/2 Generic Mouse: Applying InputClass "evdev touchpad catchall"
[    56.791] (**) PS/2 Generic Mouse: Applying InputClass "touchpad catchall"
[    56.791] (II) Synaptics touchpad driver version 1.2.2
[    57.101] (--) PS/2 Generic Mouse: no supported touchpad found
[    57.101] (EE) PS/2 Generic Mouse Unable to query/initialize Synaptics hardware.
[    57.181] (EE) PreInit failed for input device "PS/2 Generic Mouse"
[    57.181] (II) UnloadModule: "synaptics"
[    57.181] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)

So I installed gpointing-device-settings by:

Code:

sudo apt-get install gpointing-device-settings

and then running it by

Code:

gpointing-device-settings

Interesting

There was Touchpad and one checkbox saying "Disable touchpad".
I removed that checkmark.
But touchpad was not operable yet. I try one reboot. After reboot checkmark was not there as expected (touchpad should be enabled) but it was not operable yet.

So I revert settings by commenting changes in config files and after reboot I reach previous PS/2 Generic Mouse device. This time running

Code:

gpointing-device-settings

shows two settings for PS/2 Generic Mouse for emulating middle mouse button and another for Wheel emulation (which was what I missed in my touchpad). If it works too, I reach my required functionality. So I enabled it. It wants button 1 or 2 or 3 or 4 for mouse wheel emulation. Using button 1, I could vertical / horizontal scroll by mouse click and move. But in this way I could not tap-and-drag anymore. By button 2, I could not make scrolling to work. With button 3, it does tap-and-drag and scrolling and selection simultaneously which is somehow terrible. With button 4, I could not make scrolling to work again.

What should I do now?

**pi/roman** · January 12th, 2011

I don't believe you will have enough buttons under the mouse driver to have all those options. You could try to run "xinput test" on your device and see how many buttons you can get to register. Try motioning along the edge to get a scroll button or tapping to generate a button click.

There is an old topic here http://ubuntuforums.org/showthread.php?t=417492&page=5 that recommends using boot parameters and it looks like many have had success with them. I tested them myself to make sure they won't blow up the computer but I don't have any problems to fix with them. You could try i8042=reset i8042=nomux and i8042=nopnp in your grub.cfg.

Code:

sudo gedit /boot/grub/grub.cfg

Below this line

### BEGIN /etc/grub.d/10_linux ###

is your first menu entry.

In this menu entry at the end of this line

linux /boot/vmlinuz-2.6.35-24-generic root=UUID=e411621d-c5a8-4ba9-bb66-65ec1f8fa0ec ro

place a space then the boot parameters.

I would also like to see the udev attributes:

Code:

udevadm info -a -n char/13:32

**WthIteh** · January 12th, 2011

I followed the instructions for boot commands (from http://ubuntuforums.org/showthread.php?t=417492&page=5), but it made no difference.
However tpconfig could recognize my touchpad as was said there.
This is output of sudo tpconfig -i command:

Code:

Found Synaptics Touchpad.
Firmware: 8.96 (multiple-byte mode).
Sensor type: unknown (0).
Geometry: rectangular/landscape/up.
Packets: absolute, 80 packets per second.
Corner taps disabled;        no tap gestures.
Edge motion: none.
Z threshold: 6 of 7.
2 button mode; corner tap is right button click.

And here is the output of udevadm info -a -n char/13:32 command:

Code:

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/i8042/serio4/input/input7/mouse0':
    KERNEL=="mouse0"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device '/devices/platform/i8042/serio4/input/input7':
    KERNELS=="input7"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{name}=="PS/2 Generic Mouse"
    ATTRS{phys}=="isa0060/serio4/input0"
    ATTRS{uniq}==""
    ATTRS{modalias}=="input:b0011v0002p0001e0000-e0,1,2,k110,111,112,r0,1,amlsfw"

  looking at parent device '/devices/platform/i8042/serio4':
    KERNELS=="serio4"
    SUBSYSTEMS=="serio"
    DRIVERS=="psmouse"
    ATTRS{description}=="i8042 AUX3 port"
    ATTRS{modalias}=="serio:ty01pr00id00ex00"
    ATTRS{bind_mode}=="auto"
    ATTRS{protocol}=="PS/2"
    ATTRS{rate}=="100"
    ATTRS{resolution}=="200"
    ATTRS{resetafter}=="5"
    ATTRS{resync_time}=="0"

  looking at parent device '/devices/platform/i8042':
    KERNELS=="i8042"
    SUBSYSTEMS=="platform"
    DRIVERS=="i8042"
    ATTRS{modalias}=="platform:i8042"

  looking at parent device '/devices/platform':
    KERNELS=="platform"
    SUBSYSTEMS==""
    DRIVERS==""

I also checked xinput test 12 (12 is id of PS/2 in xinput list output) while my touchpad was detected as PS/2 Generic Mouse and it shows "movement", "button 1 for left click", "button 2 for emulated middle click" and "button 3 for right click" but nothing special for edge scrolling or edge tapping or tapping, etc.

**WthIteh** · January 12th, 2011

Duplicate post

**WthIteh** · January 12th, 2011

Duplicate post

**pi/roman** · January 13th, 2011

I believe in order to have edge scrolling and regular buttons too your touchpad would need to have hardware driven scrolling and maybe yours does not so then it would be necessary to load the touchpad driver to make it work. It looks to me like the only way to get touchpad driver loaded would be to apply a patch although I hope I am wrong and someone can give some advice on it.

If you do decide to patch your driver you would need to get the debug data from your touchpad. You can do so by applying the "i8042.debug" parameter to the boot options as you did previously. Then as soon as the computer boots up. Save the dmesg log to a file.

Code:

dmesg > ~/Desktop/i8042boot.log

If you wait too long you may lose some important data regarding the initialization of the touchpad so try not to use the touchpad too much before saving the log.

Then you can report the bug on Launchpad and include the logged data along with other important information like lspci and you may not receive a lot of help there so you should probably also start a new forum topic asking for help in identifying your touchpad signature and applying it to a driver patch.

**WthIteh** · January 13th, 2011

Many thanks for your helps.

My touchpad should support edge scrolling directly because I could see a physically separated area for edge scrolling on my touchpad. Below is an ascii-art picture of my touchpad

HTML Code:

...............................
...........................  ..
...........................  ..
...........................  ..
...........................  ..
...........................  ..
...............................
...............................

I also do not want to patch my driver. Instead I will wait for an official update. I want to keep my system standard!

Thread: Touchpad Vertical Scrolling does not work

Thread Tools

Display

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Re: Touchpad Vertical Scrolling does not work

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions