Everyone who had problems with 3.5.0, please test latest git and let me know if I fixed them all...
Latest git build appears to be picking up a non-existant bitfury device which (as it's not there) is gettng 100% HW errors ...
BPM 0: | 3.00/21.26/ 0.00Gh/s | A:0 R:0+0(none) HW:692/100%
redoing my standard config and disabling all bitfury related devices seems to fix it:
./configure --enable-scrypt --disable-avalon --disable-opencl --disable-bitfury --disable-bfsb --disable-bigpic --disable-modminer --disable-x6500 --disable-ztex --disable-littlefury --disable-nanofury --disable-metabank --enable-cpumining --enable-bitforce --enable-icarus --disable-knc
-although it has now 'lost' 2 of the USB-BlockErupters
Please
bfgminer -D -d?
[2013-11-07 21:26:54] Started bfgminer 3.2.1
^ its actually 3.5.1, and correctly reports that when loaded normally
[2013-11-07 21:26:54] Loaded configuration file /root/.bfgminer/bfgminer.conf
[2013-11-07 21:26:58] Devices detected:
[2013-11-07 21:26:58] 0. BFL 0a (driver: bitforce_queue)
[2013-11-07 21:26:58] 1. BFL 0b (driver: bitforce_queue)
[2013-11-07 21:26:58] 2. BFL 0c (driver: bitforce_queue)
[2013-11-07 21:26:58] 3. BFL 0d (driver: bitforce_queue)
[2013-11-07 21:26:58] 4. BFL 0e (driver: bitforce_queue)
[2013-11-07 21:26:58] 5. BFL 0f (driver: bitforce_queue)
[2013-11-07 21:26:58] 6. BFL 0g (driver: bitforce_queue)
[2013-11-07 21:26:58] 7. BFL 0h (driver: bitforce_queue)
[2013-11-07 21:26:58] 8. BFL 0i (driver: bitforce_queue)
[2013-11-07 21:26:58] 9. BFL 0j (driver: bitforce_queue)
[2013-11-07 21:26:58] 10. BFL 0k (driver: bitforce_queue)
[2013-11-07 21:26:58] 11. BFL 0l (driver: bitforce_queue)
etc 150+ times *but* D/M shows no BFL kit and
BPM 0: | 0.85/23.75/ 0.00Gh/s | A:0 R:0+0(none) HW:400/100%
explicitly adding the disables for all the *fury types and it works as expected.
the full bfgminer -D -d? output is 20 pages long and looks fine