Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!zombie.ncsc.mil!news.mathworks.com!fu-berlin.de!zrz.TU-Berlin.DE!zib-berlin.de!news.rrz.uni-hamburg.de!news.dkrz.de!newsserver.rrzn.uni-hannover.de!tubsibr!ws.rz.tu-bs.de!y0001415
From: y0001415@ws.rz.tu-bs.de (Martin Butkus)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Help: Dead mouse in XFree86
Date: 29 Dec 1995 13:04:39 GMT
Organization: TU Braunschweig, FRG
Lines: 66
Distribution: world
Message-ID: <4c0p17$l42@ra.ibr.cs.tu-bs.de>
References: <4brhb7$k17@ns1.tstt.net.tt> <4bubn9$ep7@ra.ibr.cs.tu-bs.de> <4bunt8$19q@homer.alpha.net>
NNTP-Posting-Host: rzrtr1.rz.tu-bs.de
X-Newsreader: TIN [version 1.2 PL2]
Matto (molson@milwaukee.rbvdnr.com) wrote:
: In article <4bubn9$ep7@ra.ibr.cs.tu-bs.de>, y0001415@ws.rz.tu-bs.de (Martin Butkus) says:
: >
: >feisal@tstt.net.tt wrote:
: >: From: molson@milwaukee.rbvdnr.com (Matto)
: >: >The cursor appears on the screen but X doesn't respond to
: >: >the mouse. I have a bus mouse connected to COM1. I haven't
: >: >been able to "find" the connection using "cat /dev/mouse" or
: >: >"cat /dev/cuaa*". I'm sure this is the problem but I don't
: >
: >: Try using "/dev/ttyd1" in your XF86Config, the ttyd are for
: >: "in" like logging in or mouse while cuaa's are for out like
: >: modems etc.
: >
: >: -Feisal
: >
: >Wrong: use /dev/ttyd0. BTW, some Logitech mice require a different baud rate
: >than the standard 1200 bps.
: Been there-done that. Still doesn't work. BTW it's a Mouse Systems
: serial mouse-not a bus mouse, my mistake. I'm now checking to be sure
: my external serial port is actually set as COM1. I get no response from
Good idea, do that.
: cuaa0,cuaa1,ttyd0,or ttyd1. Both COM1 and COM2 are found and configured
: by the kernel. I understand that tty's are for dial-in and cuaa's are
It has to say something like
Dec 23 04:26:48 malibu /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa
Dec 23 04:26:48 malibu /kernel: sio0: type 16450
on startup. Does it?
Check for the interrupts being correctly set on the card too,
they're hardwired in the GENERIC kernel. COM1: MUST have irq 4.
: for dial-out devices, but why do some people say they are finding their
: mice on a cuaa* device? Someone please explain this to me. Any other
man sio for explanation of this issue.
: help on this serial mouse thing would be appreciated.
Several things come to my mind:
- Hardware failure? Try a different mouse/a different serial card.
- Some no-name mice which claim to be "Mouse Systems compatible" need to be
switched to that mode eihter by a dip switch or by pressing a
mouse button on startup.
When you've improved the situation
so that a cat /dev/ttyd0 and moving the mouse puts something on your
screen the following entry in XF86Config should do the trick:
Section "Pointer"
Protocol "MouseSystems"
Device "/dev/ttyd0"
Hope this helps.
--
Martin Butkus >>> Live long and prosper. <<<
Phone/Fax: +49.5331.298710
Am Stadtwege 10, 38304 Wolfenbuettel, Germany