VOGONS


First post, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

I purchased this card a few months ago for around $30 USD. From the listing picture, the corner of TMU1 was badly damaged. 3 pins completely broken off. When the card arrived I also noticed the traces around the corner of the chip had also been partially ripped off. So now it looked the repair was job was going to be a little more difficult. According to this review http://www.dansdata.com/jatonv2.htm the Jaton Voodoo 2 only had 90MHz memory chips, however the particular revision I have had 100MHz chips. I was determined to get this thing fixed.

I ran MOJO and got the following infamous error messages;

TMU PowerOn Sense: 0xdead
Bogus number of TMUs (57005)

I started off with grinding away the corner of the chip to reveal the traces. I then connected some thin copper wire from those traces on TMU1 to the point where the traces were still intact on the PCB. I managed to repair the following;

56 TEX_DATA_0_4 - PCB trace repair
55 TEX_DATA_0_3 - Copper wire from chip to PCB trace
54 TEX_DATA_0_2 - Copper wire from chip to PCB trace
53 TEX_DATA_0_1 - Copper wire from chip to PCB trace

The attachment MojoBad.png is no longer available

Not the most beautiful job

The attachment LegsRepaired.JPG is no longer available

After the repairs MOJO was still giving 0xDead and bogus TMUs errors. Did some hunting and found 1 bent leg and a leg that was disconnected from the PCB on TMU1.

104 TEX_DATA_1_11
103 TEX_DATA_1_10

The attachment BentLeg.JPG is no longer available

Again, MOJO gave 0xDead and bogus TMUs errors. This time set the extra logging properties before running MOJO. The new log gave me;

ERROR: non-unique g_sum=0x030

set SST_INITDEBUG_FILE=sst.log
set SSTV2_INITDEBUG_FILE=sstv2.log

sst.log

sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 1
sst1InitMapBoard(): vAddr:0xde000000 pAddr:0xde000008 Dev:0xa Board:0
sst1InitRegisters(): Setting TREX-to-FBI FIFO THRESHOLD to 0x8...
sst1InitRegisters(): Setting PRELIM FT-CLK delay to 0x8...
sst1InitRegisters(): Storing TREX0INIT0=0x5441
sst1InitRegisters(): Storing TREX0INIT1=0xf420
sst1InitRegisters(): Storing TREX1INIT0=0x5441
sst1InitRegisters(): Storing TREX1INIT1=0xf420
sst1InitRegisters(): Storing TREX2INIT0=0x5441
sst1InitRegisters(): Storing TREX2INIT1=0xf420
sst1InitSetGrxClk(): Resetting TMUs after clock change...
sst1InitRegisters(): Setting up FAST DRAM Configuration
ERROR: non-unique g_sum=0x030
sst1InitFillDeviceInfo(): Retry #1 for chip GetInfo()...
ERROR: non-unique g_sum=0x030
sst1InitFillDeviceInfo(): Retry #2 for chip GetInfo()...
ERROR: non-unique g_sum=0x030
sst1InitFillDeviceInfo(): Retry #3 for chip GetInfo()...
ERROR: non-unique g_sum=0x030
sst1InitFillDeviceInfo(): Retry #4 for chip GetInfo()...
ERROR: non-unique g_sum=0x030
sst1InitRegisters(): ERROR filling DeviceInfo...

I then spent many hours checking every single resistor and looked for cracked capacitors but found nothing. In hindsight, I should have checked the legs on the other chips. Sure enough the FBI had a loose leg on;

66 FB_DATA_34

Finally MOJO was happy!

But nothing is certain until you check games.....Tomb Raider and Descent 2 are running perfectly! So happy. Another Voodoo saved.

The attachment Games.png is no longer available
The attachment JatonV2.jpg is no longer available

Many thanks to Bits und Bolts (Youtube), vswitchzero (Youtube) and sdr (Vogons) for all their knowledge.

Last edited by zuldan on 2025-03-31, 10:48. Edited 3 times in total.

Reply 1 of 13, by StriderTR

User metadata
Rank Member
Rank
Member

Very nice! Amazing repair! Nice to see these getting saved.

I've seriously considered going down this road many times if I ever come across a PCI voodoo for my DOS rig super cheap being sold as parts. I have the tools and "skills" for such a repair, I just haven't had the luck. 😜

Retro Blog & Builds: https://theclassicgeek.blogspot.com/
3D Things: https://www.thingiverse.com/classicgeek/collections
Wallpapers & Art: https://www.deviantart.com/theclassicgeek

Reply 2 of 13, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie
StriderTR wrote on 2025-03-30, 07:42:

Very nice! Amazing repair! Nice to see these getting saved.

I've seriously considered going down this road many times if I ever come across a PCI voodoo for my DOS rig super cheap being sold as parts. I have the tools and "skills" for such a repair, I just haven't had the luck. 😜

Thanks for the kind words. I think I got lucky. However, I’ve come across a problem…

Tomb Raider - Perfect
Descent 2 - Perfect
3DMark99 - Perfect
Quake 2 - Some texture issues, mainly in the menu console screen and some spotting during game play

Will post some pictures tomorrow. I’m using Fastvoodoo drivers which work fine in my Diamond cards. I doubt it’s a driver issue though. Need to do some more research.

Reply 3 of 13, by Postman5

User metadata
Rank Member
Rank
Member

It's great to see the results of your inspiring work! Unfortunately, there are no programs that allow you to test TMU. I carefully examine the textures in the demo Donut_glide2x and look for pins torn off from the contact pads under the TMU memory chips.

Reply 4 of 13, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie
Postman5 wrote on 2025-03-30, 10:02:

It's great to see the results of your inspiring work! Unfortunately, there are no programs that allow you to test TMU. I carefully examine the textures in the demo Donut_glide2x and look for pins torn off from the contact pads under the TMU memory chips.

Here is what Quake 2 looks like in-game. You can hardly noticed the spots on the ground. Everything else in the game looks normal. You wouldn't really notice the issue until someone pointed it out.

The attachment Quake2.jpg is no longer available

I ran set SSTV2_NUM_TMUS=1 before running Quake 2 and got the following result. All texture issues gone when set to 1. Do you know which TMU is disabled?

The attachment Before.jpg is no longer available
The attachment After.jpg is no longer available

I couldn't see any texture issues with the Donut demo? (sorry about the dust and wires on the screen. I got to sort that out 🤣)

The attachment Donut1.jpg is no longer available
The attachment Donut2.jpg is no longer available

Reply 5 of 13, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

I used an IR gun to work out which TMU gets disabled when you use SSTV2_NUM_TMUS=1. TMU0 got 5c hotter than TMU1 when running timedemo's on Quake 2. So TMU1 is disabled with that variable.

The attachment Board Layout.jpeg is no longer available

I tested all the pins again on TMU1 (the TMU with all the damage) with some tweezers for movement and BINGO found the following leg disconnected from the pad. I must have missed it on my first sweep.

105 TEX_DATA_1_12

So here is a recap of what had to be repaired on TMU1

Red = Disconnected leg from PCB
Yellow = Trace repair
Orange = Had to grind down chip to reveal chip traces

The attachment 3DFX_500-0004-02_TMU.png is no longer available

I suspect the main cause of the errors in MOJO was the disconnected leg on the FBI

66 FB_DATA_34

Quake 2 is working PERFECTLY now. I ran some other games and 3dMark99 a few more times. I'm happy to call this card 100% fixed.

Reply 6 of 13, by Postman5

User metadata
Rank Member
Rank
Member

Thank you for sharing this valuable repair information!

Reply 7 of 13, by grjr

User metadata
Rank Newbie
Rank
Newbie

It seems like a common issue that these cards have are pins being ripped from their pads and/or simply being knocked loose. I think to make repairs quicker on these reflowing all pins around the TMUs and FBI chips would be a first step.

Reply 8 of 13, by ZenecadE

User metadata
Rank Newbie
Rank
Newbie

I wish I could get mine working. I've gone through my board and can verify all traces are in tact, all pins on FB and both TMU's checked and connected and no components missing or shorted but still no joy at getting the card working. Every once in a while it comes out and I go through more checking and testing but alas. One day it will work again.

Reply 9 of 13, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie
ZenecadE wrote on 2025-04-09, 09:40:

I wish I could get mine working. I've gone through my board and can verify all traces are in tact, all pins on FB and both TMU's checked and connected and no components missing or shorted but still no joy at getting the card working. Every once in a while it comes out and I go through more checking and testing but alas. One day it will work again.

Highly recommend you making a post about your card. Describe everything you’ve done so far. Provide high resolution photos and provide mojo logs. Someone may give a hint as to what the problem may be 👍

Reply 10 of 13, by Postman5

User metadata
Rank Member
Rank
Member

Perhaps such a guide exists 😀

Reply 11 of 13, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

Just a little update (and a nugget of gold for someone else trying to fix their card).

After running Quake 2 for a while, the textures started going a bit wonky. Restarted Quake 2, textures are perfect but then go wonky again after a while. I thought maybe some additional legs were loose on TMU1, so I reflowed all the legs. To my dismay, the texture issue still persisted in Quake 2. No issues in 3dMark99. Anyway, I had a think about it. Why were the textures go from working perfectly to wonky after a while. If they start off being perfect, then maybe it's not a connectivity issue between components.

The attachment Wonky.jpg is no longer available

So I had an idea....I changed the memory clock from 93MHz to 90MHz using v2oc1400.zip

The attachment v2oc1400.zip is no longer available

and now all texture issues are gone. My FPS in Quake 2 went from 52 to 51.7 so no big loss.

The attachment IMG_8042.JPG is no longer available

I found some nice time demos to stress your Voodoo 2 with Quake 2. They both give the TMU's a good work out.

The attachment crusher.zip is no longer available
The attachment massive1.zip is no longer available

Reply 12 of 13, by Spark

User metadata
Rank Newbie
Rank
Newbie

Sounds like the 3dfx chips on the card would benefit from active cooling.

Reply 13 of 13, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie
Spark wrote on 2025-04-12, 11:04:

Sounds like the 3dfx chips on the card would benefit from active cooling.

There is a 120mm fan blowing right on it. IR gun say TMU/FBI chips sit around 45c. I’m using FastVoodoo drivers so maybe they overclock the Voodoo by default.