Logitech MX 518 and evdev, wheel stops working.

orjanp · 2005-10-28 08:29:21

This is my mouse input section in xorg.conf

Section "Inputdevice"

    # Logitech MX 510/518

    Identifier    "EvdevMouse"
    Driver        "mouse"
    Option        "Device"        "/dev/input/event3"
    Option        "Dev Name"        "Logitech USB*"
    Option        "Protocol"        "evdev"
    Option        "ZAxisMapping"    "11 12"
    Option        "Buttons"        "12"

EndSection

My .xinitrc

xmodmap -e "pointer = 1 2 3 6 7 8 9 10 11 12 4 5"
imwheel -k -b "67"

This is working fine.
The problem is that the wheel stops working when I disconnect and connect the mouse. To fix it I have to restart X. It is a bit annoying because I'm using a laptop, where I offen have to disconnect the mouse.

Is this fixable?

Oerjan...

mr_brightside · 2005-10-28 08:55:05

I don't suppose yo're using coldplug instead of hotplug?

orjanp · 2005-10-28 08:59:03

I'm using hotplug.

The back and forward button work fine. It's only the wheel that stops working.

Oerjan...

orjanp · 2005-10-28 10:00:36

If I hit <ctrl><alt><F1-F6> to enter text mode and <alt><F7> to go back into X, the wheel works fine again.

Oerjan...

mr_brightside · 2005-10-28 10:40:05

Try putting Option "ZAxisMapping" "4 5" instead of what you've got atm; let us know if it makes any difference.

orjanp · 2005-10-28 10:54:28

Then the wheel don't work at all.

mr_brightside · 2005-10-28 12:17:42

Yeah, I thought it wouldn't, just wanted to check though. I don't know what your problem is tbh... perhape you could try finding the hexcode for the mousewheel using xev and bind the codes for upward-scroll and downward-scroll to the right action in the keybindings file (can't remember where that is... keybindings.conf is it? I haven't edited it for ages) . I'm aware that the wheel works in the first place, but perhaps if you have a binding in there as well, it will act as a safety net.

Worth a shot if nothing else works.

shadowhand · 2005-10-30 19:27:47

mr_brightside wrote:

Try putting Option "ZAxisMapping" "4 5" instead of what you've got atm; let us know if it makes any difference.

ZAxisMapping refers the the last two buttons of the mouse always (ie: a 8 button mouse would be "7 8", 12 buttons "11 12", etc). Just fyi.

Try rerunning the xmodmap command you are using after reconnecting your mouse.

orjanp · 2005-10-30 20:15:20

It didn't make any difference.

I have found out that I get an error from X when I plug in the mouse again

(EE) EvdevMouse: Error in reading! (No such device) Disabiling.

Another ting. X won't start from a reboot if I have no mouse connected. I think it was when I used Slackware, I could modprobe usbmouse, and then I could start X. It does not work in Arch. I have to comment out a line in xorg.conf.
Is there a module that I can modprobe to be able to start X without editing xorg.conf?

shadowhand · 2005-10-31 16:40:55

You can set the "AllowMouseOpenFail" option to true.

orjanp · 2005-11-03 14:30:31

Like this?

Section "Inputdevice" 

   # Logitech MX 510/518 

   Identifier   "EvdevMouse" 
   Driver      "mouse" 
   Option      "Device"      "/dev/input/event3" 
   Option      "Dev Name"      "Logitech USB*" 
   Option      "Protocol"      "evdev" 
   Option      "ZAxisMapping"   "11 12" 
   Option      "Buttons"      "12" 
   Option      "AllowMouseOpenFail"   "true"

EndSection

I still get error

(EE) EvdevMouse: Cannot open input device
No core pointer

Fatal server error
failed to initialize core device

shadowhand · 2005-11-04 04:33:53

Section "Inputdevice" 

   # Logitech MX 510/518 

   Identifier   "EvdevMouse" 
   Driver      "mouse" 
   Option      "Device"      "/dev/input/event3" 
   Option      "Dev Name"      "Logitech USB*" 
   Option      "Protocol"      "evdev" 
   Option      "ZAxisMapping"   "11 12" 
   Option      "Buttons"      "12" 
   Option      "AllowMouseOpenFail"   "true"

EndSection

No, the "AllowMouseOpenFail" option should be under a the server section. Try using

hwd -s -x

and looking at the config file to find the proper syntax/position.

fdac · 2005-11-09 06:48:16

My MX-518 works great with the standard evdev configuration as per the wiki.

However, it only has 10 "buttons" - three clicks, up/down scroll wheel, the back/forward thumb buttons and the 3 extra buttons on top. So my xorg input device section has the lines:

Option      "ZAxisMapping"   "9 10"
Option      "Buttons"     "10"

This worked perfectly, I think I may have also had to write an ~/.Xmodmap for the back/forward buttons because I use GDM.

Francis

orjanp · 2005-11-12 09:11:57

My 518 also works in every way when it is plugged in before I start X.

What happens if you disconnect the mouse and connect it again running X? Does the wheel work?

Oerjan...

Arch Linux

#1 2005-10-28 08:29:21

Logitech MX 518 and evdev, wheel stops working.

#2 2005-10-28 08:55:05

Re: Logitech MX 518 and evdev, wheel stops working.

#3 2005-10-28 08:59:03

Re: Logitech MX 518 and evdev, wheel stops working.

#4 2005-10-28 10:00:36

Re: Logitech MX 518 and evdev, wheel stops working.

#5 2005-10-28 10:40:05

Re: Logitech MX 518 and evdev, wheel stops working.

#6 2005-10-28 10:54:28

Re: Logitech MX 518 and evdev, wheel stops working.

#7 2005-10-28 12:17:42

Re: Logitech MX 518 and evdev, wheel stops working.

#8 2005-10-30 19:27:47

Re: Logitech MX 518 and evdev, wheel stops working.

#9 2005-10-30 20:15:20

Re: Logitech MX 518 and evdev, wheel stops working.

#10 2005-10-31 16:40:55

Re: Logitech MX 518 and evdev, wheel stops working.

#11 2005-11-03 14:30:31

Re: Logitech MX 518 and evdev, wheel stops working.

#12 2005-11-04 04:33:53

Re: Logitech MX 518 and evdev, wheel stops working.

#13 2005-11-09 06:48:16

Re: Logitech MX 518 and evdev, wheel stops working.

#14 2005-11-12 09:11:57

Re: Logitech MX 518 and evdev, wheel stops working.

Board footer