After first installation of 11.3 with KDE I can not use the wheel of my mouse: It’s a Logitech MouseMan+ on PS2.
The reason is a wrong detection - only as a 3-button-type.
Here is the System Information output:
*
65: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.183]
Unique ID: AH6Q.U5GX9Ignjc0
Hardware Class: mouse
Model: “PS/2 Generic Mouse”
Vendor: 0x0002
Device: 0x0001 “PS/2 Generic Mouse”
Compatible to: int 0x0210 0x0003
Device File: /dev/input/mice (/dev/input/mouse0)
Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event1, /dev/char/13:65, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/char/13:32, /dev/input/by-path/platform-i8042-serio-1-mouse, /dev/char/13:63
Device Number: char 13:63 (char 13:32)
Driver Info #0:
Buttons: 3
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=no, avail=yes, need=no, active=unknown*
With 11.2 it was all o.k.:
61: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.183]
UDI: /org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input
Unique ID: AH6Q.GZven06_hT8
Hardware Class: mouse
Model: “PS2++ Logitech Wheel Mouse”
Vendor: 0x0002
Device: 0x0002 “PS2++ Logitech Wheel Mouse”
Compatible to: int 0x0210 0x0014
Device File: /dev/input/mice (/dev/input/mouse0)
Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event1, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse
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
I already tried a modification of the /etc/sysconfig but it had no effect. And with no sax there is no possibility to change it within KDE…
Open up a terminal session like Konsole and enter this command:
grep -i mouse /var/log/Xorg.0.log
Then copy all of the text you get and paste it into a message here in the forum. To make it easier to read after you paste the text into a new message, highlight only the new text and press the editor button labeled #. When you place your mouse pointer over the # symbol it will say “Wrap CODE tags around selected text”.
I must also suggest that if you have any way to switch to a USB mouse, this is what I would do. Problems associated with PS/2 mice detection will become ever more common in the future.
Thank You,
Thank you already - here is the text (0.k., # means “quote”):
21.597] Kernel command line: root=/dev/sda2 resume=/dev/disk/by-id/ata-WDC_WD800BB-00CAA1_WD-WCA8E4629226-part1 splash=silent quiet apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf vga=0x346
43.389] (==) NV(0): Silken mouse enabled
43.885] (II) config/udev: Adding input device Wacom Bamboo (/dev/input/mouse1)
43.885] (**) Option "Device" "/dev/input/mouse1"
43.921] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event1)
43.921] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
43.921] (**) PS/2 Generic Mouse: always reports core events
43.921] (**) PS/2 Generic Mouse: Device: "/dev/input/event1"
43.921] (II) PS/2 Generic Mouse: Found 3 mouse buttons
43.921] (II) PS/2 Generic Mouse: Found relative axes
43.921] (II) PS/2 Generic Mouse: Found x and y relative axes
43.921] (II) PS/2 Generic Mouse: Configuring as mouse
43.921] (**) PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
43.921] (**) PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
43.921] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE)
43.921] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
43.921] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
43.921] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
43.921] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
43.921] (II) PS/2 Generic Mouse: initialized for relative axes.
43.921] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)
As you can see, I also got a Wacom Bamboo (which is working fine now, including it’s “Wheel”).
And your suggestion is right - I tested my very small notebook mouse (USB) and it’s working. So I got to find an ergonomic mouse next time…
So, if using a USB mouse is a solution, I would continue with that. If not, you could modify your xorg.conf file for input devices to look like the following text. Add the section if need be. You would have to restart your PC for this to take effect. Be prepared to delete or put back to original the xorg.conf file if this should keep your mouse from working at all. To edit, use the following KDE menu Run Command:
kdesu kwrite /etc/X11/xorg.conf
The code in question for your mouse is as follows:
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
Option "CorePointer"
Option "SendCoreEvents" "true"
EndSection
You could post what it says now or if it is missing. I think the buttons item is what is up for question here for you and a PS/2 mouse. Be aware you can run with a generic xorg.conf file and newer USB mice may not need a specific entry to work. In some cases deleting the file, allow it to regenerate is also a solution. Incorrect entries can cause all sorts of problems. Make a backup of the original file using a Super User Mode File Manager (where you must enter the root user password).
Thank You,
I tried it but unfortunately it didn’t change anything…
It seems MouseMan+ with PS/2 is already obsolete. But no problem: I think we can call it solved because your recommendation using USB will do it…
Thank you for help!
I am always ready to call a problem solved, just like my IT department does me at work, a minute after I hang up my problem phone call. lol!
Let us know if you need help for anything else and have a great day HeikoHeerlein.
Thank You,