SRB on my RX 580 8Gb cards (hynix) gives on 1 card 10 h/s more than GGS, but 2nd card 10 h/s less ))))
But GGS is open source... Thats mean that devfee can be disabled on them...
+10/hs per card + 0.85% of daily earnings will get you very very rich  Every developer sets his fee. Some think their work worths more, while others are satisfied with less. Taking away that lets call it salary won't really motivate the dev to continue working. But it's non of my business what you use and how you use it As i just started this miner thing a few months ago, and see how much people support my work, im really motivated to continue working on it. Making it better every day. I get the 0.85% fee, but some people even mine on my account that i left in the config file. Just want to say thanks to everyone, it feels good that i have your support You're right. I'm agreed with all that you say. But as usual miner I'm 1st of all look into my profit, not developers of miners. Must to say that it's allready big amount of CN miners at this moment. Claymore, GGS, CastXMR, sgminer, SRB - and it's only miners that give good speed. And when I have a choise - it's normal that I choose miner that gives to me maximum earn... And I too, agree totally with you Soon you will be only using SRB as it will make you the most profit    |
|
|
|
SRB on my RX 580 8Gb cards (hynix) gives on 1 card 10 h/s more than GGS, but 2nd card 10 h/s less ))))
But GGS is open source... Thats mean that devfee can be disabled on them...
+10/hs per card + 0.85% of daily earnings will get you very very rich Every developer sets his fee. Some think their work worths more, while others are satisfied with less. Taking away that lets call it salary won't really motivate the dev to continue working. But it's non of my business what you use and how you use it As i just started this miner thing a few months ago, and see how much people support my work, im really motivated to continue working on it. Making it better every day. I get the 0.85% fee, but some people even mine on my account that i left in the config file. Just want to say thanks to everyone, it feels good that i have your support |
|
|
|
R9 380(4Gb, moded Bios,1100,1625) - 780 HS
Now this is awesome  |
|
|
|
Can someone help ! how t set difficulty on SRB 1.4.6
that is something that is pool related, not miner. |
|
|
|
@doktor83 Please make an option for simple one bat file, where we can put all data for mining, like claymore cryptonight miner, or sgminer for example with simple commands (-o -a -w -g -I...), why separate so much config, pools, etc and so much unnecessary files??
I will add that, few of you asked for it, so you will get it |
|
|
|
hy again @doktor83 is SRBMiner showing AMD Invalid results aswell as Acceptept total shares ? it would be verry helpful for me to know the share time in stats ... thx again Invalid results = HW errors in SRBminer Also what is a share time ? |
|
|
|
hello dok, in my 6950 I get 355 h / s with I 54.5 W 16 with OC 840/1250 usekernel 3, 90% similar to claymore 9.7, sincerely I would like you to explain how the usekernel option works to better understand the configuration, thanks and congratulations for the work done to these old gpu.
I also have a 6870 with I 22.5 W 8 and I get 170 ~ 200 h / s with OC 950/1150 usekernel 3, with claymore 9.7 I get 250, I think it can improve a bit, thank.
If you need access to my platform to perform tests, I'm willing to help.
simple, those are opencl kernels. 1 is for gcn cards, 2 is same kernel like 1 but changed a few rhing to make it work on old cards, 3 and 4 is something i was experimenting. |
|
|
|
hy after fail mining at dev fee pool, 1 mimute nothing and after this duplicat share... https://jpst.it/1e0PCdownload 1.4.6, i added duplicate share protection. ok thx and why 1 min down time ? it tried 1 min to connect to devfee and because it couldnt it switched back to mine for you |
|
|
|
hy after fail mining at dev fee pool, 1 mimute nothing and after this duplicat share... https://jpst.it/1e0PCdownload 1.4.6, i added duplicate share protection. |
|
|
|
Hi there, I've had a problem with every miner around since the monero pow change, since the only miner I was able to use was Claymore 9.7beta without it crashing my display drivers. I've tried xmr-stak, xmrig-amd, newer claymore's (No ASM bin found for my old card.) and about anything else that is supposed to work, I've compiled all the ones available and tried with stock binaries on windows.. Display drivers crash no matter which version I try.. 14.4 15.7, 15.11-beta (for some reason this one is tricky to find.) Even tried the crimson edition beta which I've found out doesn't actually include any assembler/disassembly tools for openCL.. Anywho.. Display card: AMD Ati Radeon 6530D (Evergeen or BeaverCreek as it picks it up everywhere.) Cpu: AMD A6-3620 APU w/ the onboard 6530D I've tried all 4 kernels out, all kill display, and of course can't get ADL to work, but I'd be highly surprised if that could even work at all anyways on this gpu. All in all I really don't know what to do, or even try anymore.. I'd lend a hand if I could for getting what is needed to make these A-Series APUs to work. I haven't really seen anything in the code for the other miners like xmrig/xmr-stak that would be a problem.. But I noted for some reason Claymore is posting exact driver versions for all of their releases, and wondering how they are able to compile against them specifically, or if that just happens to be what they were using when compiling... Any help is appreciated, and I'd love to get back to mining on my gpu, had a ton more shares and efficiency even at 42H/s and that's better than 0 since it's on 24/7 anyways. Here are a couple screenshots for how it's acting and what it catches, and second is showing when display was killed and came back. https://imgur.com/a/mBtohkvThanks, you really are saving miner's lives with this miner and I hope you keep at it.. So I tip my hat to you Doc. hi, remove drivers with Display Driver Uninstaller, install 14.4 and try SRBMINER 1.4.6 --userkernel 4 for XMR use "normalv7" and start with a very low intensity like 5, and only 1 thread Ok well I used DDU and found the correct 14.4 drivers.. seems the last one wasn't actually installing for some reason.. anyways now all other miners work as well. Only one issue really is the intensity setting, I can only go up to 2.0. 2.1 or higher kills display driver or gives the CL invalid buffer.. tried all 4 kernels and worksizes, kernel 2 seems to be the best at 14H/s compared to 12-13H/s on 3 & 4 kernels. I was wondering if the gpu kernels having "256" in them as being the hash size? and if so, is there a way to lower or give a CLI option to change them or maybe a 128 version? If that isn't the case, oh well. (126 intensity seemed to be the optimal number for xmr-stak for some odd reason, also with a 35.9H/s which isn't to far off of the original claymore 9.7's 42H/s with low intensity mode on before v7.) Does anyone know how to keep windows and everything from being totally unusable on all these miners? (like clay's -li low intensity mode, which doesn't seem to be related at all to actual intensity.) Best of luck to everyone. it should go up to 7 - 7.5 with 1 thread on kernel 2 |
|
|
|
With v1.4.6 I got an error message from adl
[2018-04-20 08:17:54] Failed to get ADL function pointers
[2018-04-20 08:17:54] ADL init failed
[2018-04-20 08:17:54] Gpu watchdog started
Using 17.7.1 driver win8.1
With previous version it was ok.
that version probably does not have some functions i added that read/write core&mem clock and voltages. |
|
|
|
Hi there, I've had a problem with every miner around since the monero pow change, since the only miner I was able to use was Claymore 9.7beta without it crashing my display drivers. I've tried xmr-stak, xmrig-amd, newer claymore's (No ASM bin found for my old card.) and about anything else that is supposed to work, I've compiled all the ones available and tried with stock binaries on windows.. Display drivers crash no matter which version I try.. 14.4 15.7, 15.11-beta (for some reason this one is tricky to find.) Even tried the crimson edition beta which I've found out doesn't actually include any assembler/disassembly tools for openCL.. Anywho.. Display card: AMD Ati Radeon 6530D (Evergeen or BeaverCreek as it picks it up everywhere.) Cpu: AMD A6-3620 APU w/ the onboard 6530D I've tried all 4 kernels out, all kill display, and of course can't get ADL to work, but I'd be highly surprised if that could even work at all anyways on this gpu. All in all I really don't know what to do, or even try anymore.. I'd lend a hand if I could for getting what is needed to make these A-Series APUs to work. I haven't really seen anything in the code for the other miners like xmrig/xmr-stak that would be a problem.. But I noted for some reason Claymore is posting exact driver versions for all of their releases, and wondering how they are able to compile against them specifically, or if that just happens to be what they were using when compiling... Any help is appreciated, and I'd love to get back to mining on my gpu, had a ton more shares and efficiency even at 42H/s and that's better than 0 since it's on 24/7 anyways. Here are a couple screenshots for how it's acting and what it catches, and second is showing when display was killed and came back. https://imgur.com/a/mBtohkvThanks, you really are saving miner's lives with this miner and I hope you keep at it.. So I tip my hat to you Doc. hi, remove drivers with Display Driver Uninstaller, install 14.4 and try SRBMINER 1.4.6 --userkernel 4 for XMR use "normalv7" and start with a very low intensity like 5, and only 1 thread |
|
|
|
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!
I still getting "Your IP is banned" with v1.4.6  .. https://imgur.com/a/xwTOWxXno way it happened right after connecting. you were probably banned before trying new ver and the ban still existed. |
|
|
|
try to flash this timings:
777000000000000022C39C00AC595A3D90550F12B84C8408004006007E0514206A8900A00200312 0100F292F94273116
or this
999000000000000022C39C00AC595A3D90550F123CCF530C004006007E0514206A8900A00200312 0100F292F94273116
I think these timings are for Hynix 4GB, not the 8GB ones.
I suggest to use the SRBPolaris's PimpMyStraps or One-click straps from PolarisBiosEditor. It's safe and improve performance. Oh PM me if you wanna more performance.
If you already have a biosmoded GPU, maybe you need to deal with the intensity.
Any difference between PimpMyStraps or One-click straps or is it just a name? Not sure if this a re 4Gb versions, but ill give it a try, from 1750? not the same straps, schnack took straps from the net. i didn't. |
|
|
|
|
can i get the part of log from devfee start and a little after devfee should end?
|
|
|
|
|
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
|
|
|
|
|
Show Posts
