From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] More Mach64 Problems From: Richard Miller MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-jmqgjmurtwcsxrlnoxhppzgyds" Message-Id: <20011122190651.637DC199E7@mail.cse.psu.edu> Date: Thu, 22 Nov 2001 19:06:27 +0000 Topicbox-Message-UUID: 283a0ffc-eaca-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-jmqgjmurtwcsxrlnoxhppzgyds Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit > It will help a lot if you have graphics working on this system in > some other operating system that lets you poke at the VGA card, > to read out a working register dump. Such systems include Windows 9x, > Linux, and FreeBSD but not Windows NT or 2000. Are there ready-made tools which will give you a register dump or do you have to write something specific for each card? I have access to a machine with a #9 Imagine 2 which I would quite like to use as a plan 9 terminal. The t2r4 driver looks like it should work with a bit of tweaking. -- Richard --upas-jmqgjmurtwcsxrlnoxhppzgyds Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-admin@cse.psu.edu> Received: from punt-1.mail.demon.net by mailstore for miller@hamnavoe.demon.co.uk id 1006208908:10:22893:180; Mon, 19 Nov 2001 22:28:28 GMT Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net id af1112584; 19 Nov 2001 17:28 GMT Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.6.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 3207119A06; Mon, 19 Nov 2001 12:16:13 -0500 (EST) Delivered-To: 9fans@cse.psu.edu Received: from plan9.cs.bell-labs.com (ampl.com [204.178.31.2]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 3FF3D1998A for <9fans@cse.psu.edu>; Mon, 19 Nov 2001 12:15:14 -0500 (EST) Received: from plan9.cs.bell-labs.com ([64.232.178.9]) by plan9; Mon Nov 19 12:15:13 EST 2001 To: 9fans@cse.psu.edu Subject: Re: [9fans] More Mach64 Problems From: "Russ Cox" MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20011119171514.3FF3D1998A@mail.cse.psu.edu> Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.7 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Help: List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Mon, 19 Nov 2001 12:15:11 -0500 The problem is in fact the memory timings, but it's ever so difficult to figure out the exact bits without sitting there at the machine. (It's basically trial and error, which is much harder when it takes a day or two to do a round trip.) There's some code in /sys/src/cmd/aux/vga/mach64xx.c that handles sniffing the card and trying to get the timings set right, but it appears to fail on some cards, including apparently yours. If you're game, I can tell you how to tweak the registers and you can sit there poking bits until it works, but it's really an open-ended process: sometimes you get it, sometimes you don't. It will help a lot if you have graphics working on this system in some other operating system that lets you poke at the VGA card, to read out a working register dump. Such systems include Windows 9x, Linux, and FreeBSD but not Windows NT or 2000. I tried to help someone via email with this Mach 64 problem a month ago and it just didn't work, even with working register dumps to compare against. In the case of the person with the similar S3 problem, that was more easily fixed because the S3 chipset handles most of those calculations for you. We just had to add the card type to the driver. Russ --upas-jmqgjmurtwcsxrlnoxhppzgyds--