From: fl0p+@andrew.cmu.edu (Frank T Lofaro)
Newsgroups: comp.os.linux
Subject: Fwd: X bombing *occationally*
Date: 12 Oct 92 12:07:28 GMT
Article-I.D.: andrew.seqRg0G00awAI9vVkX
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA

Return-path: <BILLH@idui1.csrv.uidaho.edu>
X-Andrew-Authenticated-as: 0;andrew.cmu.edu;Network-Mail
Received: from po3.andrew.cmu.edu via trymail
          ID </afs/andrew.cmu.edu/usr13/fl0p/Mailbox/seqRXA600UkTQock8L>;
          Mon, 12 Oct 1992 15:58:04 -0400 (EDT)
Received: from IDUI1.CSRV.UIDAHO.EDU by po3.andrew.cmu.edu (5.54/3.15)
id <AA13467> for fl0p+; Mon, 12 Oct 92 15:57:51 EDT
Received: from idui1.csrv.uidaho.edu by IDUI1.CSRV.UIDAHO.EDU (IBM VM
SMTP V2R1)
   with BSMTP id 6629; Mon, 12 Oct 92 12:58:39 PDT
Received: from idui1.csrv.uidaho.edu (BILLH) by idui1.csrv.uidaho.edu (Mailer
 R2.05) with BSMTP id 6627; Mon, 12 Oct 92 12:58:36 PDT
From: BILLH@IDUI1.CSRV.UIDAHO.EDU
To: fl0p+@andrew.cmu.edu (Frank T Lofaro)
Subject: Re: X bombing *occationally*
Date: Mon, 12 Oct 92 12:40:47 PDT
Organization: University of Idaho

In article <cepvI8G00VpNI47UZv@andrew.cmu.edu> on
10 Oct 92 21:00:56 GMT you write:

>
>Excerpts from netnews.comp.os.linux: 11-Oct-92 Re: X bombing
>*occationally* Matthew A. Lewis@po.CWRU (1288)
>
>>i think this is just due to the clocks on our video cards. Sometimes
>>they aren't exactly stable. One time X failed to boot cause it read
>>a 100 clock time. Normally , my max is 65. Oh well.....it only
>>happens once and a while
>
>        Try this, since X autodetect isn't 100% reliable. On a completely
>unloaded system (i.e. no users, daemons running, etc.) startx 2>
>/tmp/logfile.   Record the clocks reported into the Xconfig, with a line
>saying Clocks clk1 clk2 ... where clk1, clk2, etc are the clock values.
>Now when you startx in should work reliably all the time, even under
>load, since in doesn't have to depend on detecting the clocks right. If
>the fifth number is 65, for example, whenever you ask for 65MHz, it asks
>the card for clock 5. So if that really is a 65 MHz clock, it will work,
>even if X might not've been able to tell what speed clock 5 runs at
>during that invocation of X. Of course, those with variable clocks (e.g.
>the infamous Diamond) will still have problems.
>
>        So in short, hard-coding the clock values into Xconfig after you've
>determined what they are should help.
Actually, this hardcoding seems to work for my Diamond Speedstar 24, I use
the Diamond Speedstar Hicolor clocks listed in the database file, and set
the refresh rate for 72 or higher for all modes (I have a Mag Inovision
MX15F monitor which can take almost any rate I feed it).  I can't post
from my news-reader, and am still working on some other way.  I would
greatly apreciate if you could post this bit about the SS24 for me.
I would not neccessarily recomend the SS24, but it is what I've got at the
moment, and it was much easier to get it to work under Linux, than it was
under OS/2 (may both IBM, and MS eat flaming death!)

wdh

William David Heideman          Bitnet:  billh@idui1
University of Idaho           Internet:  billh@idui1.csrv.uidaho.edu
Moscow, Idaho, USA
These are my opinions, any similarity to any persons or organizations,
living, dead, or undead is purely coincidental.