 Show Posts
|
|
Pages: [1] 2 3 »
|
Over 120,000 people use a Bitcoin wallet on their iPhones and iPads. Petition for Apple to rescind their ban. Sign here: http://chn.ge/1jiZQzi now! Share with anyone you know and get the word out. |
|
|
|
Up to nearly 100,000 viewers. Congrats guys!
Congrats to you for creating the useful guide  Much better than the flyer manual (no longer?) provided with the Blades. I know, seriously, a one pager that says the ip and how to factory reset? Thanks Dogie. |
|
|
|
Overclocking requires overvolting, which increases power dissipation quite a bit. So, overheating which can lead to roasting the ASICs.
Gotcha |
|
|
|
|
What happens if you overclock too much?
|
|
|
|
|
Wait is Black Arrow a Chinese company? If so what'll happen to all the btc payments with the big Chinese btc shakeup. Are they still accepting btc?
|
|
|
|
|
Guys, for those of you who like fighting with the command line shell, use stratum. For everyone else, just use getwork or gbt protocals.
|
|
|
|
Been told it could be problems with the Stratum proxy as just changed the miners details to a different pool and works fine.
is there a way to still mine on Slush without the proxy ?
Cheers
OR can anyone recommend the best pool for the Blades, Cheers
I recently solved the same problem everyone else is having with my two v2's: Instead of connecting to eligius (my fav pool-- gives you more info than most others) via getwork, I used their gbt server. 'gbt.mining.eligius.st' with port 9337. (Remember to put two values in ports and servers) Everything's been working for 24 hours. Hope this helps! |
|
|
|
|
Chill Black Arrow! Seriously, these are some of your customers?!
|
|
|
|
That's what I was wondering... |
|
|
|
By the time that miner is released, the difficulty could be sky high,its best to buy miners there and then instead of preordering.
Exactly. But Black Arrow will make a lot of money off people willing to pay now. I almost wish I could preorder one now, and then sell my place in line to someone else in Jan/Feb  |
|
|
|
okay I got it thx 9337,9337 gbt.mining.eligius.st, gbt.mining.eligius.st Great! I left the detailed instructions up for someone else... |
|
|
|
Problem solved! Here's what I did: Instead of using getwork, I used the gbt server and port on eligius. For some reason I just can't get getwork to work any more. Input these, delete the cookies from the previous config and restart. I'll update with my hashrates tomorrow. Currently (a few minutes after startup I'm doing 20.4 gh/s). Thanks to all who contributed. This successfully proves the hypothesis that n00bs can, indeed, learn Could you be very specific please... What did you type into which fields? Sure. IPs: 192.168.1.200 (.201 for the second blade) Mask: default Gateway: default WEB port: 8000 Primary and secondary DNS: default Ports: 9337,9337 Server addresses: gbt.mining.eligius.st,gbt.mining.eligius.st user:pass:1K*my address*Q23:pwd,1K*my address*Q23:pwd Hope this helps! I reset both of mine to fac default, but I don't think I need to do that. |
|
|
|
Problem solved! Here's what I did: Instead of using getwork, I used the gbt server and port on eligius. For some reason I just can't get getwork to work any more. Input these, delete the cookies from the previous config and restart. I'll update with my hashrates tomorrow. Currently (a few minutes after startup I'm doing 20.4 gh/s). Thanks to all who contributed. This successfully proves the hypothesis that n00bs can, indeed, learn |
|
|
|
If you're trying to connect to a remote pool's getwork, you'll need their server address in the Pool addresses field, their getwork port in the Pool ports field, and an accurate Gateway so outgoing internet traffic knows where to start routing.
My initial reply was to pluMmet, using the mining_proxy command line. If you're using the mining proxy on a local machine, it might help to change the default getwork port (-gp option) and make sure to match the setting with the Pool ports field in your blade. If for some reason a local bitcoind is running on your machine, or some other software is using port 8332, it could hose up communications. That's a simple thing to rule out.
Capiche. thx, I'll give it a try. |
|
|
|
Got it. However, the port on the site is 8337 (just checked). Can I go ahead and use something else? I thought that was the port on their server? I'd give you a screenshot but I had trouble uploading. Sorry, I'm still (really) a noob at all this  |
|
|
|
No, the getwork port that is usually 8332. The -gp option in mining_proxy changes this, and it needs to match the blade's "Pool ports" setting.
Okay, do you still have to input twice (I assume so?) |
|
|
|
Have you tried changing the getwork port -gp in case something on your local machine is using it?
The 'Web Port' that's usually 8000? |
|
|
|
Will do, thanks.
It's a serious issue as I've tried lots of getwork pools and the blades don't work on any of them.
Totally-- the weird thing is they were designed for getwork. I even did a factory reset, reconfigged and it still doesn't work. I'll maybe restart my router, and then I'll go to stratum though I'm not optimistic. |
|
|
|
Also, minimum order is 10, and no group buys.
yeah, not so customer freindly. way to keep bitcoin decentralized guys  It's really kind of stupid, cause 10 x-1s = 1 x-3. |
|
|
|
What's your command line look like for the proxy?
I wanted it to use Eligius so I used (Dogies suggestion): mining_proxy.py -o mining.eligius.st -p 3334 -cu 1yourSweetCoinsComeToThisAddress -cp x Not only did it not work the terminal ignored that and was trying to connect to Slushs pool. I ended up just doing: mining_proxy.py which had the slushs stuff already going and the blades synced up right away. It looks like the proxy.py has been nurfed to just use slushes pool. I d/l'd two days ago for the slushes pool site and it's not .tar anymore but .zip. Still linux of course.. well py anyway. I have them running now even though slushs pool is not awarding me anything. Beyond that this is ridiculous. I had been using getwork just fine for months.. I obviously know how to do that but the blades just won't do it. v2 blades btw. Dude, I'm having the same problem with getwork-- it's so frustrating, especially when I didn't change anything, the blades just stopped connecting. Let me know if you get it figured out; I'll reciprocate if I discover what's happening. |
|
|
|
|
