MissouriMiner
|
|
November 20, 2014, 03:30:34 AM Last edit: November 23, 2014, 06:39:26 AM by MissouriMiner |
|
BITMAIN Promotion plan for S3+, S4 and C1 $50 coupon for S3+, $400 coupon for S4 and $50 coupon for C1 are issued to customers who ever bought miners from BITMAIN or our official distributors I have (12) S4 $400 coupons, and (4) S3+ $50 coupons and (4) C1 $50 coupons. Expire the 30th. 50 cents on the dollar seems fair to me. PM me if you are interested. Dan That's not fair. You got them for free. In fact, almost everyone here has them for free and many people will gladly give them away for free. Good luck selling at that price. I thought the same thing. They are going for 99 cents buy-it-now on eBay. I'll give away mine. I have coupons for all 3 models.
|
|
|
|
faetos
|
|
November 20, 2014, 04:37:57 AM |
|
BITMAIN Promotion plan for S3+, S4 and C1 $50 coupon for S3+, $400 coupon for S4 and $50 coupon for C1 are issued to customers who ever bought miners from BITMAIN or our official distributors I have (12) S4 $400 coupons, and (4) S3+ $50 coupons and (4) C1 $50 coupons. Expire the 30th. 50 cents on the dollar seems fair to me. PM me if you are interested. Dan That's not fair. You got them for free. In fact, almost everyone here has them for free and many people will gladly give them away for free. Good luck selling at that price. I thought the same thing. They are going for 99 cents buy-it-now on eBay. Too bad they are only good for 2 weeks. I'll give away mine. I have coupons for all 3 models. What makes me mad is I'm the dumbass who bought an S4 at full price the day before the coupons were given out. I pleaded with Bitmain to give me a break, but they said no. That's a case of "penny-wise and pound-foolish." I wouldn't be hard on yourself. BitMain should have done the right thing. Now that $50 they saved has cost them probably 10x that in bad press.
|
|
|
|
jackbox
Legendary
Offline
Activity: 1246
Merit: 1024
|
|
November 20, 2014, 05:14:57 AM |
|
BITMAIN Promotion plan for S3+, S4 and C1 $50 coupon for S3+, $400 coupon for S4 and $50 coupon for C1 are issued to customers who ever bought miners from BITMAIN or our official distributors I have (12) S4 $400 coupons, and (4) S3+ $50 coupons and (4) C1 $50 coupons. Expire the 30th. 50 cents on the dollar seems fair to me. PM me if you are interested. Dan That's not fair. You got them for free. In fact, almost everyone here has them for free and many people will gladly give them away for free. Good luck selling at that price. They saved $400. S4 coupons are $400 off, I thought the same thing. They are going for 99 cents buy-it-now on eBay. Too bad they are only good for 2 weeks. I'll give away mine. I have coupons for all 3 models. What makes me mad is I'm the dumbass who bought an S4 at full price the day before the coupons were given out. I pleaded with Bitmain to give me a break, but they said no. That's a case of "penny-wise and pound-foolish." I wouldn't be hard on yourself. BitMain should have done the right thing. Now that $50 they saved has cost them probably 10x that in bad press.
|
|
|
|
cloh76
|
|
November 20, 2014, 10:45:24 AM |
|
BITMAIN Promotion plan for S3+, S4 and C1 $50 coupon for S3+, $400 coupon for S4 and $50 coupon for C1 are issued to customers who ever bought miners from BITMAIN or our official distributors I have (12) S4 $400 coupons, and (4) S3+ $50 coupons and (4) C1 $50 coupons. Expire the 30th. 50 cents on the dollar seems fair to me. PM me if you are interested. Dan That's not fair. You got them for free. In fact, almost everyone here has them for free and many people will gladly give them away for free. Good luck selling at that price. I thought the same thing. They are going for 99 cents buy-it-now on eBay. Too bad they are only good for 2 weeks. I'll give away mine. I have coupons for all 3 models. What makes me mad is I'm the dumbass who bought an S4 at full price the day before the coupons were given out. I pleaded with Bitmain to give me a break, but they said no. That's a case of "penny-wise and pound-foolish." I wouldn't be hard on yourself. BitMain should have done the right thing. Now that $50 they saved has cost them probably 10x that in bad press. It's $400 off an S4. I wouldn't be as upset if it was only $50. My timing was so close. It was just a matter of hours before the coupons arrived. This is just my typical bad luck. I won't complain anymore. I look at it this way - We will all eventually get screwed one way or another. We may buy them -400 USD now, but eventually a newer miner will come out that will be more efficient at an even lower cost. Plus we wont ROI with the difficulty exponentially increasing. It's a viscous never ending cycle.
|
[ BTC Donations: 13RNJdT72WEd1FsT3CwdJ6jy9NAa7Hsb54 ]
|
|
|
hurricandave
Legendary
Offline
Activity: 966
Merit: 1003
|
|
November 20, 2014, 11:02:27 AM |
|
In the midnight hour babe, I want MORE MORE MOREHOR, ...........
|
|
|
|
iglasses
Legendary
Offline
Activity: 1148
Merit: 1000
|
|
November 20, 2014, 01:47:45 PM |
|
Yea I have... C1 x14 S3 x14 S4 x42
and they can keep all of them! WTF am I supposed to do with a stupid $50 coupon (.14BTC) on a device that they now want .588BTC for and then another fucking $135 to ship!!
Bitmain...you guys were good but selling overpriced hardware that you've already mined a profit with and now making a profit on shipping too is just too much for this guy.
|
I only have a signature because I'm allowed.
|
|
|
dankefoss
Newbie
Offline
Activity: 22
Merit: 0
|
|
November 20, 2014, 05:26:05 PM |
|
FYI - All my posts got deleted by Bitman. More customer ill will in my opinion.
Dan
|
|
|
|
brush242
|
|
November 20, 2014, 06:03:32 PM |
|
That's a case of "penny-wise and pound-foolish." I wouldn't be hard on yourself. BitMain should have done the right thing. Now that $50 they saved has cost them probably 10x that in bad press. Yeah, you can tell because the batches aren't selling out. Oh wait....
|
Support sidehack miner development. Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
|
|
|
solitude
|
|
November 20, 2014, 07:44:27 PM |
|
I have some Bitmain coupons for sale:
1. AntMiner C1 Coupon 50 USD x 2
2. AntMiner S3+ Coupon 50 USD x 2
3. AntMiner S4 Coupon 400 USD x 6
Good through November 30th
I'm not sure what they're worth, send me a message if you're interested.
|
Hardly anyone speaks English on this forum.
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
November 20, 2014, 08:18:43 PM |
|
I've got a bunch of coupons up for grabs. I'd like to keep one of each for myself, just in case ... but the rest I'm happy to give away. PM if you want one, and of what type if interested. First come first serve.
M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
nelsoncs
Newbie
Offline
Activity: 7
Merit: 0
|
|
November 20, 2014, 08:24:02 PM |
|
Problem with antminer s3+ solo. My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead. I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes. here is my cgminer command line (<> indicate substitutions to protect the innocent): --bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O <somename>:<some password> --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096 here is my bitcoin-qt/bitcoind command line: -datadir=/home/<some_user_path>.bitcoin -rpcuser=<somename> -rpcpassword=<some password> -blocknotify=%s -alertnotify=%s The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT". Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
|
|
|
|
MissouriMiner
|
|
November 20, 2014, 08:36:06 PM |
|
Problem with antminer s3+ solo. My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead. I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes. here is my cgminer command line (<> indicate substitutions to protect the innocent): --bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O <somename>:<some password> --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096 here is my bitcoin-qt/bitcoind command line: -datadir=/home/<some_user_path>.bitcoin -rpcuser=<somename> -rpcpassword=<some password> -blocknotify=%s -alertnotify=%s The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT". Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon. Looks like your missing --rpcallowip=<Your S3 IP> with bitcoind.
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
November 20, 2014, 08:44:09 PM |
|
Problem with antminer s3+ solo. My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead. I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes. here is my cgminer command line (<> indicate substitutions to protect the innocent): --bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O <somename>:<some password> --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096 here is my bitcoin-qt/bitcoind command line: -datadir=/home/<some_user_path>.bitcoin -rpcuser=<somename> -rpcpassword=<some password> -blocknotify=%s -alertnotify=%s The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT". Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon. I'm pretty sure Bitcoin is not capable of providing work fast enough to any of the recent ASICs. Furthermore, I'm pretty sure Bitcoin only supports the "getwork" protocol, not stratum. So essentially your S3 is starving for work. I think, but I'm not sure, that there's a way to run cgminer as a "proxy" that your S3 can point to for work. cgminer takes care of converting the getwork data from Bitcoin to stratum for your S3 to use. I don't think you should try to be using cgminer to mine against your S3 as you have it written. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
nelsoncs
Newbie
Offline
Activity: 7
Merit: 0
|
|
November 20, 2014, 08:54:31 PM |
|
Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now: bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good. Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST Nmap scan report for 192.168.0.2 Host is up (0.0000050s latency). Not shown: 9997 closed ports PORT STATE SERVICE 22/tcp open ssh 8200/tcp open trivnet1 8332/tcp open unknown 8333/tcp open bitcoin
|
|
|
|
MissouriMiner
|
|
November 20, 2014, 09:21:08 PM |
|
Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now: bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good. Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST Nmap scan report for 192.168.0.2 Host is up (0.0000050s latency). Not shown: 9997 closed ports PORT STATE SERVICE 22/tcp open ssh 8200/tcp open trivnet1 8332/tcp open unknown 8333/tcp open bitcoin Do you have a firewall running on the system running bitcoind? I have mine on a Linux host and had to add an iptables entry. And I added listen=1 to bitcoin.conf. I've tried solo mining with and S3 (and default cgminer code) and it works fine.
|
|
|
|
iglasses
Legendary
Offline
Activity: 1148
Merit: 1000
|
|
November 20, 2014, 09:51:22 PM |
|
Problem with antminer s3+ solo. My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead. I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes. here is my cgminer command line (<> indicate substitutions to protect the innocent): --bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O <somename>:<some password> --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096 here is my bitcoin-qt/bitcoind command line: -datadir=/home/<some_user_path>.bitcoin -rpcuser=<somename> -rpcpassword=<some password> -blocknotify=%s -alertnotify=%s The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT". Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon. I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person.
|
I only have a signature because I'm allowed.
|
|
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
November 20, 2014, 09:57:56 PM |
|
I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person.
They run great on p2pool, have 8 S3's and a few S1's running for a while with 0 issues...
|
|
|
|
nelsoncs
Newbie
Offline
Activity: 7
Merit: 0
|
|
November 20, 2014, 10:00:25 PM |
|
Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now: bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good. Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST Nmap scan report for 192.168.0.2 Host is up (0.0000050s latency). Not shown: 9997 closed ports PORT STATE SERVICE 22/tcp open ssh 8200/tcp open trivnet1 8332/tcp open unknown 8333/tcp open bitcoin Do you have a firewall running on the system running bitcoind? I have mine on a Linux host and had to add an iptables entry. And I added listen=1 to bitcoin.conf. I've tried solo mining with and S3 (and default cgminer code) and it works fine. yes, this is a linux machine but it is on my local network and the antminers are also on the same network, all are behind the same external firewall. sudo iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination So, my ip_table is empty, no rules. Tried -listen=1 but getting the same behaviour. Thanks for the suggestion.
|
|
|
|
nelsoncs
Newbie
Offline
Activity: 7
Merit: 0
|
|
November 20, 2014, 10:07:53 PM |
|
I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person.
They run great on p2pool, have 8 S3's and a few S1's running for a while with 0 issues... I may give p2pool a try, I have more than one machine, so I can dedicate one to serving upa pool if I need to. As for antminers being "hopeless", the reason that I am trying this is I have seen my machines Find two blocks during the last four months, for which the pool I was in gave me diddly squat. Not that I have any thing against the pool, it is a great service, but obviously if I only find on more block the rest of my life (well antminer's life) I will be soooo much better off.
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
November 20, 2014, 10:13:07 PM |
|
Problem with antminer s3+ solo. My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead. I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes. here is my cgminer command line (<> indicate substitutions to protect the innocent): --bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O <somename>:<some password> --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096 here is my bitcoin-qt/bitcoind command line: -datadir=/home/<some_user_path>.bitcoin -rpcuser=<somename> -rpcpassword=<some password> -blocknotify=%s -alertnotify=%s The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT". Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon. The way you describe this, it sounds like you are running cgminer somewhere outside of your Ants. I'm pretty sure that's not going to work for you. Try editing the cgminer config inside the Ant to have the solo mining options to point it to your Bitcoin instance: cgminer -o http://<bitcoin IP>:<bitcoin port> -u <username> -p <password> --btc-address <your address> Also, CK (author of cgminer) has a public "solo mining pool" up.. if you don't mind the 0.5% fee: https://bitcointalk.org/index.php?topic=763510.0M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
|