Sapphire Radeon R9 290 Tri-X OC

[Doom4535]

Do any of you know how to get the r9 290 to work with linux?  I've been having issues with opencl support, ect.

The same as every other ATI card, but make sure you use thr 13.12 drivers (earlier drivers and 14 beta won't work with the hawaii cards).

Ah, thanks.  I've been trying to use the 14 beta...

[mrmork666]

How are the fan noise compared to stock r9 290x?

[cloudrck]

Do any of you know how to get the r9 290 to work with linux?  I've been having issues with opencl support, ect.

I have this exact card, and the 13.10 drivers didn't even recognize it. The 13.12 work find though

[phzi]

How are the fan noise compared to stock r9 290x?

Endlessly quieter, even at 100% it is reasonable to sit right next to.

[flipme]

I run 2 of them on SMOS 1.3 with Catalyst 13.12 and cgminer kalroth

One is running smoothly at 925 khash / 70 C at 1065/1250 with TC 30719

Two blacks out at 890 khash at 1010/1250 and is 6-8 C warmer, already when idle.
I also have to lower TC to 25559, or it crashes after some hours.

I would undervolt the second one, but how to?

[lenart_o]

what are your settings phzi? i cant pull much more than 912 on both of mine.

Right now I have stabilized to:

Code:

"gpu-threads" : "1",
"xintensity" : "1100",
"thread-concurrency" : "25601",
"worksize" : "512",
"lookup-gap" : "2",

"gpu-fan" : "80",

"gpu-powertune" : "20",
"gpu-memclock" : "1499,1499,1499,1250",
"gpu-engine" : "1060,1060,1060,1020"

This yields consistently over 945KH/s (945-948) and over 900KH/s (901-905).  Reject rates are down around 0.3% (almost all my rejects are because of vardiff causing Share above target), and WU is consistent with hashrate.

The 1250/1020 card faults after about an hour if I push it beyond 1040, so I pulled it back to 1020 as seems to be stable so far.

Hi I have problem with these cards, when i put on mobo direct whitout risers cards working stable for weeks but when I connect any riser (16x16, 1x16, and new usb riser) after 2-3 minutes computer switching off and I can't switch it on after unplug power from the wall and wait 1-2 min then mobo start normal.I try on windows, linux , with diffrent drivers but I think it's not problem with drivers. can anyone help me with this?

[phzi]

Hi I have problem with these cards, when i put on mobo direct whitout risers cards working stable for weeks but when I connect any riser (16x16, 1x16, and new usb riser) after 2-3 minutes computer switching off and I can't switch it on after unplug power from the wall and wait 1-2 min then mobo start normal.I try on windows, linux , with diffrent drivers but I think it's not problem with drivers. can anyone help me with this?

Sounds like a power issue.  How many cards, what motherboard, and what PSU?

[Ik88]

Guys help, one 290x Tri-X cant work "Scrypt" all time driver down ((( only "kessak" work !.. all games work normal.

Help plz

[ozzy1926]

should we install ADL_SDK when using 13.12 @win 7 64 bit?

[Ik88]

should we install ADL_SDK when using 13.12 @win 7 64 bit?

i use this combination

[ozzy1926]

should we install ADL_SDK when using 13.12 @win 7 64 bit?

i use this combination

also i would like to know i have i4770k but i when i enabled  igpu i cant use my r290s.Why is that?

[Ik88]

should we install ADL_SDK when using 13.12 @win 7 64 bit?

i use this combination

also i would like to know i have i4770k but i when i enabled  igpu i cant use my r290s.Why is that?

i too cant use integrated and 290 (((

[phzi]

You should NEVER install ADL_SDK unless you are compiling your own mining software.  It is for development only, and serves no purpose otherwise.

Ik88: you try downclocking the memory?  kessak doesn't use much memory, whereas scrypt is highly dependent on memory bandwidth.

[Ik88]

You should NEVER install ADL_SDK unless you are compiling your own mining software.  It is for development only, and serves no purpose otherwise.

Ik88: you try downclocking the memory?  kessak doesn't use much memory, whereas scrypt is highly dependent on memory bandwidth.

Yep i use 1200-1250 Mhz memory and all time crash driver ((( games not crash (((

[dloganbill]

I made some headway last weekend.  I gave up on Linux after being unsuccessful with BAMT and SMOS.  I installed Windows 8.1 and was mining in 30 minutes.  Amazon still hasn't shipped my 1300W PSU so I'm currently only running 5 GPUs with an 850W and 1050W.  Out of the box they were all running around 860 kh/s.  I've spent the last couple evenings tuning and things are looking promising. 
Things I learned along the way that seem to have helped:
1. Use Catalyst 13.12.  The 14.2 beta drivers were very unstable.
2. Don't bother with Trixx.  Install MSI Afterburner and use the settings shown on this post (link).
3.  I don't know if this helped or not, but I'm currently running with the bios switch toggled up (toward the end with DVI ports)

I think I can push them a little harder, but am currently limited by power.  The 1050W is essentially maxed out, so I have the engines turned down on some.  Here is my screen after 6 hours of mining.  I would have had a longer run time, except the power blinked last night and for some reason it didn't autostart like it should have.



Here are my current settings.

Code:

"intensity" : "20,20,20,20,20",
"xintensity" : "0,0,0,0,0",
"rawintensity" : "0,0,0,0,0",
"worksize" : "512,512,512,512,512",
"kernel" : "ckolivas,ckolivas,ckolivas,ckolivas,ckolivas",
"lookup-gap" : "2,2,2,2,2",
"thread-concurrency" : "25601,25601,27401,25601,27401",
"shaders" : "0,0,0,0,0",
"gpu-threads" : "1,1,1,1,1",
"gpu-engine" : "1040,1020,1020,1040,1020",
"gpu-memclock" : "1500,1500,1500,1500,1500",
"gpu-memdiff" : "0,0,0,0,0",
"gpu-powertune" : "20,20,20,20,20",
"gpu-vddc" : "0.000,0.000,0.000,0.000,0.000",
"temp-cutoff" : "90,90,90,90,90",
"temp-overheat" : "85,85,85,85,85",
"temp-target" : "78,78,78,78,78",
"auto-fan" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "1",
"failover-only" : true,
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "10",
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "1",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"device" : "0,1,2,3,4"
}

[phzi]

@dloganbill:
- try running everything at the same thread concurrency.
- switch to xintensity instead of intensity to gain a few more KH/s (try xintensity 300 or 400 - adjust higher for a few more kh but potentially higher rejects depending on what pool you are mining with)
- with wafflepool, you can tune (x)intensity pretty high, because they count what would normally be 'stale' shares as valid. e.g. a share that is 1 block outdated is still valid on WP - 1100 seems like a good balance on WP.
- try worksize 256.  I stopped using 512 entirely.
- try gpu-memclock at 1499 instead of 1500 for a few KH benefit on stock
- flash to STILT's BIOS and drop gpu-memclock to 1375 or 1400 and gain a few KH/s in the process
- I always say not to use auto-fan.  Try to find a stable fan % that will keep your cards cool and noise reasonable, and fix it.
- expiry should probably be at least 2 - you will find a lot of shares being considered stale when they aren't if you use 1.  I use 4/8 for scan-time and expiry on wafflepool.
- BAMT/SMOS kinda suck.  Try rolling your own linux install if you want stable linux.  But if you have the cards running stable on Windows, keep with it.  I have never had much luck getting cards/driver stable under windows over a long period.

[dloganbill]

Thanks for the pointers phzi.  I'll try them out tonight.

[dloganbill]

One more thing, can you point me in the right direction on the Stilt bios I need? I'm a little confused because I thought I remembered reading that his BIOS was only for reference cards.

[phzi]

One more thing, can you point me in the right direction on the Stilt bios I need? I'm a little confused because I thought I remembered reading that his BIOS was only for reference cards.

For reference-design motherboards only.  The Tri-X have a reference mobo.
See my post here: https://bitcointalk.org/index.php?topic=442852.msg5352740#msg5352740

[sesko]

dloganbill: did you use 13.12 Catalyst and modified inf files in win 8.1.