Re: mouse and serial ports
Hi,
Since you didn't tell us what you have already tried, please check these
things. I'm sorry if this is redundant.
When you compiled your kernel, did you include the "Standard/generic serial
support"? It can either be compiled in the kernel or as a module but you need
it to get the mouse support.
Try command 'dmesg' so you can see the kernel's bootup messages and see if
there are lines like these:
Serial driver version 4.13 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
If you didn't see these lines, then try 'insmod serial' as root if you
compiled the serial driver as a module.
If you have the serial driver, then check /etc/X11/XF86Config and try to
locate the Pointer section that starts with a line like
Section "Pointer"
After that there are lines that tell the protocol and device in use. I, for
example have a cheap logitech 3 button mouse and the protocol and device lines
look like this:
Protocol "MouseMan"
Device "/dev/mouse"
Where /dev/mouse is a symbolic link to ttyS0 (COM1). Try man XF86Config for
more info about the pointer and other settings.
There's also XF86Setup program that comes with the 16 color SVGA server
(package 'xserver-vga16') if you'd like to try a different program to make the
XF86Config file.
You wrote:
[cut]
> I installed the packages. OK. I recompiled the Kernel to get free of unused
> drivers. OK. And now, I run XFree86 to configure X11. The problem, at this
You should try 'xf86config' or 'XF86Setup' to configure X.
> step, is that my mouse is not recognized (although a true MicroSoft mouse
> pluged on the serial port 1, fully recognized when DOS/WINDOWS is
> running).What can be done to check /dev/ttySx ? All that I tried has failed.
[cut]
--
Heikki Vatiainen * hessu@cs.tut.fi
Tampere University of Technology * http://www.cs.tut.fi/~hessu/
Tampere, Finland
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: