My original question:
> I am running DU V4.0 on an Alphastation 255. I have a PBXGB-AA video
> board (a.k.a. ZLXp2-EV4, a.k.a. Powerstorm 3D30) (why don't they
> standardize these names?). I have 2 (seemingly) identical machines
> in this configuration. I would like them both to be in 1024x768
> resolution. One works fine with the dial on the video board set to
> "6" (which corresponds to 1024x768, 72 Hz refresh, and 74.39 MHz pixel
> frequency) but the other one will only work with the dial set to "1"
> (1280x1024, 6Hz, 119.85MHz). When the 2nd machine is set to 6 it boots
> fine, but when it switches to graphics mode it goes white then black and
> every once in a while it blinks up a blue screen for a second.
>
> In the archives of this list I found a common problem solution was to
> modify the Xservers file and add "-screen 1024" to it. This did not
> help in my case. The only thing that was ever different between the
> two systems was that the one that is not working had a 15" monitor on
> it when we first booted it up (it now has a 17" monitor), while the one
> that is working had (and has) a 17" monitor.
>
> Any ideas?
Thanks to the following for their replies:
"Dr. Tom Blinn, 603-881-0646" <tpb_at_zk3.dec.com>
BigRedDog <ckrieger_at_latrade.com>
First of all, changing the Xservers file was not applicable in my case.
This file is only when the resolution is set up in software. In my case
the resolution is read from the board and you adjust it using a dial on
the board. I ended up solving my problem using some trial and error.
First I swapped monitors between the "good" machine and the "bad" machine.
The problem did not "move", so the monitor had nothing to do with the
problem. Next I swapped video cards. Again the problem did not move.
I finally decided it was a software problem for several reasons: 1) Tom
Blinn told me that my problem description sounded like the X server
failing. 2) My system had recently had several "lock-ups" that required
an ungracefull reboot (see my previous post from a couple of days ago),
and 3) I noticed that one of my disk partitions was showing a size that
wasn't correct. So I re-installed the OS and now everything is fine.
Apparently those ungraceful reboots trashed some things. Oh, and I also
had to do a newfs on that disk that was showing a bogus size in order
to fix that.
Thanks again for the help,
Mike
----------------------------------------------------------------------
Michael Galuza
DeJarnette Research Systems mgaluza_at_dejarnette.com
401 Washington Ave Suite 700 Voice: +1(410)583-0680 x691
Towson, MD 21204 Fax: +1(410)583-0696
----------------------------------------------------------------------
Received on Wed Jul 02 1997 - 19:17:44 NZST