Search content
Sort by
Showing 20 of 57 results by cereal7802
Re: Official FutureBit Apollo LTC Image and Support thread
Downloaded the apollo_image_1-29.img.zip image and on initial boot it went straight into the dashboard like nothing was wrong. I went to disable the donation pool and add my own and then the miner doesn't start. I only get that the api is refused and it never shows a hashrate. If I enable the donation again, it works fine. I would much rather this donation option was removed entirely. if people want to provide charity for a purchased device, then they can manually enter the info. Having it on by default and have issues where it refuses to work without it sounds like theft to me.
Update:
This doesn't look right. I suspect the interface is writing the config wrong.
{
"quota": "99;us.litecoinpool.org:3333",
"user": "USERNAMEHERE",
"pass": "PASSWORDHERE"
},
{
"quota": "1;stratum+tcp://us.litecoinpool.org:3333",
"user": "jstefanop.a1",
"pass": "a1"
}
Update:
This doesn't look right. I suspect the interface is writing the config wrong.
Code:
{
"quota": "99;us.litecoinpool.org:3333",
"user": "USERNAMEHERE",
"pass": "PASSWORDHERE"
},
{
"quota": "1;stratum+tcp://us.litecoinpool.org:3333",
"user": "jstefanop.a1",
"pass": "a1"
}
it just wont start my S2 asic with Paper clip. 6x pcie connected to asic.
when I hit the power, the fans and my PSU spin for a half a second and shuts off.
when psu connected to PC motherboard/gpu miner, all works.
http://www.seasonic.ru/tech-support/jump-start/
any help?
I have successfully 3 psu s working with paper clip gpu mining.
sry bad english.
when I hit the power, the fans and my PSU spin for a half a second and shuts off.
when psu connected to PC motherboard/gpu miner, all works.
http://www.seasonic.ru/tech-support/jump-start/
any help?
I have successfully 3 psu s working with paper clip gpu mining.
sry bad english.
Make sure you plugged all of your PCI-E power plugs the right way around. on one of my S3s i somehow managed to put 1 plug backwards and the psu would power up and down like you described as the psu would detect the terminals being reversed. simply unplugging the cable and putting it the right way round fixed it.
I'll give them a message and feel them out.
pervert...
Re: [ANN] solo.ckpool.org 0.5% fee anonymous solo bitcoin mining for everyone
Hi
can someone help with this?
I have pointed 4 of my Ants S3 to solo pool and get lot of discarted shares.
For example:
GetWorks 15
Accepted 79
Rejected 1
Discarded 2342
and best share is also very low afer few minutes.
When I point this miners for example to Slush I get:
GetWorks 19922
Accepted 152451
Rejected 337
Discarded 1934111
And best share is > 1 000 0000 after few minutes.
In solo pool is ratio Accepted / Discarded much bigger.
Thanks
can someone help with this?
I have pointed 4 of my Ants S3 to solo pool and get lot of discarted shares.
For example:
GetWorks 15
Accepted 79
Rejected 1
Discarded 2342
and best share is also very low afer few minutes.
When I point this miners for example to Slush I get:
GetWorks 19922
Accepted 152451
Rejected 337
Discarded 1934111
And best share is > 1 000 0000 after few minutes.
In solo pool is ratio Accepted / Discarded much bigger.
Thanks
Discards are a result of the S3 having a high queue setting. most people ignore it.
Does anyone have an idea what can lead to this hashrate?
http://s7.directupload.net/images/140730/j9cyswar.jpg
All chips seem to be fine. It is powered by a 1600W PSU (all 4 PCIe Cables connected), but it is only ~half of the promised hashrate.
Latest firmware is also installed...
Kind regards
http://s7.directupload.net/images/140730/j9cyswar.jpg
All chips seem to be fine. It is powered by a 1600W PSU (all 4 PCIe Cables connected), but it is only ~half of the promised hashrate.
Latest firmware is also installed...
Kind regards
Have you tried a lower diff? you seem to be discarding most of your work due to a high diff selected at ghash.io.
Interesting to checkout the real time connection screen:
One S3 is sending (UDP?) packets to:
tock9.usshc.com:123
ntp1.linuxhosted.ca:123
209.118.204.201:123
hydrogen.constant.com:123
Does any of this make sense?
One S3 is sending (UDP?) packets to:
tock9.usshc.com:123
ntp1.linuxhosted.ca:123
209.118.204.201:123
hydrogen.constant.com:123
Does any of this make sense?
NTP is for the time sync. Network Time Protocol. Why its going to ntp1.linuxhosted.ca:123 for time i dont know. Mine is set to openwrt.pool.ntp.org
I havent looked at the log tho.
openwrt.pool.ntp.org should be a round robin style dns pointer to the ntp servers selected by the openwrt people from the ntp.org pool list. you could use the default ntp.org pool if you prefer.
Ok so i`ve done that added my set up but its still not mining 
if it is anything like the S1, make sure you click save, then click save and apply and wait for the page to stop loading completely. if it doesn't start mining within 20-30 seconds, reboot the miner and it should start.
I received a reply from Bitmain a minute ago regarding their shipping procedures. They said they follow the "first to order, first to ship" method. I am hoping they'll be shipping today.
I don't buy it. My order was placed early in batch 1 but still hasn't shipped.
I suspect that my order won't ship until batch 2 is ready - it's possible that they are simply out of product.
Were you one of the people who ordered and then had their order marked as invalid because the payment took too long? i was and i think it has adjusted my queue position since my order creation time is 2014-06-30 17:37:11.0 but the payment details show 2014-06-30 19:10:49. i suspect this is why some people are delayed in their orders being shipped.
Re: ANN: BITMAIN has Tested Its 28nm Bitcoin Mining Chip BM1382
IMPORTANT.
Bitmain posted on the other S3 thread:
Bitmain posted on the other S3 thread:
to be fair, this isn't an S3 thread. this is a thread about their chips. the one you linked to is the S3 product/support thread as the title lists.
Re: Sonny Vleisides (Butterfly Labs CEO) 2014 Court Transcript [The TL/DR version]
It wouldn't surprise me if he resigned as a manager (CEO) or sold the company at this point (if he has any major ownership). for various reasons.
Not entirely sure selling the company would work to his benefit. The new owners would surely have a good case against previous management once they had internal information regarding invoices and communications. It might open them up to more issues than letting the ship burn in whatever way it does end up going. Also can't really see anyone willing to put money up for the company with its current standing in the community. even gox stands a better chance of clearing the shame of their name before BFL could.
IT would help if bitmain did not write BITCOIN MINER as custom description....
What should its description be then? Erm its just some circuits and stuff
could be like my gridseeds. "heatsink samples"
leave the stock one in it really moves a lot of air. but if it slows down to 1200 rpm it is not that loud. just add a good second fan.
I have some photos. This one shows how to add the second fan
how to power it I cut these
http://www.amazon.com/Syba-SY-CAB65007-Female-Connectors-Extension/dp/B002G1YNQS/ref=sr_1_5?ie=UTF8&qid=1398513944&sr=8-5&keywords=y+fan+cable
I have some photos. This one shows how to add the second fan
how to power it I cut these
http://www.amazon.com/Syba-SY-CAB65007-Female-Connectors-Extension/dp/B002G1YNQS/ref=sr_1_5?ie=UTF8&qid=1398513944&sr=8-5&keywords=y+fan+cable
Why would you cut up the fan connector and connect the cables into the power directly instead of using the fan header shown in your picture? since you have a 3 prong fan and not a 4 pin PWM fan, it should run at 100% just the same as what you did....
I'm not in front of mine right now..
But - when attempting to login it would loop back to the login screen. If I entered the wrong password it would spit back invalid creds (red font)... but trying to retry the good creds, it would almost seem like it would think for a second then just redirect to the login screen, blank out the creds..
I haven't tried a hard reboot (as the hashing was going just fine looking at pool stats).. I figured once my auto 6hr reboot occurred I would be able to get in.. but still haven't been able to.
I may be able to dig more up later if I have time.
Current config - was 18 miners on the PI split into two powered hubs, scrypt mode. I have 3 other PIs setup with the older version still (havent had time to reflash all card).. no issues logging in to the older ones (going thru same router/hubs/etc).
But - when attempting to login it would loop back to the login screen. If I entered the wrong password it would spit back invalid creds (red font)... but trying to retry the good creds, it would almost seem like it would think for a second then just redirect to the login screen, blank out the creds..
I haven't tried a hard reboot (as the hashing was going just fine looking at pool stats).. I figured once my auto 6hr reboot occurred I would be able to get in.. but still haven't been able to.
I may be able to dig more up later if I have time.
Current config - was 18 miners on the PI split into two powered hubs, scrypt mode. I have 3 other PIs setup with the older version still (havent had time to reflash all card).. no issues logging in to the older ones (going thru same router/hubs/etc).
sounds like what mine did. turned out the disk was full because hashra image logs a ton of stuff and doesn;t seem to cleanup the logs. perhaps it is a result of an older image being updated, but i have a script that cleans the log files now every so often.
Quote
Connect each worker in the form: [btcaddress]_[workername]
Each worker will be tracked separately for vardiff, however balances are calculated on a per-address (not username) basis!
Each worker will be tracked separately for vardiff, however balances are calculated on a per-address (not username) basis!
Is this working? I ask because although i have 3 different worker names, all 3 miners seem to change to the higher diff settings at the same time. if i kill one of the faster miners i have the diff drops to 16, but when i have both fast miners diff goes to 128 then after a bit drops to 64, then back to 128 like it it is combining the mining power and hitting a diff that is too high and then falling back when it detects the share submit rate of my miners.
Re: Neptune GB With Coinsortium .4 BTC=100 GH/s 14/30 shares, for a limited time
soniq - since this has not yet been ordered and the pre-order batch has sold out, are you still moving forward with this gb?
Hi soniq
Re Neptune first batch Sold Out
https://www.kncminer.com/news/news-71
Ugg !!
if we are unable to get on the pre-order batch I will not want to go ahead and will prefer a refund
please refund to
2.40 BTC
1DASRPF2P7Gaq5ZNmUR2KoTvQSbVyDvPac
Thanks
hardpick
I would agree that since the first batch is likely not to be available for this group buy that it would be in the best interest of everyone to be refunded. 1% fee should be waived as well since it was not really funded fully and the order was not completed in time.
WEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
http://cex.io/informer/cereal7802/8635fd5c29685f28b1b8285f56441306/
http://cex.io/informer/cereal7802/8635fd5c29685f28b1b8285f56441306/