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

[qwep1]

Will SRB Miner work for ETN after the fork? They have switched to CryptonightV7 apparently

sure, use normalv7

what setting for vega 56

[livada]

DOC. See this.
First. Block GPU BUS 7 but srb  say gpu3=0
Second restart miner BLOCK and stay.
Stay 2 hour - Computer work fine. but miner stop and block.
After this i close miner and komp  STUTH DOWN and reset.

This is not first time.

this is it.  Tu je zbloko i stoji tako dok ja ne skuzim da je zbloko i ne ugasim. Ktome kad to napravi nema nikakve log doatoteke - ne zapise prakticki nista. ostane zapis neki star par sati i nema nikakvog erora.. Ovo sam se vratio na stariju verziju al i u 1.5.5.1 je sve isto bilo

this is not the latest version. Please report bugs only for the latest version.

Ovo sto prijavljujes za los prikaz BUS id jer reseno u novijoj verziji, pise na prvoj strani.



Takodje smanjite ljudi intenzitet na kartama koje vam blokiraju, pa nece ni doci do pucanja drajvera / pada hasha na 0.
Ili ste jako nabrijali tj overklokovali karte, ili vozite na previsokom intenzitetu. Da iste su sve karte, ali ne moze cak ni svaka ista karta isti intenzitet.

Ok za intenzititet- ok za verziju ui krivi reoorder. Problem je sto miner prepozna 0 hash ode u restart al onda zbloka i nista se ne desava. Bolje mi je da zbloka cijeli komp i ode u restart i pokrene se ispocetka nego  ovako. ovako ne radi nista. i to je tako i u 15.5.1 verziji. Znaci komp se nije zabloko nego je jednostavno miner ostao na toj akrtici i nije radio nista a morao je radit bar nesto- otic u restart svega ili nesto. Bolje mi je da je ostala ugasena kartica nego ovo sto radi . starije verzije su uredno radile restart cijelog stroja kad je nesto zblokalo a evo sad sve staeni to je koma.

[clancy182]

hello @
what intensity do u use with vega 56 stock bios for etn mining ?

[livada]

hello @
what intensity do u use with vega 56 stock bios for etn mining ?

intensity for vega 56 with 64 bios

v7 = intensyiti 120
heavy =  56
lite = 235
lite v7 = 235
ipbc = 234/239
aeon = 235
arto = 120
b2n = 120
aloy = 120

[doktor83]

DOC. See this.
First. Block GPU BUS 7 but srb  say gpu3=0
Second restart miner BLOCK and stay.
Stay 2 hour - Computer work fine. but miner stop and block.
After this i close miner and komp  STUTH DOWN and reset.

This is not first time.

this is it.  Tu je zbloko i stoji tako dok ja ne skuzim da je zbloko i ne ugasim. Ktome kad to napravi nema nikakve log doatoteke - ne zapise prakticki nista. ostane zapis neki star par sati i nema nikakvog erora.. Ovo sam se vratio na stariju verziju al i u 1.5.5.1 je sve isto bilo

this is not the latest version. Please report bugs only for the latest version.

Ovo sto prijavljujes za los prikaz BUS id jer reseno u novijoj verziji, pise na prvoj strani.



Takodje smanjite ljudi intenzitet na kartama koje vam blokiraju, pa nece ni doci do pucanja drajvera / pada hasha na 0.
Ili ste jako nabrijali tj overklokovali karte, ili vozite na previsokom intenzitetu. Da iste su sve karte, ali ne moze cak ni svaka ista karta isti intenzitet.

Ok za intenzititet- ok za verziju ui krivi reoorder. Problem je sto miner prepozna 0 hash ode u restart al onda zbloka i nista se ne desava. Bolje mi je da zbloka cijeli komp i ode u restart i pokrene se ispocetka nego  ovako. ovako ne radi nista. i to je tako i u 15.5.1 verziji. Znaci komp se nije zabloko nego je jednostavno miner ostao na toj akrtici i nije radio nista a morao je radit bar nesto- otic u restart svega ili nesto. Bolje mi je da je ostala ugasena kartica nego ovo sto radi . starije verzije su uredno radile restart cijelog stroja kad je nesto zblokalo a evo sad sve staeni to je koma.

I za ovo pravim resenje bice u sledecoj verziji, bez brige 

[doktor83]

Electronero mining :

Example :

start.bat :

SRBMiner-CN.exe --config config-electronero.txt --pools pools-electronero.txt


config-electronero.txt

{
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"target_temperature" : 60,
"shutdown_temperature" : 90,
"api_enabled" : true
}


pools-electronero.txt

{
"pools" :
[
   {"pool" : "etnx.ingest.cryptoknight.cc:5102", "wallet" : "YOUR-WALLET", "password" : "x"}
]
}

[wgestickley]

@Doktor:

Stellite will Hardfork next Week. Can u please implement th new Code so that it is also Mine able?

THX

[Bry Guy]

@Doktor:

Stellite will Hardfork next Week. Can u please implement th new Code so that it is also Mine able?

THX

Hayzam from XTL said that they will be reaching out. I too hope that @Doktor83 is willing and able to implement their upcoming custom algo. Please keep up the good work, Dok!

[doktor83]

@Doktor:

Stellite will Hardfork next Week. Can u please implement th new Code so that it is also Mine able?

THX

Hayzam from XTL said that they will be reaching out. I too hope that @Doktor83 is willing and able to implement their upcoming custom algo. Please keep up the good work, Dok!

wtf they fork again? where can i get some info about this?

[wgestickley]

@Doktor:

Stellite will Hardfork next Week. Can u please implement th new Code so that it is also Mine able?

THX

Hayzam from XTL said that they will be reaching out. I too hope that @Doktor83 is willing and able to implement their upcoming custom algo. Please keep up the good work, Dok!

wtf they fork again? where can i get some info about this?

You can check here:
https://twitter.com/Stellite_QA/status/1001901290065100800
t.me/Stellite_EN/40349

[clancy182]

hello @
what intensity do u use with vega 56 stock bios for etn mining ?

intensity for vega 56 with 64 bios

v7 = intensyiti 120
heavy =  56
lite = 235
lite v7 = 235
ipbc = 234/239
aeon = 235
arto = 120
b2n = 120
aloy = 120

thanks !

[Bry Guy]

@Doktor:

Stellite will Hardfork next Week. Can u please implement th new Code so that it is also Mine able?

THX

Hayzam from XTL said that they will be reaching out. I too hope that @Doktor83 is willing and able to implement their upcoming custom algo. Please keep up the good work, Dok!

wtf they fork again? where can i get some info about this?

You can check here:
https://twitter.com/Stellite_QA/status/1001901290065100800
t.me/Stellite_EN/40349

Doktor, you will find a lot more detail in the XTL discord here:
https://discord.gg/S7qKV6E

I can put you in touch with the team directly if needed.

[UnclWish]

On AMD 18.5.1 driver on 1803 Windows 10 x64 my RX 580 recognized by SRB miner as R9 200 series [Ellesmere] and every launch build new kernels... It's abnormal. I think, you must update miner to support new drivers, doctor...
By the word, all Claymore's miners detects my cards right on 18.5.1...

And I still can't understand, why every lounch of SRB miner speed is different from each other... To reach max speed it's need to launch SRB several times without any changes in config or something else...
Cards is RX 580 8Gb.

[heavyarms1912]

On AMD 18.5.1 driver on 1803 Windows 10 x64 my RX 580 recognized by SRB miner as R9 200 series [Ellesmere] and every launch build new kernels... It's abnormal. I think, you must update miner to support new drivers, doctor...
By the word, all Claymore's miners detects my cards right on 18.5.1...

And I still can't understand, why every lounch of SRB miner speed is different from each other... To reach max speed it's need to launch SRB several times without any changes in config or something else...
Cards is RX 580 8Gb.

Are you mining Heavy?  If that's the case then the behavior is existent on multiple cards.

[UnclWish]

On AMD 18.5.1 driver on 1803 Windows 10 x64 my RX 580 recognized by SRB miner as R9 200 series [Ellesmere] and every launch build new kernels... It's abnormal. I think, you must update miner to support new drivers, doctor...
By the word, all Claymore's miners detects my cards right on 18.5.1...

And I still can't understand, why every lounch of SRB miner speed is different from each other... To reach max speed it's need to launch SRB several times without any changes in config or something else...
Cards is RX 580 8Gb.

Are you mining Heavy?  If that's the case then the behavior is existent on multiple cards.

Yes, heavy. But case is not in cards. Case is in miner.

[heavyarms1912]

On AMD 18.5.1 driver on 1803 Windows 10 x64 my RX 580 recognized by SRB miner as R9 200 series [Ellesmere] and every launch build new kernels... It's abnormal. I think, you must update miner to support new drivers, doctor...
By the word, all Claymore's miners detects my cards right on 18.5.1...

And I still can't understand, why every lounch of SRB miner speed is different from each other... To reach max speed it's need to launch SRB several times without any changes in config or something else...
Cards is RX 580 8Gb.

Are you mining Heavy?  If that's the case then the behavior is existent on multiple cards.

Yes, heavy. But case is not in cars. Case is in miner.

I get similar behavior on xmr-stak on Heavy. 

[MaxHa$h]

how do i properly use this command? "restart_devices_on_startup_script" :

i inserted in the config.txt like this

"restart_devices_on_startup_script" : Run_OverdriveNTool.bat,

miner goes to start then kills itself.

also anyway to control enable/ disable on which Vega's. Not sure if its the card or the riser, but one of my Vega's cant handle the disable/enable with out crashing the whole OS.

TIA

[doktor83]

On AMD 18.5.1 driver on 1803 Windows 10 x64 my RX 580 recognized by SRB miner as R9 200 series [Ellesmere] and every launch build new kernels... It's abnormal. I think, you must update miner to support new drivers, doctor...
By the word, all Claymore's miners detects my cards right on 18.5.1...

And I still can't understand, why every lounch of SRB miner speed is different from each other... To reach max speed it's need to launch SRB several times without any changes in config or something else...
Cards is RX 580 8Gb.

Are you mining Heavy?  If that's the case then the behavior is existent on multiple cards.

Yes, heavy. But case is not in cars. Case is in miner.

I get similar behavior on xmr-stak on Heavy.  

xmr stak, gateless gate also have this 'problem'.
Maybe this means the 'problem' is in the algo, not in miners?

[istr]

Hi Doc!

A strange behavior!
I've noticed that a long time ago but now I've decided to tell you.
It may help you debugging the code.

I've automated startup procedure for the miner whenever windows starts.
Let's take for example one of my rigs with 6 cards.
Windows boots and after a while miner starts.
After some time of stabilization watching memory usage in task manager I see it stable at  ~286 - 290 M.
If I kill the miner process and start it again giving it time to stabilize it stays at  ~560 - 570 M.
That's why I was saying all the time about "memory management".
I don't know but this is the behavior.
It may help.

Greetings!

ps:  in heavy algo.

well if you would follow this thread regulary you would know that this is very well known, and can be fixed by just fireing up GPU-Z

You know something Doc, you didn't understand me.
I'm not talking about the known hashrate drop problem which I first introduced to the community the temporary solution with GPU-Z
but about different seized memory (MB) into 2 different runs of miner which of course may related.
No hard feelings!

[doktor83]

Hi Doc!

A strange behavior!
I've noticed that a long time ago but now I've decided to tell you.
It may help you debugging the code.

I've automated startup procedure for the miner whenever windows starts.
Let's take for example one of my rigs with 6 cards.
Windows boots and after a while miner starts.
After some time of stabilization watching memory usage in task manager I see it stable at  ~286 - 290 M.
If I kill the miner process and start it again giving it time to stabilize it stays at  ~560 - 570 M.
That's why I was saying all the time about "memory management".
I don't know but this is the behavior.
It may help.

Greetings!

ps:  in heavy algo.

well if you would follow this thread regulary you would know that this is very well known, and can be fixed by just fireing up GPU-Z

You know something Doc, you didn't understand me.
I'm not talking about the known hashrate drop problem which I first introduced to the community the temporary solution with GPU-Z
but about different seized memory (MB) into 2 different runs of miner which of course may related.
No hard feelings!

No hard feelings, we did not understand eachother.
Also i don't take notes who said/wrote what and when , so i couldn't know you found this nice 'fix'.

Is this behaviour you are referring to happening every time (like first run always less mem used, second run always ok) ?
I see other miners have this 'problem' too on heavy.