You are not logged in.

Pages: 1

#1 2006-12-22 17:31:16

Crooksey
Member
From: UK ~
Registered: 2006-08-14
Posts: 415
Website

Logitech mx510

Im trying to get all my buttons and mousewheel working, but cant.

xorg.conf 

Section "InputDevice"

    Identifier  "Mouse1"
    Driver      "mouse"
    Option        "Protocol" "PS/2"    # PS/2 Mouse
    Option        "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
    #Option        "ZAxisMapping" "4 5 6 7"
     Option         "ZAxisMapping" "6 7"

Any ideas?

Arch Linux since 2006
Python Web Developer + Sys Admin (Gentoo/BSD)

Offline

#2 2006-12-22 18:06:46

augustob
Member
From: Florianópolis, Brazil
Registered: 2006-03-17
Posts: 135

Re: Logitech mx510

The conf for my MX500: 

Section "InputDevice"
    Identifier   "USB Mouse"
    Driver       "mouse"
    Option       "Device" "/dev/input/mice"
    Option         "SendCoreEvents"    "true"
    Option       "Protocol" "ExplorerPS/2"
    Option       "Buttons" "7"
    Option       "ZAxisMapping" "4 5"
        Option       "ButtonMapping" "1 2 3 6 7"
EndSection

Offline

#3 2006-12-22 18:11:52

ndlarsen
Member
From: Denmark
Registered: 2005-11-02
Posts: 157

Re: Logitech mx510

Use evdev instead, it's easier and works like a charm for me with my mx510. Wiki link.

I made it long
as I lacked the time to make it short...

Offline

#4 2006-12-22 18:30:37

augustob
Member
From: Florianópolis, Brazil
Registered: 2006-03-17
Posts: 135

Re: Logitech mx510

ndlarsen wrote:

Use evdev instead, it's easier and works like a charm for me with my mx510. Wiki link.

How can anything be easier than just an entry on xorg.conf? Also isn't evdev deprecated in xorg 7.1?

Offline

#5 2006-12-22 19:34:32

detto
Member
Registered: 2006-01-23
Posts: 510

Re: Logitech mx510

for reference (works fine for my mx510) 

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option       "Protocol" "auto"
    Option       "Device" "/dev/input/mice"
    Option       "ZAxisMapping" "6 7"
    Option      "Buttons" "7"
EndSection

Offline

#6 2006-12-22 19:45:42

Crooksey
Member
From: UK ~
Registered: 2006-08-14
Posts: 415
Website

Re: Logitech mx510

Whenever i change my mouse feature, i get "no screens found"

My entire xorg.conf is below, would someone with a working mouse sub in the relevant info, allowing for X to run correctly, as i have tried configs people posted here, and ones of the wiki, but X just wont start. 

Section "ServerLayout"

# The Identifier line must be present
# 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.
# 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".
   Identifier     "Simple Layout"
   Screen      0  "aticonfig-Screen[0]" 0 0
   InputDevice    "Mouse1" "CorePointer"
   InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
#    RgbPath   "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
#    FontPath   "/usr/share/fonts/TTF"
#    FontPath   "/usr/share/fonts/Type1"
#    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"
# The module search path.  The default path is shown here.
#    ModulePath "/usr/lib/modules"
   FontPath     "/usr/share/fonts/misc"
   FontPath     "/usr/share/fonts/75dpi"
   FontPath     "/usr/share/fonts/100dpi"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
#    Load        "type1"
#    Load        "speedo"
# This loads the GLX module
#    Load       "glx"
# This loads the DRI module
#    Load       "dri"
   Load  "dbe"     # Double buffer extension
   SubSection "extmod"
      Option       "omit xfree86-dga"   # don't initialise the DGA extension
   EndSubSection
   Load  "freetype"
#    Load        "xtt"
   Load  "dri"
   Load  "glx"
EndSection

Section "InputDevice"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
#    Option     "Protocol"      "Xqueue"
#    Option   "Xleds"      "1 2 3"
#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"
# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""
#    Option "XkbDisable"
   Identifier  "Keyboard1"
   Driver      "kbd"
   Option       "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
   Option       "XkbRules" "xorg"
   Option       "XkbModel" "cherryblueb"
   Option       "XkbLayout" "gb"
EndSection

Section "InputDevice"

# Identifier and driver
# the following line.
#    Option "Protocol"   "Xqueue"
# Mouse-speed setting for PS/2 mouse.
#    Option "Resolution"   "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
#    Option "BaudRate"   "9600"
#    Option "SampleRate"   "150"
# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"
# ChordMiddle is an option for some 3-button Logitech mice
#    Option "ChordMiddle"
   Identifier  "Mouse1"
   Driver      "mouse"
   Option       "Protocol" "PS/2"   # PS/2 Mouse
   Option       "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
   Option       "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection

Section "Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    HorizSync   30-64         # multisync
#    HorizSync   31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync   15-25, 30-50  # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
   Identifier   "Sync0"
   HorizSync    31.5 - 64.3
   VertRefresh  75.0 - 81.0
EndSection

Section "Monitor"
   Identifier   "aticonfig-Monitor[0]"
   Option       "VendorName" "ATI Proprietary Driver"
   Option       "ModelName" "Generic Autodetecting Monitor"
   Option       "DPMS" "true"
EndSection

Section "Device"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.
#    Chipset   "generic"
# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.
#    BusID      "PCI:0:10:0"
#    VideoRam   256
#    Clocks   25.2 28.3
   Identifier  "Standard VGA"
   Driver      "vga"
   VendorName  "Unknown"
   BoardName   "Unknown"
EndSection

Section "Device"

    #VideoRam    262144
    # Insert Clocks lines here if appropriate
   Identifier  "ati0"
   Driver      "ati"
EndSection

Section "Device"
   Identifier  "aticonfig-Device[0]"
   Driver      "fglrx"
   Option       "DesktopSetup" "horizontal"
   Option       "OverlayOnCRTC2" "1"
EndSection

Section "Screen"
   Identifier "Screen 1"
   Device     "ati0"
   Monitor    "Sync0"
   DefaultDepth     24
   SubSection "Display"
      Viewport   0 0
      Depth     8
      Modes    "1280x1024" "1024x768" "800x600" "640x480"
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     16
      Modes    "1280x1024" "1024x768" "800x600" "640x480"
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     24
      Modes    "1280x1024" "1024x768" "800x600" "640x480"
   EndSubSection
EndSection

Section "Screen"
   Identifier "aticonfig-Screen[0]"
   Device     "aticonfig-Device[0]"
   Monitor    "aticonfig-Monitor[0]"
   DefaultDepth     24
   SubSection "Display"
      Viewport   0 0
      Depth     24
   EndSubSection
EndSection

Arch Linux since 2006
Python Web Developer + Sys Admin (Gentoo/BSD)

Offline

#7 2006-12-22 20:59:25

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

Re: Logitech mx510

I hadn't heard anything about <code>evdev</code> being depreciated (hopefully it's not, since that's what I use for my MX510)...here's the relevant section of my <code>xorg.conf</code>: 

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "evdev"
    Option      "Dev Name"       "PS2++ Logitech MX Mouse"
    Option      "Dev Phys"       "isa0060/serio1/input0"
    Option      "Device"         "/dev/input/event1"
    Option      "Resolution"     "800"
    Option      "SampleRate"     "150"
EndSection

I am using it with a PS/2 adapter and not with USB since I have it hooked up to a KVM, but I don't think I had to do anything else special to get all the buttons working.  I might be wrong about that thought since it has been a while since I had to deal with it...

Offline

#8 2006-12-22 22:31:16

ndlarsen
Member
From: Denmark
Registered: 2005-11-02
Posts: 157

Re: Logitech mx510

Well, the "no screens found" error has got nothing to do with your mouse setting, not unless it's a bug that I am not aware of.
Here is a mouse related snippet from from xorg.conf. 

Section "InputDevice"

        Identifier "mx510"
        Driver  "evdev"
        Option  "Name"  "PS2++ Logitech MX Mouse"

EndSection

Now, I am not familiar with ati cards under linux but it seems that you have neither configured the display modes correctly in the appropiate screen section nor the refresh and sync settings in the appropiate monitor section.

I made it long
as I lacked the time to make it short...

Offline

#9 2006-12-22 22:47:30

ndlarsen
Member
From: Denmark
Registered: 2005-11-02
Posts: 157

Re: Logitech mx510

Well, decided to add my entire xorg.conf for reference, hope it helps you out. 

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"      # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath    "/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/share/fonts/misc"
    FontPath   "/usr/share/fonts/75dpi"
    FontPath   "/usr/share/fonts/100dpi"
    FontPath   "/usr/share/fonts/TTF"
    FontPath   "/usr/share/fonts/Type1"
    #FontPath   "/usr/lib/X11/fonts/local/"
    #FontPath   "/usr/lib/X11/fonts/misc/"
    #FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
    #FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
    #FontPath   "/usr/lib/X11/fonts/Speedo/"
    #FontPath   "/usr/lib/X11/fonts/Type1/"
    #FontPath   "/usr/lib/X11/fonts/TrueType/"
    #FontPath   "/usr/lib/X11/fonts/freefont/"
    #FontPath   "/usr/lib/X11/fonts/75dpi/"
    #FontPath   "/usr/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_>/<KP_> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier    "Keyboard1"
    Driver        "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option    "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"    "xorg"
    Option "XkbModel"    "pc105"
    Option "XkbLayout"    "dk"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier "mx510"
    Driver    "evdev"
#    Option    "Device"    "/dev/input/event9"
    Option    "Name"    "PS2++ Logitech MX Mouse"

EndSection

Section "InputDevice"

# Identifier and driver

    Identifier    "Mouse1"
    Driver    "mouse"
    Option "Protocol"    "Auto"    # Auto detect
    Option "Device"      "/dev/input/mice"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"    "Xqueue"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"    "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"    "9600"
#    Option "SampleRate"    "150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice" 
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "phillips 190s"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   30 - 83

#    HorizSync    30-64         # multisync
#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 56-76

EndSection

Section "Monitor"

    Identifier    "aoc spectrum 7g"
    
    HorizSync    30-95

    VertRefresh    50-160

EndSection

# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier    "Standard VGA"
    VendorName    "Unknown"
    BoardName    "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam    256

#    Clocks    25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "geforce 6600gt"
    Driver      "nvidia"
    Option    "NoLogo"    "1"
    VideoRam    262144
    # Insert Clocks lines here if appropriate
#EndSection

#Section "Device"

#    Option     "TwinView"
#    Option     "MetaModes"  "1280x1024,1280x1024; 1280x1024; 1024x768,1024x768; 1024x768; 800x600,800x600; 800x600"
#    Option     "TwinViewOrientation"      "RightOf"
#    Option     "SecondMonitorHorizSync"   "30-95"
#    Option     "SecondMonitorVertRefresh" "50-160"

#EndSection

#Section "Device"

#    Option "ConnectedMonitor" "LCD,CRT"

EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "geforce 6600gt"
    Monitor     "phillips 190s"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# 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    "mx510"    "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

I made it long
as I lacked the time to make it short...

Offline

#10 2008-06-13 18:04:26

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 702

Re: Logitech mx510

I have some problems with configuring buttons No 9 and 10 of my MX510. I have never had any problems with my mouse in the system, nor in Firefox and Konqueror. The problem is my favorite web browser is Opera and it seems to have some minor issues with aforementioned buttons. The funny thing is I've also used Opera on Mandriva before and didn't notice this kind of behavior described below.
I've tried dozens of xorg.conf examples, also I was modifying it by myself but in vain so far. I've also tested advice from our wiki, but even xvkbd and xbindkeys didn't help me much.
Here's my present InputDevice section

Section "InputDevice"
        Identifier  "Mouse1"
        Driver       "evdev"
        Option      "Device" "/dev/input/event4" # (cat /proc/bus/input/devices)
        Option      "Name" "Logitech MX510"
EndSection

and here is ~/.xbindkeysrc

# Mouse Buttons
"/usr/bin/xvkbd -xsendevent -text "Navigate up""
m:0x0 + b:4+9
"/usr/bin/xvkbd -xsendevent -text "Navigate down""
m:0x0 + b:5+10
"/opt/kde/bin/konsole"
  b:8

Now the problem as I understand it lies in the signals that my mouse sends, but only signals of buttons 9 (UPWARD) & 10 (DOWNWARD) - below the output of xev.

"UPWARD"

ButtonPress event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1798476, (89,155), root:(774,184),
    state 0x0, button 9, same_screen YES

ButtonPress event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1798476, (89,155), root:(774,184),
    state 0x0, button 4, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1798476, (89,155), root:(774,184),
    state 0x800, button 4, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1798612, (89,155), root:(774,184),
    state 0x0, button 9, same_screen YES

"DOWNWARD"

ButtonPress event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1856325, (120,110), root:(805,139),
    state 0x0, button 10, same_screen YES

ButtonPress event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1856325, (120,110), root:(805,139),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1856325, (120,110), root:(805,139),
    state 0x1000, button 5, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x3000001,
    root 0x8b, subw 0x0, time 1856725, (120,110), root:(805,139),
    state 0x0, button 10, same_screen YES

As you can see above when the button 9 is pressed, the mouse sends signal "9+4", and while it is released it sends "4+9". The button No 10 is acting similarly. Strangely enough it's not a problem to Firefox, but in Opera some strange things happen like text being marked (see screen shot below), menus being prompted or view being change.

aaab9e2bac14a877m.png

Are there any Opera users with similar problems who managed to resolve this?

P.S. I also tested mouse driver but then button No 9 didn't work at all, and the number of buttons was decreased so some of them were sending the same signals.

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#11 2008-06-13 19:01:10

gajo
Member
Registered: 2008-04-01
Posts: 93
Website

Re: Logitech mx510

This is my mouse xorg entry

Section "InputDevice"
    Identifier     "Logitech MX510"
    Driver         "mouse"
    Option         "CorePointer"
    Option         "Device" "/dev/input/mice"
    Option         "Buttons" "7"
    Option         "ZAxisMapping" "4 5"
    Option         "ButtonMapping" "1 2 3 6 7 4 5"
EndSection

Offline

#12 2008-06-14 08:49:18

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 702

Re: Logitech mx510

I tried something similar before, but as I mentioned above the "mouse" driver doesn't seem to recognize all of my buttons. Do you use Opera? How is your mouse buttons 9 & 10 acting there if so?

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#13 2008-06-14 09:59:01

gajo
Member
Registered: 2008-04-01
Posts: 93
Website

Re: Logitech mx510

i don't, but i do use firefox and some games, and this setup works the same as the default config in windows, that is it works as it should

Offline

#14 2008-06-14 11:21:08

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 702

Re: Logitech mx510

I've never said it wasn't working in Firefox or games. I'm having this issues on Opera exclusively but only on Arch, not in Mandriva.

Last edited by Zibi1981 (2008-06-14 13:25:39)

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#15 2008-06-14 12:28:14

gajo
Member
Registered: 2008-04-01
Posts: 93
Website

Re: Logitech mx510

ahh, sorry, i didn't really read your post, my first answer was directed to the thread starter
anyway, there was thing one thing in other distros i remember - i think it was in Mandriva as well, they had a lot of additional files/directories in the /etc/X11 folder, i didn't go far into understanding what they really did, since i didn't plan on staying long with mandriva, but iirc they remapped mouse bindings which annoyed me in general, f.e instead of getting raw mouse inputs i would get something like ctrl+left arrow and ctrl+right arrow
so i suggest you check how mandriva deals with it, and how they remap it, perhaps try and reproduce that in arch linux, not sure if you can do it so it works per application which would be preferably obviously, but that would be my course of action

Offline

#16 2008-06-15 10:30:43

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 702

Re: Logitech mx510

Related question: how to make xbindkeys start on system boot? I've tried to put it in rc.conf in both DAEMONS and MODULES sections but that didn't work.

"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI Raider GE78HX 13VI-032PL

Offline

#17 2008-06-15 10:40:51

moljac024
Member
From: Serbia
Registered: 2008-01-29
Posts: 2,676

Re: Logitech mx510

Zibi1981 wrote:

Related question: how to make xbindkeys start on system boot? I've tried to put it in rc.conf in both DAEMONS and MODULES sections but that didn't work.

xbindkeys is not a module nor a daemon, so you can't start it that way. You have to add it to the autostart script according to your WM/DE.

If you use

GNOME: Add it to session startup, you can find it in administration somewhere
KDE: Add a link to it in ~/.kde/autostart (or sth like that)
Openbox: add it to your ~/.config/openbox/autostart.sh
Other WMs: add to .xinitrc or if you use GDM or KDM, make a script.

The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...

Offline

#18 2008-06-16 00:38:01

heleos
Member
From: Maine, USA
Registered: 2007-04-24
Posts: 678

Re: Logitech mx510

I have a G5, but I have my single back button working in opera fine.

xorg.conf mouse:

Section "InputDevice"
    Identifier       "Evdev Mouse"
    Driver       "evdev"
    Option         "Name" "Logitech USB Gaming Mouse"
    Option         "Device" "/dev/input/event2"
EndSection

and xbindkeysrc (from the wiki entry):

"/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:8

Offline

Pages: 1

Board footer

Powered by FluxBB