 Show Posts
|
|
Pages: « 1 [2]
|
|
I'll be purchasing this unit. Due to tysat's staff/moderator status, I'm foregoing escrow to expedite the sale.
This is my first transaction on the forums, so I'm not sure exactly how this works. I'll send the coins as soon as tysat posts here confirming the deal (public accountability).
|
|
|
|
|
Has anyone run this miner with GTX 590s? They're not listed on the results spreadsheet.
I'm especially interested in finding out whether cudaMiner will correctly identify the two GPUs - one GTX 590 is basically two 580s stapled together and underclocked.
|
|
|
|
im interested in a group buy on the Avalon ASIC chips. The minimum order QTY is 10,000 @ 780 BTC. Im ready to put in 50 BTC which is about 640 chips. Can a trusted forum member start organizing a group buy and see if there is enough interest to meet the minimum order quantity?
I'm in for a similar amount. I think there's more than enough interest to reach the minimum order size, but an experienced and trusted community member will definitely need to take the lead on the purchase, as no one will be willing to put that many coins in the hands of someone relatively unknown. |
|
|
|
Trust me, you want to compile this for 32 bit.
Why can't it be 64-bit? I can only chroot to gentoo-prefix (which does not support multilib) to compile cudaminer. A 32-bit compile on a 64-bit host is possible but very tricky thanks mainly to libcurl. Here's a link to a 32-bit Linux binary from the April 14 code. Give it a try. Hopefully you won't run into shared library issues... https://www.dropbox.com/s/twjdug4l0z4rnz0/cudaminer_414.gzI was unable to compile cudaMiner myself (Ubuntu 12.04), so I tried your build. It fails with a shared library error on libcurl. I installed libcurl4-gnutls-dev, which had no effect. I removed it, and installed libcurl4-openssl-dev:i386, which changed a huge number of things to 32-bit. Your binary now fails on a different shared library: libcudart.so.5.0. Help on using gchill's binary, or on compiling cudaMiner under Ubuntu will be greatly appreciated! |
|
|
|
|
I'm building a gaming desktop that will also be used for mining. I've picked up 3x 7950s for the GPUs, and will be going with an Intel i5 for the CPU.
I've done a lot of searching here, but all of the recommendations are for cheap boards being used for mining-only rigs.
Which motherboards are good for both "power user/gamer" use and mining use?
|
|
|
|
What distro are you using? If Debian or Ubuntu (or some other derivative that uses APT), have you installed build-essential and automake? $ sudo apt-get install automake build-essential libcurl4-openssl-dev You got the tarball from Github, not from the Github repo. You only need autogen.sh if you cloned the repository using git. Thanks for the quick reply! I eventually noticed that autogen was in the repo and started from a repo clone instead of the tarball. I got stuck on a different error when running configure, but adding the libcurl library (in my case, libcurl-devel.x86_64) did the trick. |
|
|
|
Searched the forums, couldn't find anything about an error I'm getting on compilation.
[cpuminer-2.2.3]$ ./configure CFLAGS="-O3"
checking build system type... Invalid configuration `x86_64-unknown-linux-': machine `x86_64-unknown-linux' not recognized
Same things happens if I run configure with no args. The README says to run autogen.sh if building from the Github repo (which is where I got the source), but that file wasn't included in the tarball. Anyone else encountering the same issue? I'm not sure how to modify config.sub or which alternate args to pass to configure to resolve this... |
|
|
|
|
I'm trying to do some mining on NVidia cards (yes, I know they stink!) under Linux. Mining in a pool is nice to have, but not required.
I feel like most of the information I'm finding links to out-of-date mining software or to Windows-only applications.
Could someone please recommend a good CUDA miner? I'm totally stumped here.
Thanks in advance!
|
|
|
|
Threads are still melting my brain. Can I get the best of both worlds by doing something like this? def start_thread(function):
t = Thread(target=function)
t.setDaemon(True)
t.start()
return t
def connect(S):
#setup
start_thread(thread_func)
def reconnect(S):
S.ws.close()
S.connect()
def thread_func(S):
S.ws = create_connection(S.ws_url)
S.run = True
start_thread(keepalive_func)
msg = S.ws.recv()
while msg is not None and S.run:
S.process(msg)
try:
msg = S.ws.recv()
except:
if S.run:
S.reconnect()
break
else:
if run:
S.reconnect()
def keepalive_func():
while S.run:
try:
S.ws.send('2::')
except:
S.ws.close()
break
sleep(S.heartbeat)
The keepalive thread does nothing except send heartbeats and close the connection in the event of an exception. Thread_func reconnects if it hits an exception or exits the while loop, if run is True. Thoughts? |
|
|
|
|
runeks and molecular:
I've reviewed and begun using a combination of your codebases. I have a few questions and comments.
- Why the different approaches to your keepalive threads? Molecular's version is more concise. Is it an issue with the ws.recv() delay on disconnect?
- Is there a reason for using the urllib2 module? The requests module is much nicer.
- Why aren't you using the logging module instead of print statements?
- Consider making your SocketIO classes more generic and creating an MTGox sub-class which inherits from it, passing in event handlers (on_connect, on_msg, etc). This will make things easier if and when other exchanges add streaming APIs.
- I strongly recommend reducing your client heartbeat interval. I've set mine to 85% of the value given by the server, rounded down.
|
|
|
|
I'd like to participate on this thread. I made a previous contribution on the Newbie board, which another member copied over. This method is a bit inefficient.  |
|
|
|
Your code is for using the old http api to do commands?
I ask since now you can use the (more or less) same commands over the streaming api too..
Yes, this is for the HTTP API. It's much simpler to implement than the streaming API. It's also good to have a backup, as reports suggest the streaming API is somewhat unstable. I'm rewriting the streaming code from here as well. |
|
|
|
I found this thread to be extremely helpful, so I'm returning the favor by posting an improved and simplified version of the code. Unfortunately, my forum account is limited to the Newbie section. Mods, please move this post to the thread above. from hashlib import sha512
from hmac import HMAC
from base64 import b64decode, b64encode
from urllib import urlencode
from time import time
import requests
class MTGox:
def __init__(self, key, secret, base):
self.key = key
self.secret = b64decode(secret)
self.base = base
def query(self, path, args={}):
args['nonce'] = int(time()*100000)
headers = {
'User-Agent': 'BitcoinTalk',
'Rest-Key': self.key,
'Rest-Sign': b64encode(str(HMAC(self.secret, urlencode(args), sha512).digest()))
}
r = requests.post(self.base + path, data=args, headers=headers)
print r.text
|
|
|
|
|
