Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Oct 1999 20:09:07 -0400 (EDT)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Wilko Bulte <wilko@yedi.iaf.nl>
Cc:        freebsd-alpha@FreeBSD.ORG
Subject:   Re: Mach64-svga on FreeBSD/alpha
Message-ID:  <14359.36582.911428.608670@grasshopper.cs.duke.edu>
In-Reply-To: <199910272206.AAA67502@yedi.iaf.nl>
References:  <14358.8254.334980.730088@grasshopper.cs.duke.edu> <199910272206.AAA67502@yedi.iaf.nl>

next in thread | previous in thread | raw e-mail | index | archive | help

Wilko Bulte writes:

 > >  > >>>>>> (--) Mach64: PCI: Mach64 CX rev 1, Aperture @ 0x81000000, Sparse I/O @
 > >  > 0x02ec
 > >  > 

<...>
 > 
 > No, it does not. Which is a bit !verbose to me to be honest. Does the
 > aperture line give any useful info? It does not to me, but.. ;-)

Yes, it says what address the frame buffer is mapped into & what i/o
port it is using for register access.  Neither of those is terribly
useful for figuring out why it doesn't want to start the server.

Darn.  I should have thought about this sooner.... About 1 year ago,
when we were first getting X working, I used one of the ATI Mach64
cards that shipped in some older AS200s.  This was a borrowed card.  I
wrote the following about it in private email after getting it working:

 > I borrowed an Ati Mach64 from a friend (thanks Sean!), and it
 > appears to work just fine.  My AS200 has been up for 1/2 hour running
 > netperf TCP streams (over a 100mb nic), Bonnie, a remotely displayed
 > 'ico', all while I drag opaque windows around over a complex gif
 > background.  Its not exactly speedy, but its rock solid.
 > 
 > Speaking of the ATI server, it tries to grope around in the bios
 > strings to figure out the ramdac & clock chip. I bludgeoned the driver
 > into submission & specified the ramdac/clock chips in my config file.
 > But there are probably more drivers that do this; I guess we'll need
 > to make xf86ReadBIOS work..  

I don't know if xf86ReadBIOS was ever fixed.  But you might want to
try specifying the clock chip & ramdac.  I no longer recall what I
meant by "bludgeon the driver into submission" & I no longer have that 
copy of the X server code.  I do still have the xf86 config file where 
I said:

Section "Device"
        Identifier "m64"
        ClockChip       "ics2595"
        Ramdac  "stg1702"
        Option "override_bios"
        Option "no_block_write"
        Option "no_bios_clocks"
#       Clocks  135.0 80.0 40.0
EndSection

These are almost certainly wrong for your spiffy new card, but you get 
an idea of what I needed to inform the X server about.


Drew

------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer	http://www.cs.duke.edu/~gallatin
Duke University				Email: gallatin@cs.duke.edu
Department of Computer Science		Phone: (919) 660-6590


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14359.36582.911428.608670>