|
1501
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 10, 2018, 08:40:29 AM
|
I did not know how this works, I thought it was detected automatically. About the time, I think it depends on how often the pool sets difficulty too high. This option could be very useful for pools with badly configured vardiff to avoid loosing shares. So, for me the shortest the best but every one is different  Maybe a command to choose between 1 & 60 secs.  No worries, i managed to make it to be instant, so it will be a next version update. Also i changed the reconnecting procedure, don't know if it will help you in the miner closing after 4th diff reconnect. (i can't reproduce this) |
|
|
|
|
1502
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 10, 2018, 06:12:56 AM
|
I keep getting this now on 1.5.9 every now and then. Nothing changed in settings.
shut_down_miner exception: Resource deadlock avoided
I also getting this, suddenly all GPU hashing speed 0 h/s. [2018-06-10 00:41:42] pool_ping: Sent keepalive message to pool [2018-06-10 00:41:42] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}} [2018-06-10 00:41:42] json_receive: Pool responded with KEEPALIVED [2018-06-10 00:42:07] watchdog: GPU0 [BUS: 1] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU1 [BUS: 2] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU2 [BUS: 3] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU3 [BUS: 4] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU4 [BUS: 5] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU6 [BUS: 9] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU7 [BUS: 10] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU8 [BUS: 11] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU9 [BUS: 12] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU10 [BUS: 13] hashing speed is 0 H/S [2018-06-10 00:42:07] watchdog: GPU11 [BUS: 15] hashing speed is 0 H/S [2018-06-10 00:42:33] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0707d1a3f0d805256279b460556b7c15ee3cd01fcdba90cfdadfbdcc0654c667f5a4ae0a9a78530 00000001ab26cc8554f6b2671add6a9c76cbaaa20eb9f31179f7e0d5c9d969a8fd7194303","job_id":"276673124018431","target":"cf8b0000"}} [2018-06-10 00:42:38] pool_ping: Sent keepalive message to pool [2018-06-10 00:42:38] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}} [2018-06-10 00:42:38] json_receive: Pool responded with KEEPALIVED [2018-06-10 00:42:56] shut_down_miner exception: Resource deadlock avoided [2018-06-10 00:42:56] Stopping miner process 0 hash and shutdown exception are not related. this is just an information that on shutdown process resource clean up avoided a deadlock  |
|
|
|
|
1504
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 10, 2018, 06:06:48 AM
|
V1.6.0
+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that
Reproduced [2018-06-10 02:38:44] Heating up system, please wait... [2018-06-10 02:38:28] Miner version: 1.6.0 [2018-06-10 02:38:43] AMD Platform ID: 1 [2018-06-10 02:38:43] AMD platform FOUND [2018-06-10 02:38:43] Found 13 AMD devices [2018-06-10 02:38:43] GPU0: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.0][W: 12][T: 2][K: 1][BUS: 1] [2018-06-10 02:38:43] GPU1: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 4] [2018-06-10 02:38:43] GPU2: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 6] [2018-06-10 02:38:43] GPU3: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 8] [2018-06-10 02:38:43] GPU4: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 9] [2018-06-10 02:38:43] GPU5: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 10] [2018-06-10 02:38:43] GPU6: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 11] [2018-06-10 02:38:43] GPU7: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 12] [2018-06-10 02:38:43] GPU8: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 13] [2018-06-10 02:38:43] GPU9: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 14] [2018-06-10 02:38:43] GPU10: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.0][W: 12][T: 2][K: 1][BUS: 15] [2018-06-10 02:38:43] GPU11: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 16] [2018-06-10 02:38:43] GPU12: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 17] [2018-06-10 02:38:43] ADL is enabled [2018-06-10 02:38:43] CryptonightV7 mode enabled [2018-06-10 02:38:44] DevFee pools loaded [2018-06-10 02:38:44] DevFee pool SET [2018-06-10 02:38:44] DevFee address SET [2018-06-10 02:38:44] Starting init of mining threads ok, now i know its not the new devfee method that is problematic. But i would suggest to try now a previous version that you know was working good. Nothing was changed in the new version in the GPU's initialisation process (this is where it hangs), so my guess is something at your side is causing this. |
|
|
|
|
1505
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 09, 2018, 06:32:55 PM
|
V1.6.0- Added support for Haven new algo after fork (block 89200) - Added support for Masari new algo (fast) after fork (block 204000) - Job timeout default is now 20 minutes - More logging on miner startup - Added option 'persistent_memory' in gpu_conf + 2 new algos added : 'haven' and 'fast' So after the fork you can use them like : "cryptonight_type" : "fast"
"cryptonight_type" : "haven"+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that + 'persistent_memory' parameter added to gpu_conf, basically what it does is tries to allocate some memory that is normally not available to the GPU. It can increase hashrate in some ocassions, by finding the right intensity and threads setup, but also it can make the gpu crash, so it's up to you to experiment I am still looking for the cause of random miner crashes (mostly on new 'great' win 1803 update), also for the abnormality that causes higher hashrate on after X runs. Hi Doc! as I told you before, you have to take a good look at memory usage in task manager for the first run after reboot and all the next ones. There is something strange there! Behaviour is different. PS. This doesn't happening in other miners. did you test this on one card, a rig, or multiple rigs? All behave same? We are talking about memory usage for the miner, not the gpu (as you say task manager). On start miner 'eats' more memory, after that it slowly decreases over time. |
|
|
|
|
1506
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 09, 2018, 04:24:20 PM
|
V1.6.0
- Added support for Haven new algo after fork (block 89200)
- Added support for Masari new algo (fast) after fork (block 204000)
- Job timeout default is now 20 minutes
- More logging on miner startup
- Added option 'persistent_memory' in gpu_conf
Hey Dok, thanks for the update. I just started playing with persistent_memory. I know that your notes in CAPS after each option shown in the ReadMe are meant to be purely informational, but you may want to change the TRUE OR FALSE to lower case or use it in an example config to limit potential confusion, since the parser will throw an error if true/false is in CAPS when loading. Keep up the great work! yeah i wrote all in caps to draw attention When i get some time i will change it here and in the docs too. Do you have any success with per.mem on ? Using it should allow to go for a bigger intensity setting, on my test card (580 8g) algo normalv7, the best setting was i:54 / w:8 / t:2 i got ~926hs , now i can go to i:60 without problems, and have ~933-936hs edit: i:63 ~940hs  |
|
|
|
|
1507
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 09, 2018, 02:11:19 PM
|
dok,
I have an interesting problem. Using v1.6.0, with 5 rx470-8gb, stellite4 algo: All 5 GPUs initialize and are identified correctly on your miner, then after pool connection, display shows only FOUR GPUs, but the first one, GPU0, has DOUBLE the output of all others, I tried restarting, but with same output. Now this isn't a hashrate problem at the pool, just on the miner display. I think that the GPU bus identification is wrong on one of the cards by the miner software.
are you also on win 10 v1803 and some 18.5.2 or newer drivers? Win 7-64, blockchain drivers (Aug), and yes the first and last GPU are both being identified as bus 7 could you turn on logger and send it to me? |
|
|
|
|
1508
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 09, 2018, 02:05:51 PM
|
dok,
I have an interesting problem. Using v1.6.0, with 5 rx470-8gb, stellite4 algo: All 5 GPUs initialize and are identified correctly on your miner, then after pool connection, display shows only FOUR GPUs, but the first one, GPU0, has DOUBLE the output of all others, I tried restarting, but with same output. Now this isn't a hashrate problem at the pool, just on the miner display. I think that the GPU bus identification is wrong on one of the cards by the miner software.
are you also on win 10 v1803 and some 18.5.2 or newer drivers? |
|
|
|
|
1509
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 09, 2018, 01:17:32 PM
|
I think I can confirm...
After the difficulty monitor is executed for 4th time the program closes itself
[2018-06-09 15:01:33] Connection to pool lost. Reconnecting in 10 seconds.
And the program is closed.
i will check it out. Also it's not triggerring momentally when the set difficulty is reached. Check is made every 45 seconds. No point setting it for ex 1 sec because it just eats up cpu resources, and i think its not THAT important to disconnect momentally. But correct me if i am wrong. |
|
|
|
|
1510
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 09, 2018, 08:41:24 AM
|
+ 'persistent_memory' parameter added to gpu_conf, basically what it does is tries to allocate some memory that is normally not available to the GPU. It can increase hashrate in some ocassions, by finding the right intensity and threads setup, but also it can make the gpu crash, so it's up to you to experiment thanks for update is this correct usage? { "id" : 0, "intensity" : 112, "worksize" : 16, "threads" : 2, "persistent_memory" : true}, didn't crash, but no hashrate changes too PS you broke JSON API. it shows "cryptonight_type": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000" instead of normalv7 FIXED, thanks for reporting |
|
|
|
|
1511
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.0
|
on: June 09, 2018, 06:50:34 AM
|
V1.6.0- Added support for Haven new algo after fork (block 89200) - Added support for Masari new algo (fast) after fork (block 204000) - Job timeout default is now 20 minutes - More logging on miner startup - Added option 'persistent_memory' in gpu_conf + 2 new algos added : 'haven' and 'fast' So after the fork you can use them like : "cryptonight_type" : "fast"
"cryptonight_type" : "haven"+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that + 'persistent_memory' parameter added to gpu_conf, basically what it does is tries to allocate some memory that is normally not available to the GPU. It can increase hashrate in some ocassions, by finding the right intensity and threads setup, but also it can make the gpu crash, so it's up to you to experiment I am still looking for the cause of random miner crashes (mostly on new 'great' win 1803 update), also for the abnormality that causes higher hashrate on after X runs.
|
|
|
|
|
1512
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 08, 2018, 01:04:27 PM
|
I know you all have your conspiracy theories that a miner must steal your hashrate, but i will have to dissapoint you.
Your math is bad, to get average of something you divide total with something, in this case :
Total time in seconds since connected to pool / total number of sent shares (good & bad)
And end of story. This is how you get average time needed to find a share.
Sorry im not stealing 9% of your hashrate.
Your case:
Mining time 15 hours, 3 minutes 10 seconds = 54190 sec (in this case this can be taken because you did not have pool disconnects)
Total shares : 1213
Average : 54190 / 1213 = 44.6 sec
Now check your screenshot.
Thanks for the reply, dear! There were no thoughts about theft of hash. Based on your mathematics, you can calculate the real hash of the miner 1213 * 240000 = 291120000 total hash. 291120000 h / 54190 sec = 5372 h/s. Why then this figure is obtained, not 5800? What am I doing wrong? too much theory guys. Better take a 24,48h average from the pool, at the end that's what really matters. If you get numbers you don't like, switch mining software Don't get mad, but i really don't have time and nerves for these kind of things. I mean if your point isn't that the miner/me is stealing from you, then what is it? What are you trying to say ? |
|
|
|
|
1513
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 08, 2018, 12:21:01 PM
|
I used the proxy with SRBMiner with good results, and tested with XMR-stak also. However, I need to add TLS support and that means I have to learn more stuff. I could also employ the max allowed difficulty in the pool switch too, it may be another parameter in the coin-switch (auto coin switch is in the works, not working ). When thing get stable enough for SRB (it never does, it's a continuous fight against new drivers and windows updates and new algos) but if at all, coin switching through job json would be super awesome (without miner restart ;=) ), to overcome the namespace problems (everybody is calling some algo differently) since there's no set standard for algo names, you could go with e.g. "_SRB_powtype": "CryptonightV7" , so the proxy can add that to the job json.. But in future if the algo names follow standards, pools can send the "powtype" for any job, this way they can signal miners any algo change due to forks etc. with no problems, so hashrates are not lost with people trying to guess when the fork is going to happen, e.g. they could send "CryptonightHeavy" for block 30000, and "HavenAlgo" for block 30001 so the change would be seamless (even for miners that would need a restart, they would restart at the proper time!), this would be very good for a comfortable transition to new algos. A man can only dream  Coin switching for the same algo shouldnt be hard, your proxy sends info in json which coin to mine, minert just switches to the pool/wallet for that coin, and continues to mine. If you manage to make it stable enough ("it never does, it's a continuous fight against new drivers and windows updates" )) ), i can make SRBMiner compatible with it. |
|
|
|
|
1514
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 08, 2018, 12:17:19 PM
|
sorry but this is similar to the ones like : "calculator shows 50% more profit then i get. why is that?"
Not at all like this. It shows not the calculator, but the miner. The calculator does not calculate the profit, but the efficiency of finding shares. So this efficiency is lower than stated. Just want to understand why. If you are used to deal with everything superficially - your right. Forgive me, doctor  Here you have 2 pictures with arrows, compare, can understand what I'm talking about ....   Good point Sx5000 ! I'm waiting for Dok's reply.. I know you all have your conspiracy theories that a miner must steal your hashrate, but i will have to dissapoint you. Your math is bad, to get average of something you divide total with something, in this case : Total time in seconds since connected to pool / total number of sent shares (good & bad)And end of story. This is how you get average time needed to find a share. Sorry im not stealing 9% of your hashrate. Your case: Mining time 15 hours, 3 minutes 10 seconds = 54190 sec (in this case this can be taken because you did not have pool disconnects) Total shares : 1213 Average : 54190 / 1213 = 44.6 sec Now check your screenshot. |
|
|
|
|
1515
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 08, 2018, 07:13:27 AM
|
Coin switchers are a meme. Very difficult to properly monitor accurate market data + nethash spikes with low latency.
Certainly that was not the case for heavy coins. You could mine 5 units per hour in one half of the day, 8 units in the other half. You may guess which half is the better choice. I am going to re-think is integrating coin switching worth the time and effort because its not as simple as i thought. First idea was to use minecryptonight.net API which is so easy, just give it your hashrate and it returns the most profitable ($$$) coins. But when you mentioned switching by difficulty, etc here things got more serious As you are already working on that proxy, i will probably leave it to you, and i will focus more on the 'miner things' , i should find the cause of why does kernel recompilation sometimes creates 'better' kernel. There are a lot of parameters used internally, not visible to the user. I have to go back to debugging the opencl kernel, this will take some time. Also i want to make miner more stable, as some users are experiencing stability issues i can't reproduce Back to the proxy, i did not check it out, but as in the current state, it can to coin switching for SRBMiner too? Also some info : Next version in a day or two , with support for the upcoming Masari and Haven forks. It's already integrated and working, but i want to be sure that everyting is ok before releasing the new version |
|
|
|
|
1516
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 07, 2018, 02:08:45 PM
|
Hi, there may be a problem configuring for Electroneum pools. Everything seems to go ok but no shares are ever found.
Miner never reports submitting a share and pools never display receiving any.
Baz
:Edit, why is it immediately after posting the solution comes to you!
You have to specify --algo 1
:Edit again, nope still not right, works on Cryptoknights pool but not Spacepools
there is no --algo parameter in SRBMiner, i think you are in the wrong thread lol |
|
|
|
|
1517
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 07, 2018, 12:52:09 PM
|
Bug in 1.5.9
I tested the max_difficulty:
When reached the value set, program restarted OK but from "CryptonightV7 mode enabled" to "Heating up system" took more than 1 minute.
After that, even restarting Windows, every time I start 1.5.9 it takes more than 1 minute to start, about 1:20
Had to go back to 1.5.8 to have a normal start.
max_difficulty isn't restarting the miner, it's only reconnecting to the pool. |
|
|
|
|
1518
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 07, 2018, 11:12:11 AM
|
Another one problem - it's happens not too often but sometimes miner gives error - "Invalid nonce; is miner not compatible with NiceHash?".
UnclWish, I have this issue as well. And just like you, not too often but sometimes. this error can not be avoided, this is something specific to stupid nicehash and their custom protocol. |
|
|
|
|
1519
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.5.9
|
on: June 07, 2018, 11:04:10 AM
|
no i did not, i would just check my monitoring app and see the miner not hashing after a few days of hashing just fine. remote desktop and i see that the miner app has closed and i have to start back up again,
not a big deal however. the miner works great.
i haven't updated yet to 1.5.9 to see if it fixed it but i will update sometime tomorrow. will update with my findings.
Logs would be awesome for me to debug the problem, as always |
|
|
|
|
Show Posts
