Pages:
Author

Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 5. (Read 85750 times)

newbie
Activity: 4
Merit: 0
Team Red Miner v0.5.9 released

https://github.com/todxx/teamredminer/releases

Changes in v0.5.9
  • Added x16rv2 for the upcoming Ravencoin fork.
  • Optimization work on x16r: +8-10% hashrate depending on clocks.
  • Optimization work on x16r: mem clock no longer as important.
  • Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.

We've added x16rv2 algo for the upcoming Ravencoin fork! (Also BitCash and a few others)
We've also put a ton of effort to squeeze out as much performance as we could for the x16* algos in this release, with an up to 10% speed-up.
before this version ,teamredminer did not recognize AMD RX 5700.
This version recognize AMD RX 5700 as 'gfx1010'  and stop working , log statements are:
{
[2019-09-28 09:45:46] Initialize error, unknown device name: 'gfx1010'
[2019-09-28 09:45:46] Failed to initialize device idx 0 (-9)
[2019-09-28 09:45:46] Successful clean shutdown.
}
Please update teamredminer  to utilize  AMD RX 5700?
member
Activity: 449
Merit: 24
RX 5700 support also!
newbie
Activity: 17
Merit: 0
waiting for that 5700 support as well Cheesy
jr. member
Activity: 46
Merit: 4
Yeah, man, we navi miners need some love too, man.
full member
Activity: 251
Merit: 100
Still now news about 5700/xt support?
member
Activity: 176
Merit: 76
Team Red Miner v0.5.9 released

https://github.com/todxx/teamredminer/releases

Changes in v0.5.9
  • Added x16rv2 for the upcoming Ravencoin fork.
  • Optimization work on x16r: +8-10% hashrate depending on clocks.
  • Optimization work on x16r: mem clock no longer as important.
  • Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.

We've added x16rv2 algo for the upcoming Ravencoin fork! (Also BitCash and a few others)
We've also put a ton of effort to squeeze out as much performance as we could for the x16* algos in this release, with an up to 10% speed-up.
member
Activity: 658
Merit: 86
So, any updates on x16v2?

It'll be out in a few hours, just wrapped up testing. Stay tuned.

Released on our discord server and github now, todxx will update threads here on bitcointalk in a bit.
member
Activity: 658
Merit: 86
So, any updates on x16v2?

It'll be out in a few hours, just wrapped up testing. Stay tuned.
newbie
Activity: 19
Merit: 0
So, any updates on x16v2?
jr. member
Activity: 46
Merit: 4
So, any updates on Navi front?
member
Activity: 658
Merit: 86
Hi.
I have problem with my vega rig on grin 29.
Hashrate jumps from 4 to 6 mh constantly (every 1~2 seconds) on all gpus and non of them can reach 7mh.
I disabled all vegas and tried one by one but same problem appears on each of them in single mining mode. (This rig works fine with all other algos including c31)
On the other rig I have one vega (+some 580) and it works normal...constantly 7.3mh without hashreate drops.
On both rigs I use same odt settings and have same driver version (Adrenaline 19.6.2)
What can be the potential issue?

Temperature or power throttling.

It's not temperature (55~60) and as mentioned rig works great on all other algos.
How is possible that single gpu (while all other are disabled) has power throttling?
Rig works fine even with MPT and ProgPow which draw a lot more power.

If there's anything separating grin/cd29 from the other algos it's that it's _really_ pushing the amount of allocated vram per gpu. It's not the amount of swap available on your rig though, then it should run fine on a single gpu. I can't say I have heard about this issue before though, hmm.

Can you lock the p-states in ODNT just to make sure you aren't bouncing around? Also, can you check with HWiNFO64 how much vram you have available on the Vegas when you are idle vs when you are running cd29? Can you also check the same HWiNFO64 nrs on the rig that is working fine?

newbie
Activity: 50
Merit: 0
Hi.
I have problem with my vega rig on grin 29.
Hashrate jumps from 4 to 6 mh constantly (every 1~2 seconds) on all gpus and non of them can reach 7mh.
I disabled all vegas and tried one by one but same problem appears on each of them in single mining mode. (This rig works fine with all other algos including c31)
On the other rig I have one vega (+some 580) and it works normal...constantly 7.3mh without hashreate drops.
On both rigs I use same odt settings and have same driver version (Adrenaline 19.6.2)
What can be the potential issue?

Temperature or power throttling.

It's not temperature (55~60) and as mentioned rig works great on all other algos.
How is possible that single gpu (while all other are disabled) has power throttling?
Rig works fine even with MPT and ProgPow which draw a lot more power.
jr. member
Activity: 194
Merit: 4
Hi.
I have problem with my vega rig on grin 29.
Hashrate jumps from 4 to 6 mh constantly (every 1~2 seconds) on all gpus and non of them can reach 7mh.
I disabled all vegas and tried one by one but same problem appears on each of them in single mining mode. (This rig works fine with all other algos including c31)
On the other rig I have one vega (+some 580) and it works normal...constantly 7.3mh without hashreate drops.
On both rigs I use same odt settings and have same driver version (Adrenaline 19.6.2)
What can be the potential issue?

Temperature or power throttling.
newbie
Activity: 50
Merit: 0
Hi.
I have problem with my vega rig on grin 29.
Hashrate jumps from 4 to 6 mh constantly (every 1~2 seconds) on all gpus and non of them can reach 7mh.
I disabled all vegas and tried one by one but same problem appears on each of them in single mining mode. (This rig works fine with all other algos including c31)
On the other rig I have one vega (+some 580) and it works normal...constantly 7.3mh without hashreate drops.
On both rigs I use same odt settings and have same driver version (Adrenaline 19.6.2)
What can be the potential issue?
jr. member
Activity: 195
Merit: 4
Desperate for some help. My vega 56 rig is doing fine but my 580 rig will not get more than 800hs per card. I have 6 sapphire nitro+, all Samsung 2100mhz memory. Trying to mine monero with them just now and nowhere near the 1000hs a card that people are saying. Any help/suggestions would be much appreciated as I want to mine the last days before randomx. I've read through the posts and tried various settings but stuck at 800, maybe I'm missing something simple

Need to run them higher than 2100 memory... 2200/2250... Core 1250... That should bump you up.

Assuming they have been bios mod?
newbie
Activity: 1
Merit: 0
Desperate for some help. My vega 56 rig is doing fine but my 580 rig will not get more than 800hs per card. I have 6 sapphire nitro+, all Samsung 2100mhz memory. Trying to mine monero with them just now and nowhere near the 1000hs a card that people are saying. Any help/suggestions would be much appreciated as I want to mine the last days before randomx. I've read through the posts and tried various settings but stuck at 800, maybe I'm missing something simple
sr. member
Activity: 1358
Merit: 267
Degens.bet - On-chain 1000x Futures
The miner runs on the phyiscal host directly not in a VM. So everything that is available at the time he can use, which is almost everything. Because the cpu load is always about 2-5%....

I understand that, but you don't understand what I'm trying to tell you. Let's try the example of analogy: in the days of mining on the graphics cards of the scrypt algorithm could run the miner and simultaneously play some game. At the end of the game, a large number of HW errors were seen in the statistics of miners - this was due to the use of two processes of the power of one graphics card. Also you, no matter how much the processor is loaded (2-5% or 90%) because VM and miner can use the same CPU core/thread. I suggest you force certain cores/threads to match certain processes. For example, a TeamRedMiner uses cores 1-4 and VM 5-8.
member
Activity: 658
Merit: 86
The miner runs on the phyiscal host directly not in a VM. So everything that is available at the time he can use, which is almost everything. Because the cpu load is always about 2-5%....

The miner doesn't really use much cpu power, we enqueue jobs on the gpu and (potentially) verify shares on the cpu, that's about it. I'd guess this is something happening in lower layers, i.e. gpu device driver/hypervisor clash.

What (gpu) driver version do you use? And, is the problem specific for TRM, or all miners? Have you tried lowering the cn_config intensity, checking if it is a vram allocation issue?
jr. member
Activity: 53
Merit: 1
The miner runs on the phyiscal host directly not in a VM. So everything that is available at the time he can use, which is almost everything. Because the cpu load is always about 2-5%....
sr. member
Activity: 1358
Merit: 267
Degens.bet - On-chain 1000x Futures
no I have something really different. It might be hardware related, that I assigned to many cores to the VM's but still it doesn't make much sense for me that I only have problems when the miner is running.

How many threads does the miner use? You assigned to comply with certain cores/threads CPU VM and miner or only VM? Maybe that's the problem.
Pages:
Jump to: