Author

Topic: Newbie: guiminer issues (Read 1738 times)

legendary
Activity: 3472
Merit: 4801
April 26, 2013, 10:39:04 AM
#2
bump
legendary
Activity: 3472
Merit: 4801
April 25, 2013, 01:16:45 AM
#1
I'm not much of an expert at mining.  Can someone from this forum help out the following Newbie.  I've linked to his post from the Newbie forum here, please post updates and questions there so he can respond:

https://bitcointalksearch.org/topic/having-a-hard-time-setting-up-guiminer-186070

Hey guys, so sorry that my first post on the forums is due to a problem I'm having but I'm pretty stumped :/

So I have the 2012-11-18 version of guiminer and I'd like to mine on my gtx480 in the BTC Guild (using the US-Stratum server). All my video card drivers are up to date. When I attempt to mine with the default setting (CPU Affinity left all blank except for the first core) and the correct username, etc. I get "NameError: name 'OpenCLMiner' is not defined" in the lower left corner and am continually stuck at "Starting..." on the right corner.
When I make a new CUDA miner (I downloaded CUDA from Nvidia this morning as well), I keep all the setting the same, but when I click "Start mining!" nothing happens at all. The button is depressed, but the status at the bottom right still reads "Stopped" and I see no change in the window.

I've searched a bit about the the NameError (though I obviously still couldn't solve the issue), but haven't really been able to find anything about the CUDA miner issue. Any help would be greatly appreciated!

I got that same error. I haven't been able to figure out what it means, but I think it may have something to do with no OpenCL device being available on the computer. Have you checked your video card for OpenCL compatibility?
Yeah, from what I've read my GPU driver should include OpenCL compatibility so I figured updating that would solve the issue. Apparently not.
I've generally associated OpenCL with ATI cards and CUDA with nVidia cards which is why I thought the CUDA Miner may be the way to go. Unfortunately, that was problematic as well.
Let me know if you find a fix for the issue!
Jump to: