Bugzilla – Bug 116396
MouseMan+ (Logitech; M-CW47) is not recognized well.
Last modified: 2005-10-07 16:22:11 UTC
I have a MouseMan+ from Logitech (model M-CW47), which isn't recognized well by the RC1 system and after manual setup still can't use the wheel on it. (I tried even various settings.) balazska:~ # hwinfo --mouse 17: PS/2 00.0: 10500 PS/2 Mouse [Created at input.157] UDI: /org/freedesktop/Hal/devices/computer_i8042_Aux_Port_logicaldev_input Unique ID: AH6Q.CjzNTUPH+qC Hardware Class: mouse Model: "PS2++ Logitech Wheel Mouse" Vendor: int 0x0210 Device: int 0x0014 "PS2++ Logitech Wheel Mouse" Device File: /dev/input/mice (/dev/input/mouse0) Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event2 Device Number: char 13:63 (char 13:32) Driver Info #0: Buttons: 4 Wheels: 1 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown balazska:~ #
a bit more information is needed. Please call from runlevel 3 as user root the following command: sax2 -r click on "Cancel" and provide the newly created log file /var/log/SaX.log Thanks Regards Marcus
Created attachment 49671 [details] SaX.log in archived form. 'sax2 -r' in 'init 3' I just pushed [ENTER], because the warning was _very_ unreadable and in about 80-85% out of the window :( I have a bloody old PCI video-card (4Mb of RAM) with a rel. good Belinea monitor, so probably I almost killed the whole stuff with the settings sax2 attempted to use there (~1600x1200). So probably there is also something wrong with the recognition of my "ELSA Victory Erazor-4" card. Yeah, it really has Riva128 chip, but I would never put it into 1600x1200... Anyway, I attached the SaX.log now (I changed only the resolution from 1600x1200 to 800x600, nothing else from the 'defaults'), and here is the _newest_ output of 'hwinfo --mouse' (& the wheel still doesn't work): 17: PS/2 00.0: 10500 PS/2 Mouse [Created at input.157] UDI: /org/freedesktop/Hal/devices/computer_i8042_Aux_Port_logicaldev_input Unique ID: AH6Q.CjzNTUPH+qC Hardware Class: mouse Model: "PS2++ Logitech Wheel Mouse" Vendor: int 0x0210 Device: int 0x0014 "PS2++ Logitech Wheel Mouse" Device File: /dev/input/mice (/dev/input/mouse0) Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event2 Device Number: char 13:63 (char 13:32) Driver Info #0: Buttons: 4 Wheels: 1 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown
Hmm, sax is using the following InputDevice section: Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Buttons" "6" Option "Device" "/dev/input/mice" Option "Name" "PS2++ Logitech Wheel Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection This is correct in my opinion because you have 4 buttons and a wheel which is a button to the front and one to the back equals to 6 buttons The wheel is available for button 4 and 5 which is the correct mapping. Are you sure the wheel is not working in the session you started with sax2 -r from runlevel 3 ?
My very first fancy-mouse still doesn' work with RC1 :( Probably you have the same type of mouse, so please let me ask something. The listed _six_ buttons are in fact: - three at the top (=one UNDER the wheel?), - two for the wheel function, - one at the left? Thanks:)
FYI: I tried the same mouse with M$ and SUSE 9.3: the wheel worked well in both cases. (On SUSE 9.3 there was another issue, because the mouse was recognized as IntelliMouse Explorer, thus the lower left button didn't work at all.)