Messages in this thread |  | | Date | Tue, 2 Sep 2008 11:23:25 +0200 (CEST) | | From | Jiri Kosina <> | | Subject | Re: Lenovo 3000 N100 i8042 problems |
| |
On Mon, 1 Sep 2008, Daniel Barkalow wrote:
> > Could you please send a dmidecode output from your system, so that we can > > compare it to the one provided by Christopher, as he as the system that > > apparently needs the nomux quirk to work correctly? It's indeed possible > > that there are various systems out there, and the DMI match has to be made > > more strict. > Attached.
Hmm, so you have
Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: LENOVO Product Name: 076836U Version: 3000 N100 Serial Number: L3H0536 UUID: 6747DA31-D471-11DA-901B-000FB0C9A0C9 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified
Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: LENOVO Product Name: MPAD-MSAE Customer Reference Boards Version: Not Applicable Serial Number: 41W1220Z1ZBUA6551DK
and the system on which Christopher reported originally this bug to me was
Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: LENOVO Product Name: 076804U Version: 3000 N100 Serial Number: L3HX754 UUID: DA02FA2F-A0AC-11DB-A093-000FB0D2560C Wake-up Type: Power Switch SKU Number: Intel Family: Lenovo
Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: LENOVO Product Name: CAPELL VALLEY(NAPA) CRB Version: Not Applicable Serial Number: 41W8025Z1ZCZ971N36R
so the product name both of System and Base Board are different, and apparently the systems differ. Dmitry, what fields would you propose to be put in the DMI matching here? I will do the patch then.
Thanks,
-- Jiri Kosina SUSE Labs
|  |