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

[xmr8218]

hi, the miner always show this error "couldn't login to pool" when my internet drop for 1 or 2 second then reconnected with new IP(dynamic IP). I tried manually switch pool O/P option but same error still appear, but if i manually close and restart the miner then the miner can connect to pool without error.

My miner setup as follow:
1. miner IP are fixed by the router
2. miner connected to giga switch then only to router
3. miner uses SSL/TLS connection to pool with keep alive turn off. I tried turn on keep alive option but have the same issue.

any idea?

a log file would be really helpful

hi, attached is the log file https://drive.google.com/file/d/106A65dEHSQHhRxPkKcYd1VrAWlxF9dNd/view?usp=sharing
thanks alot

[1685663615]

1685663615

[1685663615]

1685663615

[1685663615]

1685663615

[1685663615]

1685663615

[1685663615]

1685663615

[mk111]

Dok - any plans to implement the AMD Memory tweak into SRB?
https://bitcointalk.org/index.php?topic=5123724.0

[doktor83]

hi, the miner always show this error "couldn't login to pool" when my internet drop for 1 or 2 second then reconnected with new IP(dynamic IP). I tried manually switch pool O/P option but same error still appear, but if i manually close and restart the miner then the miner can connect to pool without error.

My miner setup as follow:
1. miner IP are fixed by the router
2. miner connected to giga switch then only to router
3. miner uses SSL/TLS connection to pool with keep alive turn off. I tried turn on keep alive option but have the same issue.

any idea?

a log file would be really helpful

hi, attached is the log file https://drive.google.com/file/d/106A65dEHSQHhRxPkKcYd1VrAWlxF9dNd/view?usp=sharing
thanks alot

I see two things in the log : time shifting, and maybe a bug in the main pool reconnection mechanism.

If you can turn off automatic time setup, and set it manually that would be good. When windows re-adjusts time BACK that can mess up a lot of things, miner thinks a day passed..

The second, main pool reconnection, i will test and fix if needed. It was implemented a long time ago, and a lot of stuff changed since, so maybe it's not working as it should.

[doktor83]

Dok - any plans to implement the AMD Memory tweak into SRB?
https://bitcointalk.org/index.php?topic=5123724.0

I have something in plan, but you can already use Eliovp's tweaker with SRB, he pushed a windows binary  

[dulama]

Hi,

Please fix "Algorithm: Cryptonight V4 (R) - after 1 minute of work produces multiple errors!"

Thanks,
Vlad

[lncm]

Why remove webchain?

Webchain fork to Lyra2-webchain algorithm and not working with cryptonight-webchain. New webchain miner works on CPU only.

Didn't know that, thanks.

[xmr8218]

hi, the miner always show this error "couldn't login to pool" when my internet drop for 1 or 2 second then reconnected with new IP(dynamic IP). I tried manually switch pool O/P option but same error still appear, but if i manually close and restart the miner then the miner can connect to pool without error.

My miner setup as follow:
1. miner IP are fixed by the router
2. miner connected to giga switch then only to router
3. miner uses SSL/TLS connection to pool with keep alive turn off. I tried turn on keep alive option but have the same issue.

any idea?

a log file would be really helpful

hi, attached is the log file https://drive.google.com/file/d/106A65dEHSQHhRxPkKcYd1VrAWlxF9dNd/view?usp=sharing
thanks alot

I see two things in the log : time shifting, and maybe a bug in the main pool reconnection mechanism.

If you can turn off automatic time setup, and set it manually that would be good. When windows re-adjusts time BACK that can mess up a lot of things, miner thinks a day passed..

The second, main pool reconnection, i will test and fix if needed. It was implemented a long time ago, and a lot of stuff changed since, so maybe it's not working as it should.

thank you, let me try to turn off automatic time setup.

[dulama]

This is the error when I use Algorithm: Cryptonight V4 (R)

[2019-04-14 12:49:03] GPU0[BUS:1] result rejected for job[15] [low difficulty share]
[2019-04-14 12:49:33] Pool sent a new job, block height 416327 [ID: 5ac7b313-96fd-4601-94a0-9e51cecb4439]
[2019-04-14 12:49:44] Pool sent a new job, block height 416327 [ID: 5ac7b313-96fd-4601-94a0-9e51cecb4439]
[2019-04-14 12:49:44] GPU1[BUS:2] result rejected for job[17] [low difficulty share]

[MagicSmoker]

This is the error when I use Algorithm: Cryptonight V4 (R)

[2019-04-14 12:49:03] GPU0[BUS:1] result rejected for job[15] [low difficulty share]
[2019-04-14 12:49:33] Pool sent a new job, block height 416327 [ID: 5ac7b313-96fd-4601-94a0-9e51cecb4439]
[2019-04-14 12:49:44] Pool sent a new job, block height 416327 [ID: 5ac7b313-96fd-4601-94a0-9e51cecb4439]
[2019-04-14 12:49:44] GPU1[BUS:2] result rejected for job[17] [low difficulty share]

I'm getting something similar with 1.8.3 and 18.6.1 drivers on a mixed RX 560 / 570 rig. Will be going back to 1.8.1 here shortly if the "low difficulty share" errors persist.


One other bug I noticed is that the min_rig_speed parameter seems to only be looking at one of the GPU's hashrate, rather the sum total.

[doktor83]

This is the error when I use Algorithm: Cryptonight V4 (R)

[2019-04-14 12:49:03] GPU0[BUS:1] result rejected for job[15] [low difficulty share]
[2019-04-14 12:49:33] Pool sent a new job, block height 416327 [ID: 5ac7b313-96fd-4601-94a0-9e51cecb4439]
[2019-04-14 12:49:44] Pool sent a new job, block height 416327 [ID: 5ac7b313-96fd-4601-94a0-9e51cecb4439]
[2019-04-14 12:49:44] GPU1[BUS:2] result rejected for job[17] [low difficulty share]

I'm getting something similar with 1.8.3 and 18.6.1 drivers on a mixed RX 560 / 570 rig. Will be going back to 1.8.1 here shortly if the "low difficulty share" errors persist.


One other bug I noticed is that the min_rig_speed parameter seems to only be looking at one of the GPU's hashrate, rather the sum total.

Just clear the drivers with DDU from here and install 18.6.1
It must work. Also make sure you use normalv4 algo, because you can get 'low difficulty shares' if you use the wrong algorithm.

Also min_rig_speed checks the sum of all gpu threads, not 1 gpu.

edit:

tested for 27 minutes, works as expected. If it was looking at the hash of 1 gpu it would trigger a few times in these 27 minutes.

[Baikal miner]

Why i want this is error Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 1 (Thread 2)
Error while creating GPU threads.. Stopping miner process.
http://prntscr.com/nbutg3
http://prntscr.com/nbutn6

[doktor83]

Why i want this is error Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 1 (Thread 2)
Error while creating GPU threads.. Stopping miner process.

Because r9 380 is not ellesmere. Integrated gpu or driver is messing up there.

[ManDoneKTM]

Hello ! After i update it to 1 8 3 i have this issues . https://imgur.com/a/jwg9PeQ

[doktor83]

Hello ! After i update it to 1 8 3 i have this issues . https://imgur.com/a/jwg9PeQ

check the second tip on the first page here : https://bitcointalk.org/index.php?topic=3167363.msg32748623#msg32748623

[Sadopwnz]

I have 8 GPUs, but the 8th GPU crashes still mining after ~5-30 min with log:
https://c.radikal.ru/c42/1904/8b/c9e6fe0e2f72t.jpg
Switching GPUs, risers, stock settings did nothing. MB asus z370-p, 8xflashed vega56.
Any ideas?

[Baikal miner]

Why i want this is error Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 1 (Thread 2)
Error while creating GPU threads.. Stopping miner process.
http://prntscr.com/nbutg3
http://prntscr.com/nbutn6

Because r9 380 is not ellesmere. Integrated gpu or driver is messing up there.

i re-install driver not work

[Dubai-Industry]

nice relise

[Rabotaet]

Увaжaeмый дoктop83.

1)Чтoбы вaшa yтилитa SRB-Restarter paбoтaлa кoppeктнo нa windows 7  нeoбxoдимo oтключить в cиcтeмe oкoшкo oб aвapийнoм зaвepшeнии пpилoжeния. Бeз этoгo вaшa yтилитa дyмaeт, чтo пpoцecc SRB-miner eщe зaпyщeн и paбoтaeт, xoтя мaйнep yжe двaнo зaвиc и виcит cиcтeмнoe oкoшкo oб oшибкe в пpилoжeнии. Haвepнo этo дeлaeтcя тaк: Пycк-Bыпoлнить-> gpedit.msc-> Computer Settings -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> Turn off Windows Error Reporting.

2)Haчинaя c вepcии 1.8.2 мaйнep нa cтapтe пoкaзывaeт oчeнь низкиx xэшpeйт и пepeзaпycкaeтcя, т.к. ycтaнoвлeн пapaмeтp "минимaльный xэшpeйт". Кapты rx562. Oпытным пyтeм былo ycтaнoвлeнo, чтo либo нe иcпoльзoвaть этoт пapaмeтp вooбщe, либo ycтaнoвить cимвoличecкoe знaчeниe, cкaжeм 100.

[doktor83]

Увaжaeмый дoктop83.

1)Чтoбы вaшa yтилитa SRB-Restarter paбoтaлa кoppeктнo нa windows 7  нeoбxoдимo oтключить в cиcтeмe oкoшкo oб aвapийнoм зaвepшeнии пpилoжeния. Бeз этoгo вaшa yтилитa дyмaeт, чтo пpoцecc SRB-miner eщe зaпyщeн и paбoтaeт, xoтя мaйнep yжe двaнo зaвиc и виcит cиcтeмнoe oкoшкo oб oшибкe в пpилoжeнии. Haвepнo этo дeлaeтcя тaк: Пycк-Bыпoлнить-> gpedit.msc-> Computer Settings -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> Turn off Windows Error Reporting.

2)Haчинaя c вepcии 1.8.2 мaйнep нa cтapтe пoкaзывaeт oчeнь низкиx xэшpeйт и пepeзaпycкaeтcя, т.к. ycтaнoвлeн пapaмeтp "минимaльный xэшpeйт". Кapты rx562. Oпытным пyтeм былo ycтaнoвлeнo, чтo либo нe иcпoльзoвaть этoт пapaмeтp вooбщe, либo ycтaнoвить cимвoличecкoe знaчeниe, cкaжeм 100.

I tried to translate with google translate but i still don't understand what you want to say 

[Rabotaet]

1) When the miner freezes, the system error window appears.

But the SRB-Miner process is still in computer memory.

The SRB-Restarter utility thinks that the miner is working. But the miner is frozen.

Perhaps this problem can be solved on Windows 7.

It is necessary to disable the output of system notifications.

 gpedit.msc-> Computer Settings -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> Turn off Windows Error Reportin

2)
RX562, miner 1.8.1 - OK
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"retry_time" : 2,
"persistent_memory" : false,
"min_rig_speed" : 2100,
"min_rig_speed_duration" : 60,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 1, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 2, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 3, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 4, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8}
]
}

RX562, miner 1.8.2 - 1.8.3 - not OK
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"retry_time" : 2,
"persistent_memory" : false,
"min_rig_speed" : 2100,  <<<<<<<<<==============   only works if set to 100. otherwise restart miner!!!!!!!
"min_rig_speed_duration" : 60,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 1, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 2, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 3, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 4, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8}
]
}