Using latest version, thank you for stellitev4 support. HashRate is also very nice, one thing I get alot of Pool rejected result 0x0001704C (low difficulty share) Other miners do not show me this message, what it mean? Anything to worry about?
it means you are using wrong algorithm. What are you trying to mine? Also where do I add the "Kernel" can you give example as I added: /* Intensity 0-> auto intensity, or value from 1-300 */ "intensity" : 0, "kernel" : 4, Tried each Kernel and made no difference in hash, so thinking put it in wrong place? Thanks man Not there, you put it in gpu_conf : "gpu_conf" : [ { "id" : 0, "intensity" : 80, "worksize" : 8, "threads" : 1, "kernel" : 1}, { "id" : 1, "intensity" : 40, "worksize" : 8, "threads" : 2, "kernel" : 2}, { "id" : 3, "intensity" : 30, "worksize" : 8, "threads" : 2, "kernel" : 3}, { "id" : 4, "intensity" : 90, "worksize" : 8, "threads" : 1, "kernel" : 4} ]What GPU's do you have?
|
|
|
Using latest version, thank you for stellitev4 support. HashRate is also very nice, one thing I get alot of Pool rejected result 0x0001704C (low difficulty share) Other miners do not show me this message, what it mean? Anything to worry about?
it means you are using wrong algorithm. What are you trying to mine? StelliteV4, I set it to this and stellite pool? Maybe pool no ready yet? nooo, they will fork next week, probably friday So it's not that algo , yet.
|
|
|
Using latest version, thank you for stellitev4 support. HashRate is also very nice, one thing I get alot of Pool rejected result 0x0001704C (low difficulty share) Other miners do not show me this message, what it mean? Anything to worry about?
it means you are using wrong algorithm. What are you trying to mine?
|
|
|
I've downloaded the V1.5.7 and connected it to etn.nanopool, algo monero7, it seems that it does not give share, only recieve job from pool, can someone check it ? i've tried on cn-heavy algo and it's working.
diff at nanopool is 240009, also the fork was activated few blocks ago, and its normalv7 here, not monero7.Looks like i screwed something when implementing Stellite, please don't yet download 1.5.7, i will fix it ASAP an re-upload.All fixed
|
|
|
V1.5.7- Added support for StelliteV4 algo - Added option "worker" in pool config - pool must support this, also CMD parameter --cworker - Fixed average hashrate display (1,5,30 min) when there are disabled GPU's + Had to push this quick update because of the upcoming Stellite fork, so you guys can get ready on time + "worker" option won't work on every pool, because pool must support 'rigid' parameter It would look something like this : { "pools" : [ {"pool" : "xmr-eu1.nanopool.org:14444", "wallet" : "your-wallet", "password" : "x", "worker" : "my-rig-name"} ] }
|
|
|
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? What about compiling kernels every launching? possibly something to do with read/write permissions for the miner, cause video driver has nothing to do with this, and 1804 v is working fine as someone wrote. And yeah, if 18.5.1 recognises RX580 as R9 then its a really f**ked up driver, something really buggy there. Yes claymore shows ok probably sees "Ellesmere XT" ah ok that is 480/580 lol
|
|
|
Hey Doktor
I was using the miner with adrenalin 17.x.1 version which month i don't remember exactly and ADL wasn't working. I upgraded the driver with adrenalin 18.5.1 and ADL problem is solved. Maybe you can add this as known issues. Keep up with good work. Regards.
i think you can use it even on 17.x drivers since i added support for Overdrive5. But i did not test this lol I did not tried that one too I am using OverdriveNtool btw. that's ok , its a great tool to set your clocks and undervolt. Version of overdrive can be set in gpu_conf for every card separately : "adl_type" : 1-OverdriveN 2-Overdrive5 "gpu_conf" : [ { "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2, "adl_type" : 1}, { "id" : 1, "intensity" : 0, "worksize" : 8, "threads" : 2, "adl_type" : 2} ]
|
|
|
When I use the function enable and disable vega card, I get the following error: cl_out_of_host_memory when creating clCreateCommandQueue for DeviceID 0 (Thread 0) , does somebody has any idea?
Make sure you have this in start.bat at top : setx GPU_FORCE_64BIT_PTR 1 setx GPU_MAX_HEAP_SIZE 100 setx GPU_MAX_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_MAX_SINGLE_ALLOC_PERCENT 100 Also try other video driver, for ex. 18.3.4
|
|
|
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
Anyone? "restart_devices_on_startup" : IF TRUE IT WILL USE DEVCON TO DISABLE/ENABLE EVERY VEGA GPU IN YOUR MACHINE BEFORE MINING STARTS "restart_devices_on_startup_script" : FILENAME, THIS SCRIPT RUNS AFTER VEGA GPU ENABLE/DISABLE PROCESS, GOOD FOR SETTING UP OVERCLOCKING so first you have to set "restart_devices_on_startup" : true, then "restart_devices_on_startup_script" : Run_OverdriveNTool.bat, where Run_OverdriveNTool.bat is in miner dir. You can disable/enable every vega at once, no option to do this card by card. Thank you Sir! Love your Miner! learned about it from Geek Mark, switched all my rigs to it! also getting my friends to switch too! thank you for the assistance an continued development of the software! Thanks Unfortunately i dont have a Vega card, but lot of folks here do, so im sure if you have any vega specific questions, they will help you!
|
|
|
Hey Doktor
I was using the miner with adrenalin 17.x.1 version which month i don't remember exactly and ADL wasn't working. I upgraded the driver with adrenalin 18.5.1 and ADL problem is solved. Maybe you can add this as known issues. Keep up with good work. Regards.
i think you can use it even on 17.x drivers since i added support for Overdrive5. But i did not test this lol
|
|
|
I would like more freedom for SRBMiner user in watchdog's events or pools'events by bat files. Please allow users to take actions on watchdog's events from bat files themselves.
"reboot_script" parameter is what you are looking for. Readme.txt or first page of this thread.
|
|
|
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
Anyone? "restart_devices_on_startup" : IF TRUE IT WILL USE DEVCON TO DISABLE/ENABLE EVERY VEGA GPU IN YOUR MACHINE BEFORE MINING STARTS "restart_devices_on_startup_script" : FILENAME, THIS SCRIPT RUNS AFTER VEGA GPU ENABLE/DISABLE PROCESS, GOOD FOR SETTING UP OVERCLOCKING so first you have to set "restart_devices_on_startup" : true, then "restart_devices_on_startup_script" : Run_OverdriveNTool.bat, where Run_OverdriveNTool.bat is in miner dir. You can disable/enable every vega at once, no option to do this card by card.
|
|
|
@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/1001901290065100800t.me/Stellite_EN/40349 Doktor, you will find a lot more detail in the XTL discord here: https://discord.gg/S7qKV6EI can put you in touch with the team directly if needed. Thanks, i will look into it.
|
|
|
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.
|
|
|
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?
|
|
|
@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?
|
|
|
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"} ] }
|
|
|
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
|
|
|
Will SRB Miner work for ETN after the fork? They have switched to CryptonightV7 apparently sure, use normalv7
|
|
|
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.
|
|
|
|