Google Answers Logo
View Question
 
Q: XF86Config ( No Answer,   1 Comment )
Question  
Subject: XF86Config
Category: Computers > Operating Systems
Asked by: salman1-ga
List Price: $5.00
Posted: 15 Jun 2003 23:05 PDT
Expires: 15 Jul 2003 23:05 PDT
Question ID: 217803
The following is the InputDevice section (for mouse) from my
XF86Config file:

Section "InputDevice"
	Identifier	"Mouse1"
	Driver		"mouse"

	Option "Protocol"    "MouseMan"

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


However, I can't seem to get my mouse (DELL, originally built by
Logitech) to work. I have another mouse which works on the same
computer with the following settings:

Protocol 	"MouseMan"
Device		"/dev/ttyS0"

The mouse is hooked up via a KVM switch (BELKIN). I need someone to
help me fix this (the gpm service is turned off).

Request for Question Clarification by maniac-ga on 16 Jun 2003 10:48 PDT
Hello Salman,

Hmm. I'd like to post an answer, but I can't be positive we have the
same hardware and software. I checked on a machine down the hall that
uses...
 - Red Hat 7.3
 - Belden OmniView PRO 16 Port KVM
 - Logitech mouse
and the relevant section from /etc/X11/XF86Config-4 on that system
is...

Section "InputDevice"
  Identifier "Mouse0"
  Driver "mouse"
  Option "Device" "/dev/mouse"
  Option "Protocol" "PS/2"
  Option "Emulate3Buttons" "off"
  Option "ZAxisMapping" "4 5"
EndSection

From what I understand (from man XF86Config), Pointer is interpreted
the same as InputDevice, so the section name you have is OK. Also note
that /dev/mouse is a soft link to /dev/psaux on this system, so the
comment that eiffel-ga made should give you the same result.

Another note - from
  http://www.xfree86.org/current/mouse4.html
it notes you should try protocol "PS/2" first for all brands of mice.
This is a conservative setting and good to check out hardware, etc.
This page also has a number of other good suggestions including a
comment to use "Mouseman" or "MIcrosoft" for new Logitech mice and
"Logitech" only for the older serial mouse models.
 
If this does not work, what messages are you getting related to the
mouse / pointer in the XFree86 log file and/or /var/log/messages?

The other thing you may want to try - especially if you have Red Hat
is to rerun a utility such as kudzu which reviews the hardware of your
system and fixes the configuration files appropriately. Let me know if
you want to pursue such a solution.

  --Maniac

Clarification of Question by salman1-ga on 16 Jun 2003 22:50 PDT
I am running on Slackware (9.0, 2.4.2). The computer has a serial
port, the mouse itself is PS/2 (I therefore used a PS/2->serial
converter, to connect them). I tried changing the protocol to PS/2,
MouseMan, Microsoft, all on device /dev/ttyS0 and it still didn't
work. I am sure /dev/ttyS0 is correct since my other mouse works on
this setting.

Here's some stuff from var/log/XFree86.0.log (anything related to
mouse):

....
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
....
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
	compiled for 4.3.0, module version = 1.0.0
	Module class: XFree86 XInput Driver
	ABI class: XFree86 XInput driver, version 0.4
....
(**) Option "Protocol" "MouseMan"
(**) Mouse1: Protocol: "MouseMan"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/ttyS0"
(**) Option "BaudRate" "1200"
(**) Option "StopBits" "1"
(**) Option "DataBits" "7"
(**) Option "Parity" "None"
(**) Option "Vmin" "1"
(**) Option "Vtime" "0"
(**) Option "FlowControl" "None"
(**) Option "Emulate3Buttons" "off"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 5
(**) Mouse1: BaudRate: 1200
(II) Keyboard "Keyboard1" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)


I don'I am running on Slackware (9.0, 2.4.2). The computer has a
serial port, the mouse itself is PS/2 (I therefore used a
PS/2->serial converter, to connect them). I tried changing the
protocol to PS/2, MouseMan, Microsoft, all on device /dev/ttyS0
and it still didn't work. I am sure /dev/ttyS0 is correct since my
other mouse works on this setting.

Here's some stuff from var/log/XFree86.0.log (anything related to
mouse):

....
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
....
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
	compiled for 4.3.0, module version = 1.0.0
	Module class: XFree86 XInput Driver
	ABI class: XFree86 XInput driver, version 0.4
....
(**) Option "Protocol" "MouseMan"
(**) Mouse1: Protocol: "MouseMan"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/ttyS0"
(**) Option "BaudRate" "1200"
(**) Option "StopBits" "1"
(**) Option "DataBits" "7"
(**) Option "Parity" "None"
(**) Option "Vmin" "1"
(**) Option "Vtime" "0"
(**) Option "FlowControl" "None"
(**) Option "Emulate3Buttons" "off"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 5
(**) Mouse1: BaudRate: 1200
(II) Keyboard "Keyboard1" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)

I don't think Slackware has the kudzu tool maniac-ga was talking
about.

Request for Question Clarification by maniac-ga on 17 Jun 2003 05:31 PDT
Hello Salman,

Hmm. What you provided looks OK. It is odd that the "other mouse"
works on the serial port but the logitech one does not.

You didn't mention the type of the "other mouse". If it is a PS/2
mouse, that means the PS/2 to serial adapter is OK. If the "other
mouse" is serial, I would suspect the adapter if the logitech mouse
works on a PS/2 PC.

The other possible problem remaining is the use of the KVM on a serial
port. You did not say, but have you connected the logitech mouse
directly to the serial port (w/ adapter)? That would rule out problems
with the KVM / serial port combination.

  --Maniac

Request for Question Clarification by sycophant-ga on 22 Jun 2003 20:24 PDT
I am not that familiar with Slackware, but I was often caught out in
Debian by the fact a serial point was setup with a getty by default,
so was in use already.

Try something like: 

fuser /dev/ttyS0

If it is being used by any other process, fuser should tell you.
Answer  
There is no answer at this time.

Comments  
Subject: Re: XF86Config
From: eiffel-ga on 16 Jun 2003 06:03 PDT
 
Hi salman1,

For what it's worth, when my Dell/Logitech mouse is connected to my
PS/2 port it needs the following setting:

    Protocol    "PS/2"
    Device      "/dev/psaux"

I don't know whether your Dell/Logitech mouse is Serial or PS/2 (or
indeed which mice the Belkin KVM supports). I also don't know whether
the Belkin does anything "smart" or is effectively just a switch - but
if your mouse is a PS/2 (small round plug) and the Belkin KVM is
connected to the first serial port, then it could be worth trying

   Protocol "PS/2"
   Device "/dev/ttyS0"

Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Google does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. Please read carefully the Google Answers Terms of Service.

If you feel that you have found inappropriate content, please let us know by emailing us at answers-support@google.com with the question ID listed above. Thank you.
Search Google Answers for
Google Answers  


Google Home - Answers FAQ - Terms of Service - Privacy Policy