From owner-freebsd-alpha Thu Oct 28 14:33: 6 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 96F7C14C18 for ; Thu, 28 Oct 1999 14:32:59 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA15028; Thu, 28 Oct 1999 22:56:14 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA17273; Thu, 28 Oct 1999 21:54:44 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910281954.VAA17273@yedi.iaf.nl> Subject: Re: Mach64-svga on FreeBSD/alpha In-Reply-To: <14359.36582.911428.608670@grasshopper.cs.duke.edu> from Andrew Gallatin at "Oct 27, 1999 8: 9: 7 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Thu, 28 Oct 1999 21:54:44 +0200 (CEST) Cc: freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Andrew Gallatin wrote ... > > Wilko Bulte writes: > 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 I tried these, building on my i386 version of XF86config that I used on my Intel box with this card. The only difference is my Ramdac BTW. Alas it does not work :-( Some more hacking to do I guess. > 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. It is not a spiffy new card :) I already have it a couple of years (and I bought it for a few bucks at a flea market) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message