Maybe you lot can help me out ... I'm too busy earning potz of dosh to
have time to investigate this, and I know y'all are just bound to
"know" the answer already, so there's no point to my spraining a 'cell,
is there?



Ahem. OK. That wasn't entirely the whole truth.

Nevertheless, I have just noticed that when I reboot my TP X24 laptop
under the 2.6.3 kernel, my external USB mouse scroll button stops moving
pages in mozilla 6.x. It works fine in 2.4.22 (wot I am using now). I
only "noticed" because I never usually reboot - I last rebooted over
six months ago, according to the log.

Any idea if there's some reconfiguration to be done for 2.6? Nothing
obvious occurs to me! Perhaps the 2.6 mouse driver needs changing to
emit events from the higher buttons. No, I haven't rebooted under a
later 2.6 kernel still to check if it's cured.

Under 2.4.22 the driver is


usbmouse 2592 0 (unused)
input 5216 0 [usbmouse hid mousedev]
usb-uhci 25956 0 (unused)
usbcore 71840 1 [usbmouse hid usb-uhci]


(it'll show "unused" when X isn't engaging the extra mouse) And the
relevant bit of XF86Config-4 for "XFree86 Version 4.2.1 Debian 4.2.1-3
20030201050042 root@lab.it.uc3m.es)" is

InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "USB Mouse" "SendCoreEvents"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
^^^^^^^^^^^^^^^^^^^^
Option "Buttons" "5"
# This shouldn't hurt..
Option "Emulate3Buttons"
EndSection

(the keyboard PS/2 mouse trackpointer is my main mouse, and that is
using device type IMPS/2 too, with the same config as above, except
pointed at /dev/mouse, plus Option "SendCoreEvents").

I BELIEVE that under 2.6 kernels, the driver is STILL "usbmouse". Now
why has it stopped producing button 4 and 5 events, if it has? Mozilla
IS receiving input from that extra mouse - I can click and move with it
happily. Just no scroll.

My mozilla prefs.js file seems to contain:

user_pref("mousewheel.withaltkey.action", 3);
user_pref("mousewheel.withcontrolkey.action", 2);
user_pref("mousewheel.withnokey.numlines", 2);
user_pref("mousewheel.withnokey.sysnumlines", false);
user_pref("mousewheel.withshiftkey.action", 1);

but then I knew it was musewheel aware! The problem is that there seem
to be no wheel (i.e. button 4/5) events generated under 2.6.

No - no distribution in particular. Debian potato, much hacked.


Peter

In comp.os.linux.setup Peter T. Breuer <ptb@oboe.it.uc3m.es>:
[stuff]

> Nevertheless, I have just noticed that when I reboot my TP X24 laptop
> under the 2.6.3 kernel, my external USB mouse scroll button stops moving
> pages in mozilla 6.x. It works fine in 2.4.22 (wot I am using now). I
> only "noticed" because I never usually reboot - I last rebooted over
> six months ago, according to the log.

> Any idea if there's some reconfiguration to be done for 2.6? Nothing
[stuff]

> but then I knew it was musewheel aware! The problem is that there seem
> to be no wheel (i.e. button 4/5) events generated under 2.6.A

'xev' should tell.

> No - no distribution in particular. Debian potato, much hacked.

Looks like a pretty ancient kernel you should upgrade. Anyway
under 2.6 needed the following (lilo.conf append line) to make
my pointing devices working probably: "psmouse.proto=imps". Never
tested if it is still needed running 2.6.14, it's just there and
my Kensington USB trackball works like a charm.

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 304: routing problems on the neural net

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

On Tue, 22 Nov 2005 23:54:39 +0100, Peter T. Breuer
<ptb@oboe.it.uc3m.es> wrote:
>
> Yerrrs. And what is a person supposed to do when he ALSO runs a 2.4
> kernel? (and reboots every six months).
>
I'm just wondering, do you use 2.4 in summer and 2.6 in winter, or the
reverse?



--
Ginsburg's Law:
At the precise moment you take off your shoe in a shoe store, your
big toe will pop out of your sock to see what's going on.

In comp.os.linux.setup Peter T. Breuer <ptb@oboe.it.uc3m.es>:
> Michael Heiming <michael+USENET@www.heiming.de> wrote:
[stuff]

>> 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.

Sure, but it remains old and buggy, a more recent version might
handle your multiple pointing devices better.

>

>> 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
[..]

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

It's some time, but iirc grep helped:

/usr/src/linux/Documentation/kernel-parameters.txt

[..]

> 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.

From my XF86Config:

Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "no"
Option "Device" "/dev/input/mice"
Option "Buttons" "13"
Option "ZAxisMapping" "6 7"
Option "SendCoreEvents" "true"

Modules concerning mouse:

usbmouse 5696 0
usbcore 124816 7 usb_storage,usblp,usbmouse,usbhid,ehci_hcd,ohci_hc d


>> 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!

Seems like, strange that you are running such an old kernel,
usually look over the ChangeLog, wonder how my system which is
working rock stable could boot up at all with all those bugs that
have been gladly fixed now. AFAIK, USB wasn't that great with
early 2.6 kernels but has improved tremendously, there were many
changes and a couple of other improvements, you shouldn't miss
just because of insisting on your uptime. ;-)

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 38: secretary plugged hairdryer into UPS

Bill Marcum <bmarcum@iglou.com> wrote:
> On Tue, 22 Nov 2005 23:54:39 +0100, Peter T. Breuer
> <ptb@oboe.it.uc3m.es> wrote:
>>
>> Yerrrs. And what is a person supposed to do when he ALSO runs a 2.4
>> kernel? (and reboots every six months).
>>
> I'm just wondering, do you use 2.4 in summer and 2.6 in winter, or the
> reverse?

Depends which hemisphere I'm in.

Peter

Michael Heiming <michael+USENET@www.heiming.de> wrote:

>> :-). 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.

> Sure, but it remains old and buggy, a more recent version might
> handle your multiple pointing devices better.

It's not an old kernel - it's a nice kernel. The 2.6.recent series is
not stable on my machine - mouse motion tends to lock it up, probably
because I run SMP and preempt, and the finer grained locking in the
2.6 kernels tickles a bug somewhere that is shown up by my single cpu.
2.6.3 is usually alright for a couple of weeks work, but anything more
recent than that barely lasts a few hours.

It's probably a spurious irq from the hardware - as the machine ages it
seems to trigger the condition more frequently. I've more or less gone
back to 2.4 permanently on it, since I'm not doing kernel development
on it at the moment, but "just" writing papers. If I were doing
development, 2.6 would be bearable since I'd have to reboot frequently
anyway.

> /usr/src/linux/Documentation/kernel-parameters.txt

I see. Nothing for usbmouse, though.

>> Sigh - somebody has made a mess there.

> From my XF86Config:

> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "ExplorerPS/2"
> Option "Emulate3Buttons" "no"
> Option "Device" "/dev/input/mice"
> Option "Buttons" "13"
> Option "ZAxisMapping" "6 7"
> Option "SendCoreEvents" "true"

That's your ps mouse for 2.6, no? But it wouldn't work under 2.4.
Or is it a real usb mouse? Maybe.

> Modules concerning mouse:

> usbmouse 5696 0
> usbcore 124816 7 usb_storage,usblp,usbmouse,usbhid,ehci_hcd,ohci_hc d



Peter

In comp.os.linux.setup Peter T. Breuer <ptb@oboe.it.uc3m.es>:
> Michael Heiming <michael+USENET@www.heiming.de> wrote:

[..]

>> /usr/src/linux/Documentation/kernel-parameters.txt

> I see. Nothing for usbmouse, though.

Hard to tell, it's just that "psmouse.proto=imps" works fine for
me, but I can't not tell for sure what kind of pointing device
was used when I added this line.

>>> Sigh - somebody has made a mess there.

>> From my XF86Config:

>> Identifier "Mouse0"
>> Driver "mouse"
>> Option "Protocol" "ExplorerPS/2"
>> Option "Emulate3Buttons" "no"
>> Option "Device" "/dev/input/mice"
>> Option "Buttons" "13"
>> Option "ZAxisMapping" "6 7"
>> Option "SendCoreEvents" "true"

> That's your ps mouse for 2.6, no? But it wouldn't work under 2.4.
> Or is it a real usb mouse? Maybe.

It's a real USB mouse (Kensington Trackball), can't remember with
2.4 anymore, since I switched some fs to LVM2 they can not be
read anymore from kernel 2.4, so it wouldn't make much sense
booting 2.4.

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 407: Route flapping at the NAP.

Michael Heiming <michael+USENET@www.heiming.de> wrote:
> It's a real USB mouse (Kensington Trackball), can't remember with
> 2.4 anymore, since I switched some fs to LVM2 they can not be
> read anymore from kernel 2.4, so it wouldn't make much sense
> booting 2.4.

You can patch the device mapper module into 2.4. I did. That's enough
for lm2.

/usr/local/src/linux-2.4.22-xfs/drivers/md/dm.c
/usr/local/src/linux-2.4.22-xfs/drivers/md/dm.c.pre-dm00001
/usr/local/src/linux-2.4.22-xfs/drivers/md/dm.c.pre-dm00007

Hmm .. I seem to have patched up to dm00013 at least!




Peter

In comp.os.linux.setup Peter T. Breuer <ptb@oboe.it.uc3m.es>:
> Michael Heiming <michael+USENET@www.heiming.de> wrote:
>> It's a real USB mouse (Kensington Trackball), can't remember with
>> 2.4 anymore, since I switched some fs to LVM2 they can not be
>> read anymore from kernel 2.4, so it wouldn't make much sense
>> booting 2.4.

> You can patch the device mapper module into 2.4. I did. That's enough
> for lm2.

Good to know. Won't go back to 2.4, if you can have 2.6 with all
the bells and whistles. ;-)

Did you solve your pointing device problems in the meantime?

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 257: That would be because the software doesn't
work.