Reply 180 of 1037, by xjas
- Rank
- l33t
wrote:Thank you for running the tests and generating the files. These confirm that the issue is the PCI Command register being 0x0002 rather than 0x0003 is the root cause of the issue. Is there any reason for having the Rage as the primary VGA device?
If I set the Voodoo as primary, I can't enable dual-head mode & span the desktop, because I get an error that the frame buffer address space conflicts between the two cards & can't be remapped. With the Rage as primary it works fine. Someone mentioned in my other thread that some Rage cards have a jumper that allow them to be used as a secondary card, but this one doesn't. Anyway that's the only reason I'm using the Rage as primary in this system; it was really just an experiment to see if it would work.
wrote:I could get SIV to enable I/O Access, but feel I should have a think about this before making any changes, epically so as I plan to release SIV 5.42 tomorrow. I suspect it would be wise to wait 'till you have figured out why your get the 125 MHz rather than a 143 MHz clock first, what do you think?
BTW for the 3dfx the RAMDAC Clock is the current clock so if you change the display resolution this should change.
wrote:Why is the speed 166 MHz rather then 143 MHz, is this 3000 vs. 2000 please?
AFAIK it's supposed to be: Voodoo3 1000 (just a few OEM versions) = 125MHz, V3 2000 = 143MHz, 3000 = 166MHz, and 3500 = 183MHz, but obviously I've found a mutant card that identifies itself as a 2000 but still runs at 125MHz. The clock speed is the only major difference between the cards from the 2000 and up. (Some '1000' implimentations only had 8MB RAM and one TMU disabled.)
I'm pretty sure my card really is running at 125MHz, because that would bear out some benchmark results I got where it's slower than the K6-2 system despite the P3 itself being a significantly faster CPU.
wrote:This comes down to what AMD did, the PCI Device ID is made up of a Vendor ID + Device ID, ATI was vendor 1002 and AMD is vendor […]
wrote:(One thing that's bugging me a little is the reporting of ATI cards as AMD cards
This comes down to what AMD did, the PCI Device ID is made up of a Vendor ID + Device ID, ATI was vendor 1002 and AMD is vendor 1022, but AMD now use 1002 for such as my AMD Radeon RX 5700 which has an ID of 1002-731F. Clearly it should be reported as AMD so to do what you would like I would need to know which Vendor 1002 Device IDs were ATI. This would be possible, but I feel the effort needed would be excessive just to say ATI rather than AMD. Looking on my Matisse system the Device IDs for RX 5700 are not even adjacent.
[ 10 - 00 - 0 ] 4 1002-1478-00000000-C4 PCI Bridge (10-11:12) x8@4 (x16@4) AMD Radeon Navi PCIe Switch Upstream Port
[ 11 - 00 - 0 ] 4 1002-1479-00000000-00 PCI Bridge (11-12) x16@4 (x16@4) AMD Radeon Navi PCIe Switch Downstream Port
[ 12 - 00 - 0 ] 1002-731F-0B361002-C4 VGA Controller x16@4 (x16@4) AMD Radeon RX 5700 [GPU-1]
[ 12 - 00 - 1 ] 51 1002-AB38-AB381002-00 High Def Audio x16@4 (x16@4) AMD Radeon Navi 10 HDMI Audio
I was afraid that was the case... If it leads to some horrible GPU-by-GPU checks and spaghetti code, it's not worth doing, IMHO. Maybe others feel more strongly about it than I do. I just like seeing ATI's good old red logo where it's appropriate. 😉
twitch.tv/oldskooljay - playing the obscure, forgotten & weird - most Tuesdays & Thursdays @ 6:30 PM PDT. Bonus streams elsewhen!