SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[Cideg]

Please add the new RandomXL algorithm for Loki. The algorithm name used by the miner is randomx / loki or rx / loki.

Loki has a new fork, block 321467 -> RandomXL loki-project / https://github.com/loki-project/loki/pull/675

[hesido]

I think there's a bug with --maxnosharessent , Whether I set it to 5 or 10, it resets miner after only 1 minutes (and it says 1 minute in the log, not the 5 or 10 I'm setting..). Anybody else have a similar problem?

[MixedupDownstairs]

I think there's a bug with --maxnosharessent , Whether I set it to 5 or 10, it resets miner after only 1 minutes (and it says 1 minute in the log, not the 5 or 10 I'm setting..). Anybody else have a similar problem?

its been like that since the version it was added.

[ruslan4040]

How start mining r9 390,290,270 CCN coin? I try, but dont work, r9 280, r9 fury work fine.

[doktor83]

I think there's a bug with --maxnosharessent , Whether I set it to 5 or 10, it resets miner after only 1 minutes (and it says 1 minute in the log, not the 5 or 10 I'm setting..). Anybody else have a similar problem?

its been like that since the version it was added.

Since then ? I know there is some issue with this when windows changes time (pulls from NTP or user changes clock) - this happens rarely, but other than it should work fine. I will check it.

How start mining r9 390,290,270 CCN coin? I try, but dont work, r9 280, r9 fury work fine.

Those gpu's should also work. Give more info, which algo is that CCN coin, which miner version are you trying with?
A logfile would be very helpful.

[hesido]

Since then ? I know there is some issue with this when windows changes time (pulls from NTP or user changes clock) - this happens rarely, but other than it should work fine. I will check it.

This thing is for sure, SRB says "1" minute regardless of what setting it is, it may think more / less minutes have passed if there was a clock change (my clock seems fine though), but it specifically says 1 minute still.

[doktor83]

Since then ? I know there is some issue with this when windows changes time (pulls from NTP or user changes clock) - this happens rarely, but other than it should work fine. I will check it.

This thing is for sure, SRB says "1" minute regardless of what setting it is, it may think more / less minutes have passed if there was a clock change (my clock seems fine though), but it specifically says 1 minute still.

Have you tried with 1 's' (--maxnosharesent , not --maxnosharessent like you wrote). Also it's not set in minutes, you set it in seconds.

[hesido]

Since then ? I know there is some issue with this when windows changes time (pulls from NTP or user changes clock) - this happens rarely, but other than it should work fine. I will check it.

This thing is for sure, SRB says "1" minute regardless of what setting it is, it may think more / less minutes have passed if there was a clock change (my clock seems fine though), but it specifically says 1 minute still.

Have you tried with 1 's' (--maxnosharesent , not --maxnosharessent like you wrote). Also it's not set in minutes, you set it in seconds.

Ah, I had the option name correct in the command line, but I had no idea it was in seconds!

Code:

--maxnosharesent value (if no share is sent to the pool for x time, restarts miner. def. is 30 min)

Could be changed to:

Code:

--maxnosharesent value (if no share is sent to the pool for x seconds, restarts miner. def. is 1800 seconds (30 min))

Thanks Dok.

[doktor83]

Since then ? I know there is some issue with this when windows changes time (pulls from NTP or user changes clock) - this happens rarely, but other than it should work fine. I will check it.

This thing is for sure, SRB says "1" minute regardless of what setting it is, it may think more / less minutes have passed if there was a clock change (my clock seems fine though), but it specifically says 1 minute still.

Have you tried with 1 's' (--maxnosharesent , not --maxnosharessent like you wrote). Also it's not set in minutes, you set it in seconds.

Ah, I had the option name correct in the command line, but I had no idea it was in seconds!

Code:

--maxnosharesent value (if no share is sent to the pool for x time, restarts miner. def. is 30 min)

Could be changed to:

Code:

--maxnosharesent value (if no share is sent to the pool for x seconds, restarts miner. def. is 1800 seconds (30 min))

Thanks Dok.

Theres a notice on the first page and in the readme that all parameters that take a time value are in seconds

[hesido]

Since then ? I know there is some issue with this when windows changes time (pulls from NTP or user changes clock) - this happens rarely, but other than it should work fine. I will check it.

This thing is for sure, SRB says "1" minute regardless of what setting it is, it may think more / less minutes have passed if there was a clock change (my clock seems fine though), but it specifically says 1 minute still.

Have you tried with 1 's' (--maxnosharesent , not --maxnosharessent like you wrote). Also it's not set in minutes, you set it in seconds.

Ah, I had the option name correct in the command line, but I had no idea it was in seconds!

Code:

--maxnosharesent value (if no share is sent to the pool for x time, restarts miner. def. is 30 min)

Could be changed to:

Code:

--maxnosharesent value (if no share is sent to the pool for x seconds, restarts miner. def. is 1800 seconds (30 min))

Thanks Dok.

Theres a notice on the first page and in the readme that all parameters that take a time value are in seconds

Lol, sure, but as you might have realized from the many questions posed here, that's not how an averagely dumb brain works . I personally skim for the part I need, that's how I probably missed that one. Still, it's good to be explicit

[ruslan4040]

rig r9 390x. win 8.1 drivers 16.3.2 dont start srbminer.

Benchmark mode
------------------------

Miner will benchmark every algo defined in algos.txt for 60 seconds and return r
esults
You can use these values for the 'hashrate' parameter in algos.txt
The benchmark will use configs you defined in algos.txt

Tweaking is not available in benchmark mode, sorry.

[2019-07-29 23:34:11] Compiling [normal] kernel for DEVICE BUS_ID[1]
error: Unknown attribute kind (45)
Для пpoдoлжeния нaжмитe любyю клaвишy . . .

[doktor83]

rig r9 390x. win 8.1 drivers 16.3.2 dont start srbminer.

Benchmark mode
------------------------

Miner will benchmark every algo defined in algos.txt for 60 seconds and return r
esults
You can use these values for the 'hashrate' parameter in algos.txt
The benchmark will use configs you defined in algos.txt

Tweaking is not available in benchmark mode, sorry.

[2019-07-29 23:34:11] Compiling [normal] kernel for DEVICE BUS_ID[1]
error: Unknown attribute kind (45)
Для пpoдoлжeния нaжмитe любyю клaвишy . . .

Maybe try newer drivers.. 

[3MEHDI]

2 minute tests with just 2 accepted shares are very accurate!

A good setup with perfectly tuned Vega's can do great on average and poolside, but not that great as you want to show here. Please don't try to confuse beginners here. I own enough Vega's and use both miners, both have their advantages and disadvantages. But you have a very big problem mate. If you really want to help, here or there, this doesn't matter, post your own real settings (not the copied ones from the Vega Mem Tweak thread) and don't hide behind the anonymity with your daily blabla.

post setings like DOCTOR?. he posted  tweeking setings for 10 step? he say posted but never posted setings here or AMD TWEAK topic. but he block AMD TWEAK.hmm.
i use pbfarmer seting and my vega block(etc i chg only RAS 28 t oRAS 32 and 1 gpu work)- every vega have diferent seting. but you know this if you try any setign with vega. AND this test not amd tweak test this test only give other solution with big HR and little power . before 30 day srbminer is very good miner- today srbimner nod good miner- TRM ias good miner today. Tomorow? mybe  JCE back and best who know....

You think this test is fake ( 3min only) ? post your here if you have better. Today i post test after 2-3 hour and what you say after this? hmm you not postet after 10 day. when i posted after 10 day you say not tested 30 day?

If you have 1 vega you know for TRM and if your vega not have identical HR like my test(+ - 2%) you not good setup your vega. Read my other post- before 1 yrs. i love srbminer but i hate DEV like DOCTOR. He stole -and use for all and give what? BLOCK AMD TWEAK.

see this test(2-3 min etc) srb mineron on this day have best HR. but this is past.
This is my post old 1 YEARS

INFO - TEST VEGA 56 PowerColor

3*Vega56 flashed to 64
Crimson-ReLive-Beta-Blockchain driver
SRBminer 1.4.9
GPU - 1442/1437/1407mhz 905-907mv
MEM - 1095/1100mhz 900mv

Cryptonight V7(monero)
"intensity" : 120  HR=6000 - 560W
https://ip.bitcointalk.org/?u=https%3A%2F%2Fimage.prntscr.com%2Fimage%2FrK5kLVCPQQS89xDEIYhHgQ.jpg&t=601&c=FKvSCLfftQcJ3A

Cryptonight lite(aeon)
"intensity" : 235  HR=12900 - 570W
https://ip.bitcointalk.org/?u=https%3A%2F%2Fimage.prntscr.com%2Fimage%2F23TkvCkvRMCvC9p2YhxiCQ.jpg&t=601&c=jzKrcqeLttCNog

Cryptonight liteV7(trtl)
"intensity" : 235  HR=12900 - 570W
https://ip.bitcointalk.org/?u=https%3A%2F%2Fimage.prntscr.com%2Fimage%2FXb6WiZ1EQaS5UMmWq3KHuw.jpg&t=601&c=40wL1salqQB41w

Cryptonight ultraheavy-lightv3(ipbc)
"intensity" : 239  HR=11100 - 550W
https://ip.bitcointalk.org/?u=https%3A%2F%2Fimage.prntscr.com%2Fimage%2FPeiajoLsTJO3Zwc1ZX8f8A.jpg&t=601&c=EecXYBVgOUeWpg

Cryptonight heavy(sumo)
"intensity" : 56  HR=4550 - 530W
https://ip.bitcointalk.org/?u=https%3A%2F%2Fimage.prntscr.com%2Fimage%2F2xW89wB8SxaZeSWX1n6zjQ.jpg&t=601&c=F9A7K4vsm20wsA

Cryptonight artocache(arto)
"intensity" : 118  HR=5400 - 550W
https://ip.bitcointalk.org/?u=https%3A%2F%2Fimage.prntscr.com%2Fimage%2FAopDRnW8R0m9EDnqyB8-aw.jpg&t=601&c=y0v-sXDjA4afqw

For all other AMD MEM tWEAK setings you have topic for this but this is universal seting for start...

Lucky Vega 64 or flashed 64 (Samsung):
--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248

Weaker Vega 64 or flashed 64 (Samsung) - use if lucky timings aren't stable:
--CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248

Lucky Vega 56 (Hynix):
--RAS 22 --RCDRD 17 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 4 --RFC 148 --REF 15600

Weaker Vega 56 (Hynix):
--RAS 24 --RCDRD 19 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 5 --RFC 148 --REF 15600



i just chg RFC and RAS for testing . any gpu must start solo and test. after test and see just go on next gpu.

check it

https://bitcointalk.org/index.php?topic=5170902.new#new

[commonorx]

Has to be the worst miner I have ever used. I get so many rejected shares. My has rate even though over 2K is meaning less at the pool. My hash rate is the same as when I used CASTXMR, but I made more money with CAST because I didn't have as many rejected and stale shares as SRB. Restart restart restart.. that is the answer??

What a joke.

[Lunga Chung]

Has to be the worst miner I have ever used. I get so many rejected shares. My has rate even though over 2K is meaning less at the pool. My hash rate is the same as when I used CASTXMR, but I made more money with CAST because I didn't have as many rejected and stale shares as SRB. Restart restart restart.. that is the answer??

What a joke.

tell us who's forcing you to use SRB miner and we will rescue you! right guys ?

[burntroach85]

you have to have something not setup rite on the miner  because thats insane  SRB is prolly THE BEST one you can get  no only that  cast xmr is dead

Has to be the worst miner I have ever used. I get so many rejected shares. My has rate even though over 2K is meaning less at the pool. My hash rate is the same as when I used CASTXMR, but I made more money with CAST because I didn't have as many rejected and stale shares as SRB. Restart restart restart.. that is the answer??

What a joke.

[lsHaKeRl]

Hi Guys!
I've been working on the constellation MiningRig Vega64 for the past 2 years - water cooled and fe cooled mix.

With the following settings and setup:

SRB Miner 1.9.3.
Windows 10 (1803)
Adrenaline Driver 18.6.1
ASUS B250 Mining Expert
2x Enermax Platimax 1700W ATX 2.4
8x Vega64 - WATER cooled // 4x Vega64 FE

Today I spent the whole day testing my rig again and again and again, and was able to reach the following values:

Highest daily value: 2346 H/s
https://drive.google.com/file/d/1uYAECE4AHwyW87EuXRnN7DFuBFH4PWBO/view?usp=sharing

Settings CONFIG:
{"id": 0, "intensity": 124, "worksize": 16, "threads": 2, "tweak_profile": 10},
{"id": 1, "intensity": 124, "worksize": 16, "threads": 2, "tweak_profile": 10},

POWERTABLE settings:
https://drive.google.com/file/d/1E13BCCLTxWO6yf4sGDfVG93XAiw-HRE7/view?usp=sharing
Download LINK:
https://drive.google.com/file/d/1UDGf8JcuKY4mFrSiFdrcWeYd24Gh2rtT/view?usp=sharing

(IMPORTANT: Then adjust the values in the OverdrivnTool for P7 and P3 to: 1435Mhz // 966mV and 1100Mhz // 923mV

I have now searched for a strong and stable attitude and personally changed something. I have also tried to reduce power consumption a little, but it comes with P7 (mV) from 950 crash of the system. So 966mV I think is the safest and option, with P3 (mV) 923 is very close, as I have a lot of experience with P3 (MhZ) of 1100, where they have set in the old PowerTables between 905mv and 915mv, that often crashed the system.
Maybe those are not the best values, but I'm pretty happy. I am always happy to work on it and reach new heights in mining with my Vega`s.  

I worked for a long time with the TABLE // P7 - 1408/915 and P3 - 1100/905, but unfortunately I had to realize that these are no longer stable or I could not find a stable version and I tried a lot.

I hope I could possibly help, you can always send me a message.

Best regards
Patrick

[AlexMineX]

Hi,

Need some guidance. I have Rigs with RX580 - bios moded.
I was mining Cryptonight algo - Tube for quite some time. My rigs were with Blockchain AMD drivers and SRBMiner 1.7.3 - I have very small problems with rigs, from some time the miner software crashes but is something like once in a 2-3 days. I just restart the miner software and continue to mine for another 2-3 days. When it crashes my rig is  ~140 W till i restart it. SRBRestarter does not work for some reason probably because see that the process is ON /crashed but is not absent /

I decided to upgrade the miner with the last version first without changing the drivers. And all the problems started every night at about the same time all rigs stop sending to the pool but they continue to draw full power from the wall .
I tried to set --minrigspeed but the miner works at full power just not submitting to the pool  so the string does not work for me /pool is https://bittube.miner.rocks/

Then I changed the drivers with 18.5.1 but without luck - the problem stays. It works for most of the day but then stops submitting to the pool and continues to draw full power from the wall /and not 140w like with 1.7.3/

Current setup is
SRB Miner 1.9.3
Afterburner 4.5.0
AMD Driver 18.5.1

Screenshot https://pasteboard.co/IrsHrzW.png

[abg00]

Hi,

Need some guidance. I have Rigs with RX580 - bios moded.
I was mining Cryptonight algo - Tube for quite some time. My rigs were with Blockchain AMD drivers and SRBMiner 1.7.3 - I have very small problems with rigs, from some time the miner software crashes but is something like once in a 2-3 days. I just restart the miner software and continue to mine for another 2-3 days. When it crashes my rig is  ~140 W till i restart it. SRBRestarter does not work for some reason probably because see that the process is ON /crashed but is not absent /

I decided to upgrade the miner with the last version first without changing the drivers. And all the problems started every night at about the same time all rigs stop sending to the pool but they continue to draw full power from the wall .
I tried to set --minrigspeed but the miner works at full power just not submitting to the pool  so the string does not work for me /pool is https://bittube.miner.rocks/

Then I changed the drivers with 18.5.1 but without luck - the problem stays. It works for most of the day but then stops submitting to the pool and continues to draw full power from the wall /and not 140w like with 1.7.3/

Current setup is
SRB Miner 1.9.3
Afterburner 4.5.0
AMD Driver 18.5.1

Screenshot https://pasteboard.co/IrsHrzW.png

check power connector and power wire
also check undervolt
compute error possible memory error

[TheRealSTU]

Hi,

Need some guidance. I have Rigs with RX580 - bios moded.
I was mining Cryptonight algo - Tube for quite some time. My rigs were with Blockchain AMD drivers and SRBMiner 1.7.3 - I have very small problems with rigs, from some time the miner software crashes but is something like once in a 2-3 days. I just restart the miner software and continue to mine for another 2-3 days. When it crashes my rig is  ~140 W till i restart it. SRBRestarter does not work for some reason probably because see that the process is ON /crashed but is not absent /

I decided to upgrade the miner with the last version first without changing the drivers. And all the problems started every night at about the same time all rigs stop sending to the pool but they continue to draw full power from the wall .
I tried to set --minrigspeed but the miner works at full power just not submitting to the pool  so the string does not work for me /pool is https://bittube.miner.rocks/

Then I changed the drivers with 18.5.1 but without luck - the problem stays. It works for most of the day but then stops submitting to the pool and continues to draw full power from the wall /and not 140w like with 1.7.3/

Current setup is
SRB Miner 1.9.3
Afterburner 4.5.0
AMD Driver 18.5.1

Screenshot https://pasteboard.co/IrsHrzW.png

Also have similar problem. Use to be 24/7 stable ~0.1% HW errors.
Been mining TUBE on and off so I can't figure out exactly when the problem started but I think after SRBMiner v1.8.8.
Happens after 1-3 days of mining, then all of a sudden starts spitting out 100% HW errors, continues retrieving jobs from pool but doesn't restart.

Current setup:
5x Vega 56s (no bios mod)
AMD drivers 18.6.1
SRB Miner v1.9.3 (Run through AwesomeMiner + Remote Agent if that makes a difference, although never used to be a problem)
Parameters: --ccryptonighttype bittubev2 --cgpuid 0,1,2,3,4 --cgpuintensity 56,56,56,56,56 --cgpuworksize 8,8,8,8,8 --cgputhreads 2,2,2,2,2 --cgpufragments 1,1,1,1,1 --cgputweakprofile 5L,10L,10L,2,9L --cgpuheavymode 2,2,2,1,2 --resetvega --enablegpurampup --nobinaries --preparedata

Still trying to figure it out with low clocks ~900mhz atm but still same problem.
--nobinaries doesn't help.