You are not logged in.

#1 2005-10-31 22:31:39

whargoul
Member
From: Odense, Denmark
Registered: 2005-04-04
Posts: 546

evdev won't work?

I have tried to get evdev to work, but it isn't working?

/etc/X11/xorg.conf

---------
Identifier  "EvdevMouse"
    Driver      "mouse"
    Option "Protocol"    "evdev"
    Option "Device"      "/dev/input/event1"
    Option "Dev Name"    "Logitech MX1000"
    Option "ZAxisMapping" "4 5"
    Option "Buttons"     "5"
--------

lsmod:

[root@matrix ~]# lsmod | grep evdev
evdev                   7808  0
[root@matrix ~]#

/var/log/Xorg.0.log:

 ---------
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain)
(II) XINPUT: Adding extended input device "EvdevMouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(**) Option "Dev Name" "Logitech MX1000"
(EE) EvdevMouse: cannot open input device
No core pointer

Fatal server error:
failed to initialize core devices

Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

What is the problem?


Arch - It's something refreshing

Offline

#2 2005-10-31 22:34:08

whargoul
Member
From: Odense, Denmark
Registered: 2005-04-04
Posts: 546

Re: evdev won't work?

Oh, could it be because I plugged my mouse into a PS/2 port instead of USB?

EDIT: No that didn't help.


Arch - It's something refreshing

Offline

#3 2005-10-31 22:40:02

elasticdog
Member
From: Washington, USA
Registered: 2005-05-02
Posts: 995
Website

Re: evdev won't work?

I'm not on my home machine right now, but I believe that you have to have an option that labels a <code>CorePointer</code>.  Take a look at the wiki article regarding mouse buttons for an example.

If that's not the issue, I can double check my settings once I get home tonight.

Offline

#4 2005-10-31 22:51:03

whargoul
Member
From: Odense, Denmark
Registered: 2005-04-04
Posts: 546

Re: evdev won't work?

I Have followed that How to, and it didn't work either.

Some more info:

[whargoul@matrix ~]$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0002 Version=000f
N: Name="PS2++ Logitech MX Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=143

I: Bus=0003 Vendor=046d Product=c50e Version=2500
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:02.0-1/input0
H: Handlers=mouse1 event2
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143

[whargoul@matrix ~]$

xorg.conf ServerLayouts:

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

#    InputDevice "Mouse1" "CorePointer"
    InputDevice "EvdevMouse" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Arch - It's something refreshing

Offline

#5 2005-10-31 23:49:04

elasticdog
Member
From: Washington, USA
Registered: 2005-05-02
Posts: 995
Website

Re: evdev won't work?

It looks like you might be missing your Dev Phys option, which could be important.  I think you might also want to switch over to using  <code>/dev/input/mice</code> for your Device section to let the kernel decide how it should be setup.  That way you won't have to worry if it's plugged into PS/2 or USB.  Your Dev Name also doesn't match up exactly to what's shown when running <code>cat /proc/bus/input/devices</code>, but I doubt that is causing the issue.

Taking all of that into account, you should have something more like this:

Section "InputDevice"
    Identifier    "Configured Mouse"
    Driver         "mouse"
    Option         "CorePointer"
    Option         "Protocol"         "evdev"
    Option         "Dev Name"         "PS2++ Logitech MX Mouse"
    Option         "Dev Phys"         "isa0060/serio1/input0"
    Option         "Device"           "/dev/input/mice"
    Option         "Buttons"          "5"
    Option         "ZAxisMapping"   "4 5"
EndSection

To get all the buttons working properly, you might have to adjust your settings...you can test what signals are being sent with the <code>xev</code> command typed into a console when you're running X.  You might also want to set the proper <code>Resolution</code> option to make sure all of that laser accuracy isn't lost.

Hopefully something in there will help you out  big_smile

Offline

#6 2005-11-01 15:15:22

whargoul
Member
From: Odense, Denmark
Registered: 2005-04-04
Posts: 546

Re: evdev won't work?

Yeah it works now, though my scroll whell won't work now.

Identifier  "EvdevMouse"
    Driver      "mouse"
    Option "CorePointer"
    Option "Protocol"    "evdev"
    Option "Device"      "/dev/input/event1"
    Option "Dev Phys"    "isa0060/serio1/input0"
    Option "Dev Name"    "PS2++ Logitech MX Mouse"
    Option "ZAxisMapping" "11 12"
    Option "Buttons"     "12"

EDIT: My scroll whell seems to be working when starting from GDM.


Arch - It's something refreshing

Offline

#7 2005-11-01 18:58:05

elasticdog
Member
From: Washington, USA
Registered: 2005-05-02
Posts: 995
Website

Re: evdev won't work?

What you can do is check how the buttons are mapped when you log in using GDM and then check out how they're mapped when not using that.  The command is <code>xmodmap -pp</code> and should give you something like this:

$ xmodmap -pp
There are 7 pointer buttons defined.

    Physical        Button
     Button          Code
        1              1
        2              2
        3              3
        4              6
        5              7
        6              4
        7              5

If they're not the same when you log in using GDM and when you don't, look for where it might be changing the order. The command to change the order would be something like this:

$ xmodmap -e "pointer = 1 2 3 6 7 4 5"

Offline

#8 2005-11-04 04:30:10

shadowhand
Member
From: MN, USA
Registered: 2004-02-19
Posts: 1,142
Website

Re: evdev won't work?

"Dev Phys" Shouldn't be necessary (tm). This may not be the case with PS/2 mice.

I wrote that guide, and with testing, removed the "Dev Phys" option because it didn't appear to do anything. If it's necessary for PS/2 mice, please edit the guide accordingly.


·¬»· i am shadowhand, powered by webfaction

Offline

Board footer

Powered by FluxBB