Results 1 to 6 of 6

Thread: Two fingers required for scroll??

Hybrid View

  1. #1
    Join Date
    Nov 2005
    Location
    Jackson, TN USA
    Beans
    462
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Two fingers required for scroll??

    It is the PS/2 Logitech Mouse device name.

    With that much identified, how do I control how many fingers to use?
    If I could just get the touchpad to show up under the system-->preferences-->mouse...

    not sure if I mentioned this, but I am also unable to load the synaptics driver, which i presume is the root of the problem. The driver is most definitely on the computer, I just cant load it, not even manually:

    Code:
    myk@mobileThree:~$ sudo modprobe synaptics
    [sudo] password for myk: 
    FATAL: Module synaptics not found.
    myk@mobileThree:~$ locate synaptics
    /lib/modules/2.6.31-14-generic/kernel/drivers/input/mouse/synaptics_i2c.ko
    /lib/modules/2.6.31-19-generic/kernel/drivers/input/mouse/synaptics_i2c.ko
    /lib/modules/2.6.31-20-generic/kernel/drivers/input/mouse/synaptics_i2c.ko
    "Despite millions of dollars of research, Death continues to be Americas number one killer."

    Kingdom Computer Solutions

  2. #2
    Join Date
    Jan 2010
    Location
    65 AD
    Beans
    304
    Distro
    Ubuntu Development Release

    Re: Two fingers required for scroll??

    Here are some things you could try:
    Code:
    lshal -s | grep i8042
    then do:
    Code:
    lshal -u output
    where output=whatever was listed on the first lshal which pertains to the mouse
    You can pass boot options to our input controller like listed here:
    http://lkml.indiana.edu/hypermail/linux/kernel/0401.0/0436.html
    You could try i8042.reset for instance open /boot/grub/grub.cfg and place "i8042.reset" at the end of the "linux /boot/vmlinuz" line.

    for more system data try
    Code:
    hwinfo --mouse
    cat /proc/bus/input/devices
    grep "^(EE)" /var/log/Xorg.0.log
    grep "^(WW)" /var/log/Xorg.0.log
    You could also check other logs in /var/log/ like syslog kern.log udev dmesg and messages
    You could try blacklisting the driver that is loaded by placing it in /etc/modprobe.d/blacklist.conf
    That's all I can think of now.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •