VOGONS


First post, by stlouis1

User metadata
Rank Newbie
Rank
Newbie

Hey everyone,

I have a voodoo 2 here that I've had since 2002. Recently pulled it out for a k6-2 machine and it's one of a matching pair I have, but it has issues. Part of it seems to be my own fault due to careless storage as 8-9 pins on the bottom right corner of the framebuffer chip were bent and shorted together which I didn't notice before powering it on. I was able to straighten them with a razer blade but it still doesn't work. I found some info and ran mojo and below is what I get.

As a best guess at the moment, I'm figuring that FB chip is pooched given the FBI memory detected is 0 and FBI PowerOn Sense is 0 as well. the traces for those pins that were bent seem to lead to the FB memory so it makes sense to me that part of the FB is buggered

DPMI: In DpmiHookFxMemmap, addr=e1000000, size=01000000
DPMI: Loading fxmemmap.vxd
DPMI: mapping e1000000 size 01000000
VoodooMEssage: pSST: 0x0 data0: 0x0 data1: 0xe1000001 fn: 0x1000000
DPMI: VoodooMessage: NULL ptr
Finally: 00000000
Info for Voodoo board # 0:
=====================================================
Virtual Base Address: 0xe1000000
Physical Base Address: 0xe1000008
PCI Device Number: 0xb
Vendor ID: 0x121a
Device ID: 0x2
FBI Revision: 2
FBI Memory: 0 MB
FBI PowerOn Sense: 0x0
TMU PowerOn Sense: 0xdead
FBI DAC Output Color Format: 24BPP
Scan-Line Interleaved? No
TMU Revision: 57005
Number TMUs: 57005
WARNING: Board 0: Bogus number of TMUs (57005)!
DpmiUnmapMemory
sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 1
sst1InitMapBoard(): vAddr:0xe1000000 pAddr:0xe1000008 Dev:0xb Board:0
sst1InitRegisters(): Setting TREX-to-FBI FIFO THRESHOLD to 0x8...
sst1InitRegisters(): Setting PRELIM FT-CLK delay to 0x8...
sst1InitDacDetect(): Entered...
sst1InitDacDetectICS(): Entered...
dacWr(0x7,0xb)
dacRd(0x5,0x79)
dacRd(0x5,0x2e)
dacWr(0x7,0x1)
dacRd(0x5,0x55)
dacRd(0x5,0x49)
dacWr(0x7,0x7)
dacRd(0x5,0x71)
dacRd(0x5,0x29)
sst1InitDacDetectICS(): Exiting...
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(): Entered...
dacWr(0x7,0xe)
dacRd(0x5,0x0)
dacWr(0x4,0xa)
dacWr(0x5,0x7b)
dacWr(0x5,0x6c)
dacWr(0x4,0xe)
dacWr(0x5,0x0)
sst1InitSetGrxClk(): Resetting TMUs after clock change...
sst1InitResetTmus(): Could not reset TMUs...

just wondering if anyone here might have a more experienced opinion before I get a replacement FB chip. I've had this card for 21 years and have no intention of letting it go that easily

Attachments

Reply 1 of 3, by Thermalwrong

User metadata
Rank Oldbie
Rank
Oldbie

Don't get a replacement FBI chip, it's working. To be clear, the FBI chip is managing PCI communication so if it detects in BIOS and mojo.exe detects it, the framebuffer chip itself is successfully performing most of its functions already.

The SST log file gives a clear indication of where the fault is:
1. The DAC is working
2. The TMUs are being initialised I think
3. It's failing out when it tries to reset the TMU, there can be a few causes of this, not really the FBI's fault

In this other thread someone had the same fault you've got, which was tracked down to a bad trace from the LS244 which provides the clock signals to the TMUs: Re: Voodoo 2 repair, missing legs on Chuck
Check out this video too: https://www.youtube.com/watch?v=tRFucW4uB5k
The big ASICs are much more resilient than the 25 year old PCBs they're attached to
See this thread for TMU pin information, we've confirmed the pinout for the TMU on the Voodoo 1 & Voodoo 2 are the same: 3Dfx Voodoo 1 - Low level hardware information and diagnostics thread

Maybe also check that the reset pin (pin 208) is soldered down solidly on both TMU chips, since it's right on the edge at pin 208 - I've found that pins on the edge are most likely to come loose over time.

Reply 2 of 3, by analog_programmer

User metadata
Rank Oldbie
Rank
Oldbie

Try to resolder these bent pins to contact pads on the PCB.

P.S. You can always use the "Video" section of the forum for videocard's related topics instead of this more common section.

from СМ630 to Ryzen gen. 3
engineer's five pennies: this world goes south since everything's run by financiers and economists
this isn't voice chat, yet some people, overusing online communications, "talk" and "hear voices"

Reply 3 of 3, by stlouis1

User metadata
Rank Newbie
Rank
Newbie

I've looked over those posts, and doing some probing with my meter around the DAC, clock and reset pins. Mine is a rev 2.0 card (picture attached) so the layout is a bit different. Where those threads reference a 74AC244 IC, my card has a 74LXC04 IC according to this diagram I found here

download/file.php?id=91548&mode=view

That said, meting the clck pin 186 on both TMU's, I get continuity with 22 ohm resistance on one of the pins on the 74LXC04. So traces appear to be fine there

FBI pin 227 also connects to a pin on 74LXC04 just fine, again, 22 ohm resistance

I also checked pin 11 on the DAC to the 74LXC04 and again found continuity between one of the pins there, and the DAC.

The reset pin 208 on each TMU has continuity to pin 197 on the FBI as well

as far as the idea of broken traces between any of those, that doesn't seem to be the case, unless I missed something.... this isn't exactly my area of expertise by any means...

The pins in the lower right of the FBI have been resoldered though, not as pretty as it was, but the joints are good

Attachments