From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: bcrawford Message-ID: <3BF8A8D6.6030909@hotmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit References: Subject: Re: [9fans] More Mach64 Problems Date: Mon, 19 Nov 2001 09:58:56 +0000 Topicbox-Message-UUID: 24572762-eaca-11e9-9e20-41e7f4b1d025 I have /exactly/ the same issue here with another mach64. Its not exactly the same card, but it has the same issue. One of the things I intend to try is running though the vagdb and hacking the id strings so as to fake the card type till i find one that works. (that part assumes that the id strings there do something aside from merely identifying the driver to use as 'yet another mach64', someone please let us know if this is/is-not the case). Several months ago, somone posted these symptoms with an (s3? (I found it on groups.google.com, but cant find it since)) card. The fix desribed a small hack to the drivers to zero the timings somehow. (this is hard to do without a workign display from which to modify the drivers & recompile... is there a howto on recompiling your kernel from a foriegn system?) Anyways, the short story is that this symptom has been seen and dealt with in the past by someone, so /someone/ has some idea how to deal with it.. if that someone is still out there, we would appreciate hearing from you. Cameron Morland wrote: > Hello, > > I managed to acquire a Mach64 Rage II PCI card, which appears to be > supported. Using a new download, I get > > aux/vga: controller not in /lib/vgadb > 0xC0000 55 AA 40 EB 7B D9 5A 00 00 00 00 00 00 00 00 00 U.@.{.Z......... > 0xC0010 00 00 00 00 00 00 00 00 58 01 00 00 00 00 49 42 ........X.....IB > 0xC0020 4D 00 37 7C 01 65 5A 08 00 00 00 00 00 00 00 00 M.7|.eZ......... > 0xC0030 20 37 36 31 32 39 35 35 32 30 00 00 9A 7B 57 D5 761295520...{W. > 0xC0040 33 3F 00 3C 00 00 00 00 0A 01 00 00 00 00 00 00 3?.<............ > 0xC0050 31 39 39 36 2F 31 32 2F 30 34 20 31 35 3A 34 39 1996/12/04 15:49 > 0xC0060 00 00 00 00 E9 42 51 00 E9 37 51 00 E9 DF 12 00 .....BQ..7Q..... > 0xC0070 00 00 00 00 00 00 00 00 00 00 00 00 9A 7B 57 D5 .............{W. > 0xC0080 E9 ED 00 0D 0A 41 54 49 20 4D 41 43 48 36 34 20 .....ATI MACH64 > 0xC0090 47 54 42 20 42 49 4F 53 20 50 2F 4E 20 31 31 33 GTB BIOS P/N 113 > 0xC00A0 2D 33 38 32 30 34 2D 31 30 32 20 0D 0A 00 28 43 -38204-102 ...(C > 0xC00B0 29 20 31 39 38 38 2D 39 36 2C 20 41 54 49 20 54 ) 1988-96, ATI T > 0xC00C0 65 63 68 6E 6F 6C 6F 67 69 65 73 20 49 6E 63 2E echnologies Inc. > 0xC00D0 42 4B 33 2E 38 2E 31 2F 33 2E 30 33 33 20 67 74 BK3.8.1/3.033 gt > 0xC00E0 67 70 31 6A 2E 61 73 20 36 20 4D 41 43 48 36 34 gp1j.as 6 MACH64 > 0xC00F0 47 54 50 43 49 55 59 4D 55 32 34 31 30 30 2D 34 GTPCIUYMU24100-4 > > Searching in vgadb, I find > > 0xC00E1="MACH64GTPCIUYMU" # ATI Rage II PCI > > Which has the wrong offset, but the right string. So I replaced the > 0xC00E1 with 0xC00EA. Now I get a video signal, but instead of being > the entire screen it is the first 1/3 of the screen, repeated 3 > times. The mouse moves over the whole screen (due to the hardware > cursor). I've tried some adjustment to the monitor size and type, but > no changes were apparent. (I'm running at 640x480x8 right now.) > > Actually it's not exactly the first 1/3. More precise would be: > > 0123 4567 89AB CDEF > > turns into > > 0123 4012 3451 2345 > > ie the three bands are slightly different. > > Suggestions? > > +---------------------------------------------------------- > | PGP http://www.eng.uwaterloo.ca/student/cjmorlan/pgp.txt > | cjmorland@uwaterloo.ca > | > | The easiest way to get shot is to carry a gun. > | --Atticus Finch > +----------------------------------------------------------