Quote from: wzl on November 10, 2013, 03:16:40 AM

Quote from: ckolivas on November 09, 2013, 11:54:34 PM

Quote from: expalpo on November 09, 2013, 10:47:08 PM

Just noticed that ckolivas commited a changeset a few hours ago with an update to the bitfury driver. Re-compiling from source, with those changes, made a difference in the numbers I was seeing in cgminer. Cgminer reported hash rate went from around 1.7-1.8Gh/s to around 2.2 - 2.5Gh/s.

I didn't think the changes would make such a difference, but there will be hardware errors reported now.

Anyway in case someone cares to try it, here's an updated windows binary with the changes:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe

I'm not on Windows so I can't try that - checked out what's on git right now and didn't seem to make much difference (except now I am getting HW errors).

Before:
BF1 0: | 2.089G/2.037Gh/s | A:1538 R:2 HW:0 WU:29.4/m

After:
BF1 0: | 1.991G/1.973Gh/s | A:273 R:0 HW:114 WU:27.7/m

Anyone have any suggestions?

It just wasn't reporting them before. Any difference there is purely luck related and the performance is, presumably, identical otherwise. I wasn't expecting performance advantages which is why I was surprised anyone noticed any. However there may be some usb devices out there that benefited from the flushing code I added, and they were previously performing really bad (1.3GH). 2-2.2GH seems about normal for these devices.

Interesting how scary actually seeing hardware errors is - it's probably going to be enough for droves of people to go "Oh my god it now has hardware errors, I'm downgrading". I've seen the pattern enough by now Undecided