mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Toby A Inkster <tobyink@goddamn.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Mouse wheel problems again...
Date: Tue, 16 Mar 2004 01:32:23 +0000	[thread overview]
Message-ID: <20040316013223.GA4170@ophelia.goddamn.co.uk> (raw)

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

Dear all,

Am having problems using my mouse wheel on 2.6.3, when it worked fine in
2.4.24.

Technically it's not a mouse, but a trackball. And technically not a wheel,
but a couple of buttons. But this shouldn't make any difference, should it?

When I click the scroll buttons they are both treated as middle-click (button
2) when they should be treated as scrolling (buttons 4 and 5) -- this is
according to xev.

The mouse is plugged into the PS/2 port, but I also have the USB mouse stuff
compiled as a module just in case I change my mind.

I think I've tried most of the suggestions I could find in the archive and
on Google.

Using hexdump on /dev/input/mice, the signals sent for up and down scroll
buttons seem identical to each other.

Here is some (possibly relevent) information:

[tai@ophelia (pts/1) ~]$ cat /boot/config | grep -i mouse ; echo ''
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
CONFIG_USB_MOUSE=m

[tai@ophelia (pts/1) ~]$ dmesg | grep -i mouse ; echo ''
mice: PS/2 mouse device common for all mice
input: PS/2 Logitech Mouse on isa0060/serio1

[tai@ophelia (pts/1) input]$ cat /proc/bus/input/devices|tac|tail -n 8|tac
I: Bus=0011 Vendor=0002 Product=0001 Version=006d
N: Name="PS/2 Logitech Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 
B: EV=7 
B: KEY=70000 0 0 0 0 0 0 0 0 
B: REL=3 


And here's some stuff from XF86Config-4:

Section "InputDevice"
    Identifier  "Mouse1"
    Driver      "mouse"
    Option      "SendCoreEvents"        "true"
    Option      "Device"                "/dev/input/mice"
    Option      "Protocol"              "ExplorerPS/2"
    Option      "Buttons"               "5"
    Option      "Emulate3Buttons"
    Option      "Emulate3Timeout"       "50"
    Option      "ZAxisMapping"          "4 5"
EndSection
# [...]
Section "ServerLayout"
    Identifier "layout1"
    InputDevice "Keyboard1" "CoreKeyboard"
    InputDevice "Mouse1" "CorePointer"
    Screen "screen1"
    InputDevice "Mouse1" "SendCoreEvents"
EndSection
                                     
                                     
Any suggesitons?

Thanks in advance for any light than can be shed.

-- 
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

Q: WHY DO ELEPHANTS HAVE BIG EARS?
A: BECAUSE NODDY WOULDN'T PAY THE RANDOM.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-03-16  1:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040316013223.GA4170@ophelia.goddamn.co.uk \
    --to=tobyink@goddamn.co.uk \
    --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®