From owner-freebsd-alpha Wed Oct 27 17:10:12 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9143014D09 for ; Wed, 27 Oct 1999 17:09:41 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id UAA09568; Wed, 27 Oct 1999 20:09:38 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA30135; Wed, 27 Oct 1999 20:09:07 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 27 Oct 1999 20:09:07 -0400 (EDT) To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Mach64-svga on FreeBSD/alpha In-Reply-To: <199910272206.AAA67502@yedi.iaf.nl> References: <14358.8254.334980.730088@grasshopper.cs.duke.edu> <199910272206.AAA67502@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14359.36582.911428.608670@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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