Topic: python OpenCL bitcoin miner - page 36. (Read 1239035 times)

Weird, I just tried 2.2, but same result.

My fault, didn't notice
I read somewhere that you should use ati stream 2.1 or 2.2, not the latest one.

You're right, I see now, the only options I have is:
But no GPU? Why is that?

Hi,
get rid of "http://:8332" from the host line, and put the port number after the "--port=" switch.

Hello, I currently have 2x6950 in crossfire, i7 2600k, 11.1a drivers, ATi Stream 2.3.

When I try to run it with the following parems:
poclbm.exe --user=x --pass=y --host=http://mining.bitcoin.cz:8332 -d 0

•      Cayman
[1]     Cayman
[2]            Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz

It gives me this error:

InvalidURL: nonnumeric port: ''
Unexpected error:
Traceback (most recent call last):
  File "BitcoinMiner.pyc", line 171, in mine
  File "BitcoinMiner.pyc", line 157, in getwork
  File "jsonrpc\proxy.pyc", line 42, in __call__
  File "urllib.pyc", line 89, in urlopen
  File "urllib.pyc", line 208, in open
  File "urllib.pyc", line 334, in open_http
  File "httplib.pyc", line 1008, in __init__
  File "httplib.pyc", line 656, in __init__
  File "httplib.pyc", line 673, in _set_hostport

Any help? Thanks!

Is anyone else having trouble, with not finding any blocks at all with the last 2 versions of this miner post 2/1/11?

I've mined for well over 5 or 6 days with nothing and I'm running about 630khash between the 2 cores on my 5970. I'm just using -v -w 128 -f 120........... I haven't found a block in what seems like far too long.

Device 0 is your CPU, most likely.  Try device=1 or start the miner with no options and it will list the devices.

I just get 3500 khash/s

--device=0 -f 5 -v -w 128 (tried different combinations like f 30 and w 256 etc)

What am I doing wrong?

What is the -askrate flag doing? How does it help if set to something non-default? thanks for any input.

OpenCL HOWTO FOR FEDORA 14 LINUX

Here are some notes which may be useful to anyone who wishes to mine for bitcoins on Fedora 14 Linux. It's simpler than the instructions I posted for Fedora 12, because Bitcoin now supports the 'getwork' call and therefore doesn't need to be recompiled.

===

Check your software versions, and upgrade as necessary. The gcc compiler needs to be 4.x (for PyOpenCL), and Python needs to be 2.4 or newer (again, for PyOpenCL), but not Python 3.x.


You need to have either the full kernel source, or the kernel headers (because the ATI GPU driver is installed by compiling a kernel module). You also need the Python headers.


===

Update your display driver.

I followed the instructions from here:
http://gofedora.com/how-to-install-ati-catalyst-fglrx-98-drivers-fedora-11/
except that I used the version 11.1 11.2 of the ATI Catalyst Display Driver for Linux x86 from here:
http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.42&lang=English

Supposedly some of the installation steps are no longer needed with version 11.1, but I wasn't completely certain which ones, so I did them all anyway.

===

Get the ATI Stream SDK v2.1 (NOT any later version, according to brocktice), from here: http://developer.amd.com/gpu/ATIStreamSDK/pages/ATIStreamSDK-Archive.aspx

You need two downloads from that page: the Linux SDK (32-bit or 64-bit according to your version of Linux), plus icd-registration.tgz

Untar the SDK anywhere convenient. Add these lines to your .bash_profile file (in your login directory):


These pathnames will vary slightly if you have a 32-bit Fedora installation.

Move icd-registration.tgz into your root directory and (as root) untar it from there. It puts some essential config files into /etc.

If you like, follow the documentation that is included in the SDK to compile the examples. Execute ati-stream-sdk-v2.1-lnx64/samples/opencl/bin/x86_64/CLInfo to check that things are working and that your GPU card is detected.

===

Install the Python OpenCL module (PyOpenCL). Broadly, follow the instructions here:
http://wiki.tiker.net/PyOpenCL/Installation/Linux

However, in step 2 I couldn't install the Numpy dependency this way. Instead I ran "System | Administration | Add/Remove Software", then searched for numpy and installed it.

In step 3, the OpenCL headers and libraries weren't found, so I had to use the longer configure.py example and provide explicit paths.

I don't think the "Boost C++" libraries are required for this version of PyOpenCL.

===

Install the JSON-RPC module for Python. This was straightforward using the instructions here:
http://json-rpc.org/wiki/python-json-rpc

===

Go to m0mchil's Git repository:
https://github.com/m0mchil/poclbm

Click the "Download" button. Download and unpack these files anywhere convenient. Change poclbm.py to executable and check that it's working:


===

If you don't already have a file bitcoin.conf in your ~/.bitcoin directory, create one and put a username and password in it:


Go back to the bitcoin/bin/64 directory and start bitcoin in rpc server mode:


Go to the directory where you built poclbm.py and run it:


It will tell you which devices it can see. Choose the one that's not your CPU, and add that one to the command line with the "-d" switch:


Watch the khash/s figures with sweet delight, and enjoy the few moments before the roar of your GPU fan starts up.

Many thanks to m0mchil and the many others who have offered code or helpful tips.

(PS: If you upgrade your kernel, the ATI driver might hang on startup. If this happens, boot into runlevel 3, delete /etc/X11/xorg.conf , reboot and reinstall the ATI driver.)

Ok I understand, thanks for the help Cryptoman and BitLex

Yes and yes.  
it's not that you're making any "progress" that could be lost,
you start from scratch with any single hash, like drawing lottery-tickets a few thousand/million times a second,
you either get a winning-ticket, or a loser. won't help you to keep the loser in your pocket.

Finding a correct hash is a completely random event, and the probability depends only on the hash rate and the total amount of time dedicated to mining.  You lose a little time having to reconnect to the network and retrieve the latest transactions, but it's pretty insignificant.  A 280 Mhash/s rig turned on for 12 hours a day should perform the same as a 140 Mhash/s rig running 24 hours a day.

I think you misunderstood my question. I do keep both bitcoin.exe and poclbm.exe running at the same time, what I'm wondering is what happens if I restart the programs, or reboot my computer. Will I start again from scratch or does the mining continue where it left off?

Both m0mchil's python program and bitcoind must be running continuously for mining to take place.  I have no idea how to run or monitor detached processes on Windows, but my guess is that you have to keep the command windows open.  Maybe someone with Windows experience will chime in here.

Aye a couple showed up when I let it run for a while longer, thanks

Another question, it's ok to close poclbm.exe and bitcoin, correct? It isn't necessary to keep them running non-stop untill a block is solved?

The last time I looked, the testnet difficulty factor was around 350.  Using that number as a guide, 280 Mhash/s should yield a block on average every 1.5 hours.

Hi. I'm trying to get this to work, and want to check it with the "testnet" I've heard about.

What I've done:
Followed the guide. After starting bitcon.exe -server and the .bat-file as described I get a cmd window with the hash speed showing.
I then copied the bitcoin.conf to %appdata%/bitcoin/testnet, ran bitcoin.exe -server -testnet and then launced the .bat-file as before. Again the hash speed is showing in a cmd-window, but after about 30 minutes with ~280000 khash/s I've still not gotten any messages about completed blocks. My impression was that that should happen very quicly on the testnet. What am I doing wrong?

Thanks for any help.

There are two ways to get something like this - first one is using ask rate of more than ~12 seconds with an overclocked 5870 (stock max -a is 10 seconds). Other one is network problems triggering resubmission of results - this mechanism is removed since last version. Since you said it happened with stock miner I vote for the latter. 

So getworks are now going stale even faster....thanks for clarifying.