input: Thinkpad R31 i8042 nomux quirk
Subsystems (2)
PATCH 1/1 input: Thinkpad R31 i8042 nomux quirk
Subject: [PATCH] input: Thinkpad R31 i8042 nomux quirk
from: Colin B Macdonald <[email protected]>
Thinkpad R31 needs i8042 nomux quirk. Stops jittery jumping mouse and random keyboard input. Fixes kernel bug #11723. Cherry picked from Ubuntu who have sometimes (on-again-off-again) had a fix in their patched kernels.
---
drivers/input/serio/i8042-x86ia64io.h renamed from drivers/input/serio/i8042-x86ia64io.h.orig +7 -0
@@ -322,6 +322,13 @@ static struct dmi_system_id __initdata i DMI_MATCH(DMI_PRODUCT_NAME, "N34AS6"), }, }, + { + .ident = "IBM 2656", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "IBM"), + DMI_MATCH(DMI_PRODUCT_NAME, "2656"), + }, + }, { } };
Quoted 8 lines · Colin Macdonald
Subject: [PATCH] input: Thinkpad R31 i8042 nomux quirk
from: Colin B Macdonald <[email protected]>Thinkpad R31 needs i8042 nomux quirk. Stops jittery jumping mouse and random keyboard input. Fixes kernel bug #11723. Cherry picked from Ubuntu who have sometimes (on-again-off-again) had a fix in their patched kernels.
Applied, thank you Colin.
Signature · 1 line
Dmitry
Hello,
I also have a notebook, Maxdata Pro 7000X (Fujitsu clone), which has such problem (needs i8042.nomux=1, perhaps kernel bug #8740).
Can we also use a patch for it?
dmidecode useful information:
Handle 0x0001, DMI type 1, 25 bytes
System Information
Manufacturer: MAXDATA
Product Name: Pro 7000X
Version: xxxxxxxxxx
Serial Number: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
UUID: xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx Wake-up Type: Power Switch
Thanks,
--
Daniele C.
Colin Macdonald ha scritto:
Quoted 34 lines
Subject: [PATCH] input: Thinkpad R31 i8042 nomux quirk
from: Colin B Macdonald <[email protected]>Thinkpad R31 needs i8042 nomux quirk. Stops jittery jumping mouse and random keyboard input. Fixes kernel bug #11723. Cherry picked from Ubuntu who have sometimes (on-again-off-again) had a fix in their patched kernels.
Signed-off-by Colin B Macdonald <[email protected]>---
drivers/input/serio/i8042-x86ia64io.h renamed from drivers/input/serio/i8042-x86ia64io.h.orig +7
-1@@ -322,6 +322,13 @@ static struct dmi_system_id __initdata i DMI_MATCH(DMI_PRODUCT_NAME, "N34AS6"), }, }, + { + .ident = "IBM 2656", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "IBM"), + DMI_MATCH(DMI_PRODUCT_NAME, "2656"), + }, + }, { } }; --To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 4 lines · legolas558 wrote:
I also have a notebook, Maxdata Pro 7000X (Fujitsu clone), which has such problem (needs i8042.nomux=1, perhaps kernel bug #8740).
Can we also use a patch for it?
Can you test the patch below and see if it fixes the problem?
Quoted 7 lines
Handle
0x0001, DMI type 1, 25 bytes
System Information
Manufacturer: MAXDATA Product Name: Pro 7000X
Version: xxxxxxxxxx
Serial Number: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
UUID: xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx Wake-up Type: Power Switch
drivers/input/serio/i8042-x86ia64io.h renamed from drivers/input/serio/i8042-x86ia64io.h.orig +7 -0
@@ -329,6 +329,13 @@ static struct dmi_system_id __initdata i DMI_MATCH(DMI_PRODUCT_NAME, "2656"), }, }, + { + .ident = "Maxdata Pro 7000X (Fujitsu clone)", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "MAXDATA"), + DMI_MATCH(DMI_PRODUCT_NAME, "Pro 7000X"), + }, + }, { } };
Hi Colin,
I have removed 'i8042.nomux=1' from my kernel command line (kernel 2.6.25-gentoo-r8) and the mouse glitches bug has not yet happened (last time I had 2.6.22 or so).
I assume it has been fixed in previous releases, and got unnoticed. I will reply again to this message if there is again necessity to use i8042.nomux=1.
Thanks for your help, and sorry for the noise.
Best regards,
--
Daniele C.
Colin Macdonald ha scritto:
Quoted 39 lines
Quoted 5 lines · legolas558 wrote:
I also have a notebook, Maxdata Pro 7000X (Fujitsu clone), which has such problem (needs i8042.nomux=1, perhaps kernel bug #8740).
Can we also use a patch for it?
Can you test the patch below and see if it fixes the problem?
Quoted 8 lines
Handle
0x0001, DMI type 1, 25 bytes
System Information
Manufacturer: MAXDATA Product Name: Pro 7000X
Version: xxxxxxxxxx
Serial Number: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
UUID: xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx Wake-up Type: Power Switchdrivers/input/serio/i8042-x86ia64io.h renamed from drivers/input/serio/i8042-x86ia64io.h.orig +7
-0@@ -329,6 +329,13 @@ static struct dmi_system_id __initdata i DMI_MATCH(DMI_PRODUCT_NAME, "2656"), }, }, + { + .ident = "Maxdata Pro 7000X (Fujitsu clone)", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "MAXDATA"), + DMI_MATCH(DMI_PRODUCT_NAME, "Pro 7000X"), + }, + }, { } };
Hello Colin,
today I got the usual messages in dmesg which witness that kernel bug 8740 is not yet fixed. Please add your patch to the tracker http://bugzilla.kernel.org/show_bug.cgi?id=8740 and set it to CODE_FIX as I have again to use i8042.nomux=1 to prevent these messages.
[ 3203.402077] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 3203.403431] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 3203.405245] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 3203.406608] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 3203.407971] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 3203.407979] psmouse.c: issuing reconnect request
It is a very rare event but with i8042.nomux=1 it never happens, it has happened because I removed i8042.nomux=1 when I sent you the below message. The patch simply prevents me to set manually that kernel parameter, which is an annoyance.
Thank you,
--
Daniele
legolas558 ha scritto:
Quoted 56 lines
Hi Colin,
I have removed 'i8042.nomux=1' from my kernel command line (kernel 2.6.25-gentoo-r8) and the mouse glitches bug has not yet happened (last time I had 2.6.22 or so).
I assume it has been fixed in previous releases, and got unnoticed. I will reply again to this message if there is again necessity to use i8042.nomux=1.
Thanks for your help, and sorry for the noise.
Best regards,
Signature · 3 lines
Daniele C. Colin Macdonald ha scritto:Quoted 41 lines
Quoted 5 lines · legolas558 wrote:
I also have a notebook, Maxdata Pro 7000X (Fujitsu clone), which has such problem (needs i8042.nomux=1, perhaps kernel bug #8740).
Can we also use a patch for it?
Can you test the patch below and see if it fixes the problem?
Quoted 8 lines
Handle
0x0001, DMI type 1, 25 bytes
System Information
Manufacturer: MAXDATA Product Name: Pro 7000X
Version: xxxxxxxxxx
Serial Number: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
UUID: xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx Wake-up Type: Power Switch--- linux-2.6.27/drivers/input/serio/i8042-x86ia64io.h.orig
2008-10-12 11:31:43.000000000 -0700+++
linux-2.6.27/drivers/input/serio/i8042-x86ia64io.h2008-10-12
11:33:11.000000000 -0700drivers/input/serio/i8042-x86ia64io.h renamed from drivers/input/serio/i8042-x86ia64io.h.orig +7
-0@@ -329,6 +329,13 @@ static struct dmi_system_id __initdata i DMI_MATCH(DMI_PRODUCT_NAME, "2656"), }, }, + { + .ident = "Maxdata Pro 7000X (Fujitsu clone)", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "MAXDATA"), + DMI_MATCH(DMI_PRODUCT_NAME, "Pro 7000X"), + }, + }, { } };