Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!mcsun!Germany.EU.net!lemis!grog From: grog@lemis.uucp (Greg Lehey) Newsgroups: comp.unix.bsd Subject: Re: Diamond Speedstar dot frequencies Message-ID: <2397@adagio.lemis.uucp> Date: 31 Oct 92 16:23:14 GMT References: <1992Oct23.112529.29202@Urmel.Informatik.RWTH-Aachen.DE> <veit.720177860@du9ds3> Organization: LEMIS, W-6324 Feldatal, Germany Lines: 25 In article <veit.720177860@du9ds3> veit@du9ds3.uni-duisburg.de writes: >In <1992Oct23.112529.29202@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: > >>I have observed that sometimes when I startx I get dotclocks xx xx 79 xx xx >>ans sometimes I get xx xx 80 xx xx . I tried a configuration 1024x768 using >>the 79 MHz dot clock but next time I started X I got 'clock not supported' >>or something close. Then I changed that 79 to 80 in my Xconfig and it now >>works for a while. > >Just write the configuration line twice in your config file, one with >79 and one with 80 MHz. The difference is caused by measuring inaccuracies. >I suppose you have a board with a clock of 79.9 MHz or 80.1 or at least close >in this range. The real frequency isn't important. You could put 30 there, as long as the frequency was unique. The only thing that is important is that it matches up in the modes line. In other words, if this change made the difference, then it was because it was fixing a semantics error in the Xconfig, not because the frequencies were now correct. I use a SpeedStar, and only recently discovered that the fastest clock was 80 MHz. I had told Xconfig that it was 76 MHz, and everything ran fine. -- Greg Lehey | Tel: +49-6637-1488 LEMIS | Fax: +49-6637-1489 Schellnhausen 2, W-6324 Feldatal, Germany