The probles ins that my logitech mouse wheel doen't work, any help, y have this code in XF86Config-4
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

# Option "SendCoreEvents" "true"
# Option "Emulate3Buttons" "off"
# Option "Buttons" "5"
Option "Protocol" "MouseManPlusPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "SampleRate" "120"
Any help?

uncomment (remove the #) from the line

Option "emulate3buttons "off"

You cannot emulate 3 buttons with the wheel

HTH

Steve

Change the protocol to IMPS/2

if I change the protocol to IMPS/2 the mouse gets the crazy mouse sindrome and starts moving kind of wird and stays in the left bottom corner, an i turn off the Emulate3Button option, so still desnt work, thanks for the help
-Kired

These are my mouse entries in xf86. I have the same mouse.

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Also check the following section to make sure the proper input devices are referred to:

Section "ServerLayout"
Identifier "Anaconda Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

If the server layout section isn't correct, it will cause problems like you describe.

Steve

Please note that this is in RedHat, but your file should not differ much.

Still the same problem, qhen i change the Protocol to IMPS/2 th mouse doent work(it gets crazy), i have a question in the last part i have this:
Section "ServerLayout"

Identifier "Simple Layout"
Screen "Screen 1"
InputDevice "Mouse0" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Is there something wrong on it, i add the two mouses Mouse 0 & 1 like you said, but if there is any problem please tell me, thanx

1. is this the original or did you change it to this?

2. I don't want to tell you to make changes to XF86Config that aren't needed. The thing to be sure of with the ServerLayout section is that if Mouse0 is listed as the CorePointer or Screen1 is listed as the screen, then these have to be defined elsewhere in XF86Config. Otherwise X won't start and you'll get an error message telling you that "screen 1" is not defined or somesuch.. In otherwords, I can't tell if something is wrong with it because I don't know what the rest of your XF86Config says.

3. This mouse thing happened to me in RedHat 7.3 (I'm using 8.0 now) and looking at the original post, I notice that you state that you're editing XF86Config-4. Is there another XF86Config in /etc/X11? RedHat had 2 XF86Configs, one was -4 and the other was just plain XF86Config (i think). When I was having mouse problems I was told that the -4 file was the one that was being read, but it wasn't until i changed the entries in both files that the mouse worked. This did not make sense to me at the time but the mouse worked so i didn't care. This was some time ago and i appologize for not being able to be more specific. Of couse, if you only have the one file (excluding backups) then this does not apply.

1. This is the one i moddified
2. the mouse works except the wheel, si the X works, i gave me no error message, i'll put the file below.
3. There is another XF86Config but i copy it every time i change in XF86Config-4
this is my hole XF86Config-4, hope you can help me, thanks, and I m sorrry if im not that explicit because English is not my native lengauage, thank you for all the help you are givin to me.so this is the file:

# 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.
# **********************************************************************

# **********************************************************************
# 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 Type1 and FreeType font modules
Load "type1"
Load "freetype"

# 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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path. 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><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 "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 "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"

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" "pc102"
# 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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc102"
Option "XkbLayout" "es"

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse0"
Driver "mouse"

Option "Protocol" "PS/2"

Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "dev/input/mice"
Option "Protocol" "PS/2"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"


# 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


# **********************************************************************
# 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 XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "PS2"
# 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 "IBM"

# 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 31.5 - 48.5

# 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 50-90

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 xf86config:

Section "Device"
Identifier "TNT2"
Driver "nv"
#VideoRam 32000
# Insert Clocks lines here if appropriate
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 "TNT2"
Monitor "IBM"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600"
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 "Mouse0" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

A mouse wheel will not work with Option "Protocol" "PS/2", never, nada, not going to happen.
You need to use "IMPS/2" or "ExplorerPS/2" if you want to use the mouse wheel. Do you have gpm running? gpm is often the cause of "crazy mouse syndrome", if it's yhere then try killing it before you change the protocol.

Oh yes I Know you tell me that before, but i havet in PS/2 Because the mouse work with it but with no scroll, thats why i havet like that

Hello Kired

Sorry to disappear on you, but life got in the way for a while. I didn't forget about you though.

I have been able to recreate your mouse problem (i think) in my laptop running RH 7.3. Sorry, I don't use debian.

By crazy, I assume that you are referring to the mouse behaving as thought the x and y axis as well as one or more buttons have been assigned to the mouse ball so when you move the mouse you click things at the same time and dozens of windows open etc. and the cursor shoots to the lower left corner. (or something similar).

Unfortunately, I have not been able to fix this either (on this machine), but I can tell you what I tried.

I have two versions of this mouse - a ps/2 and a usb version. The usb version comes with an adapter so that it too can be plugged into the ps/2 mouse port if you don't have usb. Both of these mice work as advertised when plugged into the ps/2 port on my desktop with the following;

driver mouse
protocol imps/2
emulate3buttons no
device /dev/mouse or /dev/psaux (works with both)
zaxismapping 4 5

Therefore, nothing wrong with the mice.

I have 3 linux distros on this desktop, SuSE, RH, and Slack. The mice work fine in all 3. Minor variations in the options (i.e. SuSE uses Option Buttons 5, RedHat set me up with 2 mice etc.)

The problems come with the laptop and RH 7.3

I used all the options found on the desk top and edited the XF86config by hand - no go. ps/2 and /dev/psaux worked (with no wheel of course) with either mouse plugged into the ps/2 port, but changing to IMPS/2 caused crazy mouse.

I was going to post to try turning off gpm but aussie beat me to it. Then I tried it and it did not work either. I tried to configure /etc/sysconfig/mouse by hand. This did not work. I tried using redhats mouseconfig utility - it changed /etc/sysconfig/mouse and XF86Config, but the thing still did not work.

Then I tried using the usb mouse as a usb mouse and this worked as advertised using /dev/mouse and IMPS/2 with the other options descrbed before.

I used to run RH 7.3 on my desktop and these mice worked well with that distro then so I don't think that this is a distro issue. I don't know what kind of hardware you are using but perhaps this is the problem? I just don't know.

My advice to you would be to go get the usb version of the logitech mousewheel and be done with it. It's not too pricey and so long as you have a usb port this may be an option.

If your a glutton for punishment, you could try some options that more specifically assign x,y,z axis, and buttons etc. but I don't know enough to suggest what they might be or if there are any.

Good luck

Steve

Ok thank you for all you have done for my problem, i really apreciate that, I'm going to try with other mouses. So Thx for all the help Bye, CU around
--Derik

Hello all.

I don't speak very well english, but if it's can help you...

I had some trouble for do it, (and your thread help me)
but now it's work, then I give you my configuration.

I use debian (the current stable, I just install it with floppy...)
I use a Logitech USB with an adapter PS/2.

I use gpm

I had install gpm it with the command :
apt-get install gpm

At the question :
Do you want to change anything (Y/n) ?
my anwser was 'n'

but I had change the protocol in the file /etc/gpm.conf
I use imps2.

When I do :
ps -wx|grep gpm
the anwser is :
/usr/sbin/gpm -m /dev/psaux -t imps2 -Rms3

and my section mouse in XF86Config-4 is :

Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"

and it's work

good luck for your config.

A++, Xav.

After 1 day of use...

gpm and X have often conflict...

then I must kill gpm when I use X and
restart it when I use console

start gpm :
/usr/sbin/gpm -m /dev/psaux -t imps2 -Rms3

kill gpm :
/usr/sbin/gpm -k

and it's work better

A++ Xav.