OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB

[Lucko]

After running this getwork functionality for some time I would say it it working as good as proxy server if you look at speed only. The only difference is that proxy is just proxy but BFGMiner is not. So it doesn't send out garbage. That is why you see less shares and lower speed and efficiency in Blade interface. So if anyone is worried don't be. It works!

I also found this: https://asktom.cf/index.php?topic=251224.0 and this one explains all https://asktom.cf/index.php?topic=251224.msg3078019#msg3078019

[Luke-Jr]

NEW VERSION 3.2.1, SEPTEMBER 19 2013

Human readable changelog:

• Win32 (but not Win64) binaries now support the getwork server/proxy (for Block Erupter Blades).
• Support for Windows Embedded Standard (excluding X6500 and ZTEX).
• Allow startup with no devices, even if RPC and HTTP server are disabled, so long as the user can add new ones via the curses TUI.

Full changelog:

• Only show long-poll message in pool summary if it's not using stratum.
• README.ASIC: Clarify syntax of --scan-serial usage for USB Erupters
• Bugfix: RPC: Defer allocation of apisock until after we check for --api-listen
• make-release: Only try to include libmicrohttpd if bfgminer.exe depends on it
• Bugfix: make-release: Include libplibc-1.dll if available
• SGW: For Windows builds, include winsock2.h instead of POSIX networking headers
• configure: Display getwork proxy server support in summary
• Bugfix: SGW: Pass actual cgpu_info to prune_worklog_thread instead of silently casting one from getwork_client
• Bugfix: Get total_staged with lock for TS stat, before getting console lock
• Bugfix: bitforce: Correct fanmode RPC help
• bitforce: Hide fan control when disabled in firmware
• Bugfix: bitforce: Correct fanspeed TUI setting
• Bugfix: logging: Allow up to 4 KB for log lines
• Bugfix: icarus: Ensure last2_work exists before trying to check nonces fit it
• README.OpenWrt: Include serialusb drivers
• README: Include OpenWrt serialusb driver package names
• Bugfix: Initialise notifier (as invalid) for no-thread devices (SGW)
• Bugfix: Free temporary kernel path copy when writing config file
• Bugfix: Put kernel path on the (main) stack after initialisation from commandline/config, to avoid appending an argv or jansson string
• Bugfix: Always allow startup with curses enabled (since the user can use Manage devices to add new ones, and display Ctrl-C for text-only quit help
• Bugfix: Ignore/reject libmicrohttpd before 0.9.5, which introduced symbols we need
• README: Elaborate on format of BW
• Bugfix: Try to initialise libusb later, so any mutexes applog might need are initialised
• Bugfix: Implicitly initialise timer_set_now when it is first called
• util: Eliminate unsafe const-removing casts
• configure: Cleanup CFLAGS/LDFLAGS display
• Show RT_LIBS in ./configure output.

[vulgartrendkill]

NEW VERSION 3.2.1, SEPTEMBER 19 2013

Human readable changelog:

• Win32 (but not Win64) binaries now support the getwork server/proxy (for Block Erupter Blades).

Does this mean I still need the slush proxy program or can it support it natively?

Thanks[/list]

[Luke-Jr]

NEW VERSION 3.2.1, SEPTEMBER 19 2013

Human readable changelog:

• Win32 (but not Win64) binaries now support the getwork server/proxy (for Block Erupter Blades).

Does this mean I still need the slush proxy program or can it support it natively?

You don't need any other software. Check out README.ASIC.

[HellDiverUK]

The proxy running under Win32 is a godsend.  Thanks, Luke.  Looks like my little NUC mining machine will be turning in to a Windows box this evening.

[Mudbankkeith]

Thanks Luke-Jr
You have been very busy, 3.2.0 was nice, but 3.2.1 looks the dream version for blade users.
when my blade arrives I will send you some of the first coin.

[Lucko]

Nice... Windows... Bye Bye Linux VM... BTW you don't need to run just a blade from it... I'm now running all miners from different machines from it Central control

But I do have a stupid question since I coming from CGminer camp. You have 3 hash speeds. First one is probably 5 second or so average... One would probably be all time average but what is the reaming one?

[vulgartrendkill]

Thanks Luke.  BFG  is my favourite miner by far. Everything just works. Major props for getting a proxy within it too.

[Luke-Jr]

You have 3 hash speeds. First one is probably 5 second or so average... One would probably be all time average but what is the reaming one?

The third one is utility, but measured in hashes/sec instead of shares/min. (README)

[Lucko]

The third one is utility, but measured in hashes/sec instead of shares/min. (README)

I must of missed that in README... I did looked at it... But it was a glancing look after first 50%. If it help to improve README I can tell you why I missed it. I was looking for something like you see not line by line... And I was sure it will be at the start not the end... But I must say I was missing that in cgminer. Hashrate that is reported by pool... Nice...

EDIT: definitely some donations coming your way when I stop investing everything into COINTAMINATION

[HellDiverUK]

Any news on BFG supporting the RedFury USB (2.5GH) miners, Luke?

[OtaconEmmerich]

This keep happening to me on this PC, I'm on 3.2.1. Everything runs fine on my second PC with 3.1.4.

Any idea what might be wrong?

[Luke-Jr]

Any news on BFG supporting the RedFury USB (2.5GH) miners, Luke?

Andreas has provided some code, but I don't have a unit to test with.
Just pushed a "bigpic" branch based on Andreas's code merged up, if you want to try it out.
It looks like there's a lot of code in there that will be redundant with the metabank/littlefury code, so I should probably merge the two before it'll be 3.3-ready.

[Luke-Jr]

This keep happening to me on this PC, I'm on 3.2.1. Everything runs fine on PC with 3.1.4.

Any idea what might be wrong?

Likely overheating or defective unit.

[OtaconEmmerich]

Nope, typo'd slightly on the post. Everything runs fine on the OTHER PC with 3.1.4.

[Luke-Jr]

Nope, typo'd slightly on the post. Everything runs fine on the OTHER PC with 3.1.4.

Same hub?

[OtaconEmmerich]

Yep, same setup.

[Luke-Jr]

Yep, same setup.

Can you try 3.1.4 on the same PC that 3.2.0 has the issue on?

[JBT]

ok maybe i read this wrong can i disable the gpu but autoscan for all the usb eruptors?


ed. nm found it -S eruper:all  -G ,still pondering going the usb route since the comm ports change sometimes and would like to see if a device is zomby or working

[Luke-Jr]

ok maybe i read this wrong can i disable the gpu but autoscan for all the usb eruptors?

-S opencl:noauto -S erupter:all