SUMMARY: Where are my X-windows.

From: <6160.-.FAX:"02)"268"8094)">
Date: Thu, 18 May 1995 20:39:28 +1000

   Hi Digital Unix managers,
   
   Many thanks to the following people for helping me solve my problem:
      anthony ?? (anthony_at_aaii.oz.au)
      Dr. Tom Blinn
      Dave Cherkus
      Dave Hill
      Stuart Kreitman
   
   (Three of these people pointed out that my "From" address is scrambled,
   sorry about that, I am using All-in-one via MRgate via X400, and for
   some unknown reason my phone number and fax number appears in my "From"
   address. Any hints appreciated ;-) )
   
   The original question was:
   
   **********************************************************************
   
   I am in the process of adding a graphics card to a DECstation 3000/700.
   The DECstation had its initial software installed using a VT320 via the
   serial port, with no graphics card fitted. I have carried out the
   following steps to get the system to recognise the graphics card:
   
   1. I deleted OSFSER320 and reinstalled it. I then did a "doconfig",
   without the -c option, and rebuilt the kernel using a new config file.
   Upon rebooting on the new kernel, I got a message on the VRT19 saying
   that there was no graphics console support in the kernel, and that it
   was switching to the alternate console. The boot finished with messages
   appearing on the VT320 connected to the serial port.
   
   2. I added "pseudo-device ws" to the kernel, and then rebuilt the
   kernel. Upon reboot, all output went to the VRT19, but it stayed in text
   mode, ie, no login widget appeared, just the login prompt (text).
   
   3. I did ps axw | grep xdm, and found that output was:
       /usr/bin/X11/xdm -config /usr/lib/X11/xdm/xdm-config.fs
       My other system outputs:
       /usr/bin/X11/xdm -config /usr/lib/X11/xdm/xdm-config
   
   4. "sizer -wu" returns 0. My other system returns a 1.
   
   What else do I need to do to get X-windows on the local display??
   
   **********************************************************************
   
   I carried out the following steps to get the X-windows to work:
   
   1. Checked that the console switch was in the correct position, (it
   was).
   
   2. I found all the X-windows related subsets, using:
   "setld -i | grep -i x" and deleted the inventory control files for any
   subsets that are related to the X windows system. The inventory control
   files live in /usr/.smdb.
   
   3. I rebooted the node using the generic kernel, (boot -fi /genvmunix),
   and found that the X-windows worked fine. I then reinstalled the subsets
   for which I deleted the inventory control files for.
   
   4. I rebuilt the kernel using "doconfig" (no -c option), and moved the
   kernel to /vmunix.
   
   5. When I rebooted, everything worked fine.
   
   Thanks again, I have not included full responses, but they are available
   on request.
   
   Garry.
   
   ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
   + + +
   + Garry Optland + Even wise men were once babes. +
   + Pacific Power + +
   + NSW Australia +++++++++++++++++++++++++++++++++++++
   + [61] (2) 268 6160 +
   + <garry.optland_at_com.pacpower.nswgovpower.telememo.au> +
   + +
   ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Received on Wed May 17 1995 - 20:45:03 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:45 NZDT