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

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" (in case you're wondering, that's 1107 * 100, converted to hex, byteswapped, applied to state 07.)

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

It might make sense in that you could manually adjust the top SOC clock rate in your SoftPowerPlay mod.

https://i.gyazo.com/4a1ed3ce7cc6919dc301470fe3e313ec.png

If I am recalling correctly from a few years back, this involved a little endian conversion?  Which someone explained how to do using the Windows calculator/some setting.

It's been a while, but I know this is what I did (bumped up the SOC value) when I wanted P3 to stay at 1100 for memory.

any chance of getting higher numbers than 16 for cn_config.... vega VII only gets 2.5Kh with TeamRed.   I get 2.9Kh with SRBminer for cnr.

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...

That doesn’t really make sense.  You should only be running 1107 SOC for 1100 mem.  You sure about these settings?

My flashed 56 has been slowly degrading and requiring more voltage over time - tho nowhere near this bad.  Assuming you want to run reasonably efficiently hr/w, you’re actually better running stock - you’ll save power on the lower mem voltage/clock, for similar performance due to the tighter straps (at least that was true for cnv2).  64 flash was really only useful for mem clocks over 1100.  Maybe try flashing one back and see if that helps - should mean a mem clock around 900-950.

If it’s an SOC issue though, that won’t help, since it still runs 1107 in p3 from what I’ve heard.

Soc clocks freq shown at 1199 MHz in GPU-Z while mining.
Core volts around 0.9688

These are reference Sapphire 56's flashed to ref Sapphire 64.
This is my ppt:

Windows Registry Editor Version 5.00
Get in touch via bitcointalk on updates or further development wishes. User brnsted
ETH A13015081E1f9CF27A2843e2A623F362D0d08666
XMR 47NgZN7Mp5CcfKzUKhFHXiMuXghudzFegUPWaTUJU71QVze3P1o2gd9MuhroHrYGAH1spqWEWDrnvUp eqFCic8B772ySpCM
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0005]
"PP_PhmSoftPowerPlayTable"=hex:B6,02,08,01,00,5C,00,E1,06,00,00,EE,2B,00,00,1B,\
  00,48,00,00,00,80,A9,03,00,F0,49,02,00,8E,00,08,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,02,01,5C,00,4F,02,46,02,94,00,9E,01,BE,00,28,01,7A,00,8C,00,\
  BC,01,00,00,00,00,72,02,00,00,90,00,A8,02,6D,01,43,01,97,01,F0,49,02,00,71,\
  02,02,02,00,00,00,00,00,00,08,00,00,00,00,00,00,00,05,00,07,00,03,00,05,00,\
  00,00,00,00,00,00,01,08,20,03,52,03,52,03,52,03,52,03,52,03,6B,03,89,03,01,\
  01,89,03,01,01,84,03,00,08,60,EA,00,00,00,40,19,01,00,01,80,38,01,00,02,DC,\
  4A,01,00,03,90,5F,01,00,04,00,77,01,00,05,90,91,01,00,06,C0,D4,01,00,07,01,\
  08,D0,4C,01,00,00,00,80,00,00,00,00,00,00,1C,83,01,00,01,00,00,00,00,00,00,\
  00,00,70,A7,01,00,02,00,00,00,00,00,00,00,00,88,BC,01,00,03,00,00,00,00,00,\
  00,00,00,38,C1,01,00,04,00,00,00,00,00,00,00,00,88,D5,01,00,05,00,00,00,00,\
  01,00,00,00,70,D9,01,00,06,00,00,00,00,01,00,00,00,00,26,02,00,07,00,00,00,\
  00,01,00,00,00,00,05,60,EA,00,00,00,40,19,01,00,00,80,38,01,00,00,DC,4A,01,\
  00,00,90,5F,01,00,00,00,08,28,6E,00,00,00,2C,C9,00,00,01,F8,0B,01,00,02,80,\
  38,01,00,03,90,5F,01,00,04,F4,91,01,00,05,D0,B0,01,00,06,C0,D4,01,00,07,00,\
  08,6C,39,00,00,00,24,5E,00,00,01,FC,85,00,00,02,AC,BC,00,00,03,34,D0,00,00,\
  04,68,6E,01,00,05,08,97,01,00,06,EC,A3,01,00,07,00,01,68,3C,01,00,00,01,04,\
  3C,41,00,00,00,00,00,50,C3,00,00,00,00,00,80,38,01,00,02,00,00,A0,86,01,00,\
  04,00,00,01,08,00,98,85,00,00,40,B5,00,00,60,EA,00,00,50,C3,00,00,01,80,BB,\
  00,00,60,EA,00,00,94,0B,01,00,50,C3,00,00,02,00,E1,00,00,94,0B,01,00,40,19,\
  01,00,50,C3,00,00,03,78,FF,00,00,40,19,01,00,88,26,01,00,50,C3,00,00,04,40,\
  19,01,00,80,38,01,00,80,38,01,00,50,C3,00,00,05,80,38,01,00,DC,4A,01,00,DC,\
  4A,01,00,50,C3,00,00,06,00,77,01,00,00,77,01,00,90,5F,01,00,50,C3,00,00,07,\
  90,91,01,00,90,91,01,00,00,77,01,00,50,C3,00,00,01,18,00,00,00,00,00,00,00,\
  0B,E4,12,60,09,60,09,4B,00,0A,00,54,03,90,01,90,01,90,01,90,01,90,01,90,01,\
  90,01,00,00,00,00,00,02,04,31,07,DC,00,DC,00,DC,00,90,01,00,00,59,00,69,00,\
  4A,00,4A,00,5F,00,73,00,73,00,64,00,40,00,90,92,97,60,96,00,90,55,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,02,D4,30,00,00,02,10,60,EA,00,\
  00,02,10

Bought the GPUs new on Amazon back in September 2017 iirc. Chinese third party seller ofc. Could very well all be duds. Mind you they've been hashing fast and all... Just been an absolute pain on power as soon as I need memory to do its thing. As said, x16rt at 850mV core, mem pstates disabled and all was peachy.

You have 64s, right?  Are they purchased from a (reputable) retailer, or secondhand?  Starting to wonder if those things got cooked in the past and maybe you have some hardware faults now - those clocks shouldn’t need more than 850mv.

Btw - assuming these are your runtime settings...  what does your ppt look like?

Just an update.

Downloaded the latest version last night and mined lyra2rev3 last night and did notice a slight increase in hashing performance.

Switched over to CN R just recently and got everything running within 10-15 minutes no problems. I did not measure voltage or anything but settings have been left mostly the same as with CN v8. Im on Windows 10 1607 with the network update. I think most of the drivers are the 19.x.x but might have a few on 18.x.x. Performance seems to be on par with what it was before and now just testing for stability and longevity.

Overall this is probably the smoothest fork update for my little farm! Im liking the addition of color, so much easier to read things lol.

No, working fine here.  Have issues with one card that I will need troubleshoot, but working fine on Nanopool after the fork.

Edit: 18.5.1 driver, OCN settings 1407/910 1100/895, Vega 56 cards (reference -> flashed to 64) + some Sapphire Pulse Vegas 1407/900 960/890.  One card acting up, but the others working fine.  1960/1980 kh/s at 15+14

All my shares are rejected now! Anybody else?

[2019-03-09 20:38:04] Pool pool.supportxmr.com share rejected. (GPU2) Error code: -1 - Low difficulty share (a:141 r:6) (188 ms)
[2019-03-09 20:38:22] Stats Uptime: 0 days, 01:04:31
[2019-03-09 20:38:22] GPU 0 [59C, fan 87%] cnr: 2.311kh/s, avg 2.315kh/s, pool 2.235kh/s a:27 r:0 hw:0
[2019-03-09 20:38:22] GPU 1 [57C, fan 86%] cnr: 2.342kh/s, avg 2.336kh/s, pool 1.774kh/s a:23 r:1 hw:0
[2019-03-09 20:38:22] GPU 2 [55C, fan 86%] cnr: 2.306kh/s, avg 2.304kh/s, pool 1.845kh/s a:24 r:2 hw:0
[2019-03-09 20:38:22] GPU 3 [63C, fan 87%] cnr: 2.279kh/s, avg 2.279kh/s, pool 2.649kh/s a:32 r:1 hw:0
[2019-03-09 20:38:22] GPU 4 [54C, fan 88%] cnr: 2.274kh/s, avg 2.279kh/s, pool 2.888kh/s a:35 r:2 hw:1
[2019-03-09 20:38:22] Total                cnr: 11.51kh/s, avg 11.51kh/s, pool 11.39kh/s a:141 r:6 hw:1
[2019-03-09 20:38:26] Pool pool.supportxmr.com received new job. (job_id: PnLU2XWpyX31dj7IhXHtUQHsgi5h)
[2019-03-09 20:38:26] Pool pool.supportxmr.com share rejected. (GPU3) Error code: -1 - Low difficulty share (a:141 r:7) (89 ms)
[2019-03-09 20:38:52] Pool pool.supportxmr.com received new job. (job_id: PRfxENISbIlmg3C0riLiIqM1Gf3/)
[2019-03-09 20:38:52] Pool pool.supportxmr.com share rejected. (GPU1) Error code: -1 - Low difficulty share (a:141 r: (114 ms)
[2019-03-09 20:38:52] Stats Uptime: 0 days, 01:05:01
[2019-03-09 20:38:52] GPU 0 [58C, fan 88%] cnr: 2.315kh/s, avg 2.315kh/s, pool 2.218kh/s a:27 r:0 hw:0
[2019-03-09 20:38:52] GPU 1 [57C, fan 85%] cnr: 2.335kh/s, avg 2.336kh/s, pool 1.760kh/s a:23 r:2 hw:0
[2019-03-09 20:38:52] GPU 2 [57C, fan 86%] cnr: 2.306kh/s, avg 2.304kh/s, pool 1.831kh/s a:24 r:2 hw:0
[2019-03-09 20:38:52] GPU 3 [62C, fan 87%] cnr: 2.279kh/s, avg 2.279kh/s, pool 2.629kh/s a:32 r:2 hw:0
[2019-03-09 20:38:52] GPU 4 [54C, fan 88%] cnr: 2.281kh/s, avg 2.279kh/s, pool 2.866kh/s a:35 r:2 hw:1
[2019-03-09 20:38:52] Total                cnr: 11.52kh/s, avg 11.51kh/s, pool 11.30kh/s a:141 r:8 hw:1
[2019-03-09 20:39:03] Pool pool.supportxmr.com received new job. (job_id: 9c5hNr/H/mBkFQ6w5pbU+nSUk5Jv)
[2019-03-09 20:39:03] Pool pool.supportxmr.com share rejected. (GPU4) Error code: -1 - Low difficulty share (a:141 r:9) (93 ms)
[2019-03-09 20:39:12] Pool pool.supportxmr.com share rejected. (GPU0) Error code: -1 - IP Address currently banned for using an invalid mining protocol, please check your miner (a:141 r:10) (17 ms)

EDIT: was pool side problem, it is OK now. THX!

check what's your SoC clocks, core volts are in Hwinfo when you get those hangs.

@pbfarmer
I'm having the same issues as in the other thread we chatted a while ago.
Those Vegas are just horrible. I have to set Mem_P3 and Core_P7 at 1000 to be able to run the miner. Anything below and the miner will not even initialise and the rig reboots.

I was able to run low core voltages with x16 algos by disabling the Mem states. Got rid of all problems. As soon as I need memory (like for CN) all hell breaks loose. Here's what I'm having to deal with now:

GPU_P0=852;800
GPU_P1=991;805
GPU_P2=1084;810
GPU_P3=1138;820
GPU_P4=1150;830
GPU_P5=1202;840
GPU_P6=1250;845
GPU_P7=1408;1000
Mem_P0=167;800
Mem_P1=500;805
Mem_P2=800;810
Mem_P3=1100;1000
Fan_Min=3600
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=0
Power_Temp=85
Power_Target=0

Total power draw at the wall for 6 Vegas: 1400W

No, i asked Kerney, and so far it is not supported. They MAY look at it, since its really close to CNv8, but i would guess, they will want to get the CN-R fixed first.

thanks guys, seems to work ok after the fork, (for my 550s, running 520h/s +)

This is what happens on Vega 56s.  Seems like one thread hangs no matter what.  Will try increasing volts.

Todxx is getting some sleep, and I won’t be available until maybe 3h.

We’ve had some issues with testnet pools that our dev fee server(s) connect to. We thought we had solved it by switching to a more stable one, but seems like there are still issues. Probably a factor that more and more people are putting stress on the testnet pools right now before the fork.

So, for anyone else having the same issue, I hope it will be resolved as soon as we’re on the mainnet instead. Otherwise we’ll go to work and sort it out.

The reduced rate should be resolved as soon as you connected again though, should happen quickly. Do you see a log line about being connected again?

[2019-03-09 17:57:06] Dev pool connection was closed by remote side.
[2019-03-09 17:57:06] Mining will proceed at reduced rate while not connected to dev pool.


hmmmm
any fix soon?!

Haha nice, appreciate the shilling! Cast was indeed a great miner when it came out, I remember it well. Let us know if there’s anything else you need or have questions about!