|
Title: Miner Running, but No Shares? Post by: tvynr on February 05, 2013, 06:38:56 PM I just set my little mining rig back up after a year of downtime. I'm having some strange trouble making progress, though. It's a Debian Wheezy box and OpenCL is running properly; poclbm and cgminer both report ~175Mh/s from my 5750. But I never seem to register any shares, which strikes me as odd. I've tried both poclbm and cgminer on both Slush and Eligius; both times, the miner ran for a couple hours and I scored nothing. Does anyone have any idea what I might be doing wrong? Everything seems fine, except that the shares are neither accepted nor rejected. Please see the following output from cgminer for an example:
Code: [2013-02-05 13:37:39] (5s):187.8M (avg):178.2Mh/s | Q:23 A:0 R:0 HW:0 E:0% U:0.0/m That line is after about 20 minutes of runtime. Does anyone have any thoughts? Title: Re: Miner Running, but No Shares? Post by: Gabi on February 05, 2013, 07:37:17 PM Did you checked the shares on the pool website? Check your worker there
Title: Re: Miner Running, but No Shares? Post by: tvynr on February 05, 2013, 08:46:07 PM I did check both pools' websites; I my worker showed no shares completed. :(
I was using the AMD APP SDK v2.1 to do my mining. I tried upgrading to v2.4. Unfortunately, cgminer built on this machine under v2.4 produced a segmentation fault; poclbm, meanwhile, kept claiming that PyOpenCL was not available (despite the fact that it was fine before). By happenstance in mucking about with the environment variables, I accidentally got things running... but it's not pretty. cgminer still won't work, but poclbm will run if I set LD_LIBRARY_PATH to the v2.1 SDK but set the ATISTREAMSDKROOT to the v2.4 SDK. I'm not sure why this strange hybrid environment is working, but it is. Unfortunately, it's working at a reduced hashing speed: 167MH/s instead of 175MH/s. I'll live with that for now. Also, cgminer was behaving strangely; I tried to use "-k" to set the kernel but it ignored that flag and went with phatk (which it then complained about because it seemed to think I was running SDK v2.6, which I hadn't even downloaded). Fun times. :-P |