Topic: python OpenCL bitcoin miner - page 38. (Read 1239072 times)

Where are you getting these .debs from?

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

Anyone found a block with this new kernel on this miner? I know difficulty recently went up but my last block found was on my 5870 with the previous kernel on 01/24/22 11:46... more time has elapsed than I would have expected.

@m0mchil: Man, you are a genius! Still not accepting donations?

I am getting extra 10khash/s on my 4850: was ~65Mhash/s, now ~75Mhash/s
On the 5850 got extra 8~- up from 292Mhash/s to 300Mhash/s

OS on both: Windows XP

I'm getting an extra 10-20khash/s on my 5970. Kudos sir.

Thanks for the update on the miner, I was using the previous version of the ArtForz, and was getting approximately 332khash/sec, with your update I'm getting ~340khash/sec, so certainly an improvement!

Miner is now fixed. It found blocks on testnet. Added verification of kernel result in host.

I will highly appreciate any reports about hash speed with this version.

This is nice urban legend. With current drivers, it isn't true (this issue is probably related to some ancient drivers). I had also 5970 miner on Win and without problem.


Nice trick! I failed to connect second 5970 to my Win box on the same issue. Now I'm running Linux, but it was a pain (related to non-problem setup of single 5970 on Windows).

Here's what I've observed with a 5970 and now a 5870 as well.  Hope it helps someone.  First and foremost, a few posts back someone noted to use the "Known Best Settings".  I added the -f5 switch and I went from about 560Mhash/sec to consistently over 600Mhash/sec on the 5970 alone. 

Next, the first post in this thread says . . .
"5970 is actually two 5870s with internal crossfire. OpenCL doesn't work with crossfire. It must be switched off. You can't switch it off on Windows. For now, 5970 can be used fully on Linux only."
I have used the 5970 for over a month on Windows 7 and get results from both cores, about 300Mhash/sec each.  So I don't know what that comment is all about.

Next, I finally was happy with my results with the 5970 and I can never leave well enough alone.  So I bought a 5870 tonight and threw that into my motherboard as well.  At first I was getting "Disabled Adapter" in Catalyst Control Center, although I could see the third GPU (now as GPU #1) in MSI Afterburner.  It did nothing and just sat there very cool.  poblcm only recognized the two 5970 cores and the CPU.  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.

Is there a guide on how to compile poclbm on windows from source? Or rather, a step-by-step guide on installing python, required packages, and then executing the source?

I can't seem to find one, but I believe I saw one before. All current windows guides just direct you to use the pre-compiled binary.

My fork has been reverted.

Hello all,

New here to the BC scene, I've everything setup successfully with the pOpenCL miner, but have just 2 questions if anyone could fill me in I wasnt able to find much information on:

1) What exactly is the -w / workspace variable doing? I understand where it's pulling the value from in OpenCL, but how does adjusting this effect the process?
2) I've tuned the -w variable down as best I know how to attempt using BC, (running @ -w 62) so I can try to run this in the background while working. It's using 100% of the CPU. Not a huge problem I just saw someone here mentioning it shouldn't be that high? Any ideas on what might be the cause?

Ok, just confirmed... latest version is good only with 'difficulty = 1'. Working properly only on slush's pool.

Please revert to previous version for mining solo. I'm working on a fix.

On testnet I got only a "invalid or state" error message. Has anybody successfully mined a Block with the new Software?

Updated to use ArtForz kernel. Lowered default 'frames' to 30.

I am seeing biggest improvement on linux, Stream 2.1, 2x5970 - ~5%

Thanks ArtForz, tcatm

http://pastebin.com/v98gWWLc (port of ArtForz's code)

567 Mhash/s on a 5970 @ 725 MHz

sad that it still doesn't run both 5970 cores,
i'm still forced to use poclbm_py2exe_20101126 on GPU2 (which runs fine, except it crashes, or just stops working from time to time, at least on the pool).

I made some pool related changes - socket timeout is now 5 seconds to avoid solving some jobs more than once. Exception handling should be somewhat better too.

Hi geebus.  I suspect this is an OpenCL issue since I see the same behavior on Linux.  Have you tried backing the clocks down?  Others have reported that things are more stable if not overclocking.  I decided to just dedicate some machines to mining.  They tend to be unstable even when browsing flash-enabled web pages.

I'm having an odd issue, seeing if anyone else has seen it...

On my HD6950 running m0mchill's miner, I get ~300Mhash/s and it runs relatively well until I open any other program that uses video acceleration, at which point, my display freezes. To elaborate, my PC doesn't freeze. I can remote desktop into the box, and likewise view my account activity on Slush's pool and see I'm still submitting shares, but the display itself is frozen. Running puddinpop's rpcminer I see the same situation, but his will eventually crash, driver will reset and I get a nice event viewer log for atiocl.dll crashing.

Running Windows 7 Ultimate x86, Sapphire HD6950 (tried with BIOS mod to 6970 as well) with Catalyst 10.12a and Stream SDK 2.3. This configuration seems the most stable out of all, but still occurs.

I've also tried the following:
Catalyst 10.10 / Stream 2.1
Catalyst 10.12 / Stream 2.2
Catalyst 10.12 / Stream 2.3
Catalyst 10.12a / Stream 2.2
Catalyst 11.1a / Stream 2.3

Issue occurs regardless of driver/stream configuration. I am running HDMI digital out on my card.

I don't know if this is an issue of how the OpenCL miners are handling the calls to atiocl.dll, a digital-out issue, or a driver/stream config issue. Any help would be greatly appreciated though.