Bug 765949

Summary: Touchpad not recognised: Lenovo u300s
Product: [Fedora] Fedora Reporter: Daniel Mircea <daniel>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: extras-orphan, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, notting, peter.hutterer
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-08 23:28:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Xorg log none

Description Daniel Mircea 2011-12-09 18:11:10 UTC
The touchpad tab is missing from gnome's "Mouse and Touchpad" tab although a touchpad is present on the current machine (and works pretty well, including side scrolling).

The laptop in question is a Lenovo u300s (it's only been released last month or so, so perhaps it only needs to be whitelisted).

Comment 1 Peter Hutterer 2011-12-12 00:43:18 UTC
Xorg log please. This is usually a sign of the kernel not initialising the touchpad as such (it runs in PS2 compat mode). The X synaptics driver then doesn't hook onto it and gnome won't show the touchpad panel.

Comment 2 Daniel Mircea 2011-12-12 04:08:50 UTC
Created attachment 545542 [details]
Xorg log

Comment 3 Josh Boyer 2011-12-12 12:35:46 UTC
Can you attach the dmesg from boot please

Comment 4 Daniel Mircea 2011-12-13 09:32:10 UTC
I had a minor hardware issue with the laptops keyboard and had to send it back for repairs. I'm going to post the log you asked for as soon as I get it back.

Comment 5 Daniel Mircea 2012-02-08 23:28:19 UTC
The laptop couldn't be repaired and because it was out of stock I got a refund and bought something else.

Considering the new one had the same problem on a fresh installation, but it was fixed after a kernel update there's a good chance this bug has already been fixed.

As such I'm going to close it.