try using xIntensity in CGMiner 3.7.3 or SGMiner 4.1.0
intensity is a direct multipier. meaning.
Int Threads
13 8192
14 16384
15 32768
16 65536
17 131072
18 262144
19 524288
20 1048576
the jump at 20 basically overloads the cards.
using xInt allows you to tune it because its a nuliplier of your shader count. The 290 has a shader count of 2560. so an equivilent Xint in comparison to Int 19 is
Int Threads
19 524288
524288 / 2560 = 204.8.
i currently have mine at an xInt of 256 as it a nice mulitplier of 4.
xInt Threads
256 655360
good luck!
Also, as a reminder, your thread concurrency is usually best at a multiplier of your shader count plus 1 so 2560*N+1 mine currently set at a mulitplier of 12. (2560*12+1) = 30721.
Topic: Asus R9 290 problems - page 2. (Read 1266 times)
Post your config here.
But regardless, since you used to handle 280x I'd venture to guess you're using -g 2 ? If that's the case than R9 290 are using -g 1 and with that you can also increase the TC (20481, 24500, 32765 works for most pretty well).
But regardless, since you used to handle 280x I'd venture to guess you're using -g 2 ? If that's the case than R9 290 are using -g 1 and with that you can also increase the TC (20481, 24500, 32765 works for most pretty well).
Hi, thanks for the reply.
I have actually stripped back the entire config to realise it was the intensity causing the issues...
but i had already changed the -g 1 after spending the last few hours on google trying to fix this before posting here...
my config is purely stock right now - its simply when i change the intensity it goes crazy - stock intensity is 8 - even trying the 280x "normal" of 13 causes issues so you can imagine what happens when i go -I 20
Post your config here.
But regardless, since you used to handle 280x I'd venture to guess you're using -g 2 ? If that's the case than R9 290 are using -g 1 and with that you can also increase the TC (20481, 24500, 32765 works for most pretty well) and after that you can increase your -i.
But regardless, since you used to handle 280x I'd venture to guess you're using -g 2 ? If that's the case than R9 290 are using -g 1 and with that you can also increase the TC (20481, 24500, 32765 works for most pretty well) and after that you can increase your -i.
Hi guys - so im having issues...
i decided to build another rig this time using Asus 290's not X.
i have built many many rigs based on 280x with not many issues but this time im stumped.
so 3 x Asus 290 all being detected as i would expect running via windows 7 64bit in cgminer 3.7.2
i came to write the BAT file and the issues start, as soon as i enter an intensity number over stock(
i get HW errors galore.
Everyone seems to be running these cards at 20 with no problems....
if i run without an intensity number specified everything runs fine... everything else is tweaked.
problem is it is only hashing at 30kh/s or something like that...
ideas?
full spec
3 x Asus r9 290
asrock MB - fatal1ty z77
80+ platinum PSU 1200w
6GB ram
intel something processor
windows 7
cgminer 3.7.2
drivers 13.2 suite - i thought this could be my problem, but have used this fine on every build i have done
i decided to build another rig this time using Asus 290's not X.
i have built many many rigs based on 280x with not many issues but this time im stumped.
so 3 x Asus 290 all being detected as i would expect running via windows 7 64bit in cgminer 3.7.2
i came to write the BAT file and the issues start, as soon as i enter an intensity number over stock(
i get HW errors galore.Everyone seems to be running these cards at 20 with no problems....
if i run without an intensity number specified everything runs fine... everything else is tweaked.
problem is it is only hashing at 30kh/s or something like that...
ideas?
full spec
3 x Asus r9 290
asrock MB - fatal1ty z77
80+ platinum PSU 1200w
6GB ram
intel something processor
windows 7
cgminer 3.7.2
drivers 13.2 suite - i thought this could be my problem, but have used this fine on every build i have done
Jump to: