[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bgsdev::open3d

Title:open3d
Notice:Kits on notes 3 and 4; Documents note 223
Moderator:WRKSYS::COULTER
Created:Wed Dec 09 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1306
Total number of notes:5260

1230.0. "X-server can not be started on display :0" by TROOA::HANDY (L. Handy, MCSE DTN 626-3210) Tue Jan 28 1997 20:08

    I am experiencing problem in starting up the Digital Unix X-server on
    the following platform:
    
    Alphastation 500/500
    Digital Unix 4.0a
    128MB memory
    lazy swap enabled
    Open3D v4.2 beta installed with (I hope) valid Open3D license
    4D60 graphics adapter
    VRT17 monitor
    
    The system boots fine, and h/w diagnostics pass.  At the end of the
    Unix boot stream, the graphics adapter attempts to initialize, and I
    get the error:  "The X-server can not be started on display :0".  The
    system is running fine with text-only console access.
    
    /var/adm/messages looks fine, and uerf output look fine too.  Could
    someone point out the recommended troubleshooting procedure for this
    type of error message?
    
    Thanks,
    
    Lyndon Handy
T.RTitleUserPersonal
Name
DateLines
1230.1Some suggestionsRUSURE::FRANZINIWed Jan 29 1997 11:0114
If you are using the CDE desktop, try looking in /usr/var/dt/Xerrors for error
messages.  If you are using the XDM desktop, try looking in
/usr/lib/X11/xdm/xdm-errors.

Try starting the X server by hand to see if you get any error messages:

	# /sbin/init.d/xlogin stop
	# /usr/bin/X11/X

Also, please verify that Open3D is installed correctly.  The X server should
come up even without a valid license.

John F.

1230.2could not open default font 'fixed'TROOA::HANDYL. Handy, MCSE DTN 626-3210Wed Jan 29 1997 17:4818
    I am using CDE.  There are repeated error messages in
    /usr/var/dt/Xerrors , ie.
    "...failed to set default font path '/usr/lib/X11/fonts/decwin/100dpi/,
    ...  ... ...
    could not open default font 'fixed'
    ..."
    
    The font directories specified above are intact, but the font files
    themselves are compressed (eg. .Z files).  Are these normally
    compressed?
    
    The command /sbin/init.d/xlogin stop executes without error, but
    manually starting the x-server generates identical error messages after
    attempting to initialize the display :0.
    
    I reviewed the installation guide and release notes.  The installation
    completed successfully, and I made no manual changes to Xserver.conf.
    Any suggestions?
1230.3Deleted some modules, installed 100dpi fonts, etcTROOA::HANDYL. Handy, MCSE DTN 626-3210Wed Jan 29 1997 20:2228
    Rebuilding the kernel had no effect, so I 'cleaned' up the system
    again:
    
    -  deleted 'stereo graphics modules that were installed'
    -  deleted 'Freedom' support module that was installed for some reason
    
    Now, since the errors pointed to 'fonts' in general, I did the following:
    
    -  setld -i grep FONT  (noticed that 100dpi fonts missing)
    -  setld -l OSFFONT15405
    -  starting x-server at this time resulted in grey screen, hung
    -  rebooted and tuned system, vm: and ipc: for shared memory for
    high-end graphics
    -  rebooted again and display seems to be working now.  Noted that the
    colours seem to be washed out (don't know why...)
    
    What I don't understand is:
    #1: Why is this requirement no documented in the Open3D installation 
    guide or release notes?
    #2: Why would my 100dpi fonts be missing?
    
    Also, is there a 'light and sound' demo that we can execute to fully
    test out the graphic card's capabilities?  For the casual observer, our
    4D60 display appears at first glance to be just like any SuperVGA
    display.
    
    LKH
    
1230.4Similar problemRDGENG::READINGS_RRichard ReadingsFri Jan 31 1997 06:0814
Re .3

#2: Why would my 100dpi fonts be missing?

I had the same problem. ISTR being asked for PowerStorm drivers during the
install (DUNIX V4.0A), but I didn't have these (where are they, perhaps 4.0B
will remove this requirement). The display then came up in VGA mode. Perhaps
that's why the 100dpi fonts didn't get loaded.

When I installed Open3D V4.2 I got the messages reported in .2. I then installed
the 100dpi fonts from the base CD, but ISTR that dragged in a couple of other
subsets. Sorry I can't be more precise.

Richard