mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Of Mice and Linux
Date: 08 Dec 2003 13:55:26 -0700	[thread overview]
Message-ID: <1070916926.20390.8.camel@localhost.localdomain> (raw)
In-Reply-To: <3FD4BD1B.1060708@coyotegulch.com>

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]

On Mon, 2003-12-08 at 11:04, Scott Robert Ladd wrote:
> Please indulge a minor story in regard to testing beta kernels.
> 
> Last Friday, I made a minor change to my Linux .config and rebuilt 
> 2.6.0-test11. Soon thereafter, my mouse began getting "stuck", sometimes 
> for several seconds, refusing to move no matter how vigorously I wiggled 
> my wrist.
> 
> I rebuilt the kernel a couple of times, turning on and off various 
> options; I plugged and unplugged devices from the USB ports; a 
> considerable amount of cursing ensued. The problem was erratic -- and 
> frustrating, because I hadn't had much trouble with 2.6 (which I've been 
> using since the 2.6.4x days).
> 
> Then I borrowed a mouse from another machine, plugged it in -- and the 
> replacement rodent worked flawlessly. It seems that my mouse broke just 
> about the same time as I installed test11. Being a software guy, I 
> should have blamed the hardware first...
> 
> ...especially since the truth was right in front of me, emblazoned 
> boldly across the mouse: the word "Microsoft".
> 
> I think the replacement will be from Logitech.

Are you _sure_ your mouse is broken?  Did you try your Microsoft mouse
on another machine?

I ask because my Microsoft Intellimouse wireless started doing the same
thing after I installed 2.6.0-test11.  I haven't made a bug report
because I haven't had time to bother retrying -test10, removing the
binary Nvidia drivers, and taking out the Reiser4 patches.

But now that you've mentioned the same problem, I'm going to add a "Me
Too!"

And on a different machine, I'm using a Logitech MX700, and it works
perfectly under -test11.
-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-12-08 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 18:04 Scott Robert Ladd
2003-12-08 19:52 ` Florin Iucha
2003-12-08 20:56   ` Scott Robert Ladd
2003-12-08 22:12     ` [OT] " Wakko Warner
2003-12-09  1:43     ` Joshua Kwan
2003-12-08 20:55 ` Zan Lynx [this message]
2003-12-09 13:35   ` Scott Robert Ladd

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=1070916926.20390.8.camel@localhost.localdomain \
    --to=zlynx@acm.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®