5 button wheel mouse (tried all forums)

Section "InputDevice"

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"

Option "Device" "/dev/mouse"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
EndSection


this is the input section from my XF86Config file, my log file shows that this is the file that X is using, but whenever i type xmodmap -e "pointer = 1 2 3 6 7 4 5" it tells me that i have the incorrect number of buttons and that it needs to be 3 buttons instead of 7, ive tried changing every XF86Config file on my computer to this, and no such luck, it just will not recognize that I have declared more than 3 buttons to my mouse, any ideas? Been searching the forums and the web all night with no luck, any help would be appreciated

also, /dev/mouse if a symbolic link to /dev/psaux, and my mouse is a ps2 mouse

running slackware 9.1

Yes well I'm afraid that's as far as your going to get. There is only support for up to 3 buttons on your mouse(usually the middle wheel counts as a button). I have yet to see anyone get those extra buttons on their mice to work. That's why usually even in windows you have to use software from the manufacturer to use those buttons cause even windows doesn't know what to do with those 4 extra buttons without software to configure them.

In fact, it is possible to get your extra mouse buttons to work. But, it depends on what you want to do with them. After you start X with that configuration, run xev in a terminal, and see if it registers your buttons. If you have a back button on the mouse, and you want it to go back in history in your browser, you will need IMWheel to translate the button press into an Alt+Left keystroke.

Ian

Huh, that's interesting. I've never seen that before. good thing to know.

uhm, not sure if this applies, but change protocol to IMPS/2, change ZAxisMapping to "4 5" thats how mine is, but if u use explorer mouse now it is likely a different issue/mouse type and such

now, i am very drunk, so forgive me if i mispell or whatever, but i do know what i have tried, i tried the imPS/2 protocol, no luck with that, i have also tried changing Option "Buttons" "7" to Option "Buttons" "5" with no avail, i also mapped the zmappingaxis to 4 5 with no luck, it still said that i only had 4 buttons on my mouse but i have edited every XF86Config file on my computer, even the ones that the XFree96.log.0 file said it wasnt using, im completely shot out of ideas, and my face hurts
im going to sleepy, but i really really really, appreciate your guys help, regardless of whether it solves the problem or not, at least you were willing to post and try to help me, thank you, my email address is macken@mchsi.com if you need help with something let me know and i will do my best to help you out

support on only 3 buttons for a mouse makes me sad, the linux community is so much better than the windows community, i know it can do better then that

it does do better than that, the problem is eather some slight mistake we aren't catching liek a misspelling in your config, or the problem is specific to your mouse. I have 7 buttons w/ scroller wheel working on a standard logitech wheelmouse usb.

# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# 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 XFREE86 PROJECT 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 XFree86 Project 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
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me.

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy!
# -- volkerdi@slackware.com
#

# **********************************************************************
# 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 "freetype"
Load "speedo"

# This loads the GLX module
Load "glx"

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/X11R6/lib/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)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

# ModulePath "/usr/X11R6/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 <Crtl><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 <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

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

# Option "DontZoom"

# 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"

# Set the basic blanking screen saver timeout.

# Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option "standby time" "20"
# Option "suspend time" "30"
# Option "off time" "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option "EstimateSizesAggresively" "0"

Option "NoLogo" "true"
# Disable drawing of the NVIDIA logo splash screen at
# X startup. Default: the logo is drawn.

# Option "UseEdidFreqs" "true"
# This option causes the X server to use the HorizSync
# and VertRefresh ranges given in a display device's EDID,
# if any. EDID provided range information will override
# the HorizSync and VertRefresh ranges specified in the
# Monitor section. If a display device does not provide an
# EDID, or the EDID does not specify an hsync or vrefresh
# range, then the X server will default to the HorizSync
# and VertRefresh ranges specified in the Monitor section.

EndSection

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

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

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"
# 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"

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

# Option "AutoRepeat" "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# 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 XFree86
#
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option "Protocol" "Auto"

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 Mouse1 IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option "Protocol" "ExplorerPS/2"

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.


Option "Device" "/dev/mouse"
# Option "Device" "/dev/mouse"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"

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

# Option "Protocol" "Xqueue"

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

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

# Emulate3Buttons is an option for 2-button Microsoft 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

# Some examples of extended input devices

# 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 "My 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-96

# HorizSync 30-96 # 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 50-160

vendorname "[NEC]"
modelname "[MultiSync FE991sb]"
ModeLine "1024x768/85Hz" 65 1024 1032 1176 1344 768 771 777 806 -HSync -VSync
ModeLine "1280x1024/85Hz" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +HSync +VSync
ModeLine "1152x900/58Hz" 80 1152 1208 1368 1474 900 901 911 932
ModeLine "1024x768/100Hz" 115.5 1024 1056 1248 1440 768 771 781 802 -HSync -VSync
EndSection


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

# Any number of graphics device sections may be present

Section "Device"
Identifier "nvidia"
Driver "nvidia"
#VideoRam 4096
# Insert Clocks lines here if appropriate
vendorname "vesa"
boardname "Generic"
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 "nvidia"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1024x768/85Hz" "800x600" "640x480"
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768/85Hz" "800x600" "640x480"
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768/85Hz" "800x600" "640x480"
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768/85Hz" "800x600" "640x480"
Virtual 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 "Keyboard1" "CoreKeyboard"

EndSection


Section "InputDevice"

Identifier "Keyboard"

Option "XkbModel" "microsoft"
Option "XkbLayout" "us"
Driver "keyboard"
EndSection


Section "InputDevice"

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"

Option "Device" "/dev/mouse"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
EndSection


its like linux doesnt even recognize the mouse potion of the config file, i know it reads the monitor and graphics card area because thats all setup properly, is there something that disables this or?

You have two input device listings

you only need one, and it should look something like mine:

Section "InputDevice"
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "ExplorerPS/2"
    Option "Device" "/dev/psaux"
    Option "ZAxisMapping" "6 7"
EndSection

then in your ~/.xinitrc, add the following line:

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

if you install imwheel, add the following to ~/.xinitrc:

 imwheel -k -f -b "0067"

create a file called ~/.imwheelrc that contains the following:

".*"
 None, Left, Alt_L|Left
 None, Right, Alt_L|Right

and scroll wheel will work. left side button goes back in web page, right side button goes forward in web page.

How's your hangover?

# 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 "Keyboard1" "CoreKeyboard"

EndSection


Section "InputDevice"

Identifier "Keyboard"

Option "XkbModel" "microsoft"
Option "XkbLayout" "us"
Driver "keyboard"
EndSection


Section "InputDevice"

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"

Option "Device" "/dev/mouse"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
EndSection

you said i have 2 input devices and that i only need to list one, not exactly sure what you meant by that, but i commented off the one line (see above) with no luck, still says that my mouse only has 3 buttons, could this have anything to do wtith gpm? ive tried disabling that also but it didnt seem to have any affect either

i appreciate all of the help, and no hangover actually
thanks for asking though

its a MS intellimouse explorer btw

I think what bnice is referring to is you have two identifiers with the same name. "Mouse1". One is at the bottom and the other is up in the middle of the config file (right below the "Core Pointer's InputDevice section").....................Simply rename the Identifier tag for the one you don't want to use to "Mouse". In other words you have two lines that read:

Identifier "Mouse1"

This might be causing some conflict, like reading the first one and not reading the one you want to use. By changing the identifier name, it should work as intended. These Identifier tags must have unique names for each device to avoid confusion for XFree86.

You want to name the mouse Identifier tag you want to use to match the Server Layout's line at the bottom:

InputDevice "Mouse1" "CorePointer"

HTH
---thegeekster




Edit: typos

thanks for all the help guys, got it fixed

other than making changes to so many files, is there any way to get a 3 button scroll mouse to work? i don't wanna try all these steps straight off. it's a ps2 mouse. got two buttons. the third is a scroll wheel which can be clicked. it's button3/middle-button and i know it 'clicks' coz netscape can identify it. i've tried the zaxismapping 4 5 line but that doesn't work either. and can the solution be made effective for all users of a system and not have to add it for each user?

editing all of those files isnt really that hard, but if you edit /etc/X11/xinit/xinitrc then if the user doesn't have his own .xinit file in his home directory then it uses that file so you dont have to add them all individually

I've tried everything said here and the only thing I get is my wheel moving horizontally and my two thumb buttons act as page up and page down. I'm usin' a M$ intellimouse in Slack 9.1. Any idears mates? Thanks!