V1.4.9- Possibly fixed bug some were having when switching pool from user to devfee - Removed location parameter from config file as it just confused people  - Added resources cleanup on miner shutdown Please everyone having issues with miner crashing and stuck on change to devfee mining, download this version, it should fix these issues. Hi, Dok. 16 rigs, 9+ hours, all ok so far... Not so much time to test, but looking promissing. Thanks. thanks for your feedback , i hope it will work from now on as intended and i can carry on and work on new stuff. |
|
|
|
Hm, i will try to find a workaround with BUSid detection.
Which drivers are you using?
this particular machine have 17.12.2. this is what i found : There is currently an issue in the AMD Adrenalin drivers (17.12.1+) that makes pciebus detection impossible. AMD is aware of the bug and hopefully there is a new version that fixes it soon. Update: 18.1.1 Alpha drivers tested and bug remains.
In a functioning driver, a query returns the PCIe bus ID for each GPU, however in the Adrenalin drivers a bus ID of 0 is always returned.
This bus ID is necessary to query the AMD Display Library (ADL). Because bus IDs are not actually being returned, ADL cant get information like temperature/usage, UUID, PCIe location, etc.So i found what is causing the problem, but i don't understand how does Claymore miner detect busid on those drivers. ? I can add a parameter where you can manually enter busid, and it should work. It's easy to get PCI bus id from device manager. |
|
|
|
Dok, the miner shows locally 4.6 as speed, but the pool detects only 4.4. Earlier when I was using lower intensity I was getting locally less hashrate and the reported hashrate by the pool was quite bigger!
Has anyone ever experienced something like that?
the hashrate on pool side is never constant, now you have 4.4, in 1 hour you will maybe have 4.8 and so on.. the 48h average is what matters. |
|
|
|
V1.4.9- Possibly fixed bug some were having when switching pool from user to devfee - Removed location parameter from config file as it just confused people - Added resources cleanup on miner shutdown Please everyone having issues with miner crashing and stuck on change to devfee mining, download this version, it should fix these issues.
|
|
|
|
For H5GQ8H24MJR try this folks:
999000000000000022339D00CEDD6B4470551414B80D960B0040C400750314204A8900A00200000 018123745B92B3A16  960 h/s @1240/2100 Lets see if its stable  this strap is a ok for ETH and Cn. Its not CN specific, it could be tuned more for CN possibly. 1150/2100 = 30.5 ETH, or 930 h/s CN  |
|
|
|
hai guys please help me why srbminer take long time for devfee more than 3 hour so my rig goes to idle   i will upload 1.4.9 version today that i hope fixes this issue, it happens on some ocassions when switching pool from user to devfee. stay tuned |
|
|
|
For H5GQ8H24MJR try this folks:
999000000000000022339D00CEDD6B4470551414B80D960B0040C400750314204A8900A00200000 018123745B92B3A16
|
|
|
|
yes time is key to success I hope i managed to fix this devfee problem once and for all, going to let it run for the night, and if everything looks ok i will upload corrected version. |
|
|
|
|
On win7 there is even no compute mode for the new adrenaline drivers
|
|
|
|
|
yeah i know some users reported it too.
Im working on it.
Ok now i found something insane : if i connect with teamviewer to the rig it won't crash. Without it it crashes on one of my rigs.
Anyone else can confirm this?
guys stay on 1.4.7 or a version that best works for you until i resolve this
|
|
|
|
Doc, I don't know if it's possible to solve my issue, because it's a little specific I have three different GPU variants, that have different strong points and weaknesses: RX580 8GB (awesome for Heavy) RX570 4GB (good for V7) R7 260X 2GB (not bad for Lite) To make use of the best of each card I've had to rename the SRBMiner (to avoid the check) executable and run three instances, one for each card. So, I run three SRBMiners lol Is possible (or, better, it worth the work) to run different algorithms/pools in the same miner in the future? (if not, it's fine. I like your miner ) lol sorry it's not in plan any soon |
|
|
|
Dok, hi.
Can send only 2 private messages per day.
Testing what you asked in last message. I'll write you ASAP.
Thank you, i hope this is it now |
|
|
|
i fu***D up something obviously. Use previous version , im working on a fix.
Damn right you did. I want a refund Just kidding, keep up the good work. that pool switching thing i added in 1.4.8 is guilty,its not me  |
|
|
|
|
i fu***D up something obviously. Use previous version , im working on a fix.
|
|
|
|
Hey Doktor
First of all thanks for good work, SRB Miner is the best.
I have a request for pool switch option. While using pool switch option i can switch coins sharing same algorihtms. Can you adjust the miner for pool switch option such as while switching pool, algo switch is also possible. For example while i am mining a coin with normalv7 algo, i can switch a heavy alogrithm coin or lite1 without closing and restarting miner. Is this possible. Thanks in advance.
Sorry but that is not in plan any soon |
|
|
|
This night I had a problem , can`t connect to pool for devfee and it has been for 7 hours like this. What could be the issue?
miner version, algo you are mining? The miner is 1.4.7 mining Heavy algo. I see others have issue too. Hope it is just a pool problem. but what error did you get? It said "Can't connect to devfee pool" ? Or just connected to devfee pool and nothing happens for a long time, or ? |
|
|
|
ok, i will rewrite this the third time...  |
|
|
|
Hi, doctor.
Still there is a problem with devfee in last version.
My rigs updated to 1.4.8 today, and after connection to devfee pool no reconnection to user pool.
From log:
[2018-04-25 20:21:16] miner_result: Pool accepted result 0x00003805
[2018-04-25 20:21:28] miner_result: Sending user result to pool
[2018-04-25 20:21:28] json_send: {"method":"submit","params":{"id":"2412128013","job_id":"54eb","nonce":"802b56d5","result":"af0ff0380c8bc50cc70f9c9c0fa13124378013c6fa542d8aa6ee1dd3dc680000"},"id":1}
[2018-04-25 20:21:28] json_receive: {"id": 1, "jsonrpc": "2.0", "result": {"status": "OK"}, "error": null}
[2018-04-25 20:21:28] miner_result: Pool accepted result 0x000068DC
[2018-04-25 20:21:28] switch_pool: Connected to devfee :)pool
[2018-04-25 20:53:52] DevFee stops in 18446744073709549737 seconds
Any ideas?
where is rest of log after devfee started? from 20:21:28 this is insane really |
|
|
|
I get error when miner went for devfees on both my rigs.... anyone else
what kind of error and which version? |
|
|
|
doctor, I have strange thing with 1.4.7. After closing SRB miner clocks, voltages and tt of cards resets to bios defaults. And I forced to set them again to start SRB with needed clocks, etc.
Maybe you make setting hardware parameters via your miner?
ADL enabled and works with my RX 580 8Gb cards.
yes i had on cleanup settings reset i removed that in latest version. you have eyes of an eagle |
|
|
|
|
Show Posts
