|
teknohog
|
 |
December 09, 2010, 05:17:27 PM |
|
The latest revision seems to have a problem with vectors. So far, I get about 59 Mhash/s without, and 60.7 with, on a HD5570. However, the latest version slows down to 53.7 with vectors, while it stays at 59 without them.
|
|
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
m0mchil (OP)
|
|
December 09, 2010, 07:30:29 PM |
|
Please provide full information about your platform - driver, SDK, OS. Did you tried with different values for worksize, '-f'? With catalyst 10.11, SDK 2.2 on windows I actually see slight improvement with vectors against previous version.
|
|
|
|
|
teknohog
|
|
December 09, 2010, 08:07:39 PM
Last edit: December 09, 2010, 10:23:21 PM by teknohog |
|
Please provide full information about your platform - driver, SDK, OS. Did you tried with different values for worksize, '-f'? With catalyst 10.11, SDK 2.2 on windows I actually see slight improvement with vectors against previous version.
First of all, going back to commit 99c57637ca0d1db70187 fixes the issue, so the problem seems to be isolated to the last revision. The system is a Gentoo Linux, kernel 2.6.36.1, with catalyst 10.11 drivers and SDK 2.2. I have not tried any other performance options besides -v and -f 1. Work size 256 seems to bring the performance back to the expected levels, or at least very close. I should probably keep trying more of these options  Edit: I chose 256 as it is the default/maximum for my card. Smaller powers of two seem to work better, -w 64 gives 63.0 Mhash/s. Edit 2: It seems I had failed to update back to the latest version for these tests (I'm a complete newbie with git ). The issue with the latest version is not much improved by the -w options. |
|
|
|
kwukduck
Legendary
 Offline
Activity: 1937
Merit: 1001
|
|
December 10, 2010, 12:45:01 AM
Last edit: December 10, 2010, 01:24:06 AM by kwukduck |
|
I'm trying gpu mining with my new gtx 470 on win7-64
but i get only 77 khash/s
i tried changing -w and -v, doesn't change much on -w, changing -v crashes the process.
i'd estimate this card would generate about 300000khash
any idea what could be wrong?
[EDIT]
Issue resolved, seems nVidia just has realy bad OpenCL performance
[/EDIT]
|
14b8PdeWLqK3yi3PrNHMmCvSmvDEKEBh3E
|
|
|
berserk9779
Newbie
Offline
Activity: 9
Merit: 0
|
|
December 10, 2010, 04:36:37 PM |
|
I have pyopencl installed from packaged deb on launchpad, and when I try to run I get: File "poclbm.py", line 6
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
^
SyntaxError: invalid syntax
thanks |
|
|
|
|
davout
Legendary
Offline
Activity: 1372
Merit: 1007
1davout
|
|
December 10, 2010, 04:42:53 PM |
|
I have pyopencl installed from packaged deb on launchpad, and when I try to run I get: File "poclbm.py", line 6
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
^
SyntaxError: invalid syntax
thanks lol |
|
|
|
berserk9779
Newbie
Offline
Activity: 9
Merit: 0
|
|
December 10, 2010, 05:26:55 PM |
|
I am a linux noob and don't know anything about python.
And the how to above is for ATI, I am on Nvidia GT9800
|
|
|
|
|
berserk9779
Newbie
Offline
Activity: 9
Merit: 0
|
|
December 10, 2010, 05:57:55 PM |
|
Now that the noobish mistake is solved I get: bruno@bruno-desktop:~/bitcoin-0.3.17$ python ./poclbm.py
File "./poclbm.py", line 27
print 'No device specified or device not found, use -d to specify one of the following\n'
^
IndentationError: expected an indented block |
|
|
|
|
|
|
davout
Legendary
Offline
Activity: 1372
Merit: 1007
1davout
|
|
December 10, 2010, 08:47:46 PM |
|
Now that the noobish mistake is solved I get: bruno@bruno-desktop:~/bitcoin-0.3.17$ python ./poclbm.py
File "./poclbm.py", line 27
print 'No device specified or device not found, use -d to specify one of the following\n'
^
IndentationError: expected an indented block No offense intended , I asked questions that probably seemed stupid to the people that answered me. Now I'm happily crunching at 600mh/s thanks to the people that helped me out. Maybe you should simply clone the git repo so you can transparently get upgrades and forget about this kind of issues altogether You need to apt-get install git-core and then git clone <url> and then you can just git pull from time to time to upgrade. |
|
|
|
berserk9779
Newbie
Offline
Activity: 9
Merit: 0
|
|
December 12, 2010, 07:55:46 AM |
|
It runs for 4-5 seconds, then asks me for my user-password again. ~/bitcoinminer$ python ./poclbm.py -d 0
Enter username for jsonrpc at 127.0.0.1:8332: berserk9779
Enter password for berserk9779 in jsonrpc at 127.0.0.1:8332:
20842 khash/sEnter username for jsonrpc at 127.0.0.1:8332: berserk9779
Enter password for berserk9779 in jsonrpc at 127.0.0.1:8332:
20847 khash/sEnter username for jsonrpc at 127.0.0.1:8332: By the way, before poclbm I need to run bitcoind. Is there an option to have it running with the gui open? |
|
|
|
|
ribuck
Donator
Hero Member
Offline
Activity: 826
Merit: 1039
|
|
December 12, 2010, 09:29:13 AM |
|
It runs for 4-5 seconds, then asks me for my user-password again.
If you supply the user-password on the command line, you won't get asked for it again: ./poclbm.py --user=whatever --pass=whatever That's not ideal from a security point of view, perhaps someone will suggest a better way. By the way, before poclbm I need to run bitcoind. Is there an option to have it running with the gui open?
You can use bitcoin instead of bitcoind, provided you are using a recent version of Bitcoin (0.3.15 or later) and the latest version of poclbm. This gives you the GUI, plus OpenCL mining. |
|
|
|
|
davout
Legendary
Offline
Activity: 1372
Merit: 1007
1davout
|
|
December 12, 2010, 09:46:38 AM |
|
It runs for 4-5 seconds, then asks me for my user-password again.
If you supply the user-password on the command line, you won't get asked for it again: ./poclbm.py --user=whatever --pass=whatever That's not ideal from a security point of view, perhaps someone will suggest a better way. By the way, before poclbm I need to run bitcoind. Is there an option to have it running with the gui open?
You can use bitcoin instead of bitcoind, provided you are using a recent version of Bitcoin (0.3.15 or later) and the latest version of poclbm. This gives you the GUI, plus OpenCL mining. Or you can just edit poclbm source for a quick slightly securer dirty hack |
|
|
|
berserk9779
Newbie
Offline
Activity: 9
Merit: 0
|
|
December 12, 2010, 06:48:03 PM |
|
It's finally up and running. 22 Mhash on average on a Nvidia 9800GT But it only works with bitcoind. And I had to start it like that: ./bitcoind -rpcuser=berserk9779 -rpcpassword= and ./poclbm.py -d 0 --user=berserk9779 --pass= |
|
|
|
|
Mahkul
Sr. Member
Offline
Activity: 434
Merit: 250
Every saint has a past. Every sinner has a future.
|
|
December 13, 2010, 12:14:33 AM |
|
Has anyone tried connecting to the bitcoin-server from a different machine using m0mchil's miner?
I am using Windows binary poclbm.exe. I have my bitcoin -server running on a local machine and have no problems connecting from poclbm.exe and generating using my GPU on the same local machine.
When I try to connect to the same bitcoin -server from a different PC using:
poclbm --user=user --pass=password --host=remoteip --port=8332
I keep on getting the message "Unable to communicate with bitcoin RPC".
The firewall on the PC running bitcoin.exe is disabled.
Is what I want to achieve at all possible?
|
|
|
|
|
berserk9779
Newbie
Offline
Activity: 9
Merit: 0
|
|
December 13, 2010, 12:36:44 AM |
|
I think you should substitute remoteip for the actual private IP of the local machine where the server is running (usually 192.168.x.x)
|
|
|
|
|
|
m0mchil (OP)
|
|
December 13, 2010, 05:10:52 AM |
|
From bitcoin docs # By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*
|
|
|
|
Mahkul
Sr. Member
Offline
Activity: 434
Merit: 250
Every saint has a past. Every sinner has a future.
|
|
December 13, 2010, 08:15:29 AM |
|
From bitcoin docs # By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*
Thanks m0mchil. RTFM. :/ |
|
|
|
|
Mahkul
Sr. Member
Offline
Activity: 434
Merit: 250
Every saint has a past. Every sinner has a future.
|
|
December 13, 2010, 08:18:29 PM |
|
It's me again... I managed to connect to my bitcoin -server from two different remote machines. With the third one I am getting the following error: pyopencl.RuntimeError: CommandQueue failed: out of host memory Does this mean my server has no more memory to accept more miners? |
|
|
|
|
|
m0mchil (OP)
|
|
December 14, 2010, 10:54:22 AM |
|
Added update of block time every second and support for targets < 32 bits. Output now shows block hash and acceptance status.
|
|
|
|
|
