It has previously run in another mobo before being added to this machine as a replacement for an even old Nvidia card.  I have completely removed (per "uninstall all AMD product") the drivers and reinstalled.  Would physically removing it be any different?    The card works for normal graphics - its the only video card in the box.

Good news, bad news.  I cranked up GUIMiner and it is having the same issue of not accepting work.  At least bfgminer is giving us a hint with that error message.  Alas, I'm clueless what it means, other than my wifes machine is borked.  Down to running (3) different anti-virus programs on her machine now.

Hrm, that means my refactors didn't do it after all!

Can you post your (original checkout)'s .git/logs/HEAD file so we can figure out what the last version that worked for you was?
[/quote]

This feels like something on my end.  I've mentioned that my 3 systems are somewhat similar, so I just grabbed the binary off of miner 1, which works as expected, and tried it on miner 2 and 3.  Works on miner 1, only displays the temp on CL 0 on miners 2 & 3...

Excuse me while I go wash my hands... I'm feeling pretty dirty right now (sharing binaries across Linux boxes and all).

Be back in a few hours.

Great idea!  Unfortunately, didn't help.  Still seeing the "Failed to open Device Parameters registry key in lowl-vcom.c _vcom_devinfo_scan_windows__hubport(
):440: The system cannot find the file specified." after selecting Auto. 

Started with a fresh clone:

git clone https://github.com/luke-jr/bfgminer
cd bfgminer
./autogen.sh
./configure -enable-opencl --enable-scrypt
make -j3

And reproduced the problem.

git checkout 223df8d
make

problem still there.

git checkout 98e5076
make

problem still there.  Very weird that its working normally on one of the three machines.


git checkout 223df8d
make

problem still there.

Doing Pooled mining Bradley.  We are finding blocks every many many times a day and I see my other miners accepting shares within seconds.  But appreciate the thought.  Fixated on the error message right now.

I hate Windows, Windows hates me - its an equitable relationship...

I just spent 3 hours this morning screwing around of my wife Windows 7 machine trying to get bfgminer 64-bit to work.

I've tried the 13.9 catalyst drivers, the 13.12 ones, and the 14 beta ones.  All are having the same problem.  I actually don't think this is directly bfgminer's issue, but rather some driver, lack therefore, or other corruptions on her machine.

BFGminer will start, but not find the Radeon 5770 GPU.  If I do M-->+-->Auto it finds it, but generates the following error:

[2014-02-10 12:17:36] Failed to open Device Parameters registry key in lowl-vcom.c _vcom_devinfo_scan_windows__hubport(
):440: The system cannot find the file specified.

The card will then appear to work, but the system never accepts any work.  Over hours, I will see a few rejects.

Startup command is normal, identical to what I use on my nice logical Linux machines:

bfgminer -S opencl:auto --intensity 20 --temp-overheat 80 --temp-cutoff 100 --temp-target 80 --scrypt --gpu-fan 100 --auto-gpu -o ...

Help please.  What have I done wrong?

ps.  I want to hunt down and punish the AMD folks responsible for their Raptr code - it is not optional, and pesters you to death to install it.  Of course, I refuse, cursing it each time.

The one I pulled less than 2 hours ago?  Is there a way for me to ID what I pulled?

All the files are timestamped 2/9/2014 around 23:07 - but I'm GMT -6 (US Central).

I apologize for not really understanding git beyond how to fetch things.

Oh... I have no idea if this is significant, but miner #1, which is working as expected, has an Intel CPU.  Miners #2 and #3 that are being quirky are AMD.  Beyond that, they are pretty similar setups.

Being masochistic, I like to start my mining week out from a common spot, so I tend to pull the latest bfgminer git, install, and reboot my (3) miner machines.

Tonight being the night for such things, I found I'm having a new quirk:

Miner machine #1, with (2) GPUs, is working as expected:

 bfgminer version 3.10.0 - Started: [2014-02-09 23:32:26] - [  0 days 00:04:08]
 [M]anage devices [P]ool management [ S]ettings [D]isplay options       [H]elp [Q]uit
 Connected to multicoin.zapto.org diff 0 with stratum as user Cassey.miner1
 Block: ...2317815661a13055  Diff:1 (11.32Mh/s)  Started: [23:36:33]:37]
 ST:4  F:0  NB:6  AS:0  BW:[ 48/ 29 B/s]  E:0.00  I:15.74 BTC/hr  BS:0
 2      77.0C | 889.0/658.3/593.9kh/s | A:50 R:2+0(none) HW:0/none
-------------------------------------------------------------------------------------
 OCL 0: 73.0C | 407.7/306.4/259.9kh/s | A:22 R:0+0(none) HW:0/none
 OCL 1: 77.0C | 463.7/346.5/329.2kh/s | A:28 R:2+0(none) HW:0/none
-------------------------------------------------------------------------------------
 [2014-02-09 23:35:38] Accepted 027cc63e OCL 1  pool 0 Diff 0/0
 [2014-02-09 23:35:54] Accepted 03aa2c12 OCL 1  pool 0 Diff 0/0

Note that both GPUS are reporting their temps.

Miner machine  #2, with (2) identical GPUs to machine #1, is only reporting temps on the first GPU:

 bfgminer version 3.10.0 - Started: [2014-02-09 23:22:51] - [  0 days 00:14:22]
 [M]anage devices [P]ool management [ S]ettings [D]isplay options      [H]elp [Q]uit
 Connected to multicoin.zapto.org diff 0 with stratum as user Cassey.miner2
 Block: ...2317815661a13055  Diff:1 (11.32Mh/s)  Started: [23:36:33]
 ST:4  F:0  NB:29  AS:1  BW:[ 39/ 22 B/s]  E:0.01  I: 5.39 BTC/hr  BS:0
 2      80.0C | 834.9/853.0/791.9kh/s | A:134 R:8+0(none) HW:0/none
------------------------------------------------------------------------------------
 OCL 0: 80.0C | 410.5/405.6/383.1kh/s | A: 65 R:4+0(none) HW:0/none
 OCL 1:       | 452.0/447.7/441.8kh/s | A: 71 R:4+0(none) HW:0/none
------------------------------------------------------------------------------------
 [2014-02-09 23:37:06] Accepted 008ca2e8 OCL 0  pool 0 Diff 0/0
 [2014-02-09 23:37:10] Accepted 00fa9edb OCL 1  pool 0 Diff 0/0

Miner machine #3 is acting like Miner machine #2.

I rather like seeing the temps as it allows me to tweak intensities to keep at or below 80C (wouldn't want to burn any out too quickly!).

Start-up scripts have not changed in weeks.  Typical command line:

./bfgminer -S opencl:auto --intensity 17,18 --temp-overheat 90 --temp-cutoff 100 --temp-target 80 --scrypt --gpu-fan 100 --auto-gpu -o ...

Any ideas on what I broke?  

Presuming you are talking about Antminer U1s you need to use "-S antminer:all" and optionally "--set-device antminer:clock=x0981" or whatever clock you want.

Oh, you MUST be running 3.10.0, not an older version, too.

Please add http://multicoin.zapto.org:8080

Proportional payout, 2% fee, rapid payout (settable, but defaults to payout at coin discovery time which happens dozens of times a day).  Site is fully functional, with a sister forum site for discussion (http://multicoin.x10.mx), but under active development as well.  Forum has moderators on both sides of the pond.

We would love to have you come check us out!

Can't forget one of the newer multi-coin pools (the one I'm having fun with):  multicoin.zapto.org:8080.  Its scrypt only at the moment, but still under active development.  Would love to get your comments on it.  I'll ask about stale/orphan shares.

Hi...

Now that I have most things running as desired, I'm circling back and trying to clean up a few things.  One of those is to address:

[2014-02-08 12:30:39] temp-cutoff is deprecated! Use --set-device for better control

What are the appropriate --set-device parameters for GPU temp control?

Thanks Luke, although I don't recall ever seeing it before last night.  Maybe just never noticed it...

Now I'm trying to figure out why my all time average and effective average has changed.  I was pretty much 2's across the board until last night, but there were lots of rebuilds on the system yesterday.

bfgminer version 3.10.0 - Started: [2014-02-07 10:15:53] - [  0 days 02:24:
 [M]anage devices [P]ool management [ S]ettings [D]isplay options [H]elp [Q]u
 Connected to us-east.multipool.us diff 64 with stratum as user Cassey.miner
 Block: ...b3a79105 #752072  Diff:7.65k (54.79Gh/s)  Started: [12:40:22]
 ST:8  F:3  NB:43  AS:0  BW:[871/ 10 B/s]  E:2.80  I: 3.54 BTC/hr  BS:9.36k
 6            | 12.73/ 6.46/ 5.37Gh/s | A:319 R:45+6( 14%) HW:8/.06%
----------------------------------------------------------------------------
 AMU 0:       |  2.06/ 1.08/ 0.91Gh/s | A: 50 R: 7+0( 12%) HW:2/.10%
 AMU 1:       |  2.06/ 1.08/ 0.83Gh/s | A: 60 R:11+5( 21%) HW:2/.10%
 AMU 2:       |  2.05/ 1.08/ 0.96Gh/s | A: 59 R: 6+0(9.2%) HW:1/.05%
 AMU 3:       |  2.05/ 1.08/ 0.91Gh/s | A: 54 R: 7+0( 11%) HW:1/.05%
 AMU 4:       |  2.06/ 1.08/ 0.93Gh/s | A: 53 R: 4+1(8.7%) HW:2/.10%
 AMU 5:       |  2.05/ 1.08/ 0.86Gh/s | A: 44 R:10+0( 18%) HW:0/none
----------------------------------------------------------------------------
 [2014-02-07 12:40:18] Accepted 0347e94d AMU 0  pool 0 Diff 78/64
 [2014-02-07 12:40:22] Network difficulty changed to 7.65k (54.79Gh/s)
 [2014-02-07 12:40:22] Stratum from pool 0 detected new block

Maybe its just a reporting change? When I look at the pool stats I see:

Active Workers
      Hashrate
Coin   Worker Name   1 minute   10 minute
btc   Cassey.miner2am   13744   12599

Which is a bit higher than the 12Gh/s I expected, but in line with the 20-second decaying rates reported above.

Sorry guys, I wasn't clear.

This was working fine until I pulled a new clone from github yesterday and rebuilt bfgminer.  The behavior is different now: its almost like the code is trying to push the chips dynamically, although it settled in around 1.8 rather than 2 per antminer after running for several hours.

Trying again right now on the chance I caught Luke in the middle of updating something last night.

Yep, still seeing it - although just for a second before the screen clears and the normal window appears.
 
./bfgminer -S antminer:all --set-device antminer:clock=x0981 -o ...

 [2014-02-07 10:10:52] AMU: Applying rule antminer:clock=x0981: Unknown option: clock

bdgminer then proceeds to run with the reported 20s decaying hashrate ramping up quickly to around 1.6 and then up about 0.01 S per cycle until around 2.0, then slowly moving up from there (at 2.04-2.07 across my 6 antminers right now).  It appears Luke is trying to auto-set clockrates in the most current version.

Cassey

Pulled a new clone this evening and now seeing:

[2014-02-07 02:36:31] AMU: Applying rule antminer:clock=x0981: Unknown option: clock

... when bfgminer launches.

Suggestions?

My final thought:

Say you call it "Ralph".  For the next several years, every time you use the term "Ralph", your going to have to say "Ralph (formally bfgminer)".  I see no point.

Yep - I recloned and all is good now.  Sorry for bothering you.

Basically F**king Good Miner - I like it.  In mixed company it becomes Basically Friggen Good Miner.  With my British fans:  Bloodly  Friggin Good.

Keep the name, color is sometimes good.

Thanks.  Figured it would be 3.10.1 if it had changed, but I'm new to the git world.