Well ... you have several options.
But first, make sure you identified the right location for your mouse --
Linux doesn't actually have anything called "port 1", so I'm not certain
what you mean by it. If the mouse was on COM1 under WinXX, it is on
/dev/ttyS0 in Linux. If on COM2, it's on /dev/ttyS1 in Linux. And actually
I'm surprised that the mouse and modem (apparently) succeed in sharing an
interrupt under Windows; I thought WinXX had problems with that as well as
production versions of Linux.
Anyway, your options include these:
1. Move the mouse from COM1 to COM2. COM2 and COM3 (/dev/ttyS1 and
/dev/ttyS2) don't share an interrupt.
2. If you modem is PnP, use the appropriate Linux PnP manager (e.g., isapnp
for isa boards) to change the IRQ of the modem card.
3. Upgrade to kernel 2.2.x (I think). I don't use it yet myself, but I
understand that it contains a system for sharing IRQs (perhaps someone who
actually uses 2.2.x can confirm this?).
At 07:14 PM 5/3/99 -0500, Vox wrote [abridged]:
> I'm YALN (yet another Linux newbie) with a question that may sound silly
>to some :) I installed TurboLinux 3.40 today, and everything went through
>smoothly....Once the install is done, and I get to finally boot into Linux, I
>startx and everything goes well until I try to move the mouse....it's as if
>it were dead. During turboxcfg I told this thing that the mouse was a
>serial mouse in port 1. I *think* I know what the problem is, but have no
>clue as of how to fix it. I have a Motorola Voice Surfer 56k (internal),
>and that one uses (at least in windoze) COM3...and I seem to remember from
>the old DOS days that COM 1 and 3 share the same IRQ or some other
>thing...
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
