Quote from: BenTuras on March 18, 2014, 08:08:44 AM

Quote from: Taugeran on March 18, 2014, 08:00:35 AM

...the issue lies in the way bfgminer uses the FW response to VERSION to allocate and setup the queue. since it replies only 2 chip in the response the other 12 are left hungry as f*** and any values they find arent being logged since as far as BFG knows they dont exist
^_^ hoora stubbornness for digging

Thank you for investigating. I will forward your message. And love your phrase 'hungry as f***' Wink

well its true. they arent being fed work items. since bfg only sees 2 chips.

**update

manually changing the procs count in the cgpu initialization (hardcode from .procs = chips, to .procs = 15,) leads to a moderate increase in hashrate. moderate as in from utility hashrate of 7Ghash to about 10 but that was a short 45 second run. but still not optimal. more investigating to do. and there goes my sleep. just downed a glass and a half of turkish coffee

on a side note debug outputs a s**tload of useful data. 45 seconds produced 4MB logfile