 Show Posts
|
|
Pages: « 1 [2] 3 4 5 »
|
|
Is it possible to enable automatic withdrawals on Ghash? I can only see the option for on demand payouts with a 0.001 fee.
|
|
|
|
I'm actually having the same old problem with 1.0a: too many rejects (compared to 0.9c). Setting --no-refresh seems to make it worse (will keep running for a while longer to confirm this).
Don't use --no-refresh if you are having issues with rejects, it does make it worse as it only sends new work when a new block is detected, as opposed to always sending new work to the GC3355. It's a command line option specifically for the Blade users. OK. I've switched to another pool (ghash) and cpuminer is not giving high rejects. But, difficulty stays @ 16, which is lower than I'm used to seeing - is that anything to worry about? More traffic? (noob questions I know) I know the admins @ GiveMeCoins tested cpuminer with their pool but I don't think they tried the Windows builds, FWIW. That's no issue, the bandwidth consumed when mining is relatively low. BTW, there is no difference between Windows build or the others. I still stand by that it's a pool issue, because I'm getting 0.2-1% reject rate on any pool I tested except that one. Sure I see what you mean. Its just curious that 0.9c works fine with GiveMeCoins pool. |
|
|
|
I'm actually having the same old problem with 1.0a: too many rejects (compared to 0.9c). Setting --no-refresh seems to make it worse (will keep running for a while longer to confirm this).
Don't use --no-refresh if you are having issues with rejects, it does make it worse as it only sends new work when a new block is detected, as opposed to always sending new work to the GC3355. It's a command line option specifically for the Blade users. OK. I've switched to another pool (ghash) and cpuminer is not giving high rejects. But, difficulty stays @ 16, which is lower than I'm used to seeing - is that anything to worry about? More traffic? (noob questions I know) I know the admins @ GiveMeCoins tested cpuminer with their pool but I don't think they tried the Windows builds, FWIW. |
|
|
|
|
I'm actually having the same old problem with 1.0a: too many rejects (compared to 0.9c). Setting --no-refresh seems to make it worse (A:241 R:20 H:0 in 20mins).
|
|
|
|
Latest build of 0.9g instantly crashes on me (Win 8.1). Build from a few hours ago works unless I specify 2 pools, or use the --no-refresh switch, in which instance it also instantly crashes.
That being said, it (the previous build of 0.9g) is the first version since 0.9c that is giving me a nice low amount of rejects (0.5%). During the last 10 hours: A:5826 R:29 HW: 2 (var diff ~64) Keep an eye on the dropbox links, the binaries are updated once in a while. Should work without any crashes now. As of now the link on your dropbox is saying its 11hours old. I think thats the one I'm already using but updated again just to be sure. Still crashing unfortunately. Screenshot: http://i.snag.gy/lkQ54.jpgCrash info from Windows: Problem signature:
Problem Event Name: APPCRASH
Application Name: minerd-gc3355.exe
Application Version: 0.0.0.0
Application Timestamp: 536c1f0e
Fault Module Name: minerd-gc3355.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 536c1f0e
Exception Code: c0000005
Exception Offset: 00004054
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: d1d9
Additional Information 4: d1d94a13d3609d6b740644c12508f581 EDIT: Oh sorry, you are saying just keep an eye on the dropbox links, i.e. the next compile shouldn't crash? The latest build on dropbox (13h ago) should not crash. What is your cpuminer command line? It works OK when I remove this part from my bat file: --gc3355-freq=\\.\COM1:875,\\.\COM1:850:2,\\.\COM2:850:0,\\.\COM2:850:1,\\.\COM2:825:2,\\.\COM2:875:3,\\.\COM2:850:4, Is there a problem with that syntax? 0.9c does not have a problem with it. |
|
|
|
Latest build of 0.9g instantly crashes on me (Win 8.1). Build from a few hours ago works unless I specify 2 pools, or use the --no-refresh switch, in which instance it also instantly crashes.
That being said, it (the previous build of 0.9g) is the first version since 0.9c that is giving me a nice low amount of rejects (0.5%). During the last 10 hours: A:5826 R:29 HW: 2 (var diff ~64) Keep an eye on the dropbox links, the binaries are updated once in a while. Should work without any crashes now. As of now the link on your dropbox is saying its 11hours old. I think thats the one I'm already using but updated again just to be sure. Still crashing unfortunately. Screenshot: http://i.snag.gy/lkQ54.jpgCrash info from Windows: Problem signature:
Problem Event Name: APPCRASH
Application Name: minerd-gc3355.exe
Application Version: 0.0.0.0
Application Timestamp: 536c1f0e
Fault Module Name: minerd-gc3355.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 536c1f0e
Exception Code: c0000005
Exception Offset: 00004054
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: d1d9
Additional Information 4: d1d94a13d3609d6b740644c12508f581 EDIT: Oh sorry, you are saying just keep an eye on the dropbox links, i.e. the next compile shouldn't crash? |
|
|
|
Latest build of 0.9g instantly crashes on me (Win 8.1). Build from a few hours ago works unless I specify 2 pools, or use the --no-refresh switch, in which instance it also instantly crashes.
That being said, it (the previous build of 0.9g) is the first version since 0.9c that is giving me a nice low amount of rejects (0.5%). During the last 10 hours: A:5826 R:29 HW: 2 (var diff ~64) |
|
|
|
OK I finally got the top off my gridseed lol. But now..
How do I get the bottom off? Mite seem like a basic question but do I need to use a spanner to unscrew those 4 gold posts, before the bottom heatsink will come loose?
Yes - those 4 posts are what screws down the circuit board to the other half of the heatsink. Thanks! I'll try that out tomorrow if I can find a pair of pliers. |
|
|
|
|
Latest build of 0.9g instantly crashes on me (Win 8.1). Build from a few hours ago works unless I specify 2 pools, or use the --no-refresh switch, in which instance it also instantly crashes.
|
|
|
|
|
OK I finally got the top off my gridseed lol. But now..
How do I get the bottom off? Mite seem like a basic question but do I need to use a spanner to unscrew those 4 gold posts, before the bottom heatsink will come loose?
|
|
|
|
For those who had a high reject rate since v0.9e, you should try v0.9g. It has an additional command line parameter to only send work when a new block is detected (--no-refresh), by default it always sends new work as previously, so there should be much less rejects. You may enable this if your G-Blade is having trouble keeping up with the work sent.
Thanks, tried this with 0.9g but it says: minerd-gc3355: unrecognised option `--no-refresh'
Try `minerd --help' for more information.I did a little update while I was uploading v0.9g, redownloading the binaries should fix it. OK got the new version now. This however finds my gridseeds, sets their frequencies, but then shows 0 speed and there is no activity in relation to accepted shares. Very curious. Anyone else getting this? |
|
|
|
For those who had a high reject rate since v0.9e, you should try v0.9g. It has an additional command line parameter to only send work when a new block is detected (--no-refresh), by default it always sends new work as previously, so there should be much less rejects. You may enable this if your G-Blade is having trouble keeping up with the work sent.
Thanks, tried this with 0.9g but it says: minerd-gc3355: unrecognised option `--no-refresh'
Try `minerd --help' for more information. |
|
|
|
|
I'm still getting lots of rejects with cpuminer 0.9d onwards so I'm going to try a different pool to see if that helps. Is there a switch in cpuminer to set the diff? cex.io (GHash.IO - same thing?) does not seem to use vardiff and its default 16 seems a bit low. My main pool (give-me-coins) starts at 16 but usually goes up to 96-128+ within minutes.
And FWIW the rejects I get from give-me-coins pool only start to happen when diff goes up to 64+. What diff are you guys getting/setting?
|
|
|
|
I've unscrewed my gridseed but it won't seem to come apart. Brute force required?
no, should go loose pretty easy once you got the 4 screws out, could stick a little due to thermal pad but nothing excessive Hmm if the thermal pad is stuck that tight I'm worried that its going to rip some components off the PCB if I apply enough force to seperate it. |
|
|
|
|
I've unscrewed my gridseed but it won't seem to come apart. Brute force required?
|
|
|
|
Looks like both version work fine (at least for me).
Is this the RPi or Windows build you were testing? Windows here, with my problems.. |
|
|
|
I appreciate what you are saying but in answer to your question yes I am sure, here's a screenshot from 0.9c where the message "Stratum detected new block" can be seen: http://i.snag.gy/jOzeL.jpg |
|
|
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply.  In 0.9d, new work is sent when there is a new job and after a nonce is found, in 0.9c it would stop hashing immediately and send the new work. The latter is actually inefficient and slows down the mining. Could you post a log with --debug and --protocol option enabled? Personally I'm still getting 0.2% rejects whatever the pool I go with. Sure thing. Just add --debug and --protocol-dump to my bat file? I assume it will output the debug dump into a file in the same directory. How long should I run it for to produce something useful. An hour? I'll do it tomorrow its 3am here and I need to collapse. Sandor I can't see that the debug/log is being stored anywhere just printed to the screen? Rejects still seem high for me in your Windows build from today of 0.9e (A:306 R:36 H:0 over 60mins). Here is an excerpt from the log when some errors occured. Does this shed any light? [2014-05-06 10:55:11] 1: Dispatching new work to GC3355 cores (0xb1547f34)
[2014-05-06 10:55:11] > {"method": "mining.submit", "params": ["Rowan.1", "139937 0091 3796", "55555581", "5368b16b", "a098f0cc"], "id":4016}
[2014-05-06 10:55:11] < {"error": [20, "unknown-work", null], "result": null, "id": 4016}
[2014-05-06 10:55:11] Rejected ccf098a0 GSD 1@4
[2014-05-06 10:55:11] DEBUG: reject reason: unknown-work
[2014-05-06 10:55:11] 0@0 875MHz: Got nonce 002ede29, Hash <= Htarget! (0xb1547f34) 74.1 KH /s
[2014-05-06 10:55:11] 0: Dispatching new work to GC3355 cores (0xb1547f34)
[2014-05-06 10:55:11] > {"method": "mining.submit", "params": ["Rowan.1", "139937 0091 3796", "8000002b", "5368b16b", "29de2e00"], "id":4017}
[2014-05-06 10:55:11] < {"error": [20, "unknown-work", null], "result": null, "id": 4017}
[2014-05-06 10:55:12] Rejected 002ede29 GSD 0@0
[2014-05-06 10:55:12] DEBUG: reject reason: unknown-workAdd --log Here is an hours worth of log: http://pastebin.com/BghRt9LXFWIW this was my bat file (running 2 Gridseeds): minerd-gc3355 --debug --protocol-dump --log --freq=850 --gc3355=\\.\COM1,\\.\COM2 --url=stratum+tcp://xxxxxxxxx.com:3333 --userpass=Rowan.1:pass --gc3355-freq=\\.\COM1:875,\\.\COM1:850:2,\\.\COM2:850:0,\\.\COM2:850:1,\\.\COM2:825:2,\\.\COM2:875:3,\\.\COM2:850:4,
pauseThe pool doesn't report new blocks at all (WTF?), so of course cpuminer sticks with the old work. I would suggest that you try a different pool. When I run with 0.9c I do get "Stratum detected new block" messages in the log, if that is what you mean (same pool). |
|
|
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply. In 0.9d, new work is sent when there is a new job and after a nonce is found, in 0.9c it would stop hashing immediately and send the new work. The latter is actually inefficient and slows down the mining. Could you post a log with --debug and --protocol option enabled? Personally I'm still getting 0.2% rejects whatever the pool I go with. Sure thing. Just add --debug and --protocol-dump to my bat file? I assume it will output the debug dump into a file in the same directory. How long should I run it for to produce something useful. An hour? I'll do it tomorrow its 3am here and I need to collapse. Sandor I can't see that the debug/log is being stored anywhere just printed to the screen? Rejects still seem high for me in your Windows build from today of 0.9e (A:306 R:36 H:0 over 60mins). Here is an excerpt from the log when some errors occured. Does this shed any light? [2014-05-06 10:55:11] 1: Dispatching new work to GC3355 cores (0xb1547f34)
[2014-05-06 10:55:11] > {"method": "mining.submit", "params": ["Rowan.1", "139937 0091 3796", "55555581", "5368b16b", "a098f0cc"], "id":4016}
[2014-05-06 10:55:11] < {"error": [20, "unknown-work", null], "result": null, "id": 4016}
[2014-05-06 10:55:11] Rejected ccf098a0 GSD 1@4
[2014-05-06 10:55:11] DEBUG: reject reason: unknown-work
[2014-05-06 10:55:11] 0@0 875MHz: Got nonce 002ede29, Hash <= Htarget! (0xb1547f34) 74.1 KH /s
[2014-05-06 10:55:11] 0: Dispatching new work to GC3355 cores (0xb1547f34)
[2014-05-06 10:55:11] > {"method": "mining.submit", "params": ["Rowan.1", "139937 0091 3796", "8000002b", "5368b16b", "29de2e00"], "id":4017}
[2014-05-06 10:55:11] < {"error": [20, "unknown-work", null], "result": null, "id": 4017}
[2014-05-06 10:55:12] Rejected 002ede29 GSD 0@0
[2014-05-06 10:55:12] DEBUG: reject reason: unknown-workAdd --log Here is an hours worth of log: http://pastebin.com/BghRt9LXFWIW this was my bat file (running 2 Gridseeds): minerd-gc3355 --debug --protocol-dump --log --freq=850 --gc3355=\\.\COM1,\\.\COM2 --url=stratum+tcp://xxxxxxxxx.com:3333 --userpass=Rowan.1:pass --gc3355-freq=\\.\COM1:875,\\.\COM1:850:2,\\.\COM2:850:0,\\.\COM2:850:1,\\.\COM2:825:2,\\.\COM2:875:3,\\.\COM2:850:4,
pause |
|
|
|
|
