CPU miner working but not in API output, GPU & CGminer aren't working

Chris Nochance

GPU Miner (cont'd):

   

 [2014-05-13 08:40:24] OCL 0 being re-enabled                    

 [2014-05-13 08:40:24] Attempting to reinitialize OCL 1                    

 [2014-05-13 08:40:24] OCL 1 being re-enabled                    

 [2014-05-13 08:40:24] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)                    

 [2014-05-13 08:40:24] OCL 0 failure, disabling!                    

 [2014-05-13 08:40:24] OCL 0 being disabled                    

 [2014-05-13 08:40:24] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)                    

 [2014-05-13 08:40:24] OCL 1 failure, disabling!                    

 [2014-05-13 08:40:24] OCL 1 being disabled                    

 [2014-05-13 08:40:36] Attempting to reinitialize OCL 0                    

 [2014-05-13 08:40:36] OCL 0 being re-enabled                    

 [2014-05-13 08:40:36] Attempting to reinitialize OCL 1                    

 [2014-05-13 08:40:36] OCL 1 being re-enabled                    

 [2014-05-13 08:40:36] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)                    

 [2014-05-13 08:40:36] OCL 0 failure, disabling!                    

 [2014-05-13 08:40:36] OCL 0 being disabled                    

 [2014-05-13 08:40:36] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)                    

 [2014-05-13 08:40:36] OCL 1 failure, disabling!                    

 [2014-05-13 08:40:36] OCL 1 being disabled                    

20s:  0.0 avg:  0.0 u:  0.0  h/s | A:0 R:0+0(none) HW:0/none          

20s:  0.0 avg:  0.0 u:  0.0  h/s | A:0 R:0+0(none) HW:0/none          

 [2014-05-13 08:40:59] Attempting to reinitialize OCL 0

 [2014-05-13 08:40:59] OCL 0 being re-enabled

 [2014-05-13 08:40:59] Attempting to reinitialize OCL 1

 [2014-05-13 08:40:59] OCL 1 being re-enabled

 [2014-05-13 08:40:59] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)

 [2014-05-13 08:40:59] OCL 0 failure, disabling!

 [2014-05-13 08:40:59] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)

 [2014-05-13 08:40:59] OCL 1 failure, disabling!

 [2014-05-13 08:40:59] OCL 0 being disabled

 [2014-05-13 08:40:59] OCL 1 being disabled

 [2014-05-13 08:40:59] Attempting to reinitialize OCL 0                    

 [2014-05-13 08:40:59] OCL 0 being re-enabled                    

 [2014-05-13 08:40:59] Attempting to reinitialize OCL 1                    

 [2014-05-13 08:40:59] OCL 1 being re-enabled                    

 [2014-05-13 08:40:59] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)                    

 [2014-05-13 08:40:59] OCL 0 failure, disabling!                    

 [2014-05-13 08:40:59] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)                    

 [2014-05-13 08:40:59] OCL 1 failure, disabling!                    

 [2014-05-13 08:40:59] OCL 0 being disabled                    

 [2014-05-13 08:40:59] OCL 1 being disabled                    

20s:  0.0 avg:  0.0 u:  0.0  h/s | A:0 R:0+0(none) HW:0/none

Chris Nochance

Using legacy set up seems to revert me to the panda pool?

FabulousPanda

Legacy should set you up with panda pool as a backup, but only if you enter a BTC address for rewards.

The problem with your GPU is unfortunately just that it's crapping out under the strain, that's what the -54 error means, you could try with a lower intensity or an easier coin but it's not a good sign I'm afraid!

Confused about how the CPU can be running half as fast, unless one of your processors died :S or maybe it was just reporting the speed wrong before? It could be a confusion between the speed per thread and the total speed which is those speeds combined.

Chris Nochance

Well I generally am doing other things at the same time on this machine, I've been downloading the block chain for a while now. Not to mention I probably had several large apps open & running while making these stats. My motherboard has been recently rebuilt this year, so I doubt a core has died on it. Looking at the Activity Monitor it seems to be working fine. But granted this is an older Intel core 2 duo running a 9600 card. I'm not expecting it to "scream", I'm happy w/ it "clunking along". LOL I just think it's odd that when nothing else is running how it goes "idle"? (this coming from my pool.) not from my machine. Maybe because it was taking my machine longer to solve hashes than expected? I dunno? That being said, what "intensity" do you think I should be setting this at? Too I've wanted to ask you, what about those lil usb script miners, can MacMiner run those things? or do I have to dip down to the command line? I've been trying to get Cuda miner working but... No love. any advice would be greatly appreciated! Thx.

FabulousPanda

If you're mining BTC on anything other than fast ASIC you probably will experience the pool showing you as inactive for periods as each share takes the hardware so long to solve the pool doesn't know better! MacMiner can run the gridseed hardware, that would be a better bet What problems are you running in to with cuda miner? There are guides around!

Chris Nochance

Actually I'm mining LTC if you haven't noticed? I was thinking about getting one of those little usb scriptminers I've seen on eBay. I've checked the guides, they make me feel like a 6 mo/o hammering keys on the kb when I can't get it going. I'm not claiming to be a command line guru but I can follow directions, I just don't understand error messages very well, or know what to do about them?  

Paul Coates

Check to make sure you are not behind a firewall, this includes any software firewalls or net monitors on your Mac "Little Snitch?" ... BFG tends to get touchy when it can't reach out and touch someone.

As for the NVidia GeForce 9xxx video cards, unfortunately these are known to be poor for mining... The defaults in BFGminer generally will not work and need a minor tweek... Be sure to set your GPU settings to dynamic intensity and set work size to 64 or 128, and check override default... even then expect 2-4 Kh/s per card once you have your network communications and settings issues worked out.