ejm@coyote.datalog.com (E.J. McKernan) (02/25/91)
We just installed Roells X386 1.1 here and are having major problems.
The installation went smoothly, replacing the old X386 1.0 system.
The 1.0 version worked great.
Executing:
X -debug
Results in:
Creating TCP socket: No such file or directory
InitOutput(pScreenInfo=0x40ae04, argc=2, argv=0x7fffff44)
X386VTInit()
vgaScreenInit(index=0, pScreen=0x42d400, argc=2, argv=0x7fffff44)
bus error
Our Xconfig contains:
ET4000 1024 1152 900 25 28 32 36 40 45 55 64 "800x600"
"800x600" 36 800 820 956 1000 600 610 617 633
Our system doesn't have TCP/IP installed.
Any idea what's wrong? I'd love to use 1.1 but will go back to 1.0
if need be.
Thanks in advance.
--
/|_|\ Datalog Consulting, Tucson, AZ
( . . ) ejm@datalog.com
\ / ...!noao!datalog.com!ejm
\_/ brians@eecs.cs.pdx.edu (Brian Smith) (02/26/91)
In article <1991Feb25.035635.5003@coyote.datalog.com> ejm@coyote.datalog.com (E.J. McKernan) writes: >[stuff related to v1.0 deleted] > >Creating TCP socket: No such file or directory >InitOutput(pScreenInfo=0x40ae04, argc=2, argv=0x7fffff44) >X386VTInit() >vgaScreenInit(index=0, pScreen=0x42d400, argc=2, argv=0x7fffff44) >bus error Are you using a Microsoft mouse? If so, that is your problem! I had the exact same bus error when using a MS mouse. Switching to a Mouse Systems mouse cut out the bus errors. Try fiddling with the config settings, and see if that doesn't reduce your bus errors. It won't help you if you don't have a Mouse Systems or Logitech mouse, but you will know where the problem lies. Brian (brians@cs.pdx.edu)