Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!umn.edu!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: S3 server on Orchid F1280, Problem Message-ID: <1992Oct24.052650.17914@netcom.com> Keywords: S3, Orchid Organization: Netcom - Online Communication Services (408 241-9760 guest) References: <1992Oct23.130246.14480@udel.edu> Date: Sat, 24 Oct 1992 05:26:50 GMT Lines: 63 In article <1992Oct23.130246.14480@udel.edu> mm@brl.mil writes: >Last night I loaded the latest version of Amancio Hasty's S3 server and >ran into a problem. After an "xinit > &uhoh", this is what uhoh contained: > > > S3 0.1 / X Windows System > (protocol Version 11, revision 0, vendor release 5000) > > S3 > failed to set default font path '/usr/X386/lib/X11/fonts/misc/, > /usr/X386/lib/X11/fonts/75dpi/' > Fatal server error: > could not open default font 'fixed' > XIO: fatal IO error 32 (Broken pipe) on X server ":0.0" > after 0 requests (0 known processed) with 0 events remaining. > The connection was probably broken by a server shutdown or KillClient. > > >And then I had a nice deep blue screen but had to kill the server. The same >font path works fine for the X386mono server. Has anyone else had this >problem or have an idea what's wrong? I even tried changing my RGB and Font >Paths to /bd/X11R5/lib where lib was a link to /usr/X386/lib. No luck. > >As mentioned in the subject line, I'm using an Orchid Fahrenheit 1280 (on a >486DX 33MHz, with switch 3 "on" and the others "off" on the F1280 card). >Here is the Xconfig file I used: > >RGBPath "/usr/X386/lib/X11/rgb" >FontPath "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/75dpi/" > >Keyboard > AutoRepeat 500 5 > ServerNumLock > >Microsoft "/dev/com1" > >VGA256 > Vendor "Orchid" > Clocks 0 3 5 > Virtual 640 480 > ViewPort 0 0 > Modes "640x480" > Videoram 1024 > >ModeDB ># name clock horizontal timing vertical timing flags > "640x480" 0 640 672 768 800 480 490 492 525 ># "800x600" 3 800 824 896 1024 600 601 603 625 ># "1024x768i" 5 1024 1064 1224 1264 768 776 785 817 Interlace > >Thanks for any insight at all into this problem! >-- >Mike Markowski >mm@brl.mil >(410)278-6674 I managed to reproduce the problem . It should be easy to fix and will be more than happy to let everyone know when is fixed. Amancio