[ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More

[kerney666]

oh this looks like I have some for to do here.

I have been pointing the vegas to BCI

have not mined this coin in a while. other then with my thread ripper.

I will need to check out how to get the threadripper to mine this.

will a thread ripper work with this software or is it all cpu bound.

Scrolling back in the thread and see that I missed this, sorry about that!

We’re AMD gpus only. For cpu, the only available options are the open source miners now. JCE has thrown in the towel unfortunately.

[1715356645]

1715356645

[1715356645]

1715356645

[1715356645]

1715356645

[1715356645]

1715356645

[1715356645]

1715356645

[kerney666]

Any idea why I have no status info or hashrates display for me with 0.4.0 ?

It just says Team Red miner Version 0.4.0 with a blinking cursor behind it.
But mining is working normally in the backround as I can see with my power consumption and with the pool-monitor.

I was using 0.3.7 before that which worked fine.

That is odd. You are of course certain you haven’t clicked the win cmd window somewhere so you’ve marked a char somewhere? Does it happen every time or occasionally?

[oxzhor]

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx 

[vmozara]

Any idea why I have no status info or hashrates display for me with 0.4.0 ?

It just says Team Red miner Version 0.4.0 with a blinking cursor behind it.
But mining is working normally in the backround as I can see with my power consumption and with the pool-monitor.

I was using 0.3.7 before that which worked fine.

Did you try to restart the miner? This happened to me when antivirus ate my exe during mining. Mining continued for days until i had to restart, and then discovered windows defender activated somehow and ate my miner exe

[kerney666]

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx  

We will start chewing away at variants shortly. I just finished adding the most low hanging fruit one of them all, cn/half for MSR and XTL, will continue with others the next few days. We will add heavy and derived variants in a not too distant future, but it's a little more work getting the base heavy kernels going first.

Edit: I've added heavyx for x-cash as well now, I thought it was a Heavy-derived algo, not CNv8 with 2x iterations. What a stupid choice of name .

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

[nordmann666]

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx  

We will start chewing away at variants shortly. I just finished adding the most low hanging fruit one of them all, cn/half for MSR and XTL, will continue with others the next few days. We will add heavy and derived variants in a not too distant future, but it's a little more work getting the base heavy kernels going first.

Edit: I've added heavyx for x-cash as well now, I thought it was a Heavy-derived algo, not CNv8 with 2x iterations. What a stupid choice of name .

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

wo need more non-CN-algo devs and miners

[kerney666]

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx  

We will start chewing away at variants shortly. I just finished adding the most low hanging fruit one of them all, cn/half for MSR and XTL, will continue with others the next few days. We will add heavy and derived variants in a not too distant future, but it's a little more work getting the base heavy kernels going first.

Edit: I've added heavyx for x-cash as well now, I thought it was a Heavy-derived algo, not CNv8 with 2x iterations. What a stupid choice of name .

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

wo need more non-CN-algo devs and miners

Couldn't agree more. Just need to wrap this up in a better way than last time we did CN work, we dropped everything and went on to do other things, and it's such a headache to pick things up again since the inner guts of our CN work is rather complex. It takes ~1 week before you're fully back into the saddle again. So, we'll do some concentrated CN work now, then pick up something else.

[gulagminer]

cnr won't start...lyra2rev3 works though.

https://i.imgur.com/H8oLL3i.png

win10, driver ver. 18.6.1 // 1408-905 | 1100-900
What could be the problem?

im having exact same errors but with pure rx580 rig(no vegas), rx470/480rig, and rx570 rig, and on all of them im getting error that my gpu1(display output gpu) is dead.

tried with adding line set GPU_MAX_WORKGROUP_SIZE=256 but no luck, tried lovering clocks, no luck.


for the algo maybe u can add CN revere waltz algo for GRAFT coin

[PIOUPIOU99]

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx  

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

Cn Upx
Cn Wownero 
Cn Graft
Cn X-cash 

[nordmann666]

and i still have

[2019-03-10 18:40:01] Dev pool connection was closed by remote side.
[2019-03-10 18:40:01] Mining will proceed at reduced rate while not connected to dev pool.

[dragonmike]

Yep, absolutely. Now also confirmed in HWINFO64.
GPU Clock = 1360-ish (vs 1408 set, so 50-ish droop)
GPU Memory Clock = 1100.0 MHz (solid)
GPU SOC Clock = 1199.0 MHz (solid)

EDIT: same accross all 6 cards.

EDIT 2: I've now been playing with the lower mem pstates and noticed that whatever clocks I enter there are being ignored and the cards are using presets instead. Very weird. SOC then sets itself to different freqs as well depending on which mem p_states are active...

Ok, I see what happened...  Looks like your PPT has an edit changing p7 SOC to 1200 from 1107.  

Look for "C0,D4,01,00,07" (only first occurrence) and try changing it to "6C,B0,01,00,07".

Still not sure why that would require 1v.  When I run 1200 SOC, i generally see voltage requirements around 900mv +/- 20mv.

So the 1200 is hardcoded in the reg, yeah. I can change it down to 1107, it'll spare me more headaches.

Now why are the mem p_states hard coded too?
Whatever clocks I enter there are being ignored and the cards are using presets instead.
Currently I run in mem_p2 and it forces 800MHz clock. That gives me 1800h/s per card (power draw for 6 at the wall is 1120W) and is actually more efficient than running 2000 at total power draw of 1400W!

That drop from 1200 to 1107 SOC should save you at least 50mv, from my experience.

Drivers don't allow changing mem states p0-p2 at runtime.  You should be able to edit them in PPT if you want, but i've never bothered.  In the past, you could not edit core p0-p5 either (the whole reason everyone uses PPTs,) but this was changed w/ 19.x drivers.  Unfortunately, they didn't make the same change for mem states (at least in early vers of 19.x - haven't tested latest versions.)

I can confirm that hardcoding back down to 1107 solved everything.
I'm now running 1408/1100 @ 850mV, SOC clock @ 1107 MHz. 12Kh/s, 1200W at the wall.
Of course this means I will not push the mem clocks higher, but tbh it was never really worth it. Especially as it completely buggered up the power states/delivery.

Thanks WillJ7 and pbfarmer you've been legends, as usual. If I only had merit left to spare I'd dish it all out to you!

Awesome!  Glad you got it worked out.  A couple last tweaks for you...

1. You can go up to 1107 on mem - tho obv won’t make much of a diff.

2. I tend to see 1400 effective possible w/ 850mv.  W/ a 1408 setting, you’re prob running quite a bit lower at least on some of your GPUs due to acg - my 64 settings range from 1425-1550 to get to 1400..  Just keep bumping your clock setting til you see close to 1400 in hwinfo.

3. If you really want to shave the last bit of excess power, you might be able to get voltages on some cards down as low as 825mv.  Every card is different tho, so like the core clock setting, you’ll have to tune each individually.  And it’s an opaque relaionship between voltage and core clock - as you drop mv, core will need to be raised to maintain your target clock.  It’s a bit of an art form finding the balance.

1. Yeah I will, gotta make the most out of it. Will keep the upper mem p_states disabled on configs that don't require memory (x16 algos etc).

2. I'm trying this just now on x16r. Apart from one card that clearly doesn't like higher clocks at all (must have terrible asic quality), the other ones seem to do well enough at 1458 set (~1410 effective). Testing with slightly higher voltage, but will lower if no accidents happen.

3. Exactly. Also, what works for "normal" algos like the CN variants is trickier on x16/20/22/etc as you need to see the cards survive all the cycles - several times - before you can declare a clock/voltage combo "stable". But at least now I have a solid basis to work from, not the absolute mess I had before.

Thanks again for your help!

[dragonmike]

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though

Ahem.
I think you know already what I'm gonna say so no, I'm not gonna say it!

[Iamtutut]

Please add "cn-rwz" (GRAFT algo).

[wei0339]

i have vega *9 , but --list_devices  can't find.

[kerney666]

i have vega *9 , but --list_devices  can't find.

Unexpected, what’s the OS and driver? Other miners working ok?

[pbfarmer]

i have vega *9 , but --list_devices  can't find.

You probably need to specify a platform id

[wei0339]

i have vega *9 , but --list_devices  can't find.

Unexpected, what’s the OS and driver? Other miners working on?

win10 ver.1607
drive:18.6.1
swap space: 128GB

teamredminer-v0.3.8       v8                       OK
gminer 1.32                    equihash150_5     OK

add  --platform=1 or 0 ,both are not normal.
only message "Team Red Miner veersion 0.4.0"

Team Red Miner 0.4.0 mineing, also show "Team Red Miner veersion 0.4.0".
But the temperature of the graphics card will rise

[kerney666]

i have vega *9 , but --list_devices  can't find.

Unexpected, what’s the OS and driver? Other miners working on?

win10 ver.1607
drive:18.6.1
swap space: 128GB

teamredminer-v0.3.8       v8                       OK
gminer 1.32                    equihash150_5     OK

add  --platform=1 or 0 ,both are not normal.
only message "Team Red Miner veersion 0.4.0"

Team Red Miner 0.4.0 mineing, also show "Team Red Miner veersion 0.4.0".
But the temperature of the graphics card will rise

I’m guessing it’s the old win 10 version not liking a terminal command we run to enable colors. Will check later tonight.

[GordoLui]

i have vega *9 , but --list_devices  can't find.

Unexpected, what’s the OS and driver? Other miners working on?

win10 ver.1607
drive:18.6.1
swap space: 128GB

teamredminer-v0.3.8       v8                       OK
gminer 1.32                    equihash150_5     OK

add  --platform=1 or 0 ,both are not normal.
only message "Team Red Miner veersion 0.4.0"

Team Red Miner 0.4.0 mineing, also show "Team Red Miner veersion 0.4.0".
But the temperature of the graphics card will rise

I’m guessing it’s the old win 10 version not liking a terminal command we run to enable colors. Will check later tonight.

I'm running the exact same version of windows and everything is working fine. Might be worth try this update, second one from the top.

http://www.catalog.update.microsoft.com/Search.aspx?q=KB4103723

I don't know why but it help me run this miner on 1607.

[tvukoman]

Miner failed to start over after crash:

log:
[2019-03-10 23:17:44] GPU 3: detected DEAD (03:00.0), will execute restart script start_reset_skript.bat
[2019-03-10 23:17:44] Watchdog triggering miner shutdown after restart script execution.
[2019-03-10 23:17:44] Shutting down...
[2019-03-10 23:17:44] GPU 1 CN thread 1 exiting.
[2019-03-10 23:17:44] GPU 2 CN thread 0 exiting.
[2019-03-10 23:17:44] GPU 0 CN thread 0 exiting.
[2019-03-10 23:17:45] GPU 0 CN thread 1 exiting.
[2019-03-10 23:17:45] GPU 2 CN thread 1 exiting.
[2019-03-10 23:17:45] GPU 1 CN thread 0 exiting.
[2019-03-10 23:17:54] GPU 3 thread 0 shutdown timed out.
[2019-03-10 23:17:54] GPU 3 thread 1 shutdown timed out.

Miner program is open "freezed" with this last note:
          Team Red Miner version 0.4.0
[2019-03-10 23:18:22] Auto-detected AMD OpenCL platform 1

I have reset script that work just fine with Vertcoin in 0.3.10 version (disable / enable vegas with devcon, apply overdriveNtool profiles, start miner again)

Any help?