Literally just got these
05/02/2011 22:00, 2a07e960, accepted
05/02/2011 22:00, fe7439af, accepted
05/02/2011 22:01, 2a07e960, invalid or stale
05/02/2011 22:01, fe7439af, invalid or stale
05/02/2011 22:01, 2a07e960, invalid or stale
05/02/2011 22:01, fe7439af, invalid or stale
05/02/2011 22:01, 2a07e960, invalid or stale
05/02/2011 22:01, fe7439af, invalid or stale
This is on a stock miner....no mods of any kind.
6 getworks were requested, and the answer found were repeats.
Topic: python OpenCL bitcoin miner - page 37. (Read 1239072 times)
I'm still seeing several invalid stale hashes being submitted.
Any idea as to why?
Any idea as to why?
Maybe because they are really stale? http://blockexplorer.com/block/00000000000018cf119be227dcf0d7403b20dc9b8fa0c3d6bc9022c65baf9a39
I'm still seeing several invalid stale hashes being submitted.
05/02/2011 16:12, 3725321b, accepted
05/02/2011 16:13, b794eb73, invalid or stale
05/02/2011 16:13, 898ceca7, invalid or stale
05/02/2011 16:13, bde1a5f3, invalid or stale
05/02/2011 16:14, 0a07cf1a, accepted
Any idea as to why?
05/02/2011 16:12, 3725321b, accepted
05/02/2011 16:13, b794eb73, invalid or stale
05/02/2011 16:13, 898ceca7, invalid or stale
05/02/2011 16:13, bde1a5f3, invalid or stale
05/02/2011 16:14, 0a07cf1a, accepted
Any idea as to why?
30Mhash/s slower after the update.
HD6950 went from 226M to 196M.
HD6950 went from 226M to 196M.
No obvious change for me ( 5850 ), still getting between 249M - 251M.
No change for me either, getting the exact same, no slowdown.
@LobsterMan, the default '-f' is 30 now, use '-f 60' (previous default) or more if it hogs your desktop
My hash rate is actually somewhat higher with the new version, I went from about 50mhash/s per gtx275 to around 58mhash/s, but my desktop is somewhat less responsive with the miners running now where it was not before
30Mhash/s slower after the update.
HD6950 went from 226M to 196M.
HD6950 went from 226M to 196M.
No obvious change for me ( 5850 ), still getting between 249M - 251M.
30Mhash/s slower after the update.
HD6950 went from 226M to 196M.
HD6950 went from 226M to 196M.
This makes me not want to update.
30Mhash/s slower after the update.
HD6950 went from 226M to 196M.
HD6950 went from 226M to 196M.
Fixed issue with lost results due to single output per kernel run (thanks OneFixt, ArtForz).
Ack, it broke compatibility with my daemon.py but I got it all fixed up. Thanks for the fixes!
Fixed issue with lost results due to single output per kernel run (thanks OneFixt, ArtForz).
Where is the guide for compiling (not just running from executable) poclbm on Windows? Last time I needed to do it on a Windows box was when the 2011-11-26 version was out, but now the only guide I can seem to find for windows is the "You only need this if you cant RTFM" py2exe guide...
What software needs to be installed?
What addons for Python?
What dependencies for PyOpenCL?
Versions?
Presently, I followed the install guide for PyOpenCL (updating for newer versions) and installed json-rpc from the SVN, but every time I try to run 'python poclbm.py' with any flags, it crashes.
Using:
Windows 7 Ultimate x64
Stream 2.3 (also tried with 2.1 and 2.2)
Catalyst 11.1 (also tried with 10.11 and 10.12)
Python 2.6.6 (32-bit)
Boost 1.44
MSVC 2008 (9.0)
Numpy 1.5.1
SciPy 0.8.0
SetupTools 0.6c11
What software needs to be installed?
What addons for Python?
What dependencies for PyOpenCL?
Versions?
Presently, I followed the install guide for PyOpenCL (updating for newer versions) and installed json-rpc from the SVN, but every time I try to run 'python poclbm.py' with any flags, it crashes.
Using:
Windows 7 Ultimate x64
Stream 2.3 (also tried with 2.1 and 2.2)
Catalyst 11.1 (also tried with 10.11 and 10.12)
Python 2.6.6 (32-bit)
Boost 1.44
MSVC 2008 (9.0)
Numpy 1.5.1
SciPy 0.8.0
SetupTools 0.6c11
After looking at posts on Google as far back as 2008, someone said, "Plug in another monitor". Not having another monitor, I plugged in my monitor to the 5870 instead. Now, the 5870 GPU was the only core recognized by poblcm along with the CPU. So I ran poblcm with a device=1 and it worked! Then I unplugged the monitor from the 5870 and replugged it into the 5970. Now, even though the 5870 was the disabled adapter again, poblcm was still running on the 5870. Then I ran poblcm again on device=1 and device=0 and both of the 5970 cores were running alongside the 5870, for a total of about 875Mhash/sec. Pretty good. So that's just FYI for anyone running multiple 5870's, 5970's or combinations thereof. I wish there was a way to get Catalyst Control Center, or ATI Stream, or whatever ATI driver it is to enumerate all three cores so I would not have to unplug and replug the monitor into different cards every time I want to run poblcm on the 5870 and 5970 at the same time. I would suspect this would be a similar problem, and a similar solution, for running poblcm on two 5970's on Windows.
I can confirm this trick works on my 5970 + 5770 setup. First start 2 poblcm instances for the 5970, then unplug monitor, plug into 5770, start instance of poblcm. 5970 + 5770 goodness!
~800000 k/hash/s
Note: Many off-topic posts about mining efficiency were moved here.
Had you read it, you would know that it wasn't off topic. Slush kept talking about the pool, but we're talking about the miner and the pool.
Note: Many off-topic posts about mining efficiency were moved here.
Can anyone tell me why this miner would be using 100% CPU for me on a Core2Duo e8400 3.69ghz processor? I think something changed in a version update in the last week or so since I started with the miner,
I'm not mining on my CPU, I'm mining with my 5970, 1 miner client ran for each core. Each client process is using 50% of the cpu... I've just seen people mention it should be using much lower CPU resources if not mining w/ it.
Using Stream 2.3
I'm not mining on my CPU, I'm mining with my 5970, 1 miner client ran for each core. Each client process is using 50% of the cpu... I've just seen people mention it should be using much lower CPU resources if not mining w/ it.
Using Stream 2.3
I'm under windows! Everything works pretty well right now if I was to be honest, since I'm using 2 different miners, one for CUDA and the poclbm for OpenCL. But having to switch to another miner was soooo sad I loved the m0mchil one
I loved the m0mchil one 
bitk, are you using Linux or Windows? I was unsuccessful at getting nvidia and ATI cards working on the same machine under Linux. I wasn't even trying to mine with the nvidia card, just use it for the GUI. According to ArtForz, the nvidia and fglrx drivers don't play well together.
Hello m0mchil.
I've been using your client a lot lately with a GTS 250 card...
Today I got a new shiny ATI card and I can't use it with your miner, even if they get recognized by software like GPU Caps Viewer! Let me explain...
I got both VGAs on my PC, ofc there's no "Crossfire" or "SLI" since they are from different vendors. The problem arises since the nvidia uses the CUDA OpenCL, the ATI uses (of course) the Stream impementation. This way, my 2 physical cards reside on 2 different cl_platform....
Now, I never touched python in my entire life... but those 2 lines looks... suspicious
I really suspect this is what's giving me problems: I can't see the ATI as listed in the devices I can choose! I could physically swap the cards, or maybe unistall and reinstal all the video drivers so that the first OpenCL platform is the ATI one, but this doesn't really look an elegant solution IMHO
Suggestions for solving my problem are welcome! EG: patches, or how to compile 2 different executables for windows.
I've been using your client a lot lately with a GTS 250 card...
Today I got a new shiny ATI card and I can't use it with your miner, even if they get recognized by software like GPU Caps Viewer! Let me explain...
I got both VGAs on my PC, ofc there's no "Crossfire" or "SLI" since they are from different vendors. The problem arises since the nvidia uses the CUDA OpenCL, the ATI uses (of course) the Stream impementation. This way, my 2 physical cards reside on 2 different cl_platform....
Now, I never touched python in my entire life... but those 2 lines looks... suspicious
Code:
platform = cl.get_platforms()[0]
devices = platform.get_devices()
I really suspect this is what's giving me problems: I can't see the ATI as listed in the devices I can choose! I could physically swap the cards, or maybe unistall and reinstal all the video drivers so that the first OpenCL platform is the ATI one, but this doesn't really look an elegant solution IMHO
Suggestions for solving my problem are welcome!
EG: patches, or how to compile 2 different executables for windows. Can anyone explain a bit on the advantages of Pool mining with Slush's pool vs Mining solo?
I'm solo mining and am still pretty new to this scene, and I've seen the details on HOW to mine in Slush's pool, but I haven't grasped the advantages if any, for my situation
I'm solo mining and am still pretty new to this scene, and I've seen the details on HOW to mine in Slush's pool, but I haven't grasped the advantages if any, for my situation
What are you using to mine?
- If it's a slower machine you'd benefit a lot more by joining a mining pool as it may be weeks or months before you mint your first block. By joining a pool you'd have a steady stream of coins.
- Faster systems, you have a choice. Sometimes there is network latency issues with retrieving/sending work and/or sending timed out invalid work. When I say fast I would say at least a single 5970 to qualify.
Jump to: