VOGONS


First post, by DonutKing

User metadata
Rank Oldbie
Rank
Oldbie

I had a system with 2 12MB STB Voodoo 2's in SLI. Iuse past tense here as it appears only one of the cards is working and so no more SLI 🙁

One of the cards seems to work fine. The are both detected in Device Manager.
When the faulty one is installed in the system, whether by itself or in SLI with the working one, I get this error upon launching any Glide game:

yb4WuSm.jpg

When I try to go into the Desktop properties and click the Voodoo tab, I get this error:

x4n7bYM.jpg

If I remove the faulty one, the other one works fine.

I have tried different motherboards, reinstalled Win98, tried the reference 3.02 drivers and FastVoodoo 4.6 drivers, swapped PCI slots, swapped primary video cards...

I've inspected the card and as far as I can see there are no damaged components, the legs on the chips all appear to be straight and not shorted. I've cleaned the PCI contacts and blown dust off the card with compressed air.

Any other ideas or is the card basically rubbish?

If you are squeamish, don't prod the beach rubble.

Reply 2 of 13, by Tronix

User metadata
Rank Member
Rank
Member

Some quick and dyrty tricks to diagnose your Voodoo2:

First of all, you need clean system with MS-DOS. Pentium 1 or 2 class machine is ideal. Pentium III, 4 and later PC is a bad choice for diagnoses purpose. Do not use any type of overclocking your system, run it with default CPU, Memory and BUS clocks. PCI = 33 MHz.

Secondly, you need download 3dfx Glide2 SDK for DOS/Win32 V2.43 and unpack gwebvgr3.exe. Then change dir to /Glide/Diags/DOS and find diagnose utility MOJO.EXE . Run it with clean MS-DOS enviropment and analyze results.

And, thirdly: glide use some enviropment settings to configure and logging itself. You can try add some string to your AUTOEXEC.BAT for deeper logging whats going on with your Voodoo2:

set SST_INITDEBUG=1
set SSTV2_INITDEBUG=1
set SST_INITDEBUG_FILE=c:\sst1_3dfx.log
set SSTV2_INITDEBUG_FILE=c:\sst2_3dfx.log
set SST_DEBUGDAC=1
set SSTV2_DEBUGDAC=1

Run MOJO.EXE again and then analyze files sst1_3dfx.log and sst2_3dfx.log on your hard disk. If MOJO.EXE halting system, and sst1_3dfx.log and sst2_3dfx.log have zero size when reboot, you can redirect logging output to screen (or RS-232 or printer port):

set SST_INITDEBUG_FILE=CON
set SSTV2_INITDEBUG_FILE=CON

https://github.com/Tronix286/

Reply 3 of 13, by DonutKing

User metadata
Rank Oldbie
Rank
Oldbie

Many thanks for the response, I ran the mojo.exe utility and get this output:

qiuelGdl.jpg

Below is the log file:

sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 1
sst1InitMapBoard(): vAddr:0xde000000 pAddr:0xde000008 Dev:0xd 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,0x37)
dacWr(0x4,0xa)
dacWr(0x5,0x7b)
dacWr(0x5,0x6c)
dacWr(0x4,0xe)
dacWr(0x5,0x27)
sst1InitSetGrxClk(): Resetting TMUs after clock change...
sst1InitResetTmus(): Could not reset TMUs...

However I put in my working Voodoo 2 and seem to get the same output on screen and in the log file?

If you are squeamish, don't prod the beach rubble.

Reply 4 of 13, by DonutKing

User metadata
Rank Oldbie
Rank
Oldbie

I put both cards in and now I get a different result:

sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 2
sst1InitMapBoard(): vAddr:0xde000000 pAddr:0xde000008 Dev:0xd Board:0
sst1InitMapBoard(): vAddr:0xdf000000 pAddr:0xdf000008 Dev:0x11 Board:1
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)
sst1InitRegisters(): Setting up FAST DRAM Configuration
sst1DeviceInfo: Board ID: Obsidian GE
sst1DeviceInfo: FbiConfig:0x2, TmuConfig:0x8d1
sst1DeviceInfo: FBI Revision:2, TMU Revison:1, Num TMUs:2
sst1DeviceInfo: FBI Memory:4, TMU[0] Memory:4, TMU[1] Memory:4
sst1DeviceInfo: Dac Type: ICS ICS5342
sst1DeviceInfo: SliDetect:0
sst1InitRegisters(): LFB Writes go through memory FIFO...
sst1InitRegisters(): TEXTURE Writes go through memory FIFO...
sst1InitRegisters(): exiting with status 1...
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
Show last 32 lines
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)
sst1InitRegisters(): Setting up FAST DRAM Configuration
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #1 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #2 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #3 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #4 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitRegisters(): ERROR filling DeviceInfo...
sst1InitShutdown(): Shutting down SST-1 #0...
sst1InitSetGrxClk(): Entered...
dacWr(0x7,0xe)
dacRd(0x5,0x0)
dacWr(0x4,0xa)
dacWr(0x5,0x41)
dacWr(0x5,0x62)
dacWr(0x4,0xe)
dacWr(0x5,0x0)
sst1InitShutdown(): Returning with status 1...

This section is of note:

sst1InitRegisters(): Setting up FAST DRAM Configuration
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #1 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #2 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #3 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitFillDeviceInfo(): Retry #4 for chip GetInfo()...
ERROR: non-unique r/b_sum=0xf80
sst1InitRegisters(): ERROR filling DeviceInfo...
sst1InitShutdown(): Shutting down SST-1 #0...

Could it be a faulty DRAM chip?

If you are squeamish, don't prod the beach rubble.

Reply 5 of 13, by bjwil1991

User metadata
Rank l33t
Rank
l33t

Did the same diagnostics as well and no errors in the log files.

SST1_3DF.log - MS-DOS mode (cleaned up the autoexec.bat file)
SST1_3DFX.log - Windows 9X
VooDoo2.txt - made using this command: MOJO > VooDoo2.txt in MS-DOS mode

Filename
VooDoo2 Logs.zip
File size
2 KiB
Downloads
138 downloads
File comment
VooDoo2 Logs
File license
Fair use/fair dealing exception

Discord: https://discord.gg/U5dJw7x
Systems from the Compaq Portable 1 to Ryzen 9 5950X
Twitch: https://twitch.tv/retropcuser

Reply 8 of 13, by RadiTwo

User metadata
Rank Newbie
Rank
Newbie

I have a basically pristine Creative Voodoo 2 CT6670.
Looks like it´s never been used.
It has EXACTLY the same error log with mojo as Donut King back in 2019 with his card.
FBI Memory shows 0 MB and TMU PowerOn Sense is 0xdead.

Has anybody an idea what causes this?

Reply 9 of 13, by drosse1meyer

User metadata
Rank Member
Rank
Member
RadiTwo wrote on 2023-07-26, 16:03:
I have a basically pristine Creative Voodoo 2 CT6670. Looks like it´s never been used. It has EXACTLY the same error log with mo […]
Show full quote

I have a basically pristine Creative Voodoo 2 CT6670.
Looks like it´s never been used.
It has EXACTLY the same error log with mojo as Donut King back in 2019 with his card.
FBI Memory shows 0 MB and TMU PowerOn Sense is 0xdead.

Has anybody an idea what causes this?

I would start with checking for missing caps/resistors, disconnected/shorted pins, verify the chip(s) is getting voltage, tone out traces, etc.

P1: Packard Bell - 233 MMX, Voodoo1, 64 MB, ALS100+
P2-V2: Dell Dimension - 400 Mhz, Voodoo2, 256 MB
P!!! Custom: 1 Ghz, GeForce2 Pro/64MB, 384 MB

Reply 10 of 13, by bloodem

User metadata
Rank Oldbie
Rank
Oldbie
RadiTwo wrote on 2023-07-26, 16:03:
I have a basically pristine Creative Voodoo 2 CT6670. Looks like it´s never been used. It has EXACTLY the same error log with mo […]
Show full quote

I have a basically pristine Creative Voodoo 2 CT6670.
Looks like it´s never been used.
It has EXACTLY the same error log with mojo as Donut King back in 2019 with his card.
FBI Memory shows 0 MB and TMU PowerOn Sense is 0xdead.

Has anybody an idea what causes this?

This may not necessarily be the case for your particular card, but I've seen those exact Mojo errors when trying Voodoo 2 cards - which are known working - on specific motherboards with certain VIA chipsets. Last time I saw this problem was on a VIA KT266A motherboard. I tested three different fully working Voodoo 2 cards (Diamond, Gainward, Creative) and Mojo reported the same problems for all of them. Furthermore, all three cards were completely unusable in Win98SE (display out of range or Windows freezing during boot after installing the Voodoo 2 drivers, etc).

So, my suggestion is to always try the card on multiple boards. Personally, my go-to platform for testing Voodoo 2 cards (and making sure that they actually work) is the 440BX. You can't go wrong with it.

1 x PLCC-68 / 2 x PGA132 / 5 x Skt 3 / 9 x Skt 7 / 12 x SS7 / 1 x Skt 8 / 14 x Slot 1 / 5 x Slot A
5 x Skt 370 / 8 x Skt A / 2 x Skt 478 / 2 x Skt 754 / 3 x Skt 939 / 7 x LGA775 / 1 x LGA1155
Current PC: Ryzen 7 5800X3D
Backup PC: Core i7 7700k

Reply 12 of 13, by BitsUndBolts

User metadata
Rank Newbie
Rank
Newbie
chaoscontrol wrote on 2023-08-26, 21:10:

Wasn't this on the Bits und Bolts youtube channel some time ago? I think it was the TMU solder detaching ever so slightly in the corners of the chips or something.

My card was a Diamond Monster 3D (Voodoo 1). In my case, the issue was a cracked resistor on the back of the card. I would check all solder joints on the 3Dfx chips and look for cracked SMDs.

Reply 13 of 13, by Thermalwrong

User metadata
Rank Oldbie
Rank
Oldbie
RadiTwo wrote on 2023-07-26, 16:03:
I have a basically pristine Creative Voodoo 2 CT6670. Looks like it´s never been used. It has EXACTLY the same error log with mo […]
Show full quote

I have a basically pristine Creative Voodoo 2 CT6670.
Looks like it´s never been used.
It has EXACTLY the same error log with mojo as Donut King back in 2019 with his card.
FBI Memory shows 0 MB and TMU PowerOn Sense is 0xdead.

Has anybody an idea what causes this?

For diagnostics output from the Voodoo 1 / 2 cards, the mojo.exe program has several break points that will give results like you're seeing if there are faults that register before the application reads out the FBI memory and TMU status. Resulting in the FBI having 0MB memory and 57005 TMUs 😀

To see what those are, you need to set up the logging environment variable to get an SST.log / SST2.log file in the same directory as mojo is in.
In my case the FBI was working so drivers could be installed, but it could not communicate with the DAC and therefore mojo.exe faulted out before FBI / TMU status was read. I've written out my experience with this error here: Re: What retro activity did you get up to today?