On Sat, Jan 23, 2010 at 11:13 AM, electronmuontau neutrino
<[email protected]> wrote:
> On Fri, Jan 22, 2010 at 2:57 AM, J.C. Roberts <[email protected]>
wrote:
>> On Thu, 21 Jan 2010 00:42:26 -0500 electronmuontau neutrino
>> <[email protected]> wrote:
>>
>>> I have an Acer Aspire One D250 running snapshot (2010-01-20). The
>>> mouse will work for a couple of seconds and then freeze. This has
>>> occured when running wsmoused in a console(not in X), inside of X, and
>>> when I run od /dev/wsmouse. If I kill wsmoused and start it again,
>>> the mouse works and then freezes. When I go to a console
>>> (ctrl+alt+f1) from X and go back to X, the mouse works, then freezes.
>>> When I run od /dev/wsmouse, I see output and then nothing after a
>>> couple of seconds. I can kill od and run it again and see the output
>>> again for a short time. This behavior occurs in releases 4.3, 4.4,
>>> 4.5, 4.6, and snapshot (2010-01-20). The mouse works fine in releases
>>> 4.0, 4.1, and 4.2. Something was done between 4.2 and 4.3 that causes
>>> this problem. The mouse is seen as a ps2 mouse. The easiest work
>>> around is to plug in a usb mouse which works in all the releases
>>> mentioned as well as current. Any help is appreciated.
>>>
>>
>> There was some discussion on the Acer AspireOne mouse just a few days
>> ago on the bugs@ list, although it was a slightly different model.
>>
>> http://marc.info/?t=126391984800003&r=1&w=2
>>
>> Thanks for posting your dmesg, but I have an odd question.
>>
>> Do you ever see "pmsattach: disable error" in your dmesg?
>>
>> According to Stuart (sthen@), the message above is not consistent so
>> you'd only see it some of the time.
>>
>>
>> --
> Sorry, I have never seen that error on my Aspire One, just the odd
> mouse behavior. Have you tried to install previous releases like I
> did? The mouse worked fine on releases 4.0, 4.1, and 4.2, but did not
> work on 4.3, 4.4, 4.5, 4.6, and any of the snapshots.
