Bug 927251 - Cypress Touchpad isn't identified correctly on Dell XPS 12
Summary: Cypress Touchpad isn't identified correctly on Dell XPS 12
Keywords:
Status: CLOSED DUPLICATE of bug 912166
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Sten Turpin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-25 13:42 UTC by Sten Turpin
Modified: 2013-03-25 15:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 912166
Environment:
Last Closed: 2013-03-25 15:00:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci -vvnn (18.11 KB, text/plain)
2013-03-25 13:42 UTC, Sten Turpin
no flags Details
lsusb -vv (50.15 KB, text/plain)
2013-03-25 13:43 UTC, Sten Turpin
no flags Details
xinput list (914 bytes, text/plain)
2013-03-25 13:44 UTC, Sten Turpin
no flags Details
dmesg (75.09 KB, text/plain)
2013-03-25 14:52 UTC, Sten Turpin
no flags Details

Description Sten Turpin 2013-03-25 13:42:49 UTC
Created attachment 716024 [details]
lspci -vvnn

+++ This bug was initially created as a clone of Bug #912166 +++

Description of problem:

The Dell XPS 12 touchpad is improperly identified as an IMPs/2 device; enhanced features like tap-to-click and palm rejection are not available. 


I included the following outputs :

#lspci -vvnn
#lsusb -vv
$xinput list

Comment 1 Sten Turpin 2013-03-25 13:43:58 UTC
Created attachment 716025 [details]
lsusb -vv

Comment 2 Sten Turpin 2013-03-25 13:44:35 UTC
Created attachment 716026 [details]
xinput list

Comment 3 Josh Boyer 2013-03-25 14:32:26 UTC
Please attach the dmesg output from a fresh boot of the latest kernel as a plaintext attachment.

Comment 4 Sten Turpin 2013-03-25 14:52:27 UTC
Created attachment 716055 [details]
dmesg

Had added psmouse boot parameters to grub config as part of trying to get the mouse to work under older kernels. Removed the parameters, and mouse works as expected now. Sorry for the noise, and thanks!

Comment 5 Josh Boyer 2013-03-25 15:00:43 UTC
Ah.  Great, thanks.

*** This bug has been marked as a duplicate of bug 912166 ***


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