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

[heavyarms1912]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

[1713584749]

1713584749

[1713584749]

1713584749

[1713584749]

1713584749

[1713584749]

1713584749

[1713584749]

1713584749

[eduardooaz]

From my experience Micron kinda shit for cryptonight, my hynix at  1150/2100 can do 1050hs but i got 1 micron at 1150/2200 com PB timmings and doing around 940h/s. and sometimes  it starts at 1020h/s but go down to 940h/s, its a shame atleast at heavy the values are not stable.
No 1 wanna share some good timmings for Micron for cryptonight? PBE timmings not giving good values

[eduardooaz]

Cryptonighy-Heavy.  1200+ H/s on RX 570 8gb (Micron).  Also, serving as primary display card so couldn't push them too far.  Makes my Vega 56 look bad hashing at 1400 H/s  

https://i.imgur.com/D6pGkAF.jpg

have left them hashing at 1130 H/s 1250/2200 clocks @ 906mV.

Are you using PBE timmings? me at 1150/2200 clocks i got 930h/S

[doktor83]

V1.5.5
- No need for all that stuff in start.bat anymore, because watchdog can now restart the whole miner process without it

Hi and thanks for the updates.

Is it possible to configure SRBMiner to simply terminate in case it run into any crashes/issues - so it doesn't restart itself?

When using SRMMiner from applications like Awesome Miner, it's preferred to let Awesome Miner detect and restart any crashed/stopped mining processes.

Thanks!

"reboot_script" : FILENAME, TURN OFF BUILT IN WATCHDOG AND INSTEAD RUN A USER DEFINED .BAT FILE ON GPU FAILURE (included windows restart .bat)

Example:

tskill SRBMiner-CN

[doktor83]

V1.5.5
- No need for all that stuff in start.bat anymore, because watchdog can now restart the whole miner process without it
- Fixed kernels 3 & 4 for heavy algo
- Fixed OCL binary caching for Vega cards
- Added last job received info in stats and API
- Added 'job_timeout' parameter to pools config, it reconnects to pool if no job received for 'job_timeout' time (in seconds), default is 5 min
- Pool reload now checks if current pool is first in reloaded pools list, if not, it switches to first pool


+ Finally, start.bat has been cleaned, as of now miner (watchdog) can restart itself. (woohoo)
Now you can run multi instances of miner if you need to, without renaming hacks etc.. Every miner instance can restart itself.

+ Kernels 3 & 4 couldn't mine heavy algo, as no result was ever found. Fixed.

+ New parameter that goes in pools config is 'job_timeout'. If not set default is 300 sec (5 min). This can be helpful if for some reason the pool stops sending us new jobs, after the defined time the miner automatically reconnects to the pool.

+ Pressing 'r' reloads pools (defined through CMD line + pools list), and now if it finds the currently running pool on the first place in the new list, it just sets the pointer to it, and pressing 'p' to change pool will jump to the second pool from the list.
If the currently running pool is not same as the one on the first place on this new list, miner automatically connects to that new first pool.

Hey man, just downloaded this release for the first time trying the miner.
I'm using 6 RX580s overclocked correctly (no noob bios flashing shit)
I been using Claymore's CryptoNote AMD GPU Miner v11.3 with a total hash on Stellite coin of 5120
Now with your miner I'm getting 4841 only, much less hashrate. Intensity is 0

Double Thread Enabled Gives me 5100, this is closer to Claymore

Is there anything that can be done to try and tweak this for higher hash for me to switch to your miner.
Claymore one is currently dev free now.

Yes, 1st page and readme has a lot of info about manual gpu tweaking.

[doktor83]

- Fixed kernels 3 & 4 for heavy algo

+ Kernels 3 & 4 couldn't mine heavy algo, as no result was ever found. Fixed.

Sorry can you clarify that bit? What exactly are kernels 3 & 4? You mean GPUs 3 and 4 would not have found any share prior to this update?

1st page and readme:

Some additional parameters you can use in gpu_conf:
"kernel" : 0-4 , IF 0, MINER WILL SELECT MOST SUITABLE KERNEL, OTHERS ARE : 1-FOR GCN CARDS, 2-FOR PRE-GCN CARDS, 3-FOR PRE-GCN EXPERIMENTAL 1, 4-FOR PRE-GCN EXPERIMENTAL 2

[doktor83]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

[eduardooaz]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

How many memory you recomend for 4 rx 580, being 3 8gb version dual threath.

[doktor83]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

How many memory you recomend for 4 rx 580, being 3 8gb version dual threath.

i think 32gb vmem should be enough

[heavyarms1912]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

Cause this is weird behavior I observed today.  Same I/W/T settings 59/8/1 on 4gb RX 570 which was working fine.  Restarting the miner it gave the error related to below error message,


So yup is there a specific memory requirement during the compilation process?  Trying to debug why this happened.
Note:  Rebooting system, the miner will work with same config.

[doktor83]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

Cause this is weird behavior I observed today.  Same I/W/T settings 59/8/1 on 4gb RX 570 which was working fine.  Restarting the miner it gave the error related to below error message,

sometimes drivers or windows behaves strange, i bet if you delete the .srb files and reboot it will all be good.

[heavyarms1912]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

Cause this is weird behavior I observed today.  Same I/W/T settings 59/8/1 on 4gb RX 570 which was working fine.  Restarting the miner it gave the error related to below error message,

sometimes drivers or windows behaves strange, i bet if you delete the .srb files and reboot it will all be good.

Nope deleting the .srb file didn't solve it.  Rebooting did.  it seems more like a driver/miner didn't clean up memory properly?

[doktor83]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

Cause this is weird behavior I observed today.  Same I/W/T settings 59/8/1 on 4gb RX 570 which was working fine.  Restarting the miner it gave the error related to below error message,

sometimes drivers or windows behaves strange, i bet if you delete the .srb files and reboot it will all be good.

Nope deleting the .srb file didn't solve it.  Rebooting did.  it seems more like a driver/miner didn't clean up memory properly?

probably. these kind of 'errors' happen a lot after driver crash/recovery.

[heavyarms1912]

probably. these kind of 'errors' happen a lot after driver crash/recovery.

Okay so debugging further doesn't seem to be a problem with miner or drivers.  The problem occurs with Dtsm AutoRun script (one Nvidia card on equihash) for some weird reason hogs up resources, I guess.  Not going to bother debugging further into the script itself.

[eduardooaz]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

How many memory you recomend for 4 rx 580, being 3 8gb version dual threath.

i think 32gb vmem should be enough

Exactly what i am using and normaly doesnt pass the 70% but sometimes the pc sometimes from nowere stats lagging and kill my h/s.

[goodb]

Guys how to add static difficulty for pool ? is that --diff  option ?

[montas101]

This miner have  some bug on it..........on my rig it mine for some one for 3h and never come back to my pool.
For me this miner is over.

[lebuawu2]

Guys how to add static difficulty for pool ? is that --diff  option ?

static diff format should be from pool, so which pool is it?

[wudafuxup]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

Cause this is weird behavior I observed today.  Same I/W/T settings 59/8/1 on 4gb RX 570 which was working fine.  Restarting the miner it gave the error related to below error message,

sometimes drivers or windows behaves strange, i bet if you delete the .srb files and reboot it will all be good.

Nope deleting the .srb file didn't solve it.  Rebooting did.  it seems more like a driver/miner didn't clean up memory properly?

probably. these kind of 'errors' happen a lot after driver crash/recovery.

Invalid buffer size usually means you're trying to use an intesity that is too high for the card. Happens often on CN-Heavy coins. That's probably the case since you're using 4GB cards.

[heavyarms1912]

@doktor83.  Is there a virtual memory requirement or free ssd/hdd space requirement when compiling the kernels and copying over the device?

Virtual mem is same as for every other Cryptonight miner(the more, better ) , kernel compile happens on GPU, after that it's written to the hdd, miner directory, and it takes up approx 2.1-2.3mb / binary.
Or what was your question ?

Cause this is weird behavior I observed today.  Same I/W/T settings 59/8/1 on 4gb RX 570 which was working fine.  Restarting the miner it gave the error related to below error message,

sometimes drivers or windows behaves strange, i bet if you delete the .srb files and reboot it will all be good.

Nope deleting the .srb file didn't solve it.  Rebooting did.  it seems more like a driver/miner didn't clean up memory properly?

probably. these kind of 'errors' happen a lot after driver crash/recovery.

Invalid buffer size usually means you're trying to use an intesity that is too high for the card. Happens often on CN-Heavy coins. That's probably the case since you're using 4GB cards.

Is that so?  Check my post again.  I mentioned it was working and didn't work later during relaunch.
Too lazy to take another screenshot but here are 6 x 4gb card doing the same settings on CNH.  Anyways,  I got the RX570's running at 59 intensity too.
https://i.imgur.com/lavRfGo.jpg