Summary X-window problem

From: streamlight <streamlight_at_idci.net>
Date: Mon, 02 Feb 1998 16:22:30 -0500

At the bottom are three
of the responses and
thanks to all who did
respond.

The answers came from
Digital folks
There is a patch for 3.2g
to fix the problem of new
PCI cards on older OS
but no one knew if it
would work on 3.2c. It
did, it seems that new
cards and old XWindows
*.os
files point to different
characteristics on the
new cards
anyway move the new *.os
file over, rebuild
kernel, boot system
everything works
Yea Team, again thanks to
all
Even if I did not use
your answers directly,
the response time back
was great
and responses sometimes
lead to a direction to
look



On Mon, 26 Jan 1998,
streamlight wrote:
> We switched from a ATI
64
> isa card
> to a PCI card after DEC

> swapped the cards
> I rebuild the kernel
the
> system came up, but
> Windows hangs and hangs

> if I kill the X
processes
> I get a single console
> prompt
> what is wrong with the
> Windows
> help


Richard Bemrose
<rb237_at_phy.cam.ac.uk>
>wrote this

We had a similar case
when we changed graphics
card. Both cards required

Open3D to function
properly. When we
installed the new card we
assume that
the current installation
of Open3D (checked via
'setld -i') was
sufficient.
However, our system
experienced similar
problems as you report.

We resolved the problem
by totally de-installing
Open3D, booting into a
single console prompt and
re-installing it from
scratch. This method was
mentioned in a single
line of the Open3D manual
(not obvious). Following
this method the correct
drivers for the graphics
card was installed and we

have had no problems ever
since.


"Edward D. Silver"
<eds_at_ipcc.com>

>wrote his

Make sure you install the
subset
OSFSERPC425
installed X Servers for
PCbus



 Santosh Krishnan x2815
<santosh_at_heplinux1.uta.edu>

>wrote this

1. X Windows is very
specific about what X
server it uses. An ATI
Mach 64
uses the X86-Mach64
server. The new card
probably uses a different

server.

2. Even if it's the same
server, the clockchip
settings and the RAMDAC
are
most likely going to be
different. This will
prevent X windows from
loading up.

3. Then too, you may not
have the right screens
setup in the X86_CONFIG
file, or the
configuration file for X.

Best solution: Run X
-probeonly and look at
the results. This will
give
you a good idea of what's
wrong.

Better Solution: Get X
Free-86. It's a free X
windows server for
several
platforms, and it
supports almost all the
latest and greatest video
cards
out there.
Received on Mon Feb 02 1998 - 22:30:15 NZDT

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