Re: confusing X problem
> The only way I know to approach a problem like this is to get the system
> to a known state, and then proceed with a step-by-step analysis to reduce
> the number of variables, and isolate the problem. I would suggest
> something like the following:
That sounds good, but I'm not really sure how to accomplish step-by-step
analysis with X. Everything seems to be just fine until I try to run X.
Even then, everything seems fine except for the "power on" and "power off"
entries in /var/log/xdm.log and the fact that the monitor does just that.
Given my limited knowledge, it seems that the only variables are the SVGA
server and the XF86Config file. I don't know what else could cause such
weird behavior.
> Verify whether the current version of stable does have support for your
> card. If so, purge your current xserver pacakges, and reinstall them. Make
> sure that the package dependencies are all met during the installation,
> and that any packages that were not configured get configured (run dpkg
> --pending --configure).
The current version of stable does not support this card, that is why I
have tried dropping in SVGA server binaries from the newer versions.
> Gather together all the relevant docs, HOWTO's, man pages, etc. Now begin
> the X configuration process. At each step, read the relevant portion of
> the docs to verify that the correct data is entered, and that the system
> gives the correct response. Assuming all goes well, run it.
I finally see how a step-by-step analysis could help. I think it is safe
to say that the mouse and keyboard settings have nothing to do with our
problem. The monitor is clearly capable of what I am telling the
xf86config program. I have the specifications for the monitor right here.
According to to the card list on www.xfree86.org, SVGA is the right server
to use.
Now we get into things where I'm not quite so sure. In case the card
doesn't really have 2MB, I'll set it to 1MB. It certainly has that.
Since I have not been able to find the specifications for the card on the
Internet, I can only assume that the SVGA server is detecting the RAMDAC,
clockchip and chipset correctly. That could be where the problem lies.
Both Windows95 and the SVGA server say it's a 2MB card with an IBM-RGB525
RAMDAC, so it was probably safe to put those in the config file (although
it didn't fix the problem).
Taking it like that, the problems might be:
1. wrong clockchip
2. wrong RAMDAC
3. wrong X server
4. wrong amount of video RAM
5. wrong chipset
6. something else
Is this the kind of analysis you were suggesting? Any ideas for finding
the specifications on this card? Diamond seems rather tight lipped about
the specifications of its cards.
> Now observe what does or does not happen. Note the specific errors and
> where in the process they occur. Go back to the docs and read the relevant
> sections. As you attempt to resolve each error, again note what happens
> and try to find out why. In this way, the the potential problem areas are
> narrowed down and hopefully isolated. If not, it is much easier to ask
> someone to help when the problem has been clarified.
Same old problem. What sections are relevant to the monitor turning
itself off and the messages "power on" and "power off" in xdm.log? I have
certainly read the troubleshooting sections of all documents I have come
across. As far as clarifying the problem, about all I know is that it
seems to succeed except for those strange messages in xdm.log and the
monitor turning itself off.
> If this sound like a lot of work, well, it is. But IMHO it is easier than
> trying to solve a difficult problem intuitively. Taken a step at a time,
> it comes together easier than it might seem.
I have plenty of time and don't mind the work. I just wish that both the
configuration process and the documentation were a little more user
friendly.
Here is some additional information that will hopefully give someone an
idea as to the problem:
I have noticed a couple of interesting symptoms during additional attempts
I have made. I started with no one logged in on VC's 1-6 and xdm not
running. I telnetted in from another machine so that I would still be
able to issue commands after starting xdm. Of course, when I started xdm,
the screen turned
off.
Even so, I thought I might be able to log into xdm. Sure enough, ps aux
now lists /usr/bin/X11/twm! That tells me that xdm is indeed working,
albeit invisibly.
I decided to also try mode switching with the Ctrl Alt + and Ctrl Alt -.
That produced two new lines in /var/log/xdm.log (the first was already
there):
POWER ON
Mode switch failed because of hardware initialisation error
POWER ON
In addition, stopping X produced something I had not thought to mention:
All 6 VC's are now messed up vertically. The top and bottom lines are off
the screen and there is a blank gap slightly above the middle. They are
fine horizontally though.
Thank you,
Patrick Olson
Reply to: