Michael Heiming <michael+USENET@www.heiming.de> wrote:
> [ptb says usb mouse under 2.6 kernel doesn't emit button 4/5 events]
>> Any idea if there's some reconfiguration to be done for 2.6? Nothing

> 'xev' should tell.

Well, X should tell! It's the one hat gets the events and passes them
to he apps :-).

> Looks like a pretty ancient kernel you should upgrade. Anyway

:-). My kernel is most insulted. But I'm afraid I can't reboot for
another six months now, so it will have to wait. Besides, this kernel
is fine - I like it best of the many I have used. It's got nice smooth
electrons and a really shiny stack, with chromed interrupt vector hooks.



> under 2.6 needed the following (lilo.conf append line) to make
> my pointing devices working probably: "psmouse.proto=imps". Never

Aha! Michael, if that is not it, it deserves to be it! It fits the
profiled lack of 4/5 button events being produced by a driver. Well
done! You are too good. Now how did you find that out ... it'll be a
module param for me, surely? Or .. yes, in 2.6 I have psmouse as a
module, so it goes in whatever the kerneld config file is nowadays ...

Gah! Debian doesn't make it very clear to me if they want me to add a
file in /etc/modprobe.d/ or want me to edit /etc/modprobe.conf (which
includes explicitly /lib/modules/modprobe.conf, made from
/etc/modprobe.d/*). How convoluted. And what about my 2.4 module
module options? How not to mix them up with 2.6? Oh, they will still
come from the old modules.conf! I hope.


Anyway, I need this for usbmouse, not psmouse, but now I can go look at
the code ... and I see the psmouse parameter:

static char *psmouse_proto;
static unsigned int psmouse_max_proto = -1U;
module_param_named(proto, psmouse_proto, charp, 0);
MODULE_PARM_DESC(proto, "Highest protocol extension to probe (bare, imps, exps). Useful for KVM switches.");

But I don't see any PARMs like that for usbmouse! Let's google to see
wheer you got your info from ...

Linux: 2.6 Input Drivers FAQ

(I imagine) http://kerneltrap.org/node/2199

Problems:
~~~~~~~~

My mouse wheel is not working in X.
My Logitech (MousManPS/2) mouse stopped working in X.
My extra buttons don't work in X.

Solution:
~~~~~~~~

Check your XFree86 config file.

Make sure the mouse protocol is set to "ExplorerPS/2", as that is what
the 2.6 kernel exports to applications regardless of the real mouse
type.

Make sure you have an "ZAxisMapping 4 5" entry.

Make sure you have an entry for remapping the extra buttons above 5.

Yerrrs. And what is a person supposed to do when he ALSO runs a 2.4
kernel? (and reboots every six months).

It looks as though changing the X config entry for the USB mouse might
be a possibility! I wouldn't have noticed that the other mouse needed
changing because it doesn't have a scroll wheel. That's a possibility.

This entry in the FAQ is a weirdo!

Problems:
~~~~~~~~

I'm getting double clicks when I click only once.
My scroll wheel scrolls by two lines/screens instead of one.
My mouse moves too fast.

Solution:
~~~~~~~~

Check your XFree86 config file.

You probably have two "mouse" entries there, one pointing to
/dev/psaux and the other to /dev/input/mice, so that you can get both
your PS/2 and USB mouse working on 2.4.

2.6 uses the input subsystem for both PS2 and USB, and thus both
devices will report events from both mice, resulting in doubled
events.

Remove either the /dev/psaux or /dev/input/mice entry, depending what
suits you better for 2.4 compatibility should you ever need go back to
2.4.

Uh, no. I need both those entries for 2.4! I can't "remove one". What
kind of advice is that! The first mouse is:

Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"

lrwxrwxrwx 1 root 5 Feb 8 2003 /dev/mouse -> psaux

and the other mouse is

Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"

Oh, I see - it would ONLY be a problem if I didn't have two mice, and
used my ps2 mouse. Then signals from the ps2 mouse would go to both
device nodes. WAIT A MOMENT. I DO have only one ps2 mouse whenever I
don't plug the usb mouse in, and I have no such problems. I don't
believe this entry. I don't get double dsensitivity either!

Anyway, I need both entries for 2.4 use.

Sigh - somebody has made a mess there.



> tested if it is still needed running 2.6.14, it's just there and
> my Kensington USB trackball works like a charm.

Unfortunately we won't know the result for another six months!

Peter