Re: Why is setting up X so arcane? (SOLVED!!!)

[Sebastiaan <S.Breedveld@ITS.TUDelft.NL>]

On Tue, 17 Jul 2001, Nikki Locke wrote:

> In article <[🔎] Pine.HPP.3.95.1010716210606.15174C-100000@elektron.its.tudelft.nl>, Sebastiaan wrote:
> > Darmed. The problem with my card was that the clockmodes were probed
> > incorrectly. Well, do not waste your time anymore, if the whole system
> > hangs, that is a bad sign. I am told that often chips with bugs are sold
> > for cheap production. They make drivers with workaround for the bugs, but
> > unfortunately there is no information available for us open source devs.
> > Because the card is unreferenced and only identified by several
> > 'compatibles' (and no, I do not think you have a Diamond card, if it is
> > Diamond, there is a clear logo on the card and you would be sure) I have
> > reason to beleive that this is a buggy card. 
> 
> It does say Diamond on the card.
> 

Hi,

add this line to XF86Config in the video card section:

Clocks 25.2 28.3 74.6 74.4 42.9 0 74.3 0 0 0 0 0 0 0 0 74.5
Modes "1024x768"  "640x480"


and change the dotclock to one of the above values in lines like these
(it is the first number):
"640x480"   25     640  672  768  800    480  490  492  525
"1024x768"     74     1024 1024 1192 1368      768  768  779  806


Alternatively you can add this:
Section "Device"
        Identifier "Stealth 64"
        Vendorname "Diamond"
        BoardName  "Stealth 64 DRAM PCI"
        VideoRam   2048
        Chipset    "s3_generic"
        Ramdac	   "s3_sdac"
        ClockChip  "s3_sdac"
EndSection
(this is about the Chipset, Ramdac and the ClockChip).

I also saw a Ramdac "bt485" as an alternative.


Sorry, I saw a miracle yesterday, try to make one happen again. Did a
little search with google.

Greetz,
Sebastiaan