Bug 45101 - Sentelic touchpad not detected
Summary: Sentelic touchpad not detected
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-23 19:52 UTC by Pavel Belyaev
Modified: 2012-07-24 16:59 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.2.0-26
Tree: Mainline
Regression: No


Attachments
dmidecode (23.11 KB, text/plain)
2012-07-23 19:52 UTC, Pavel Belyaev
Details

Description Pavel Belyaev 2012-07-23 19:52:34 UTC
Created attachment 76031 [details]
dmidecode

My touchpad(sentelic) not detected in ubuntu 12.04, and detected after add i8024.nomux parameter
Comment 1 Pavel Belyaev 2012-07-23 19:53:43 UTC
My notebook DNS X300 (Ultrabook)
Comment 2 Dmitry Torokhov 2012-07-24 16:58:13 UTC
Unfortunately our friends at DNS were lazy and simply took Intel's reference BIOS and shoved it into the box. There is simply not enough unique information to quirk against, all relevant fields say "To be filled by O.E.M." or "Intel":

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Intel Co.,Ltd.
	Product Name: X300
	Version: To be filled by O.E.M.
	Serial Number: To be filled by O.E.M.
	UUID: <redacted>
	Wake-up Type: Power Switch
	SKU Number: To be filled by O.E.M.
	Family: To be filled by O.E.M.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: INTEL Corporation
	Product Name: HURONRIVER
	Version: To be filled by O.E.M.
	Serial Number: To be filled by O.E.M.
	Asset Tag: To be filled by O.E.M.
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: To be filled by O.E.M.
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Unfortunately you will have to continue adding i8042.nomux to the kernel boot options.
Comment 3 Dmitry Torokhov 2012-07-24 16:59:02 UTC
BTW, if there are BIOS updates that fill proper data into DMI fields this issue can be revisited.

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