|
BitLex
|
 |
October 30, 2010, 01:01:37 AM |
|
while running standalone, non-forwarded, it's 8connections
while addnode'd, it's 8connections,
while connect'ed to forwarded node, it's only one.
what also might help is just running on different (but forwarded) ports,
as mentioned before silly me isn't able to compile/patch, so i'm not able to try yet.
|
|
|
|
|
|
|
"In a nutshell, the network works like a distributed
timestamp server, stamping the first transaction to spend a coin. It
takes advantage of the nature of information being easy to spread but
hard to stifle." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
BitLex
|
|
October 30, 2010, 01:46:16 AM |
|
i usually start 'em all using addnode, these getblock-lags just happened quite often lately, so i tried using the connect-switch, here's a screeny* of 2 nodes seem to be connected to forwarded-node, both show only 1 connection, the higher blockcount is, the lower isn't, it sometimes even tells me, drops to 0connections for a sec, then back to 1, but still doesnt get any new blocks. same happens when both are addnode'd and showing 8connections, connections drop below 8 and no more blocks are downloaded, mining doesnt stop though, lots of wasted energy, at least it's green. * from front to back - GPU mining to (addnode'd) remote node (not on screen) - HD-miner-node -connect=<ip> (idle) - a random node -connect=<ip> (idle, running in VM) about half an hour after the shot was taken, the random node still hasnt loaded any blocks, it's not that it's always the VM that lags blocks though, sometimes it's the other way around. |
|
|
|
|
BitLex
|
|
October 30, 2010, 04:05:21 PM |
|
here's another unusual behaviour, a lost block. the GTX-miner found 2blocks, both show the proof-of-work found...generated 50.00 in the debug.log, but it seems only one of them made it into my wallet.
|
|
|
|
|
BitLex
|
|
October 30, 2010, 04:36:29 PM |
|
yeah, i also noticed that some blocks need some time to show up, i already restarted bitcoin, hoping it might materialize somehow,  but it didn't. first time i noticed this, hopefully the last too. |
|
|
|
|
BitLex
|
|
October 30, 2010, 08:10:26 PM |
|
...about deleting the block chain, and having the client re download it to see if it adds that block....
i just tried not a completely new, but <80.000blocks chain and re-downloading, the block is still missing. |
|
|
|
|
m0mchil (OP)
|
|
October 30, 2010, 09:14:43 PM |
|
The block won't show up. This happens when the network discovered block just after last request for work by the miner. This is the drawback of the pull manner in which getwork... works. The probability for this to happen is 1/60 with ask rate of 10 seconds and 1/120 with ask rate of 5 seconds. It will be better if work is provided in 'push' manner, but I didn't want to complicate the client with separate server thread.
|
|
|
|
|
BitLex
|
|
October 30, 2010, 10:00:26 PM |
|
ok, thanks, so it's nothing to worry about, no big deal anyway, GTX already found a new one, she's lucky lately.  |
|
|
|
|
dust
|
|
October 30, 2010, 10:55:47 PM |
|
I was generating some blocks today on a 5970 and I noticed that both instances of the the miner claimed to have found the same block (see attached image) The main bitcoin client only counts them once (as it should.) Does anyone know what is happening? I am running with default settings and -f 30.
|
|
|
|
|
m0mchil (OP)
|
|
October 31, 2010, 06:23:39 AM |
|
Well, this is not good. I will take a look to figure it out.
|
|
|
|
|
m0mchil (OP)
|
|
October 31, 2010, 08:17:19 AM |
|
Sorry guys, I screwed it with the update to SVN 170. There is a bug in getwork patch that makes poclbm useless with more than a single instance. Until this is fixed anyone using more than one instance should use previous version of the patch (against SVN 166). Win32 binary bitcoin-getwork-svn166-win32.7z |
|
|
|
|
brocktice
|
|
November 01, 2010, 01:10:20 AM |
|
Hey, anyone interested in discussing mining, especially with this miner, please join us in #bitcoin-mining on freenode IRC.
I think it'd be a good idea for everyone to be on the same page, and currently most of the mining discussion is happening in #bitcoin-dev, which may not be appropriate.
|
|
|
|
|
m0mchil (OP)
|
|
November 01, 2010, 10:15:50 AM |
|
Just fixed problem with getwork (different miners were showing same results). Updated to SVN 173. See for windows build in first post.
|
|
|
|
zipslack
Newbie
 Offline
Activity: 43
Merit: 0
|
|
November 02, 2010, 02:51:15 AM |
|
Thank you for your hard work, m0mchil! I seem to have this working properly on my GeForce 8800 GTS. I was pretty proud of my 32000 khash/s until I saw what some of you guys are getting.  |
|
|
|
|
|
brocktice
|
|
November 02, 2010, 03:27:12 PM |
|
Wow, zipslack, that's almost as much as I get on my GTS 250!
|
|
|
|
fenpark15
Newbie
Offline
Activity: 4
Merit: 0
|
|
November 02, 2010, 11:11:55 PM |
|
Sorry, I'm behind the curve. I am running the pocl binary (Win 7 64) and it says "Unable to communicate with bitcoin RPC" I have tried installing json-rpc in my Python26 directory using: setup.py install and it seems to complete without error. I already have checked my ATI 4600 drivers and ATI Stream so that Open CL is available.
Also, what user name and password are we supposed to use?
Again, I apologize if these questions are dumb. Until today my only experience with bitcoin is the GUI client hashing on my CPU (4600 k/s = not enough).
|
|
|
|
|
fenpark15
Newbie
Offline
Activity: 4
Merit: 0
|
|
November 03, 2010, 12:09:39 AM |
|
I was on Bitcoin client 3.08 beta and now have also installed and tried 3.14 beta. My bitcoin.conf file is located in directory "c:\Users\<my Windows user name>\AppData\Roaming\Bitcoin" It contains 2 lines with syntax : rcpuser=<my unique user name> rcppassword=<my unique password> I am running poclbm from a windows command line with syntax: poclbm.exe --user=<username> --pass=<password> It recognizes my CPU and GPU, then when I choose one, I get the "Unable to communicate with bitcoin RPC" Thank you in advance for any help. |
|
|
|
|
|
BitLex
|
|
November 03, 2010, 01:32:14 AM |
|
Did you build your client yourself?
it needs to have the getwork-patch included, so if you didn't,
just grab the win32-binary in the first post of this thread (works fine for me on 64bit XP&win7).
If you did (compile with patch, or grab),
you need to start the bitcoin-client with the -server switch (maybe -rpcallowip=<IP> if a miner is running on a remote machine).
|
|
|
|
xxmalouinxx
Newbie
Offline
Activity: 26
Merit: 0
|
|
November 03, 2010, 02:29:32 AM |
|
Like BitLex told, I think it's the getwork-patch. Just replace the old bitcoin.exe by the one from the getwork and it should work. Enjoy your Bitcoin !
Malouin
|
|
|
|
|
SmokeTooMuch
Legendary
Offline
Activity: 860
Merit: 1021
|
|
November 03, 2010, 01:11:09 PM |
|
I was on Bitcoin client 3.08 beta and now have also installed and tried 3.14 beta. My bitcoin.conf file is located in directory "c:\Users\<my Windows user name>\AppData\Roaming\Bitcoin" It contains 2 lines with syntax : rcpuser=<my unique user name> rcppassword=<my unique password> I am running poclbm from a windows command line with syntax: poclbm.exe --user=<username> --pass=<password> It recognizes my CPU and GPU, then when I choose one, I get the "Unable to communicate with bitcoin RPC" Thank you in advance for any help. Hmm, are you aware of that you have to start bitcoin in server mode for this to work ? |
|
|
|
|
brocktice
|
|
November 03, 2010, 01:20:45 PM |
|
Got my new 5970 and it's only showing half performance it should. I'm on Linux with SDK 2.1 and catalyst drivers 10.10. I know others have seen this problem, but I don't know whether I've seen a resolution. Does anyone know how to fix it?
|
|
|
|
|
