Statistics
Algorithm Current Speed Currently Paying 24h Payouts
Scrypt 3.7066 GH/s 5.8898 4.0027
BTC/GH/Day
are those numbers real ?
Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 314. (Read 794462 times)
May 13, 2014, 02:43:44 PM
May 13, 2014, 02:21:18 PM
have problem with r9 270.
at first it running good with 1350kh/s , settings from here http://www.reddit.com/r/Hirocoin/comments/21alr7/mining_config_gigabyte_r9_270_138_mhs/
and at some point ~15 minutes according to log file, nicehash is not providing me any block to solve and the hashrate drops to like 1150kh/s, even when I am getting back to solving a block, the hashrate stays low like that, does not go up again.
only restarting miner gives back the nice hashrate again for a while. any suggestions?
at first it running good with 1350kh/s , settings from here http://www.reddit.com/r/Hirocoin/comments/21alr7/mining_config_gigabyte_r9_270_138_mhs/
and at some point ~15 minutes according to log file, nicehash is not providing me any block to solve and the hashrate drops to like 1150kh/s, even when I am getting back to solving a block, the hashrate stays low like that, does not go up again.
only restarting miner gives back the nice hashrate again for a while. any suggestions?
May 13, 2014, 02:20:51 PM
hellow,
how often i will get paid ?
there is a minimum amount to be paid ?
thank you !
how often i will get paid ?
there is a minimum amount to be paid ?
thank you !
May 13, 2014, 01:25:14 PM
set d=0.04 in your password, works for me. I was getting the same like you before setting that.
That did the trick! Thank you, kind sir.
Default X11 diff is set to 0.2. If you have very slow miner, it may take long time for any accepted share to appear. That is why you should reduce diff manually to lower number. It is same with scrypt - if you have slow miner, it takes a while to find a share.
May 13, 2014, 12:47:26 PM
I'm using sph-sgminer and I'm not seeing a constant "accepted shares" as I normally do with scrypt or scrypt-n. And the accumulated accepted shares shown as a whole number is low because the accepted shares, when they do show, are only fractions. However, I've let my miner run for almost 24 hours and it appears that I am in fact getting paid in proportion to the pay rate. I don't have a minimum pay rate set.
I did notice that it took almost 5+ minutes before my first accepted share showed on up my miner when I initially started and there are long periods where the miner just keeps showing "Network diff set to ..", "Stratum from NiceHash detected new block", and "Stratum from NiceHash requested work restart" before an accepted share is logged. But NiceHash seems to be getting something as my BTC balance continues to go up anyway and I'm getting about the same amount as I would if I was hashing scrypt.
I have my diff set to 0.04
I did notice that it took almost 5+ minutes before my first accepted share showed on up my miner when I initially started and there are long periods where the miner just keeps showing "Network diff set to ..", "Stratum from NiceHash detected new block", and "Stratum from NiceHash requested work restart" before an accepted share is logged. But NiceHash seems to be getting something as my BTC balance continues to go up anyway and I'm getting about the same amount as I would if I was hashing scrypt.
I have my diff set to 0.04
May 13, 2014, 12:34:15 PM
set d=0.04 in your password, works for me. I was getting the same like you before setting that.
That did the trick! Thank you, kind sir.
May 13, 2014, 12:21:35 PM
Latest sph miner has to be used, else you may be getting rejects.
Note that sph miner does still have idlebug inside and does not support extranonce subscriptions. When we prepare NiceHash sph miner, these issues will be fixed.
Note that sph miner does still have idlebug inside and does not support extranonce subscriptions. When we prepare NiceHash sph miner, these issues will be fixed.
can you give ETA on that, I hope it is very soon. Very good service you've got going, GL
May 13, 2014, 12:20:07 PM
Hi Dev,
I have tried using all the different miners listed so far, however after a few minutes worth of success this morning, my cards are not able to run the X11 project.
They are not getting any rejected WU'd as they are not sending out anything at all. WU speed is 0 per second and there is a nonstop wave of "Pool requested work restart", "New block detected" going on endlessly. All other types of scrypts work fine.
I have tried using all the different miners listed so far, however after a few minutes worth of success this morning, my cards are not able to run the X11 project.
They are not getting any rejected WU'd as they are not sending out anything at all. WU speed is 0 per second and there is a nonstop wave of "Pool requested work restart", "New block detected" going on endlessly. All other types of scrypts work fine.
set d=0.04 in your password, works for me. I was getting the same like you before setting that.
May 13, 2014, 11:46:08 AM
Hi Dev,
I have tried using all the different miners listed so far, however after a few minutes worth of success this morning, my cards are not able to run the X11 project.
They are not getting any rejected WU'd as they are not sending out anything at all. WU speed is 0 per second and there is a nonstop wave of "Pool requested work restart", "New block detected" going on endlessly. All other types of scrypts work fine.
I have tried using all the different miners listed so far, however after a few minutes worth of success this morning, my cards are not able to run the X11 project.
They are not getting any rejected WU'd as they are not sending out anything at all. WU speed is 0 per second and there is a nonstop wave of "Pool requested work restart", "New block detected" going on endlessly. All other types of scrypts work fine.
May 13, 2014, 11:42:29 AM
Could you help with diff formula for x11?
Thanks
Thanks
Honestly I don't know. Don't have mining equipment on my own to give you any references. Just make it so you are getting one share per 5-10 seconds and it will be fine.
May 13, 2014, 11:38:18 AM
Could you help with diff formula for x11?
Thanks
Thanks
May 13, 2014, 11:22:32 AM
Latest sph miner has to be used, else you may be getting rejects.
Note that sph miner does still have idlebug inside and does not support extranonce subscriptions. When we prepare NiceHash sph miner, these issues will be fixed.
Note that sph miner does still have idlebug inside and does not support extranonce subscriptions. When we prepare NiceHash sph miner, these issues will be fixed.
May 13, 2014, 11:19:12 AM
Latest sph-sgminer works fine, i can set price and diff it all works well, problem remains if work is not available at my minimum price miner stays idle. And can someone please tell the formula for setting diff per MH/s, on x11 or overall on any algo, if it's default. THANKS
May 13, 2014, 10:15:10 AM
Even setting the password as x i'm not getting any accepted shares. (x11 on port 3336)
Dev?
Dev?
May 13, 2014, 09:39:39 AM
@dev, is there a table or a formula to set the diff for the hasrate I own. For example what diff for 8.6 Mh/s on x11
also, once the price was not available, sgminer stood idle, didnt switch to my backup pools. I'm using the newest SPH-sgminer you've recommended.
May 13, 2014, 09:38:24 AM
Use darkcoin miner: https://bitcointalk.org/index.php?topic=475795.0;all
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u yourbtcaddrhere -p x -I 18 -g 4 -w 128
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u yourbtcaddrhere -p x -I 18 -g 4 -w 128
When set " -p p=price " 100% reject
May 13, 2014, 09:28:40 AM
The only thing that comes to my mind is that this miner is modifying ntime. We don't allow modified ntimes, because we have no methods to evaluate whether modified ntime would be accepted by remote pool or not. There should be a way to force miner not to modify ntime; in fact, there is plenty of extranonce2 size so the ntime doesn't have to be modified. Guess that is the change compared to older miner.
ntime is modifed. As is valid on all good pools.kano ... have you incorporated the "idle bug" fix in your builds that is mentioned here?
Bummer. There are still some strange issues going on with my AntMiner S1s working against the pool with "price" thresholds.
I just came home and found my two test AntMiner S1s hung ... they *said* the NiceHash pool was alive ... but they were NOT mining it ... and they were NOT mining my backup pools.
Both were mining earlier in the day, and then when the 0.06 contracts expired, they fell back to the backup pools. That is where they were when I left the house. I come home and realized they were in some strange state ... not mining NiceHash nor the backup pools.
I had to restart the miners, and then they immediately jumped back to the backup pools as there are no 0.06 contracts.
Something is broken ...
I just came home and found my two test AntMiner S1s hung ... they *said* the NiceHash pool was alive ... but they were NOT mining it ... and they were NOT mining my backup pools.
Both were mining earlier in the day, and then when the 0.06 contracts expired, they fell back to the backup pools. That is where they were when I left the house. I come home and realized they were in some strange state ... not mining NiceHash nor the backup pools.
I had to restart the miners, and then they immediately jumped back to the backup pools as there are no 0.06 contracts.
Something is broken ...
ckolivas informed me, that idlebug is fixed in latest cgminer. Do you use latest cgminer?
May 13, 2014, 09:27:36 AM
Bummer. There are still some strange issues going on with my AntMiner S1s working against the pool with "price" thresholds.
I just came home and found my two test AntMiner S1s hung ... they *said* the NiceHash pool was alive ... but they were NOT mining it ... and they were NOT mining my backup pools.
Both were mining earlier in the day, and then when the 0.06 contracts expired, they fell back to the backup pools. That is where they were when I left the house. I come home and realized they were in some strange state ... not mining NiceHash nor the backup pools.
I had to restart the miners, and then they immediately jumped back to the backup pools as there are no 0.06 contracts.
Something is broken ...
I just came home and found my two test AntMiner S1s hung ... they *said* the NiceHash pool was alive ... but they were NOT mining it ... and they were NOT mining my backup pools.
Both were mining earlier in the day, and then when the 0.06 contracts expired, they fell back to the backup pools. That is where they were when I left the house. I come home and realized they were in some strange state ... not mining NiceHash nor the backup pools.
I had to restart the miners, and then they immediately jumped back to the backup pools as there are no 0.06 contracts.
Something is broken ...
ckolivas informed me, that idlebug is fixed in latest cgminer. Do you use latest cgminer?
I'm using the latest cgminer from user "kano" who wrote to you above ... he has been making the builds for the AntMiner S1. Do you have details of the fix/build that ckolivas made so that we can ensure that kano adds it?
May 13, 2014, 09:07:32 AM
@dev, is there a table or a formula to set the diff for the hasrate I own. For example what diff for 8.6 Mh/s on x11
May 13, 2014, 08:11:03 AM
Use darkcoin miner: https://bitcointalk.org/index.php?topic=475795.0;all
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u yourbtcaddrhere -p x -I 18 -g 4 -w 128
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u yourbtcaddrhere -p x -I 18 -g 4 -w 128
I get waiting for work to become available.
price not set. used -p x as the password.
not getting any work from pool
Jump to: