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

[Mashy81]

Any tests for RX 570/580 with new version? Thanks

I have a mixed rig with rx570 and vega.
But no increase for rx570 still the same. I do beleive nothing was changed for other cards. Only vegas

[pbfarmer]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Still using ODNT? How do you set your fan speeds? IIRC there is no target temp in the beta version.

I tested a few 19.x drivers recently, on a 3x vega 56 rig, TRM 0.4.2 (also CNR only) and came to the same conclusion. Didn't have enough time to play with ODNT, but it felt weird having to spend time tweaking fan speeds. Target temp has been a set and forget kind of thing for me so...      

You can set your target temp in PPT...

Vega (hex short, byteswapped -- e.g. "1c,00" => 0x001c => 0d28):



Polaris (hex char -- e.g. "28" => 0x28 => 0d40):

[seefatlow]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Using a PPT mod will also shave off 15W per card with either drivers. So use PPT if possible even with 19.4.2 drivers.

I can't seem to apply PPT on Sapphire Vega56 Nitro+ Limited Edition. Does anyone know how to do this? Or should I just flash it to normal Nitro+ vBios?

[seefatlow]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Did you try with the new mode 16*14 , use * instead of + for the new mode.
I got a 15% hashrate increase for 7% more power.

I haven't had the time to do any mem tweak yet. Will do it once I have more time at my hands

[Mashy81]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Using a PPT mod will also shave off 15W per card with either drivers. So use PPT if possible even with 19.4.2 drivers.

I can't seem to apply PPT on Sapphire Vega56 Nitro+ Limited Edition. Does anyone know how to do this? Or should I just flash it to normal Nitro+ vBios?

Is there NO way to change the memory voltage of the V56 or V64?

[pbfarmer]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Using a PPT mod will also shave off 15W per card with either drivers. So use PPT if possible even with 19.4.2 drivers.

I can't seem to apply PPT on Sapphire Vega56 Nitro+ Limited Edition. Does anyone know how to do this? Or should I just flash it to normal Nitro+ vBios?

Is there NO way to change the memory voltage of the V56 or V64?

Sure - flash 56 to 64.  You go from 1.25 to 1.356.

Beyond that, there is no way w/o editing the bios, which you can't do.  Other than using the bios injection trick w/a modified linux kernel

[Mashy81]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Using a PPT mod will also shave off 15W per card with either drivers. So use PPT if possible even with 19.4.2 drivers.

I can't seem to apply PPT on Sapphire Vega56 Nitro+ Limited Edition. Does anyone know how to do this? Or should I just flash it to normal Nitro+ vBios?

Is there NO way to change the memory voltage of the V56 or V64?

Sure - flash 56 to 64.  You go from 1.25 to 1.356.

Beyond that, there is no way w/o editing the bios, which you can't do.  Other than using the bios injection trick w/a modified linux kernel

"Other than using the bios injection trick w/a modified linux kernel"

modified linux kernel gets my attention. Is this yours or available if I look in the right places

[pbfarmer]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Using a PPT mod will also shave off 15W per card with either drivers. So use PPT if possible even with 19.4.2 drivers.

I can't seem to apply PPT on Sapphire Vega56 Nitro+ Limited Edition. Does anyone know how to do this? Or should I just flash it to normal Nitro+ vBios?

Is there NO way to change the memory voltage of the V56 or V64?

Sure - flash 56 to 64.  You go from 1.25 to 1.356.

Beyond that, there is no way w/o editing the bios, which you can't do.  Other than using the bios injection trick w/a modified linux kernel

"Other than using the bios injection trick w/a modified linux kernel"

modified linux kernel gets my attention. Is this yours or available if I look in the right places

Definitely not mine - i've never made the attempt.  Somewhere out there... maybe.  I only know it's possible, don't even know if the hack is publicly available.  You may have to wade through oc.net forums or something to find it (or at least info about it.) Prob look for wolf / ohgodapet posts

[carlosmonaco]

Working great with my vega 64/56 reference card ! Around 2200h/s avg..
But summer is coming , is there a way to decrease consumption with this this tool !
For now my card are running at 1407/1100 or 1407/950 at 875mV for most of them and 900-930 mV for bad ones.

[ingyenfrag]

Working great with my vega 64/56 reference card ! Around 2200h/s avg..
But summer is coming , is there a way to decrease consumption with this this tool !
For now my card are running at 1407/1100 or 1407/950 at 875mV for most of them and 900-930 mV for bad ones.

Here are my own PPT and the overdriventool settings--> https://drive.google.com/open?id=1OvKJbv7psAO59I8EavFH5704wf7sr_9z.
If it's not stable, try a litte bit higher voltage in OverdriveNTool --> GPU P7 850mV / HBM P3 860mV --> 0.8375V GPU
My worst 2 GPU-s need GPU P7 850mV/ HBM P3 880mV --> 0.850V GPU

[kerney666]

Working great with my vega 64/56 reference card ! Around 2200h/s avg..
But summer is coming , is there a way to decrease consumption with this this tool !
For now my card are running at 1407/1100 or 1407/950 at 875mV for most of them and 900-930 mV for bad ones.

Without downclocking and/or undervolting I’d say it’s highly unlikely. The CNv8-based variants (Turtle etc) are leaner. CN/r added the set of random ops which can’t really be optimized much, and it will always pull a fair bit of power.

[carlosmonaco]

On thanks, I will try to go undervolt again!
Is it possible to go under 800mV ?

[ingyenfrag]

On thanks, I will try to go undercoat again!
Is it possible to go under 800mV ?

It's possible. But over 1300MHz you need over 0.8V for a stable setup.

[GordoLui]

Alright been trying the latest 0.4.4 trm and getting mixed results. On the one system I have with the 3 vega 56, only one of the video cards is at 2130, but the other two cards are hashing at their normal rate. The thing is when i run the AMDmemtweak, it tells me it changed the settings for all 3 cards. I even went back and added a --i 0,1,2 and that again it tells me i updated all of them but when i run the miner only 1 gpu is running at the increased rate.

I'm also having issues with running the memtweak on my other miners, they are all having pathing issues, even though i know i'm typing everything correct. All the settings are the same with the one pc that i have amdtweak working. So im not sure whats going on there.

But i do have reports for the 1 gpu that is mining with the memtweaks, it has been hashing for two days now at a sustained 2130 rate and with a pool side hashrate of around 2030. I havent been able to do much yet but will get power readings later. I can say that the temperature of that one card is sitting at 66c while my other 2 cards are at 51c, which does suggest a higher power draw.

Super quick update #1

I was finally able to run the program by going to cmd as an admin and typing in cd c:\<path to folder> hitting enter, then finally typing WinAMDTweak.exe and going from there.

So far I was able to apply the memory setting to two of my other x3 vega 56 rigs. These have different firmware on them. One has the 18.0.5 and the other the 18.0.6. So far they been stable but the hashrate increase in CNr has been much less than it was on my other computer. I'm thinking the drivers maybe? Hitting around 2k on all 3 vegas with the AMD 18.0.5 drivers, and between 1910-1990 on the one with the 18.0.6 drivers. Thats still a bit higher than their original setting but not by much.

miner settings and amdmemorytweak settings are the same with all cards.

[NecronomicoN]

Hello prompt how to include a single-threaded mode, in readme read that it is necessary to use a configuration Y+0, but I tried various combinations (--cn_config=Y+0,L16+16,16+16,16+16,L16+16,L16+16) but the miner gives an error, tell me what I'm doing wrong. As the card which is inserted in X16 irrespective of dispersal and intensity gives out HW errors, I thought can the single-threaded mode will be able to solve my problem.

[iRonNuke]

Hello prompt how to include a single-threaded mode, in readme read that it is necessary to use a configuration Y+0, but I tried various combinations (--cn_config=Y+0,L16+16,16+16,16+16,L16+16,L16+16) but the miner gives an error, tell me what I'm doing wrong. As the card which is inserted in X16 irrespective of dispersal and intensity gives out HW errors, I thought can the single-threaded mode will be able to solve my problem.

Just replace Y (intensity) with a value. --cn_config=16+0 for example.

[NecronomicoN]

Hello prompt how to include a single-threaded mode, in readme read that it is necessary to use a configuration Y+0, but I tried various combinations (--cn_config=Y+0,L16+16,16+16,16+16,L16+16,L16+16) but the miner gives an error, tell me what I'm doing wrong. As the card which is inserted in X16 irrespective of dispersal and intensity gives out HW errors, I thought can the single-threaded mode will be able to solve my problem.

Just replace Y (intensity) with a value. --cn_config=16+0 for example.

Thanks

[Mashy81]

Hello prompt how to include a single-threaded mode, in readme read that it is necessary to use a configuration Y+0, but I tried various combinations (--cn_config=Y+0,L16+16,16+16,16+16,L16+16,L16+16) but the miner gives an error, tell me what I'm doing wrong. As the card which is inserted in X16 irrespective of dispersal and intensity gives out HW errors, I thought can the single-threaded mode will be able to solve my problem.

Just replace Y (intensity) with a value. --cn_config=16+0 for example.

Thanks

Also replace +  with  *  not all card like 16*16. My best value is 16*14

[SamAlackass]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Still using ODNT? How do you set your fan speeds? IIRC there is no target temp in the beta version.

I tested a few 19.x drivers recently, on a 3x vega 56 rig, TRM 0.4.2 (also CNR only) and came to the same conclusion. Didn't have enough time to play with ODNT, but it felt weird having to spend time tweaking fan speeds. Target temp has been a set and forget kind of thing for me so...      

You can set your target temp in PPT...

Vega (hex short, byteswapped -- e.g. "1c,00" => 0x001c => 0d28):

https://i.imgur.com/8JhCNwRm.png

Polaris (hex char -- e.g. "28" => 0x28 => 0d40):

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

Thank you for that!! It seems to be working! Your posts have always been immensely helpful.

I can't try the beta ODNT right now as I'm currently on old drivers and it's crashing so, am I right to assume the fan speed section can still be disabled in beta?

[pbfarmer]

FYI, I completed an evaluation between win10 driver 18.6.1 vs 19.4.2. Found no hashrate/power draw difference with TRM 0.4.4 miner. Evaluated on CNR algo only.

Still using ODNT? How do you set your fan speeds? IIRC there is no target temp in the beta version.

I tested a few 19.x drivers recently, on a 3x vega 56 rig, TRM 0.4.2 (also CNR only) and came to the same conclusion. Didn't have enough time to play with ODNT, but it felt weird having to spend time tweaking fan speeds. Target temp has been a set and forget kind of thing for me so...      

You can set your target temp in PPT...

Vega (hex short, byteswapped -- e.g. "1c,00" => 0x001c => 0d28):



Polaris (hex char -- e.g. "28" => 0x28 => 0d40):

Thank you for that!! It seems to be working! Your posts have always been immensely helpful.

I can't try the beta ODNT right now as I'm currently on old drivers and it's crashing so, am I right to assume the fan speed section can still be disabled in beta?

Np - happy to help.  I don't know about disabling, but ODNT just reads the value from PPT, so you shouldnt need to worry about it, unless you want to change it.