mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Craig Bradney <cbradney@zip.com.au>
To: rol@as2917.net
Cc: "'Erik Steffl'" <steffl@bigfoot.com>, linux-kernel@vger.kernel.org
Subject: Re: logitech mouseMan wheel doesn't work with 2.6.5
Date: Tue, 20 Apr 2004 17:36:57 +0200	[thread overview]
Message-ID: <1082475417.6543.3.camel@amilo.bradney.info> (raw)
In-Reply-To: <200404201522.i3KFMk120352@tag.witbe.net>

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

I've got 4 PCs all with logitech cordless optical mice.. all work
perfectly with Gentoo dev sources 2.6.5.. as well as 2.6.3, 2.6.1 etc

Craig

On Tue, 2004-04-20 at 17:22, Paul Rolland wrote:
> Hello,
> 
> >    it looks that after update to 2.6.5 kernel (debian source 
> > package but 
> > I guess it would be the same with stock 2.6.5) the mouse 
> > wheel and side 
> > button on Logitech Cordless MouseMan Wheel mouse do not work.
> I've got a new mouse with a wheel, and I've got the same problem,
> though I can't tell if it was working before...
> 
> > Here's the most basic/simple situation/symptoms:
> > 
> >    I stop X, read bytes from /dev/psaux (c program, using open and 
> > read). for each mouse action there are few bytes read, usually number 
> Could you provide me with the program so that I can test too ?
> 
> >    BTW X windows is confused in the same way (I guess because that's 
> > what it gets from kernel driver - using xev I found that it 
> > thinks the 
> > sidebutton is button 2 and that turning the wheel is not an 
> > event at all).
> Got the same : wheel is no-op :-(
> 
> I guess I should try a stock 2.4.x kernel to see if it working or
> not...
> 
> Regards,
> Paul
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

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

  reply	other threads:[~2004-04-20 15:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 14:14 Erik Steffl
2004-04-20 15:22 ` Paul Rolland
2004-04-20 15:36   ` Craig Bradney [this message]
2004-04-20 18:14     ` Kim Holviala
2004-04-20 19:06     ` Erik Steffl
2004-04-20 20:18       ` Craig Bradney
2004-04-20 19:03   ` Erik Steffl
2004-04-20 20:26 ` Kim Holviala
2004-04-20 23:31   ` Erik Steffl
2004-04-20 23:41     ` Randy.Dunlap
2004-04-24  7:27   ` Erik Steffl
2004-04-24  8:41     ` Craig Bradney
2004-04-27 23:18     ` Erik Steffl
2004-04-27 23:29       ` Craig Bradney
2004-04-27 23:56         ` Erik Steffl
2004-04-28  7:13           ` Craig Bradney
2004-04-28  7:22             ` Kim Holviala
2004-04-28  8:21               ` Erik Steffl
2004-04-28  8:36                 ` Craig Bradney
2004-04-28 12:41                 ` Dmitry Torokhov
2004-04-28 18:47                   ` Erik Steffl
2004-04-28 23:24                     ` Dmitry Torokhov
2004-04-29  6:34                       ` Erik Steffl
2004-06-02 23:39                         ` Vojtech Pavlik
     [not found] <1N4qh-4Ct-13@gated-at.bofh.it>
2004-04-21 16:08 ` Frank Otto

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=1082475417.6543.3.camel@amilo.bradney.info \
    --to=cbradney@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rol@as2917.net \
    --cc=steffl@bigfoot.com \
    /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®