VOGONS


First post, by quattro64

User metadata
Rank Newbie
Rank
Newbie

Hello Everyone,

I've got my Q3D card that I'd love to refurbish. I've had it in storage since I last used it in the early 2000s.

I've run witchery off freedos. It asks for which card since the x-24 is sli on the one card. The first card under witchery is the main card.

So, here is what I've done, tried so far. Witchery isn't getting to the point where it is testing FB memory, it is failing at the ramdac. I also saw on one 3dfx troubleshooting site that cards that do pass through video but fail(black screen) when trying glide, which is what mine does, have bad ramdac chips. So I removed/replaced the 'bad' ramdac chip with a known working one. Still have same issue. Witchery asks about FBs, and voltages on either sides of FBs, Capacitors being above ~300 ohms, bad solder joints, checking for proper voltages, making sure no broken traces, Making sure certain pins between ramdac an fbi chip are connected, certain pins between ramdac and xtal are connected, no shorts between adjacent pins, no shorts between certain pins and 5v or gnd...etc. I've subsequently checked all RAs Rs Ls Cs and FBs on both sides of this board with a DMM and a Magnifying glass. No bad solder joints or traces, No bent pins on anything. Everything measures fine. It is a very clean looking card, a little dusty... Witchery also suggests reflowing fbi chip, which also I've done.

I then did some googling on the errors and on one link

What are some common failure modes for defective Voodoo2 cards?

One post mentions that a bad fb edo ram chip might keep the fbi chip from correctly communicating with the ramdac, which might be my problem? I'm very stumped at this point. Hoping it is a bad fb ram chip. But maybe the FBI chip?? If it could be the fb ram chips how would I try to narrow down which one(s)?

Thanks,

Will

Here are shots of witchery output:

Reply 1 of 9, by MikeSG

User metadata
Rank Oldbie
Rank
Oldbie

RAMDAC's do take input from the EDO RAM. If bad RAM is common that could certainly affect it.

In your last image .. the PCI and register settings to the FBI test OK so I would leave that, and mainly look at the EDO RAM.

Reply 2 of 9, by quattro64

User metadata
Rank Newbie
Rank
Newbie

Hi,

Thanks for your help, Any idea which one(s) to try first? in the thread I posted above, deeper into it they talk about limiting ram to 2mb using a variable in autoexec.bat. to narrow down which 2mb chunk of ram might be the problem. I will try that to see if it allows witchery to get past the ramdac error. Even if it does I am not sure which 4 chips to remove as different cards have their memory chip chunks set up differently... Also in that last image of mine it talks about unable to detect rs2 line? Any idea what that refers to? I've included a shot of mojo output and some more images of my card.

Reply 3 of 9, by MikeSG

User metadata
Rank Oldbie
Rank
Oldbie

RS2 is a register select pin (RS0-2) for internal settings. But it's possible the RAMDAC isn't ready or intialising properly.

RS0, RS1, RS2, WR, RD, CLK0... CLK0 (video clock output) is determined by internal PPL register setup. If there's no default values and it's not setup, clock output would be wrong.

In the last image, there's a TMU count error for Board 0. TMU Revision looks wrong and PowerOn Sense is "0xdead".

Maybe TMU's didn't finish setting up, so the RAMDAC wasn't initialised either.

So RAM closest to TMU's..... or TMU's...?

Reply 4 of 9, by quattro64

User metadata
Rank Newbie
Rank
Newbie

so I should also be looking at TMU ram and TMUs? there is a tool somewhere that checks tmu ram. I need to google for that again. should ai try and reflow the tmu chips? I think I will proceed with fb ram first.

Reply 5 of 9, by MikeSG

User metadata
Rank Oldbie
Rank
Oldbie

If EDO RAM is the most common fault, and there's no visible damage to the TMU's I would do the RAM first.

FBI RAM also reports as 0MB.

Reply 6 of 9, by quattro64

User metadata
Rank Newbie
Rank
Newbie

Swapped out entire bank of fb ram on the top of the board with new ram, reflowed solder on TMUs. Still same errors in mojo/witchery. Gonna take one back of board fb ram chip off at a time to see if I can get past this ramdac error... I understand this can also be the clock buffer chip. Witchery does mention it can be this chip u65 on my board, it is a 14 leg 74ACT125... ordered a few from digikey.

Reply 7 of 9, by quattro64

User metadata
Rank Newbie
Rank
Newbie

I took off one fb ram chip at a time from the back of the board, none fixed the issue. Also, did some thinking. When SLI board is attached, Witchery reports it's ramdac working and finds only one fb ram chip bad. There is no 74ACT125 chip or xtal on the SLI board, for ramdac chip to function there both should be good on the main board, right? If so I think I am down to a bad FBI chip or a broken trace between ramdac and FBI???

Reply 8 of 9, by MikeSG

User metadata
Rank Oldbie
Rank
Oldbie

IMO if the SLI board is supposed to be attached from the factory, the BIOS may stop before initialising the majority of the board. No RAMDAC setup, no TMU count, no FBI memory count...

Only read the Witchery results when the SLI board is attached....

If FBI pins are reflowed.. and RAM is all replaced, hard to think of anything else except replace the FBI not responding in Witchery

Reply 9 of 9, by havli

User metadata
Rank Oldbie
Rank
Oldbie

The daughterboard with secondary chipset can be removed and the rest wil work just fine as single Voodoo2 (with pci-pci bridge and TV-OUT). So if the suspected defect is on the primary board, then I suggest to debug the issues with second board disconnected.

HW museum.cz - my collection of PC hardware