OLD: BFGMiner 4.10.0: GBT+Stratum, RPC, Mac/Linux/Win64, Spondoolies SP30

[Morblias]

Do I just start that with ./bfgminer --debug? Does it throw the log file into the bfgminer directory then? I will give that a shot and let you know when it happens again. Also, any idea roughly how hot we can run the Monarchs? It is showing 56C right now, so it doesn't seem too bad.

[1715696832]

1715696832

[1715696832]

1715696832

[1715696832]

1715696832

[Luke-Jr]

Do I just start that with ./bfgminer --debug? Does it throw the log file into the bfgminer directory then? I will give that a shot and let you know when it happens again.

bfgminer YOUR OPTIONS HERE --debuglog 2>debug.log

[BFL-Engineer]

Dear Morblias,

Do you have the possibility of running a bfgminer on Linux to check if the same issue persists?
Also, is it normal that you are getting 228GH instead of 700GH for Nonce-Rate? or it has happened in this instance only?

Regards,
Nasser

[Luke-Jr]

After some troubleshooting, it seems Morblias's root issue is a corrupt USB packet which the Monarch firmware is failing to recover from without being reinitialised.

Nasser, it all starts when a WX gets a "ERR:SIGNATURE" - from that point on, all commands are considered invalid.
Edit: Or more accurately, it appears as if "ERR:INVALID COMMAND" is just being flooded back forever, with or without another command...

[DELTA9]

What build options do I need to use for mining with a GAW Fury?

[nwoolls]

What build options do I need to use for mining with a GAW Fury?

Code:

--enable-scrypt

[BFL-Engineer]

We have never faced this in the many boards we tested in lab. I would suspect a weak solder joint somewhere, or some issue with this board which went undetected.

@Morblias: You could send this board for replacement. Please let me know if you do so and when so I can accelerate the process and also see what's wrong with this board.
However, if you have the possibility of testing this card on another computer, it would be very helpful, as the issue may come from the actual computer / driver that you're using.

Thanks,
Nasser

[Morblias]

We have never faced this in the many boards we tested in lab. I would suspect a weak solder joint somewhere, or some issue with this board which went undetected.

@Morblias: You could send this board for replacement. Please let me know if you do so and when so I can accelerate the process and also see what's wrong with this board.
However, if you have the possibility of testing this card on another computer, it would be very helpful, as the issue may come from the actual computer / driver that you're using.

Thanks,
Nasser

I tried it on my RPi (with minepeon) and ubuntu 14. Both came up with those same errors. Then I tried it on a windows 7 64 bit machine, and this happens, except it continues to hash after the errors. On the linux ones it would just stop hashing completely, but the windows one continues around 620gh/s. I found another USB cable and tried that also with no luck. Still happens on all of the computers. 620gh/s isn't too bad though, so I might just leave it on the windows machine.

[jorneyflair]

Hi,luke could you help me? I got that strange error only when i mined nicehash , full of hw and no accept.

[Luke-Jr]

Hi,luke could you help me? I got that strange error only when i mined nicehash , full of hw and no accept.

Looks like your miners aren't SHA256d...

[jorneyflair]

Hi,luke could you help me? I got that strange error only when i mined nicehash , full of hw and no accept.

Looks like your miners aren't SHA256d...

its definitely sha256 and i used to mine BTC in Ghash.io with no problem

sometimes it shows {"id": X, "result": true, "error": null}\n 

[BFL-Engineer]

We have never faced this in the many boards we tested in lab. I would suspect a weak solder joint somewhere, or some issue with this board which went undetected.

@Morblias: You could send this board for replacement. Please let me know if you do so and when so I can accelerate the process and also see what's wrong with this board.
However, if you have the possibility of testing this card on another computer, it would be very helpful, as the issue may come from the actual computer / driver that you're using.

Thanks,
Nasser

I tried it on my RPi (with minepeon) and ubuntu 14. Both came up with those same errors. Then I tried it on a windows 7 64 bit machine, and this happens, except it continues to hash after the errors. On the linux ones it would just stop hashing completely, but the windows one continues around 620gh/s. I found another USB cable and tried that also with no luck. Still happens on all of the computers. 620gh/s isn't too bad though, so I might just leave it on the windows machine.

The images you show are actually hashing at 680GH not 620GH (For some reason, the Job-Rate is shown less than Nonce-Rate in Bfgminer, you might want to confirm this with your pool).
Also when a unit mines and then stops, it still has job-results in it's internal buffer. Upon restart, bfgminer will see those results but won't recognize them (as it doesn't know source of those jobs),
hence you get a "Was not able to find work for result". It's basically information, and should not be considered a failure.

I have already talked to Luke, and we have discussed a recovery mechanism that can be implemented on the Host-side if a USB packet gets corrupted (for Windows). On our own, we don't see these issues in our lab, especially
on Linux (On windows you do get an error every once in a while, but never affects speed or cause failure).

EDIT: I will be shortly publishing a special built of Bfgminer (version 4.2) which was custom-built and doesn't have slowdown/failure issues on windows.

Please let me know if you had any questions.

Thanks,
Nasser

[jorneyflair]

and this is the error when i use the proxy-stratum

[BFL-Engineer]

This is the custom-build of bfgminer version 4.2.0 (For Windows).
Please try and let us know if it works and everything is OK.

http://www.butterflylabs.com/upload/drivers/software/Bfgminer-CustomBuilt-23June2014.zip


Regards,
Nasser

[Luke-Jr]

Hi,luke could you help me? I got that strange error only when i mined nicehash , full of hw and no accept.

Looks like your miners aren't SHA256d...

its definitely sha256 and i used to mine BTC in Ghash.io with no problem

sometimes it shows {"id": X, "result": true, "error": null}\n 

Oh, is this the Tube? It's known to not work with anything but Ghash.io - seems to be a serious Tube bug.

[Morblias]

The images you show are actually hashing at 680GH not 620GH (For some reason, the Job-Rate is shown less than Nonce-Rate in Bfgminer, you might want to confirm this with your pool).

Yeah you are correct, the pool is showing 680gh/s.

This is the custom-build of bfgminer version 4.2.0 (For Windows).
Please try and let us know if it works and everything is OK.

http://www.butterflylabs.com/upload/drivers/software/Bfgminer-CustomBuilt-23June2014.zip


Regards,
Nasser

Works great on my Windows 7 machine. Just curious, which distribution of linux are you using? I was trying it on Ubuntu 14.04.1 when I was having those issues. Could it possibly be a driver issue causing it not to work on mine?

[CryptoJohn]

I posted the following on the minera thread but could not get an answer. I'm coming right to the source now, hopefully you can help

Great solution for those of us using the essentially unsupported ZenController. Thanks to dev!
I would suggest better documentation and user settings for different devices in the OP. That would be huge!

Question for those more familiar with Minera:

I am up and running using bfg w/ default settings with Black Widow(14.2 mh/s w/ 5% error/reject) for 24hrs. My question involves the UI reporting my miner incorrectly. The pool hash is correct but the miner details and device tree show the Black Widow hashing @ 1gh/s. Impossible, too bad really Sad
Is there a setting or something to correct the UI reporting? Once the hash reporting is corrected can I rename devices? I ask this because I will be spinning up 4 Furys(still on zen) on a seperate Rpi and would like to name them correctly.

Another question: I have 4 furys into a hub then into Rpi...will this be an issue?

Is it possible to mix black widows @ furys on the same Rpi and it work with Minera?


Thanks to everyone for their help.

[jorneyflair]

Hi,luke could you help me? I got that strange error only when i mined nicehash , full of hw and no accept.

Looks like your miners aren't SHA256d...

its definitely sha256 and i used to mine BTC in Ghash.io with no problem

sometimes it shows {"id": X, "result": true, "error": null}\n 

Oh, is this the Tube? It's known to not work with anything but Ghash.io - seems to be a serious Tube bug.

bingo , damn tube

[BFL-Engineer]

The images you show are actually hashing at 680GH not 620GH (For some reason, the Job-Rate is shown less than Nonce-Rate in Bfgminer, you might want to confirm this with your pool).

Yeah you are correct, the pool is showing 680gh/s.

This is the custom-build of bfgminer version 4.2.0 (For Windows).
Please try and let us know if it works and everything is OK.

http://www.butterflylabs.com/upload/drivers/software/Bfgminer-CustomBuilt-23June2014.zip


Regards,
Nasser

Works great on my Windows 7 machine. Just curious, which distribution of linux are you using? I was trying it on Ubuntu 14.04.1 when I was having those issues. Could it possibly be a driver issue causing it not to work on mine?

I suspect it should be a driver issue, because the firmware and the card is the same, and bfg is bfg, but windows has some problems and linux doesn't have any. It must be OS related. I don't think we'll use FTDI For our next generation products.

EDIT: Regarding Linux distribution, we always use the latest. Never had problems. Are you using a normal computer or some RaspPi or Beaglebone for the Linux Setup?


Thanks,
Nasser

[Morblias]

EDIT: Regarding Linux distribution, we always use the latest. Never had problems. Are you using a normal computer or some RaspPi or Beaglebone for the Linux Setup?

Tried it on both a regular laptop and a RPi. I suspect the RPi is out of date with the drivers, but the laptop I had fully updated with ubuntu and all of the bfgminer dependencies, so I am not really sure what's up with it.