(OLD) BFGMiner: modular FPGA/GPU, GBT, Stratum, RPC, Avalon/Lnx/OpnWrt/PPA/W64

[julz]

Tried running 2.9.0 against my icarus boards but it says
"Detected scrypt algorithm"
and then just spits out 'invalid nonce -HW error' messages

2.8.2 was working fine.

The readme mentions --scrypt  option - but I can't seem to find a way to turn it off.

Is it just that the windows binary is compiled for scrypt and I need to compile without it?

[1713909645]

1713909645

[1713909645]

1713909645

[1713909645]

1713909645

[Luke-Jr]

Tried running 2.9.0 against my icarus boards but it says
"Detected scrypt algorithm"
and then just spits out 'invalid nonce -HW error' messages

This means the pool you have configured is a scrypt pool.

Ok it did it again
https://i.imgur.com/Ppkbq.png
https://www.box.com/s/07ahi12bvhsfs9dlaumk

Please test: http://luke.dashjr.org/tmp/code/bfgminer-20121028-stratum-A.exe

[bitpop]

Testing bfgminer-20121028-stratum-A.exe

[bitpop]

bfgminer-20121028-stratum-A.exe looking good
https://www.box.com/s/bwrji3jkixth5wdgxnoh

[hashking]

I followed the steps for installing dwmingw and nothing appears when I click on the icon.

After installing it, programs crashing will give you an option to debug.

I ran bfgminer, it crashed and nothing showed up for a debug.

What if you run it at a commandprompt with bfgminer -T -D

It crashes and goes to the windows close program or look for solution box.

[Luke-Jr]

I followed the steps for installing dwmingw and nothing appears when I click on the icon.

After installing it, programs crashing will give you an option to debug.

I ran bfgminer, it crashed and nothing showed up for a debug.

What if you run it at a commandprompt with bfgminer -T -D

It crashes and goes to the windows close program or look for solution box.

It should still print out some debug info first...?

[hashking]

I followed the steps for installing dwmingw and nothing appears when I click on the icon.

After installing it, programs crashing will give you an option to debug.

I ran bfgminer, it crashed and nothing showed up for a debug.

What if you run it at a commandprompt with bfgminer -T -D

It crashes and goes to the windows close program or look for solution box.

It should still print out some debug info first...?

I don't see a debug file.  If there is what is the name of it.

[K1773R]

I followed the steps for installing dwmingw and nothing appears when I click on the icon.

After installing it, programs crashing will give you an option to debug.

I ran bfgminer, it crashed and nothing showed up for a debug.

What if you run it at a commandprompt with bfgminer -T -D

It crashes and goes to the windows close program or look for solution box.

It should still print out some debug info first...?

I don't see a debug file.  If there is what is the name of it.

luke why helping him? scammer flaged

[hashking]

 [2012-10-29 07:05:05] ft232r_scan: Error opening device: LIBUSB_ERROR_NOT_SUPPORTED

Found this in the debug log.

[Luke-Jr]

luke why helping him? scammer flaged

I don't know why he's scammer flagged, and I don't blindly trust such flags. He seems to be behaving decently in threads I've seen, at least.
Plus he is responsible for providing the X6500 I did the development with, so if I refused to help him I would arguably be a scammer myself.

[2012-10-29 07:05:05] ft232r_scan: Error opening device: LIBUSB_ERROR_NOT_SUPPORTED
Found this in the debug log.

This should be ignored. -D -T will just print debug info to the command window, it won't make a file.
If you need a file, use:

Code:

bfgminer ... --debuglog 2>debuglog

[hashking]

luke why helping him? scammer flaged

I don't know why he's scammer flagged, and I don't blindly trust such flags. He seems to be behaving decently in threads I've seen, at least.
Plus he is responsible for providing the X6500 I did the development with, so if I refused to help him I would arguably be a scammer myself.

[2012-10-29 07:05:05] ft232r_scan: Error opening device: LIBUSB_ERROR_NOT_SUPPORTED
Found this in the debug log.

This should be ignored. -D -T will just print debug info to the command window, it won't make a file.
If you need a file, use:

Code:

bfgminer ... --debuglog 2>debuglog

That is the error that I get owhen I use bfgminer ... --debuglog 2>debuglog.  If I use -D -T it does to the windows error message.

[Luke-Jr]

That is the error that I get owhen I use bfgminer ... --debuglog 2>debuglog.  If I use -D -T it does to the windows error message.

Are you able to provide remote access to the rig having this problem? If so, would it be okay if I install debugging tools on it?
Either way, please open a GitHub Issue for further tracking and meet me on IRC sometime if possible.

[jborkl]

When I solomine

windows 64
bfgminer 2.9.0
bitcoin 0.7.1

2 different rigs each running the client

command line used
bfgminer.exe -o localhost:8332 -u x -p x --coinbase-addr 1myaddress
same for the machine with mmq except command line contains   -S modminer:\\.\COM4

It does not start working on a new block, it says,for example, started [01:30:20] and does not ever change blocks.

block:xxxx  stays the same also

I let it run for a couple hours on each machine

[julz]

Tried running 2.9.0 against my icarus boards but it says
"Detected scrypt algorithm"
and then just spits out 'invalid nonce -HW error' messages

This means the pool you have configured is a scrypt pool.

That makes no sense to me. I thought scrypt was something to do with litecoin?
I haven't changed the pool - currently BTC Guild via stratum proxy.

Why do I need to care about scrypt/litecoin and what should I be reading?

[Luke-Jr]

NEW VERSION 2.9.1, OCTOBER 30 2012

Hopefully this fixes everyone's problems and more!

I've also bumped the stable release to 2.8.4 including the fixes relevant to the 2.8.x versions.

Human readable changelog:

• X6500: Fix Windows crash.
• RPC: Add support for X6500 FPGAs.
• Enforce --expiry option to make solo mining without longpoll move on eventually (fixes jborkl's problem).
• Always detect non-scrypt if Stratum is in use (fixes julz's problem).
• Various other bug fixes, including bitpop's problem and a number of memory leaks.

Full changelog

• When we find a block, always progress to it for mining
• Bugfix: Enforce --expiry, but split --expiry-lp for a longer expiry on longpoll setups
• Bugfix: regeneratehash needs to compare hash segments in Little Endian, not Big Endian
• Bugfix: Always fail scrypt detection if Stratum is working
• Bugfix: Scan for ft232r devices later, after console lock and other mutexes are initialized properly
• ft232r: Debuglog non-FTDI device IDs found
• Bugfix: Wait to release JSON result in case of JSON-RPC error until we've logged the error
• Bugfix: RPC: Defer release of JSON until after cmd is used
• Bugfix: Release JSON result in case of JSON-RPC error
• Bugfix: Release job JSON result as soon as we are done using it
• Bugfix: Release JSON received from RPC socket after we're done using it
• Bugfix: Use clear_work and workdup everywhere work is copied around
• Bugfix: Clear work before replacing it with new, to free any pointers
• server and client sockaddr_in are no longer used in struct pool.
• Set sshare id and swork_id within the sshare mutex to avoid multiple share submits with the same id.
• Bugfix: Really use freeaddrinfo to clean up in extract_sockaddr
• Update documentation for X6500
• Bugfix: Free unused JSON returned when switching to Stratum
• Bugfix: Free unused work when switching to Stratum instead
• Bugfix: Use freeaddrinfo to clean up in extract_sockaddr
• RPC: Include PGA support for X6500-only builds
• RPC: Abstract code to handle any new device drivers as PGAs without special support
• Bugfix: Release GBT submission JSON objects after dumping them
• Bugfix: Free old stratum_work data before replacing it
• Bugfix: Release memory allocated by prior stratum sockaddr extractions
• Bugfix: Clear work template when preparing a new request
• Bugfix: Initialize temporary stratum work
• Bugfix: x6500: jtag_read buffer needs to be initialized since reading JTAG implies writing too
• Replace now-redundant accepted_weighed with equivalent diff_accepted
• Fail on select() failing in stratum thread without needing to attempt recv_line.
• Add share to stratum database before sending it again in case we get a response from the pool before it's added.
• Bugfix: modminer: Check that we have a valid fd before trying to start work
• Shorten the initiate stratum connect timeout to 30 seconds.
• Shorten the stratum timeout on read to 90 seconds to detect unresponsive pool.
• Display best share difficulty on exit.
• Make stratum socket fail more robust on windows by disabling the send buffer.
• Reuse the same curl handle forcing a new connection instead of risking derefencing.
• Add information about submission failure to stratum send.

[vitruvio]

Same isues with hashrate than reported in 2.9.0

https://bitcointalk.org/index.php?topic=78192.msg1303360#msg1303360

Regards

[HolyScott]

2.9.1 Mining nicely on a Raspberry Pi, however I do get Comm Error disconnects randomly with 4x BFL Singles. Google search lead me to the issue board, and post discussing that this is due to the usb problems on the raspberry pi. I have a 512 MB RPi on order to see if the new reversion fixes the issue.

[creativex]

New version(2.9.1) does NOT crash windows 7 x64 for me. Current uptime with new version approximately 12hrs on W8x64 & 8hrs on W7x64. Previous version(2.8.2) crashed windoze within minutes. Whatever ya done, TY! Donation inbound.

[Luke-Jr]

2.9.1 Mining nicely on a Raspberry Pi, however I do get Comm Error disconnects randomly with 4x BFL Singles. Google search lead me to the issue board, and post discussing that this is due to the usb problems on the raspberry pi. I have a 512 MB RPi on order to see if the new reversion fixes the issue.

As I understand it, there's a way to upgrade the firmware on old revisions too.

[BitMinerN8]

2.9.1 Mining nicely on a Raspberry Pi, however I do get Comm Error disconnects randomly with 4x BFL Singles. Google search lead me to the issue board, and post discussing that this is due to the usb problems on the raspberry pi. I have a 512 MB RPi on order to see if the new reversion fixes the issue.

As I understand it, there's a way to upgrade the firmware on old revisions too.

Raspberry Pi Update Tool
https://github.com/Hexxeh/rpi-update

And there is a newer Raspbian build posted on 10/28.
http://www.raspberrypi.org/downloads