From: caywood@wyvern.wyvern.com (John Caywood) Subject: Re: X386 installation -- TCP and mouse woes Date: Sat, 10 Apr 1993 23:03:26 GMT
Mike Gross (gross@maxwell.ucsc.edu) wrote:
: Hello,
: After getting some very useful Xconfig help from the net, I've managed to
: get a good picture on my X server under Linux. However, when redirecting
: stderr, I noticed a preliminary error message:
: Setting TCP SO_LINGER: Protocol not available
: No SIOCGIFCONF
I get these messages, too, but I ignore them. I tend to ignore a LOT of
X messages....
: Also, the mouse is not responding. I have a Microsoft compatible bus mouse,
: and Xconfig points directly to /dev/ttyS2. Pointing it to /dev/bmousems
: results in a "cannot open mouse" error.
I have one, too, and I had similar problems. I symlinked /dev/bmousems to
/dev/mouse, and my Xconfig has the line
busmouse "/dev/mouse"
Note, however, that the problems arose from my video card (an Orchid F1280
with the S3 video chip). I had immense quantities of garbage till I got
an S3-compatible Xserver. I'm now running XS3, I think alpha0.4.4. That
server has support for busmouse, but the Xserver that came with my SLS
distribution (0.99pl2) did not. If you've tried the things I suggested
above, then you might want to look around for a newer Xserver.
--
"If you've always done it that way, it's probably wrong"
--------------------------------------attributed to Edward Kettering
John Caywood, aspiring Linux S.A., ! caywood@wyvern.wyvern.com
vi bigot, and wine drinker ! J.S.Caywood@LaRC.NASA.GOV