🚀 go-pugleaf

Greetings,

I am trying to determine and correct, what would appear to be a (soft)
configuration problem on my system. Previously, I had a similar
problem. The cause of which, apparently turned out to be a hard-
ware problem. Linux didn't like the other busmouse card. I'm
guessing that the I/O port address for it was not 23Ch-23Fh. In any
case, the problem I am having is still apparently mouse related.

X now seems to initialize ok. I get an X session with a workspace and
a virtual desktop. However, I have almost no control over the mouse. As
you may note, a warning has been generated by xinit reguarding the
mouse:

> Warning: unable to get status of mouse fd (Invalid argument)

The behaviour of the 'mouse to cursor' interaction resembles what I
would normally conclude to be an IRQ conflict. When trying to interact
via the mouse, the cursor keeps bouncing back to the [0,0] position.
As it is moved, the cursor jumps around to about 9 or so positions
with a degree of regularity. The positions are roughly [0,100],
[100,100], [100,0]; [0,200], [200,200], and [200,0], the corners of a
square. Occasionally, the window manager control pop-up menu apprears.
I am pretty confident that the problem is not an IRQ conflict
because I have double checked the jumper configurations for all of the
boards in the machine. The system works well under windoze/DOS. No
conflicts or strange behaviours are encountered (well, other than the
stock issue ones ;} ). I also pulled all but the video, adaptec scsi
disk controller and mouse cards and tried X again. The behaviour
remained.  Have you seen this before? Any suggestions? I have tried
using all of the other mouse drivers. i.e. signifying every mouse
keyword in the 'Xconfig' file and none of those worked (as expected).

The following is output of 'startx' on my machine. I have already
reconfigured and recompiled the kernel on my machine and, yes IRQ5 is
setup for the MS bus mouse that I am using. The mouse is found and works
correctly with MS windows.  It is jumpered correctly as well (IRQ5,I/O=
23Ch-23Fh=primary,AT slot). Oh yea, I've a Trident 9200cxr which I
configured as an 8900c graphics adapter.

Here are the entries in /dev:

lrwxrwxrwx   1 root     root            8 Mar 23 08:05 mouse -> bmousems
crw-rw-rw-   1 root     root      10,   2 Nov 30 14:30 bmousems

Here is the output of startx:

> XFree86 Version 2.0 / X Window System
> (protocol Version 11, revision 0, vendor release 5000)
> Operating System: Linux 
> Configured drivers:
>   VGA256: server for 8-bit colour SVGA (Patchlevel 0):
>       et4000, et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c31, gvga, ati,
>       tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000, clgd5420,
>       clgd5422, clgd5424, clgd5426, clgd5428, clgd6205, clgd6215, clgd6225,
>       clgd6235, ncr77c22, ncr77c22e, cpq_avga, oti067, oti077
> (using VT number 7)
> 
> Xconfig: /usr2/odoncaoa/Xconfig
> (**) stands for supplied, (--) stands for probed/default values
> (**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 9600
> (**) FontPath set to "/usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts/Speedo/,
> /usr/lib/X11/fonts/misc/"
> (**) VGA256: chipset:  tvga8900c
> (**) VGA256: videoram: 1024k
> (**) VGA256: clocks:  25.20  28.30  44.90  36.00  50.35  40.35  65.00  75.00
> (--) VGA256: Maximum allowed dot-clock: 90MHz
> (**) VGA256: Mode "800x600": mode clock =  36.000, clock used =  36.000
> (**) VGA256: Mode "640x480": mode clock =  25.000, clock used =  25.200
> (**) VGA256: Virtual resolution set to 800x600
> (--) VGA256: SpeedUp code selection modified because virtualX != 1024
> Warning: unable to get status of mouse fd (Invalid argument)
>
> waiting for X server to shut down 
> 
> xinit:  Unknown error (errno 0):  Client error.

Cheers,

Doug