Diablo-D3/DiabloMiner

Refresh work: work expired and invalid solution on CentOS with Radeon 5450

Closed this issue · 3 comments

Hi,

Hopefully this is the right place for this question.

What I'm running:

lspci | grep Radeon 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cedar PRO [Radeon HD 5450/6350]

The card is a Radeon HD 5450 (I know, nothing fancy).

cat /etc/redhat-release
CentOS release 6.4 (Final)

uname -a

2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Mar 13 00:26:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I'm running the latest build of DiabloMiner from GitHub.

My issue is that I keep getting 'Refresh work: work expired' and worryingly 'Invalid solution 1 from Cedar (#1)/0, possible driver or hardware issue'

Paste of output is below. Hopefully you can help :). Many thanks.

[4/15/13 6:38:23 PM] Started
[4/15/13 6:38:23 PM] Connecting to: http://pit.deepbit.net:8332/
[4/15/13 6:38:24 PM] Using AMD Accelerated Parallel Processing OpenCL 1.2 AMD-APP (1113.2)
[4/15/13 6:38:27 PM] BFI_INT patching enabled, disabling hardware check errors
[4/15/13 6:38:27 PM] Added Cedar (#1) (2 CU, local work size of 128)
[4/15/13 6:38:29 PM] DEBUG: pit.deepbit.net: Enabling long poll support
[4/15/13 6:39:28 PM] DEBUG: Cedar (#1)/0: Refresh work: work expired
[4/15/13 6:39:29 PM] DEBUG: Cedar (#1)/1: Refresh work: work expired
[4/15/13 6:39:33 PM] DEBUG: Spurious CL_INVALID_KERNEL_ARGS error, ignoring
[4/15/13 6:40:28 PM] DEBUG: Cedar (#1)/0: Refresh work: work expired
[4/15/13 6:40:29 PM] DEBUG: Cedar (#1)/1: Refresh work: work expired
[4/15/13 6:41:28 PM] DEBUG: Cedar (#1)/0: Refresh work: work expired
[4/15/13 6:41:29 PM] DEBUG: Cedar (#1)/1: Refresh work: work expired
[4/15/13 6:42:28 PM] DEBUG: Cedar (#1)/0: Refresh work: work expired
[4/15/13 6:42:29 PM] DEBUG: Cedar (#1)/1: Refresh work: work expired
[4/15/13 6:43:28 PM] DEBUG: Cedar (#1)/0: Refresh work: work expired
[4/15/13 6:43:29 PM] DEBUG: Cedar (#1)/1: Refresh work: work expired
[4/15/13 6:44:10 PM] DEBUG: Invalid solution 1 from Cedar (#1)/0, possible driver or hardware issue

Thats completely normal output when you have debug on.

Okay, interesting. I have had about 15 mhash for 24hrs with 0 accepted blocks, 0 rejected blocks and a few hw errors. I'm running rpc-miner on my Mac (CPU mining) with about 0.2 mhash and I get many accepted blocks. Any ideas what could be wrong? Many thanks.

Unless the only shares you produce are hardware errors, then it sounds like the problem is with either your drivers or Deepbit. I also recommend you switch to p2pool.