Bug 5606 - ALPS Touchpad not correctly recognized on Dell Latitude e65220 - basic functionning only
Summary: ALPS Touchpad not correctly recognized on Dell Latitude e65220 - basic functi...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: PATCH, UPSTREAM
Depends on:
Blocks:
 
Reported: 2012-04-25 11:56 CEST by x x
Modified: 2012-05-29 11:20 CEST (History)
0 users

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description x x 2012-04-25 11:56:25 CEST
Description of problem:

On Dell Latitude e6520, the ALPS touchpad is not properly recognized, and is treated as "Generic PS/2 mouse". Scrolling is not functional, nor double touch.

#: cat /proc/bus/input/devices

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input1
U: Uniq=
H: Handlers=mouse0 event1 
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3


#: uname -r
2.6.38.8-desktop586-10.mga


This bug has already benn reported in other linux flavors, examples :

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

and is reported as a kernel bug :

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


A temporary patch has been reported here, http://mikebeach.org/2011/04/15/correctly-recognize-alps-touchpad-on-dell-e6510-in-linux/ but I haven't yet tried it.



Version-Release number of selected component (if applicable):



How reproducible:


Steps to Reproduce:
1.
2.
3.
Manuel Hiebel 2012-04-25 17:17:57 CEST

Keywords: (none) => PATCH, UPSTREAM
Component: New RPM package request => RPM Packages
Assignee: bugsquad => tmb
Source RPM: (none) => kernel
Severity: normal => enhancement

Comment 1 x x 2012-05-29 11:20:41 CEST
Fully functionnal trackpad under mageia2.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.