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

No problem.  You may not have noticed it before because previous versions of cryptonight were much less taxing on the core, so the clock (frequency) scaling, especially at 950mv, was likely significantly less aggressive.

terry1

Aaaaand where is the wallet address?

Hi dev,my 6xvega cannot login pool.Do you have any idea?

bat is :    teamredminer.exe -a cnv8 -o stratum+tcp://xmrv7-bj.ss.poolin.com:443 -u terry1.%computername%   -p x

I mean, it seems clear that there's something very uncommon going on here given that you're the only one I know of with this problem and you're also seeing the same thing with SRB. It rather feels related to your networking setup. Personally, I would install Wireshark next and look at the network traffic to see what's going on. Really shooting from the hip here, but do you have any weird IPv6 setup?

Another thing you could post here would be the output of "netstat -n -p tcp" from the command prompt when (1) xmr-stak is running and (2) right when TRM or SRB is trying to connect to the same pool.

After a Windows reinstall, with 18.5.1/18.6.1/18.11.1 in the cryptoknight and MPH pool still no luck.

Is there a log or debug mode in the miner? Maybe that could help to find my problem.

Yes, quite clearly documented both in the release docs, and for your convenience also in the log you’re pasting yourself.

Have you enabled —pool_broken_rpc as mentioned above? We might do this by default going forward. The issue is that nanopool can’t handle multiple outstanding requests.

Cheers, K

Thank you pbfarmer that makes sense.
You force me to learn more of Advanced Clock Generator(ACG)/Advanced Voltage Frequency Scaling(AVFS) :-)
Never noticed that behavior before in HWiNFO. Found some interesting stuff here: https://www.reddit.com/r/Amd/comments/7dzc9j/vega_56_w_64_bios_tweak_result_good_chip_or/

something wrong on nanopool with this miner newer seen smthg like this on SRB.and sometimes rig power consumption decrase to 100w from 1300w's

all it's clearly possible to understand from vega's fan noise.Usualy do this every 5 min. maybe much more early.

This is standard behavior of Vegas, due to ACG/AVFS.  The lower your voltages, the more clock throttling under load.  This has nothing to do with the miner, other than the fact that it puts a certain signature load on the GPU.

Would be great fun, and we have one for testing! That said, there are a few things higher up on the prio list though .

Todxx/K66,

I know you guys have plenty on your plate... figured no hurt in asking though--any plans on optimizing for VFE's or too niche a product?

N2

We’re discussing the roadmap currently, there are a few different options. If we choose heavy for the next step it will still be two weeks, I’d say.

Hi,

any estimation when you planning to release heavy variant algorithm?

Thanks.

There was a problem about 3 hours ago that would have caused miners to reconnect.  Other than that, you shouldn't be seeing it reconnect frequently.
Are you seeing frequent reconnects to the dev pool?

is there a problem with dev pool right now? reconnecting every now and then.

That is much lower than what you would typically expect from a 470.  Have you enabled compute mode on the card?  Have you modified the memory straps on it?

Yesterday run teamredminer 0.3.7 on my 470. The most stable cn_config for me is 4-4, its so low because i think monitor plugged in videocard. I got 670 H/s with 7/64 and 18.6.1

Yes kerney, that is my standard settings in OvedriveNtool.

Just did some more test and found, when applying overdrive and look in the HWiNFO64 i see that GPUP7 clocks is set on  higher values of set in overdrive.ini ?
And when i start miner values go down?
Down in profiles of ovedrivetool.ini i added actual clock values read by HWiNFO before and after start miner:

Run_OverdriveNTool.bat (OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Sapphire -p2Nitro_RX570 -p3Asus_Vega64 -p4Gigabyte)
[General]
ShowBusNumber=1
ShowPnpString=0
ShowAdapterIndex=0
ShowFriendlyName=0
ShowRegistryKey=1
MainWindowLeft=984
MainWindowTop=244

[Profile_0]
Name=Sapphire
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0    before start miner        after start miner
GPU_P7=1408;955      1437;955            1378 and 1381 (changeing)
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1088;945
Fan_Min=3500
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=0

[Profile_1]
Name=Nitro_RX570
GPU_P0=300;750;0
GPU_P1=588;765;0
GPU_P2=952;943;0
GPU_P3=1041;1012;0
GPU_P4=1106;1075;0
GPU_P5=1168;1143;0
GPU_P6=1209;1150;0
GPU_P7=1170;850
Mem_P0=300;750;0
Mem_P1=1000;800;0
Mem_P2=1970;900
Fan_Min=576
Fan_Max=2150
Fan_Target=50
Fan_Acoustic=1340
Power_Temp=85
Power_Target=0

[Profile_2]
Name=Asus_Vega64
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0
GPU_P7=1490;930             1535;930        1463 and 1466 and 1467 (changeing)
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1100;910
Fan_Min=2300
Fan_Max=3500
Fan_Target=50
Fan_Acoustic=1600
Power_Temp=85
Power_Target=0

[Profile_3]
Name=Gigabyte
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0
GPU_P7=1408;950                1444;950        1381 and 1382 and 1385 (changeing)         
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1070;950
Fan_Min=3350
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=0

Have you tried disabling all lower p-states in OverdriveNTool, i.e. click the little text "P2", "P3" etc left of the MHz column so they are greyed out? Only using the highest state has helped me sometimes to force the driver to use the specified clocks.