Sponsored Content
Full Discussion: Problem with my mouse in KDE
Special Forums UNIX Desktop Questions & Answers Problem with my mouse in KDE Post 26942 by auswipe on Monday 26th of August 2002 12:05:52 PM
Old 08-26-2002
Quote:
Originally posted by Daniela5743
I have already tried this, and my mouse did not move at all.
What is the current settings for your mouse under /etc/X11/XF86Config file?

Here is mine that I use on FreeBSD 4.5 with XFree86 4.1.0:

Code:
Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "Auto"
        Option      "Device" "/dev/psm0"
        Option      "ZAxisMapping" "4 5"
        Option      "Buttons" "6"
EndSection

I use a Microsoft Intellimouse optical PS/2 with scrolling wheel.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Mouse settings

How do I change the mouse pointer speed settings in Unix. I know in Windows there is the option to change the pointer speed. (3 Replies)
Discussion started by: chyzm
3 Replies

2. UNIX for Dummies Questions & Answers

Mouse Problem In ScoUnix

I have a problem with my mouse in scounix 5.04 i choosed my mouse during installation , but when i installed unix my mouse was hanged , and didn't works. please help me how can i install my mouse tnx alot (1 Reply)
Discussion started by: uranium
1 Replies

3. UNIX for Advanced & Expert Users

Indigo mouse

A few years ago i found i the Net a "homework" about how to convert ps2 mouse to Indigo mouse. But i do not save it. Anybody helps me? There are about 10 Indigo mice in all of my country. Thanks in advance (2 Replies)
Discussion started by: mikidimov
2 Replies

4. Solaris

urgent --- mouse hangin problem

hello everyone i ve a urgent situation of mouse hangin in our sun environment where we have one sun server n several sunray machines attached to it sunray machines ve frequent mouse hangin prob so kindly suggest how to overcome this problem thanks in advance (1 Reply)
Discussion started by: livemyway
1 Replies

5. Shell Programming and Scripting

Building a better mouse trap, or How many lines of code does it take to trap a mouse?

Hello all, I'm hoping to get a little insight from some of the wily veterans amongst you. I've written a script to check for new outgoing files to our vendors located on our ssl server. It seems to be working ok, but the final question here, will be one of logic, and/or a better way to... (4 Replies)
Discussion started by: mph
4 Replies

6. UNIX for Dummies Questions & Answers

Changing middle mouse button for pasting to right mouse button in cygwin rxvt

Hi, I'm using rxvt in Cygwin and I'm wondering how to change my mouse bindings from the middle button for pasting to the right button. The main reason why I want to do this is because my laptop doesn't have a middle mouse button. Thanks for any help! (2 Replies)
Discussion started by: sayeo
2 Replies

7. SCO

Mouse problem in sco 5.0.6

hello i have a problem with mouse in vmware with sco 5.0.6 in graphic mode X11 my mouse move to corner after a while do you have any idea about this problem vmware 6.5.2 vmware 7 (5 Replies)
Discussion started by: kaydream
5 Replies

8. UNIX Desktop Questions & Answers

KDE apple mouse

Hi - Does anyone else use KDE with apple hardware? I can't seem to find anything out there about apple mouse support for right-clicking. Any advice? Thanks (1 Reply)
Discussion started by: platz
1 Replies

9. What is on Your Mind?

Problem setting up wireless mouse

Did not know where to post this. Could someone help me with getting my wireless mouse to work? I can post more specifics at that time. Thanks. (9 Replies)
Discussion started by: drew77
9 Replies
MOUSE(4)						     Kernel Interfaces Manual							  MOUSE(4)

NAME
mouse - Mouse input driver SYNOPSIS
Section "InputDevice" Identifier "idevname" Driver "mouse" Option "Protocol" "protoname" Option "Device" "devpath" ... EndSection DESCRIPTION
mouse is an XFree86 input driver for mice. The driver supports most available mouse types and interfaces. USB mice are only supported on some OSs, and the level of support for PS/2 mice depends on the OS. The mouse driver functions as a pointer input device, and may be used as the X server's core pointer. Multiple mice are supported by mul- tiple instances of this driver. SUPPORTED HARDWARE
There is a detailed list of hardware that the mouse driver supports in the README.mouse document. This can be found in /usr/X11R6/lib/X11/doc/, or online at http://www.xfree86.org/current/mouse.html. CONFIGURATION DETAILS
Please refer to XF86Config(5) for general configuration details and for options that can be used with all input drivers. This section only covers configuration details specific to this driver. The driver can auto-detect the mouse type on some platforms On some platforms this is limited to plug and play serial mice, and on some the auto-detection works for any mouse that the OS's kernel driver supports. On others, it is always necessary to specify the mouse proto- col in the config file. The README.mouse document contains some detailed information about this. The following driver Options are supported: Option "Protocol" "string" Specify the mouse protocol. Valid protocol types include: Auto, Microsoft, MouseSystems, MMSeries, Logitech, MouseMan, MMHitTab, GlidePoint, IntelliMouse, ThinkingMouse, ValuMous- eScroll, AceCad, PS/2, ImPS/2, ExplorerPS/2, ThinkingMousePS/2, MouseManPlusPS/2, GlidePointPS/2, NetMousePS/2, NetScrollPS/2, BusMouse, SysMouse, WSMouse, USB, Xqueue. Not all protocols are supported on all platforms. The "Auto" platform specifies that protocol auto-detection should be attempted. There is no default protocol setting, and specifying this option is mandatory. Option "Device" "string" Specifies the device through which the mouse can be accessed. A common setting is "/dev/mouse", which is often a symbolic link to the real device. This option is mandatory, and there is no default setting. Option "Buttons" "integer" Specifies the number of mouse buttons. In cases where the number of buttons cannot be auto-detected, the default value is 3. The maximum value is 24. Option "Emulate3Buttons" "boolean" Enable/disable the emulation of the third (middle) mouse button for mice which only have two physical buttons. The third button is emulated by pressing both buttons simultaneously. Default: off Option "Emulate3Timeout" "integer" Sets the timeout (in milliseconds) that the driver waits before deciding if two buttons where pressed "simultaneously" when 3 button emulation is enabled. Default: 50. Option "ChordMiddle" "boolean" Enable/disable handling of mice that send left+right events when the middle button is used. Default: off. Option "EmulateWheel" "boolean" Enable/disable "wheel" emulation. Wheel emulation means emulating button press/release events when the mouse is moved while a spe- cific real button is pressed. Wheel button events (typically buttons 4 and 5) are usually used for scrolling. Wheel emulation is useful for getting wheel-like behaviour with trackballs. It can also be useful for mice with 4 or more buttons but no wheel. See the description of the EmulateWheelButton, EmulateWheelInertia, XAxisMapping, and YAxisMapping options below. Default: off. Option "EmulateWheelButton" "integer" Specifies which button must be held down to enable wheel emulation mode. While this button is down, X and/or Y pointer movement will generate button press/release events as specified for the XAxisMapping and YAxisMapping settings. Default: 4. Option "EmulateWheelInertia" "integer" Specifies how far (in pixels) the pointer must move to generate button press/release events in wheel emulation mode. Default: 50. Option "XAxisMapping" "N1 N2" Specifies which buttons are mapped to motion in the X direction in wheel emulation mode. Button number N1 is mapped to the negative X axis motion and button number N2 is mapped to the positive X axis motion. Default: no mapping. Option "YAxisMapping" "N1 N2" Specifies which buttons are mapped to motion in the Y direction in wheel emulation mode. Button number N1 is mapped to the negative Y axis motion and button number N2 is mapped to the positive Y axis motion. Default: "4 5". Option "ZAxisMapping" "X" Option "ZAxisMapping" "Y" Option "ZAxisMapping" "N1 N2" Option "ZAxisMapping" "N1 N2 N3 N4" Set the mapping for the Z axis (wheel) motion to buttons or another axis (X or Y). Button number N1 is mapped to the negative Z axis motion and button number N2 is mapped to the positive Z axis motion. For mice with two wheels, four button numbers can be specified, with the negative and positive motion of the second wheel mapped respectively to buttons number N3 and N4. Default: no mapping. Option "FlipXY" "boolean" Enable/disable swapping the X and Y axes. This transformation is applied after the InvX, InvY and AngleOffset transformations. Default: off. Option "InvX" "boolean" Invert the X axis. Default: off. Option "InvY" "boolean" Invert the Y axis. Default: off. Option "AngleOffset" "integer" Specify a clockwise angular offset (in degrees) to apply to the pointer motion. This transformation is applied before the FlipXY, InvX and InvY transformations. Default: 0. Option "SampleRate" "integer" Sets the number of motion/button events the mouse sends per second. Setting this is only supported for some mice, including some Logitech mice and some PS/2 mice on some platforms. Default: whatever the mouse is already set to. Option "Resolution" "integer" Sets the resolution of the device in counts per inch. Setting this is only supported for some mice, including some PS/2 mice on some platforms. Default: whatever the mouse is already set to. Option "DragLockButtons" "L1 B2 L3 B4" Sets "drag lock buttons" that simulate holding a button down, so that low dexterity people do not have to hold a button down at the same time they move a mouse cursor. Button numbers occur in pairs, with the lock button number occurring first, followed by the but- ton number that is the target of the lock button. Option "DragLockButtons" "M1" Sets a "master drag lock button" that acts as a "Meta Key" indicating that the next button pressed is to be "drag locked". Option "ClearDTR" "boolean" Enable/disable clearing the DTR line on the serial port used by the mouse. Some dual-protocol mice require the DTR line to be cleared to operate in the non-default protocol. This option is for serial mice only. Default: off. Option "ClearRTS" "boolean" Enable/disable clearing the RTS line on the serial port used by the mouse. Some dual-protocol mice require the RTS line to be cleared to operate in the non-default protocol. This option is for serial mice only. Default: off. Option "BaudRate" "integer" Set the baud rate to use for communicating with a serial mouse. This option should rarely be required because the default is cor- rect for almost all situations. Valid values include: 300, 1200, 2400, 4800, 9600, 19200. Default: 1200. There are some other options that may be used to control various parameters for serial port communication, but they are not documented here because the driver sets them correctly for each mouse protocol type. SEE ALSO
XFree86(1), XF86Config(5), xf86config(1), Xserver(1), X(7), README.mouse. XFree86 Version 4.7.0 MOUSE(4)
All times are GMT -4. The time now is 04:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy