Pages:
Author

Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More - page 89. (Read 211877 times)

member
Activity: 363
Merit: 16
strange issue on my side...but dont know if it´s version related

upgraded my 8xVega Rig with 2 Vegas

using 18.6.1 drivers and everything else like with 8 cards

so starting TRMiner with 8 cards...everything is good
starting TRMiner with 9 cards..BSOD with "Video Scheduler Internal Error" - it dont matter which GPU i use...i can mixe all gpus and it runs fine with only 8 cards in the batch. After adding a 9. card - BSOD


with SRBMiner i can use all 10 GPUs without error...any hint for me what can cause this problem with TRMiner?

I doubt this is it, but just in case... did you increase your windows page file size after adding the other 2 cards (or make sure it was big enough before)?

it was/is 96.000

i dont know what to do now...8 cards perfect running...9 cards dont :/
member
Activity: 340
Merit: 29
strange issue on my side...but dont know if it´s version related

upgraded my 8xVega Rig with 2 Vegas

using 18.6.1 drivers and everything else like with 8 cards

so starting TRMiner with 8 cards...everything is good
starting TRMiner with 9 cards..BSOD with "Video Scheduler Internal Error" - it dont matter which GPU i use...i can mixe all gpus and it runs fine with only 8 cards in the batch. After adding a 9. card - BSOD


with SRBMiner i can use all 10 GPUs without error...any hint for me what can cause this problem with TRMiner?

I doubt this is it, but just in case... did you increase your windows page file size after adding the other 2 cards (or make sure it was big enough before)?
jr. member
Activity: 195
Merit: 4
Trying to setup my miner for graft, my .bat is "teamredminer.exe -a cnv8_rwz -o stratum+tcp://pool.graft.hashvault.pro:7777 -u GAmjpTK.......jWcjoh1Rv9cfDLY14aMLVgugx4GqBJeo9STk8k4 -p Z...t -d 0,1,2,3 --cn_config 8+8,8+8,8+8,8+8"

I mine with 4 RX574. I use the Vega cores of my Ryzen 2400G for display but of course I don't want to mine with.

The program crashes after the auto detect of "platform 1"

What am I doing wrong  please ?


Hi tutut! 8+8 will use the full 4GB available, drivers allows it but can’t handle it. Downgrade and test 8+7, 8+6, 7+7, etc to see what gives you the best results.

6+6 seems to be magic for me... 950-1.01 khs on CNR.
jr. member
Activity: 195
Merit: 4
Hi,
Please which command can i use for temperature limit of GPU directly in bat file?

Click on the "help.bat" that gets packaged with every miner download. You'll find your answers Smiley
newbie
Activity: 51
Merit: 0
Hi,
Please which command can i use for temperature limit of GPU directly in bat file?
member
Activity: 363
Merit: 16
strange issue on my side...but dont know if it´s version related

upgraded my 8xVega Rig with 2 Vegas

using 18.6.1 drivers and everything else like with 8 cards

so starting TRMiner with 8 cards...everything is good
starting TRMiner with 9 cards..BSOD with "Video Scheduler Internal Error" - it dont matter which GPU i use...i can mixe all gpus and it runs fine with only 8 cards in the batch. After adding a 9. card - BSOD


with SRBMiner i can use all 10 GPUs without error...any hint for me what can cause this problem with TRMiner?
member
Activity: 190
Merit: 59

Hey vmozara! So, what's the cn_config and clocks you're using? Personally, my Vegas have been doing fine on 18.6.1 and 19.2.2, I haven't bumped 19.2.2 -> 19.3.x or 19.4.y on my dev workstation yet. Turtle is a little b*tchy, for many people the perf is great out of the box, for others it's a circus. Linux has been serving people better than win10. I'm not convinced about the latest and greatest Adrenalin drivers...

Myself, I can just start the miner at any clocks using L24+24 (V56 flashed V64) or L28+28 (proper V64), and I'm at 19.5-19.6 kh/s.

Ok i just tried to fire up turtle mining on one of my 18.6.1 v64 rigs and it went to 19.5kh/s straight away (1430/1100), after that i dropped the clock to 1200 and it went to 19.1 or something. cool!

How to change L26+26 and other numbers? Whatever i write in cn_config, when miner starts it always says L32+32 noob me, forgot -- in front of command

thanks!
member
Activity: 340
Merit: 29

Low power consumption TRTL mining is a hit or miss thingy and seems to depend very much on silicon lottery.


This can't be the case... I have 8 nitro 64s on a rig pulling 1112w at the wall - maybe ~35w for system, so that's <135w per GPU on average, each doing 18.5 kh/s (850/1107/818/L18+18.)  I also have a ref 64 and a flashed ref 56 (850/1107/818/L22+22) doing the same on another rig.  These were all bought over a period of many months during the vega stock shortages, so they certainly weren't all binned together.

Granted I'm on platinum PSUs and a 240v line, so your power needs could be slightly higher, but prob not more than 5%-10% max.  I'm also on linux, but my tests on windows (18.12.x drivers iirc) showed similar results.

Really, memory manufacturer is the only thing I see impacting performance - mine are all samsung, and i expect based on widespread reports, and my experience w/ polaris, that hynix would underperform.  Drivers are the other possibility - though I have yet to see any versions since blockchain significantly impact performance for any algo (other than on xmr-stack derived miners.)
full member
Activity: 1120
Merit: 131
Trying to setup my miner for graft, my .bat is "teamredminer.exe -a cnv8_rwz -o stratum+tcp://pool.graft.hashvault.pro:7777 -u GAmjpTK.......jWcjoh1Rv9cfDLY14aMLVgugx4GqBJeo9STk8k4 -p Z...t -d 0,1,2,3 --cn_config 8+8,8+8,8+8,8+8"

I mine with 4 RX574. I use the Vega cores of my Ryzen 2400G for display but of course I don't want to mine with.

The program crashes after the auto detect of "platform 1"

What am I doing wrong  please ?


Hi tutut! 8+8 will use the full 4GB available, drivers allows it but can’t handle it. Downgrade and test 8+7, 8+6, 7+7, etc to see what gives you the best results.

Tried all of them, doesn't work. Also tried 7+6.
"Open CL platform 0" is a pass
"Open Cl platform 1" then crashes after 2-3s. I wonder if this "platform" corresponds to the Vega cores inside the Ryzen 2400G. If so, how could I disable it in the .bat ?

Thanks for your help.

Aaaah of course. Yeah 99.9% certain you’re correct, it’s trying to mine on both platforms. Add —platform=0 as cmd line arg and check if it helps.

I can now mine but something's weird with GPU0.

With other miners, all my GPUs are very stable at 1240MHz core, this time I have to lower the GPU0 at 1200MHz. Still, the performance seems very ok.

I have to try with TRTL !
member
Activity: 658
Merit: 86
Trying to setup my miner for graft, my .bat is "teamredminer.exe -a cnv8_rwz -o stratum+tcp://pool.graft.hashvault.pro:7777 -u GAmjpTK.......jWcjoh1Rv9cfDLY14aMLVgugx4GqBJeo9STk8k4 -p Z...t -d 0,1,2,3 --cn_config 8+8,8+8,8+8,8+8"

I mine with 4 RX574. I use the Vega cores of my Ryzen 2400G for display but of course I don't want to mine with.

The program crashes after the auto detect of "platform 1"

What am I doing wrong  please ?


Hi tutut! 8+8 will use the full 4GB available, drivers allows it but can’t handle it. Downgrade and test 8+7, 8+6, 7+7, etc to see what gives you the best results.

Tried all of them, doesn't work. Also tried 7+6.
"Open CL platform 0" is a pass
"Open Cl platform 1" then crashes after 2-3s. I wonder if this "platform" corresponds to the Vega cores inside the Ryzen 2400G. If so, how could I disable it in the .bat ?

Thanks for your help.

Aaaah of course. Yeah 99.9% certain you’re correct, it’s trying to mine on both platforms. Add —platform=0 as cmd line arg and check if it helps.
full member
Activity: 1120
Merit: 131
Trying to setup my miner for graft, my .bat is "teamredminer.exe -a cnv8_rwz -o stratum+tcp://pool.graft.hashvault.pro:7777 -u GAmjpTK.......jWcjoh1Rv9cfDLY14aMLVgugx4GqBJeo9STk8k4 -p Z...t -d 0,1,2,3 --cn_config 8+8,8+8,8+8,8+8"

I mine with 4 RX574. I use the Vega cores of my Ryzen 2400G for display but of course I don't want to mine with.

The program crashes after the auto detect of "platform 1"

What am I doing wrong  please ?


Hi tutut! 8+8 will use the full 4GB available, drivers allows it but can’t handle it. Downgrade and test 8+7, 8+6, 7+7, etc to see what gives you the best results.

Tried all of them, doesn't work. Also tried 7+6.
"Open CL platform 0" is a pass
"Open Cl platform 1" then crashes after 2-3s. I wonder if this "platform" corresponds to the Vega cores inside the Ryzen 2400G. If so, how could I disable it in the .bat ?

Thanks for your help.
member
Activity: 658
Merit: 86
Trying to setup my miner for graft, my .bat is "teamredminer.exe -a cnv8_rwz -o stratum+tcp://pool.graft.hashvault.pro:7777 -u GAmjpTK.......jWcjoh1Rv9cfDLY14aMLVgugx4GqBJeo9STk8k4 -p Z...t -d 0,1,2,3 --cn_config 8+8,8+8,8+8,8+8"

I mine with 4 RX574. I use the Vega cores of my Ryzen 2400G for display but of course I don't want to mine with.

The program crashes after the auto detect of "platform 1"

What am I doing wrong  please ?


Hi tutut! 8+8 will use the full 4GB available, drivers allows it but can’t handle it. Downgrade and test 8+7, 8+6, 7+7, etc to see what gives you the best results.
member
Activity: 658
Merit: 86

Livada,

I still have the same issue with the TRTL algo. My V64 cards aren't stable at 1100 Mhz or higher and my V56 cards aren't stable at 940Mhz memclk. None of my V64 or V56 modded cards can give >19 kh/s. Interestingly, only my V56 stock bios Samsung is able to achieve 19.3kH/s.

vega 56 with 64bios(samsung) and vega 64 have 19k+
only vega 56 hynixstock bios have 18,5k

I use 800mv PPT table for all card-

Problem with TRTL is specific.  Start work on 19500 and after 5-10-30min hr down to 18900 and after 5-10-30min go down to 18500.(veg56 samsung)
now i start with 19000hr and after 1 day hr is 19000. freq is identical but i not use L24+24 for vega 56 - i use L28+28 and hr is lower but stability.

veg64le - start 19500 and work. if i use lower GPU frq start normal 19500 but down after 10min to 19k. use higher gpu frq and high mv. i use 880mv for gpu and mem vega64LE

I too have the same hashrate instablity issues with Vega 56 bios mod and V64 cards. However stock V56 cards are stable at 18.7kh/s for Hynix and 19.3kh/s for Samsung

Hey guys! I have a 0.4.3.1 version with a few patches. Many times the lowered hashrate after a while is due to the threads coinciding, it’s a scheduling problem rather than a hw problem. Reach out to me on PM or find me on discord directly if we share a server. I’d love to get some feedback on the patches.
jr. member
Activity: 80
Merit: 1

Livada,

I still have the same issue with the TRTL algo. My V64 cards aren't stable at 1100 Mhz or higher and my V56 cards aren't stable at 940Mhz memclk. None of my V64 or V56 modded cards can give >19 kh/s. Interestingly, only my V56 stock bios Samsung is able to achieve 19.3kH/s.

vega 56 with 64bios(samsung) and vega 64 have 19k+
only vega 56 hynixstock bios have 18,5k

I use 800mv PPT table for all card-

Problem with TRTL is specific.  Start work on 19500 and after 5-10-30min hr down to 18900 and after 5-10-30min go down to 18500.(veg56 samsung)
now i start with 19000hr and after 1 day hr is 19000. freq is identical but i not use L24+24 for vega 56 - i use L28+28 and hr is lower but stability.

veg64le - start 19500 and work. if i use lower GPU frq start normal 19500 but down after 10min to 19k. use higher gpu frq and high mv. i use 880mv for gpu and mem vega64LE

I too have the same hashrate instablity issues with Vega 56 bios mod and V64 cards. However stock V56 cards are stable at 18.7kh/s for Hynix and 19.3kh/s for Samsung
newbie
Activity: 417
Merit: 0

Livada,

I still have the same issue with the TRTL algo. My V64 cards aren't stable at 1100 Mhz or higher and my V56 cards aren't stable at 940Mhz memclk. None of my V64 or V56 modded cards can give >19 kh/s. Interestingly, only my V56 stock bios Samsung is able to achieve 19.3kH/s.

vega 56 with 64bios(samsung) and vega 64 have 19k+
only vega 56 hynixstock bios have 18,5k

I use 800mv PPT table for all card-

Problem with TRTL is specific.  Start work on 19500 and after 5-10-30min hr down to 18900 and after 5-10-30min go down to 18500.(veg56 samsung)
now i start with 19000hr and after 1 day hr is 19000. freq is identical but i not use L24+24 for vega 56 - i use L28+28 and hr is lower but stability.

veg64le - start 19500 and work. if i use lower GPU frq start normal 19500 but down after 10min to 19k. use higher gpu frq and high mv. i use 880mv for gpu and mem vega64LE
jr. member
Activity: 80
Merit: 1
Guys,

I just came back from the ship and wanted to try mining new algos.

So far for the Vega I was using windows 10 and adrenalin 18.6.1, ppt and classis disable-enable-clocks-miner combo, and that worked perfectly for me.

But now i tried to install new adrenalin, apply PPT, and tried to mine Turtle, but i can see that my friequencies both core and memory are jumping around and i only get 14-16KH/s

From what I understood, Turtle mining is very low consumption and heating, I would like to switch to it as summer is coming, and CN-R is quite demanding for cooling.

Can somebody make a short guide what steps are necessary with new adrenalin drivers? Thanks guys!

Low power consumption TRTL mining is a hit or miss thingy and seems to depend very much on silicon lottery. None of the Vega GPUs I have is able to achieve the desired >19kH/s @ 160W per GPU.
jr. member
Activity: 80
Merit: 1
Vega 56 ref(samsung) with 64bios - L24+24 best - 19500hr 1230/870mv-gpu and 1100/870mv mem - 120/127W in GPU-Z(temp=57° fan=3000pm)
this card go more up but my power is to low for 1400gpu

Vega 56 ref(samsung) with 64bios - L28+28 - 19250hr 1230/866mv-gpu and 1100/668mv mem - 112/122W in GPU-Z(temp=57° fan=2700pm)
You should be able to lower your core clocks even further to 850 or even 825. Also, max your mem clocks to 1107. That's as far as you can go on equivalent SoC.

I've noticed that accessing Teamviewer will crash my rig when running low clocks and high intensities. Also, I'm now using a staggered approach: I set higher clocks and voltages, start the miner, and once all cards are up and hashing, apply lower clocks. Just a little script with overdriventool on a timer. Works wonders.

i try all. i try your PPT but 865mv is limit. if i go on 860 or 850  rig stop work.

(SAMSUNG)if i go on mem 1102 or higher  gpu dead.
hynix v56 nitro+ is bad card- 1 card work only on 897mhz- best nitro+ card work only on 936mhz.
nitro+ hyny with 64bios unstable and i not use this(i try but unstable)

Teamviewer crash my rig only on trtl. on other algo work fine.

this is 6* vega 56 nitro+(hynix) rig stock bios - 109300hr 1088W at the wall (100h/w)


Name=trtl5
GPU_P0=852;800;0
GPU_P1=991;801;0
GPU_P2=1084;802;0
GPU_P3=1100;803;0
GPU_P4=1125;804;0
GPU_P5=1150;805;0
GPU_P6=1300;815;0
GPU_P7=1470;860
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;801;0
Mem_P3=929;870


-This is rig with 3*vega56@64 and 1*Vega 64LE. Rig problem is suply - no power for this card. 760W at the wall.(v56=L24+24 v64=L28+28)=77870hr-work only 10min with this hr and go down to 76900hr/745W

- This is rig with 3*vega56@64 and 1*Vega 64LE. Rig problem is suply - no power for this card. 750W at the wall.(v56=L28+28 v64=L28+28)=77200hr
L28+L28 for all card. L24 is beter for vag56 but use more power adn suply reset rig.
this rig have 77200hr 750W at the wal. 4extra fan  and vega 64LE use 30W more for pump.
750W-80(MB)-30W(pump)= 640W for 3*V56 +1*V64 (160W per card) = 103h/w

vega 56
Name=trtl1
GPU_P0=852;825
GPU_P1=991;825
GPU_P2=1084;825
GPU_P3=1100;825
GPU_P4=1115;825
GPU_P5=1125;825
GPU_P6=1130;825
GPU_P7=1210;870
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;900;0
Mem_P3=1100;870
Fan_Min=2300
Fan_Max=3200
Fan_Target=57
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

vega 64LE
Name=trtl3
GPU_P0=852;825
GPU_P1=991;825
GPU_P2=1084;825
GPU_P3=1100;825
GPU_P4=1115;825
GPU_P5=1120;825
GPU_P6=1135;850
GPU_P7=1145;880
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;800;0
Mem_P3=1098;880
Fan_Min=1100
Fan_Max=2400
Fan_Target=49
Fan_Acoustic=1200
Power_Temp=70
Power_Target=0

all cards can be given a lot more if they are unable to power(1000Wbronce give only 760W)



Livada,

I still have the same issue with the TRTL algo. My V64 cards aren't stable at 1100 Mhz or higher and my V56 cards aren't stable at 940Mhz memclk. None of my V64 or V56 modded cards can give >19 kh/s. Interestingly, only my V56 stock bios Samsung is able to achieve 19.3kH/s.
full member
Activity: 1120
Merit: 131
Trying to setup my miner for graft, my .bat is "teamredminer.exe -a cnv8_rwz -o stratum+tcp://pool.graft.hashvault.pro:7777 -u GAmjpTK.......jWcjoh1Rv9cfDLY14aMLVgugx4GqBJeo9STk8k4 -p Z...t -d 0,1,2,3 --cn_config 8+8,8+8,8+8,8+8"

I mine with 4 RX574. I use the Vega cores of my Ryzen 2400G for display but of course I don't want to mine with.

The program crashes after the auto detect of "platform 1"

What am I doing wrong  please ?
member
Activity: 658
Merit: 86
Guys,

I just came back from the ship and wanted to try mining new algos.

So far for the Vega I was using windows 10 and adrenalin 18.6.1, ppt and classis disable-enable-clocks-miner combo, and that worked perfectly for me.

But now i tried to install new adrenalin, apply PPT, and tried to mine Turtle, but i can see that my friequencies both core and memory are jumping around and i only get 14-16KH/s

From what I understood, Turtle mining is very low consumption and heating, I would like to switch to it as summer is coming, and CN-R is quite demanding for cooling.

Can somebody make a short guide what steps are necessary with new adrenalin drivers? Thanks guys!

Hey vmozara! So, what's the cn_config and clocks you're using? Personally, my Vegas have been doing fine on 18.6.1 and 19.2.2, I haven't bumped 19.2.2 -> 19.3.x or 19.4.y on my dev workstation yet. Turtle is a little b*tchy, for many people the perf is great out of the box, for others it's a circus. Linux has been serving people better than win10. I'm not convinced about the latest and greatest Adrenalin drivers...

Myself, I can just start the miner at any clocks using L24+24 (V56 flashed V64) or L28+28 (proper V64), and I'm at 19.5-19.6 kh/s.
member
Activity: 80
Merit: 13
I am thinking about mining Monero (cryptonight R). I have 3 290x gpu's. My electricity is about 12 cent. As far as I can see profitability will be weak to say the least, should I wait for Monero to rise in value or would the hashrate kill of profitability anyways??

Beyerd, I ABUSED 6 290x/390 , had two near new 290x gigabyte, one had  the VRM burnt for some reason (this one was unstable anyway, think the gpu had a grit of sand from factory and heat damagge happened probably with first user)
The other with the Stilt Bios and timings mods, used to do REALLY low reading, fans run lightly, it gave around 90 watts total in HWinfo mining v7 CN back in the day.
What i would do is go 1000 mhz only and undervolt-experiment (every miner is different) sometimes it can take -200 mv, the stilt bios changes VRM frequency which isa hard tweak, however they really ran with less energy.  used to do 900 h/s back in the day.... also i know what to be done with the timings for polaris but with this 290x, you need to underclock and tweak timings specifically as hell for cryptonight, what works well for Cryptonight always is, lower tRD and tRC, higher tCL and consequent timings, loosen tRFC substantially and bump Rasmactwr mainly and rasmactrd. try with 1000 mhz memory speed with tight timings and start  overclocking memory, no errors, then maybe tighten more.... elpida in polaris does miracles at lower speed than even 1750 mhz with proper timings
Pages:
Jump to: