Xserver won't start when mouse confg'd on COM2:

Xserver won't start when mouse confg'd on COM2:

Post by Jerry Heym » Fri, 12 Jan 1996 04:00:00



Hi.

We're running ODT 2, and have the following scenario:

    . Our own modem card installed on COM1
    . Serial mouse intalled on COM2

When we boot the system, scologin will show up if we have the mouse on COM2
even though we tell SCO its on tty1a.  the mouse is erratic, and we assume
that is because its really screwing around with the our unique modem card.

When we boot the system with the mouse configured on tty2a, no scologin and
obviously no mouse movement.  We do get errors in the /usr/lib/X11/scologin/
Xerrors file to the effect of "open event driver failed"

Anyone have any clues?  This has stumped us now for almost a week :-(

jerry
--

Tactical Simulation Division   | http://www.arlut.utexas.edu/~jerry/main.html
Applied Research Laboratories of UT Austin | "Software is the difference
P.O. Box 8029, Austin, TX 78713-8029       |     between hardware and reality"

 
 
 

Xserver won't start when mouse confg'd on COM2:

Post by Bela Lubki » Sat, 13 Jan 1996 04:00:00



> We're running ODT 2, and have the following scenario:

>     . Our own modem card installed on COM1
>     . Serial mouse intalled on COM2

> When we boot the system, scologin will show up if we have the mouse on COM2
> even though we tell SCO its on tty1a.  the mouse is erratic, and we assume
> that is because its really screwing around with the our unique modem card.

> When we boot the system with the mouse configured on tty2a, no scologin and
> obviously no mouse movement.  We do get errors in the /usr/lib/X11/scologin/
> Xerrors file to the effect of "open event driver failed"

> Anyone have any clues?  This has stumped us now for almost a week :-(

More detail!  I can guess a bunch -- you have the SCO serial driver
configured for tty1a (3f8/4) and tty2a (2f8/3)?  You configure the
serial mouse for tty1a and the mouse works (erratically); you configure
it for tty2a and *the same*?  Bizarre.  Does your modem thing on tty1a
work?  How about if you try to read the port, outside of X, while moving
the mouse:

  # hd /dev/tty2a
  [move the mouse a bunch]
  [DEL]
  # hd /dev/tty1a
  [move the mouse a bunch]
  [DEL]

Are you really seeing mouse data on both ports?  If so, you're going to
have to be a lot less vague about "our unique modem card" because it's
clearly doing something tres bizarre...

Quote:>Bela<


 
 
 

1. MGR can't see mouse, won't start

I just downloaded the latest MGR and installed it, but it won't
start -- it complained that the mouse is not there or is busy.

Is there some way I can diagnose the problem?

Thanks for any help.

-kin

p.s., I'm not running selection and I have no problems using my
Microsoft serial mouse under MS Windows.
--
Kin Cho, Principal Engineer (408)980-1590 X230 Fax (408)980-0400
Integrated Systems Inc., 3260 Jay Street, Santa Clara, CA  95054

2. LINUX hard to learn? (was: Make Command)

3. X won't start: can't open default font 'fixed'

4. Suggestions on backup software

5. moved HD from ICP to IPX, now xserver won't start

6. Recommended Reading

7. Yellowdog Linux: Xserver won't start

8. NAT and Port Forwarding

9. 'Server already active for display 0' - won't start

10. X won't start "could not find font 'fixed'"

11. X won't start correctly with S3 Trio64 card and MS mouse

12. PS/2 Mouse in Text Mode; X won't start

13. XFree86 won't start ,mouse problem