|
V1.4.6-fix-fixes
- Fixed duplicate share sending fix
- Fixed GPU core clock & memory display fix
Ok, try this now it should all be good.
i shouldn't rush so much, then this wouldnt happen. sorry folks.
now when a duplicate share sending occures, there is info about it in the log :
[2018-04-19 18:32:22] miner_result: Duplicate share protection kicked in!
|
|
|
|
V1.4.5- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool - Added GPU core clock & memory display (ADL OverdriveN supported cards) Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great  Dok, CC displays for me, but not MC Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1) yup just realised that myself, i tested on 570 & 580 before i uploaded the new v. After that tried on 480 and no mem clk, so in next version that will be fixed ) I was in a hurry to give you a new version with the duplicates check, so i hope no more bans. I will update all rigs now and let you know if dups aren't fixed. the critical moment could be after 2hrs when the devfee switches back to the user mining, as someone wrote |
|
|
|
V1.4.5- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool - Added GPU core clock & memory display (ADL OverdriveN supported cards) Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great Dok, CC displays for me, but not MC Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1) yup just realised that myself, i tested on 570 & 580 before i uploaded the new v. After that tried on 480 and no mem clk, so in next version that will be fixed ) I was in a hurry to give you a new version with the duplicates check, so i hope no more bans. |
|
|
|
V1.4.5- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool - Added GPU core clock & memory display (ADL OverdriveN supported cards) BETA Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great
|
|
|
|
|
i will add some logic to check if share was already sent, and if it was , don't send it again.
Maybe sometimes a sneaky share is sent two times.
|
|
|
|
sorry for noob question but how to see when miner is minig to dev? is it showed in the console?
yes, its displayed when it starts and when it ends. |
|
|
|
is xmr stak using your cpu too to get that result? cause to be honest i dont believe its faster, i looked at their opencl nothing is there that could give a boost for those old cards. |
|
|
|
excuse me , noob question, what is ADL ?
AMD Display Library, or an interface that can control the fans, clocks etc on the GPU. |
|
|
|
do you get this with kernel 3? you have 512mb 6950?
--kernel 3 ATI hd6870 1GB DDR5 (OC, timings moded) Claymor 9.7 - 290 Hs SRB 1.4.4 - 154 Hs+- xmrstak - 171 Hs+- try kernel 2 |
|
|
|
V1.4.4- Fixed (hopefully) situation when miner hashed in 'empty' for a long time - Added mining session average speed display - Removed greedybastard switch ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test. It should be ok now. Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible. I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally.  1.4.4 still crashes instantly when pressing "h" to see hashrate on all of my 15 rigs. Miner is still rather unstable with restarts every 15-20 minutes. probably crash because you overclock to much, try to decrease a bit gpu clock The machines are stable on all other different software out there - And it has been stable for months. --adldisable seems to have done the trick for now, going to test it a bit more. can you tell on which cards do you have to use the --adldisable ? I am only using MSI RX570 Armor 4GBs - All on 18.1 driver, not tested with newer ones as I have simply not had the time to tinker with it, it is working in general though. With --adldisable it is stable, at least for the last 13 hours it has been stable on the two rigs that im testing it on now, tweaked intensity and are getting slight faster speeds than GGS now aswell, overall seems quite okay. Hm on that card adl should work , at least with blockchain drivers it works. |
|
|
|
Hi guys, one question, i have 6 rx580 8g doing 1050hs in CN Heavy . It's stable, without memory erros and etc. But when dev fee starts hashrate drops to 800/900+ and stays instable and after some 1 hour+ all cards stays at 1050 again. Wich could be the problem? Or is that a normal? Thanks Edit: I'm using { "id" : x, "intensity" : 58, "worksize" : 16, "threads" : 2}, for all. It's happening now:  its normal, and its not because of devfee. heavy algo fluctuates a few hundred mhs. |
|
|
|
Tell me how in the batch file to customize for each card its intensity?
all info you need is in the first post |
|
|
|
Doctor, did you fix issue with launching Pitcairn card alone when it 3rd GPU?
V1.3.2- Hopefully fixed bug when in 'gpu_conf' you want to set only one GPU |
|
|
|
I was mining fine with (6x)Vega 64 on UltraHeavy(the lite one) despite not knowing the config. Ive set intensity 110, worksize 16 adn threads 2 = 18000h I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo. Doctor,My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2? Looks you do have the same parameter in two places. PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all... This one is better: https://cryptoknight.cc/ipbc/Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo? let me quote you this from the first page : "DON'T comment out or remove intensity and double_threads setting at the top of the config file, just leave it as-is, because when you use a per card setting, those settings will be ignored." |
|
|
|
V1.4.4- Fixed (hopefully) situation when miner hashed in 'empty' for a long time - Added mining session average speed display - Removed greedybastard switch ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test. It should be ok now. Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible. I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally. 1.4.4 still crashes instantly when pressing "h" to see hashrate on all of my 15 rigs. Miner is still rather unstable with restarts every 15-20 minutes. probably crash because you overclock to much, try to decrease a bit gpu clock The machines are stable on all other different software out there - And it has been stable for months. --adldisable seems to have done the trick for now, going to test it a bit more. can you tell on which cards do you have to use the --adldisable ? |
|
|
|
|
do you get this with kernel 3? you have 512mb 6950?
|
|
|
|
V1.4.4- Fixed (hopefully) situation when miner hashed in 'empty' for a long time - Added mining session average speed display - Removed greedybastard switch ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test. It should be ok now. Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible. I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally. Paying the dev fee wasnt an issue with me. It was the freezing that was the issue. I have used an official release of XMR-stak with dev fee since I moved to CN coins. If this new version does not freeze then I will use it with dev fee. Thanks for the update. just make sure to find the right intensities for your cards and it wont freeze |
|
|
|
V1.4.4- Fixed (hopefully) situation when miner hashed in 'empty' for a long time - Added mining session average speed display - Removed greedybastard switch ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test. It should be ok now. Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible. I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally. 1.4.4 still crashes instantly when pressing "h" to see hashrate on all of my 15 rigs. Miner is still rather unstable with restarts every 15-20 minutes. wow so fast you tried the new version on 15 rigs in 5 minutes anyways, put --adldisable in .bat and lower your intensity, dont leave it on 0, but set it up yourself, and it wont crash. |
|
|
|
Hello everyone!
Does this miner support TeraScale/VLIW Radeon GPUs?
it should work, but you wont get speeds like on old claymore. Which card do you have? Radeon 5770 1GB GDDR5. And yeah, hashing speed is only half compared to Claymore v9.7... download v 1.4.3 and add --usekernel 3 in the bat like this : %EXE% --config config.txt --pools pools.txt --usekernel 3this is a test kernel im working on for those oldies I guess this emulates the Claymore v9.7 kernel? Thanks for caring about old GPUs (most devs don't), I'll give it a try! I just tried it and I still only get 80 H/s compared to 176 H/s on Claymore v9.7... intensity is 14 (higher doesn't work), worksize 8, 1 thread. Another problem with all miners I've tried (except Claymore v9.7) is that there is no "low intensity" option, which means the UI is lagging a lot (if you want to use your PC while mining). I wish someone could replicate Claymore v9.7 characteristics and I'd gladly pay a mining fee... can you download 1.4.4 now and try again with --usekernel 3 parameter in bat, but set start intensity to 10 , and use only 1 thread. Then work up the intensity as much as you can. |
|
|
|
|
Show Posts
