From: legolas558 <legolas558@email.it>
To: Colin Macdonald <cbm@math.ucla.edu>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Thinkpad R31 i8042 nomux quirk
Date: Sat, 24 Jan 2009 21:51:53 +0100 [thread overview]
Message-ID: <497B7F69.5040705@email.it> (raw)
In-Reply-To: <48F3A87B.402@email.it>
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:
> 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:
>> 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?
>>
>>
>>> 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.h 2008-10-12
>> 11:33:11.000000000 -0700
>> @@ -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"),
>> + },
>> + },
>> { }
>> };
>>
>>
>>
>
>
prev parent reply other threads:[~2009-01-24 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 18:18 [PATCH] input: Thinkpad R31 i8042 nomux quirk Colin Macdonald
2008-10-11 22:18 ` Dmitry Torokhov
2008-10-12 7:51 ` legolas558
2008-10-12 18:39 ` Colin Macdonald
2008-10-13 19:58 ` legolas558
2009-01-24 20:51 ` legolas558 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=497B7F69.5040705@email.it \
--to=legolas558@email.it \
--cc=cbm@math.ucla.edu \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.