Noticed something odd about the Nitro Fury; if I increase the power limit, it’ll just shut the whole computer off when put under load. If I toggle on the alternate BIOS (dual BIOS card), that’ll work, though I haven’t noticed it helping OC much. Just seems an odd design choice to power off the whole freakin’ computer when increasing the PL, instead of just locking it.
Maybe it’s just acting weird because I’m using Linux+CoreCtrl instead of MSI Afterburner.
Your PSU will power off the whole computer if its overvolt / overcurrent protection is tripped out. The GPU should in theory just crash and force a driver restart. If you were on windows I’d suggest diving into the Event Viewer and seeing if there is a system log for critical Kernel-Power event, I don’t know what the Linux equivalent might be.
Is this related to it reporting as an X when it is not. If it has been lashed to think it is an X it could be trying to auto oc beyond what the card is capable of.
It was some hacked drivers (Nimez?) that detected the card as a Fury X. Linux sees it as:
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] (rev cb)
So I don’t think it’s got a funky BIOS. And it can definitely handle going over the power limit - if I enable the alternate BIOS. IIRC it did the same thing under Windows if I tried to pump up the PL with the main BIOS.
Sapphire Fury Tri-X (the model you seem to have) has a power limit change between bios switches. One of them runs at over 300~350 watt (I remember thinking that was daft reading a review of it) the other tries to keep to sub 300watt limit and a fan curve targeting 70c or 80c. IDK which way the switch needs to be in order to be the sane sub 300 watt limit.
If not mistaken, them HBM memory chips were the most finicky part, when it came to OC trials
That entire dang cards HS/Shroud, is effectively a well overbuilt assembly, for bulk of typical woes
Been playing around with this R7 1700 as well as the R9 Fury. Overclocked the 1700 to 3.9GHz @ 1.306v. Another benchmark from a AAA native game, Shadow of the Tomb Raider.
Settings are High with TAA and CAS enabled at 1080p.
Sounds like power supply over current protection to me.
My Vega 64s (as in, one of them in a single box) will trip some 850w power supplies with brief huge power spikes - but… only under Linux. Not windows. Maybe the fury does similar under Linux as well. I suspect AMDs open source driver (or some other Linux quirk) has some funky issues with the high end niche amd HBM cards.
Oh, and that’s at stock clocks. No tweaking.
you have it the wrong way round mate.
turn textures down to medium/normal
and turn up things like world detail to medium high.
leave off AA. volumentrics(clouds/lights) on but low.
hbao+ on medium.
high textures are for 1440p and ultra for 4k.
so you wont need anything more than medium at 1080p.
saving lots of vram for the other stuff.
As if the R9 Nano, wasn’t annoying [enough] to scrounge for…
I have a Radeon Pro Duo i picked up for $120 Used and it was a pretty decent deal, but honestly wasnt worth it apart from the cool factor from owning said GPU, most of my games ran at sub 50 FPS at med/high settings at 1440
and i just realised i answered someone from 7 years ago… 
Looks like this is all earlier this year to me.
I notice a distinct lack of video outputs on the Instinct cards displayed. How does one get around that issue? I do recall a thread about someone doing the same with a Nvidia Tesla, but I’m not sure the same method would work with AMD & Linux.
The instinct cards have one, it requires vBIOS flashing and cutting part of the bracket out of the way.
If I remember right, the MI8 doesn’t require a flash. The MI25 certainly does as I found out for myself. The videos already posted sure would have answered that, but whatever.
Neato. So is the mini-DP port already there, lurking behind the bracket? Or did you have to solder it to some traces on the board?
Did i mention soldering? No, I did not solder ANYTHING.
This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.
