Mailinglist Archive: opensuse-bugs (5570 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=716996

https://bugzilla.novell.com/show_bug.cgi?id=716996#c14


Bruno Friedmann <bruno@xxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED
                 CC|                            |bruno@xxxxxxxxxxx
       InfoProvider|mark@xxxxxxxx               |

--- Comment #14 from Bruno Friedmann <bruno@xxxxxxxxxxx> 2011-10-16 14:21:57 
UTC ---
On a very similar hardware Dell Precision M4600 which as this new multi-touch
ALPS touchpad
It's recognize as ps/2 too. 
Several months ago I was looking to get a solution and dig the web for what's
happen. The big trouble is Alps did give the source or spec and so nobody can
have a reliable driver for that one.

https://bugzilla.redhat.com/show_bug.cgi?id=590880#c47

Quotes from Message on the Dell Precision Mailing list

"You can patch the kernel alps.c file to stop the kernel from thinking
this mystery touchpad is a ps/2 mouse,

https://confluence.nau.edu/confluence/display/~cmg238@xxxxxxx/Recognize+ALPS+Touchpad+on+Dell+E6510+in+Ubuntu

However, you still can't access the options for scrolling or
multifinger behaviors."
There are plenty of bug reports on this, all basically point back to
Dell saying we need information about this device.  The ALPS rep said
you can/should give the information.

https://bugzilla.kernel.org/show_bug.cgi?id=14660
https://bugzilla.kernel.org/show_bug.cgi?id=28092

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625
https://bugzilla.redhat.com/show_bug.cgi?id=590880

http://bugs.gentoo.org/show_bug.cgi?id=318567

http://fossplanet.com/f10/%5Bbug-773165%5D-%5Bnew%5D-touchpad-recognized-ps-2-alpssimultaneously-144569/

I know there some quirk patches around is Ubuntu using one of them ? 


On factory up to date at today (October 16)
udevadm info -a --name=/dev/input/event1 

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/serio1/input/input1/event1':
    KERNEL=="event1"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device '/devices/platform/i8042/serio1/input/input1':
    KERNELS=="input1"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{name}=="PS/2 Generic Mouse"
    ATTRS{phys}=="isa0060/serio1/input0"
    ATTRS{uniq}==""
    ATTRS{properties}=="0"

  looking at parent device '/devices/platform/i8042/serio1':
    KERNELS=="serio1"
    SUBSYSTEMS=="serio"
    DRIVERS=="psmouse"
    ATTRS{description}=="i8042 AUX port"
    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"

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

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.