Bug 3016 - elantech touchpad detected as Logitech Wheel Mouse
Summary: elantech touchpad detected as Logitech Wheel Mouse
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2011-10-11 07:19 CEST by Michael Johnson
Modified: 2012-12-02 14:32 CET (History)
3 users (show)

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


Attachments

Description Michael Johnson 2011-10-11 07:19:45 CEST
Newer laptops (Asus 2011+, Samsung 2010+, etc.) are using an Elantech touchpad that is not supported by the kernel in the 2.6.38 series. This results in psmouse falling back to detecting the pad as a Logitech PS/2 Wheel Mouse and no touchpad functions are available.

There is a patched version of the psmouse drivers packaged at http://planet76.com/drivers/elantech/psmouse-elantech-v6.tar.bz2 adding support for the newer model.

Additionally, there is a patch at https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/681904/comments/64 to add the same support.

This bug is tracked upstream at https://bugzilla.kernel.org/show_bug.cgi?id=27442 (whenever the kernel.org bugzilla is back) and was patched in kernel 3.0.

However, given the stated release date for Mageia 2, it will be a bit before a kernel containing the support is available in a stable release.

I would like to propose that the patch for the newer touchpad models be added so that these laptops can have better hardware support now.
Thierry Vignaud 2011-10-11 08:05:06 CEST

CC: (none) => thierry.vignaud
Source RPM: (none) => kernel

Manuel Hiebel 2011-10-11 11:19:56 CEST

Keywords: (none) => PATCH
Assignee: bugsquad => tmb

Comment 1 Marja Van Waes 2012-01-16 22:32:44 CET
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.

@ Thomas

Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

Marc Lattemann 2012-02-26 15:02:57 CET

CC: (none) => marc.lattemann

Comment 2 Marja Van Waes 2012-07-06 15:05:18 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 3 Manuel Hiebel 2012-11-05 16:53:16 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 4 Manuel Hiebel 2012-12-02 14:32:35 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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


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