Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 158. (Read 1193223 times)

Ok, I believe this problem should be fixed in the latest git code.

For Windows testers... Win32 and Win64 binaries are built (drop them in a directory with 3.0.2 DLLs)

Note these builds do not have ZTEX FPGA support due to legal issues with a minor contributor, which I hope to have resolved for the 3.1 release.

They do, on the other hand, have experimental CPU mining code. No performance optimizations, but I've done some tweaking for making it more portable.
A simple way to test is to run:
If you get rejected shares, it works.
Ideal testing includes every algorithm, and that the default (fastauto) picks something that works.
x86_32 algorithms: c 4way cryptopp cryptopp_asm32 sse2_32
- VIA-specific algorithm: via
x86_64 algorithms: c sse2_64 sse4_64
PowerPC (very old Mac OS X only!): altivec_4way

I do not plan to release 3.1 with CPU mining support enabled in Windows binaries still, mainly due to the threat of malware abusing it.
If anyone has any alternative or better ways to prevent malware abuse, I'd love to hear it

Good news: I think I have stumbled upon the stratum-went-down-related crash people have been reporting while testing BFGMiner in Valgrind.
This should give me enough information to get it fixed in the next release.

BFGMiner also needs the standard FTDI/VCP driver...

Had to use zadig to change driver so both BFGMiner and CGMiner could see jalapeno. Bitminter beta needed ftdi type driver instead with VCP. Interesting. Wonder what ASICminer blade and USB need to work

Thank you. Will try in 14 hours.

The main thing to note is that BFGMiner is a command-line program. It means you have to start it from command line (a 'DOS window' in olde-speak). If you merely double-click on the bfgminer.exe program in Windows Explorer, nothing much will happen.

If you follow the following steps, you should be able to do what Luke has asked:

1. assuming you have the folder 'bfgminer-3.0.2-win64' already extracted somewhere, use Windows Explorer to move that folder to the root of your C: drive. This will simplify the following steps.
2. click 'Start' on your Windows taskbar, in the search box type in "cmd" (without the quotes), and hit . You should see a black 'DOS box' appear. That is the command-line window.
3. now in that command-line window type in "cd \bfgminer-3.0.2-win64" (again, without the quotes) and hit . You should now be in the bfgminer directory. You should now see a prompt that looks like this:

        C:\bfgminer-3.0.2-win64>

4. now you can type in what Luke asked. That is, type "bfgminer -D -T -d" (without quotes) and hit . You should see a bunch of text appear on the screen, and you can report back here with what you see.

Sorry, not right now as I am heading to work soon. Not too familiar with BFGMiner. How do I runbfgminer -D -T -d? Thanks for your help.

Sounds like you have the driver installed already...
Can you run bfgminer -D -T -d? and post the results here?

Also using WIN64 version with windows 7.

I am using 3.02 . Not auto detected. Do I need a driver somewhere? Or do I need to enter some code at startup to get it to detect it. Jalapeno is currently on COM3 port (USB). It is auto detected in bitminter beta though.

It should autodetect... Be sure you're using 3.0.

How do I enable BFGminer to see my Jalapeno? I currently am running it on bitminter beta miner but would like to try it on BFGMINER. Thanks!

Like you, for the time being I have a workaround, but will be looking for an alternative ahead of my long-awaited Bitminers.  Don't want to buy another PC just to get 4 more built-in USB ports.

Further to this: I've now also swapped hubs, and I've also swapped Singles from a 2nd cluster, and saw something interesting.

The original problem was that BFL14 (always #14) was giving the 'Error: Get temp returned empty string". Not immediately, but once it started (typically after a few minutes or hours) it would not recover until bfgminer was restarted.

Now, even with the swapped PC (and OS change from Win7/64 to Win7/32), swapped USB hubs, *and* swapped Singles (I swapped BFL14 for a  'known good' Single from a different cluster), I'm still getting the same error message. The interesting part is that it is being reported on the 'new' BFL14!

Since I replaced basically *everything* and the error did not go away, there's not much else I can do with this cluster. I've since reduced it down to 14 Singles and haven't encountered the error since; the Single I removed is mining elsewhere, and it hasn't had a problem either. Perhaps there is an issue with 15+ USB devices? I suspect this is not a common configuration so it probably does not get a lot of testing.

For now I have a workaround so I'm not particularly concerned. I'm more concerned about the general instability of bfgminer versions higher than 2.9.9 on my systems. I may as well ask: Does anyone else have a 15+ cluster of Singles running on a single instance of bfgminer? If so, what version are you running and what are your experiences?

But not 3.0.0? More info?

BFGminer 3.0.1-.02 crashing no matter what on 6970

I've actually been experiencing a similar problem (same error message) for the past few days, but with bfgminer 2.9.9. Looking into it now. I've swapped PCs and get the same problem. I'm focusing on the hubs right now, seeing if the problem follows the Single or if it stays with the USB port.

Having a problem using bfgminer-3.0.0-win64 with usb hubs.

4 BFL FPGAs tried on Satechi 10-port USB 3.0 hub, Satechi 12-port USB 2.0 hub, and Stratitec 4-port USB 2.0 hub.  All hubs are powered.

bfgminer will find and start all four miners, but almost immediately will start throwing HW error "Error: Get temp returned empty string" for all but the first miner found.  bfgminer runs normally if I plug the miners into 4 of the PC's 2.0 and 3.0 USB ports.

Suggestions?

[Edit] Just to be more clear -- decided to free up the USB ports on my PC so moved the FPGAs to the 4-port hub and saw the errors when I restarted bfgminer.  Tried moving the hub input to different ports on the PC, same result.  Tried switching the FPGAs around on the 4-port and it was always the first detected that ran ok with other three miners throwing the error.  Thought maybe the hub was bad, so tried the 12-port 2.0 hub (it has 2 independently switched banks of 6 powered ports each) -- same result irrespective of ports connected on the hub or the PC.  Next, tried the 10-port 3.0 hub (3 independently switched banks of 3 ports each plus one iphone/ipad charger port) -- same result.  Moved the miners back to ports on the PC, no errors.

BFGminer running for 2 months without issues. Updated to AMD drivers 13.4 today. Now it's crashing on startup everytime. Using AMD HD6850 and Windows 7 x64 SP1 + all windows updates.

Command line: --gpu-threads 1 --queue 0 --intensity=d --gpu-dyninterval 16 --failover-only

I deleted the precompiled kernel and it's not making a new one. There's nothing written to the console.

Problem Event Name:   APPCRASH
  Application Name:   bfgminer.exe
  Application Version:   0.0.0.0
  Application Timestamp:   517cb77a
  Fault Module Name:   bfgminer.exe
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   517cb77a
  Exception Code:   c0000005
  Exception Offset:   000000000003c9d9
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   1033
  Additional Information 1:   e68f
  Additional Information 2:   e68fabd2622a99ce852fcf528f13d88e
  Additional Information 3:   bf43
  Additional Information 4:   bf43415df077bf09da15770f50cc570b


Both 3.0.2 and 2.10.8 crash in the same manner.

EDIT:

Fixed. I am leaving this here for those who end up having my issue.

-Uninstall all ATI software.
-Restart.
-Create a batch file with the following and run it:

@C:
@cd C:\Windows\System32
del SlotMaximizerAg.dll
del SlotMaximizerBe.dll
del amdocl64.dll
del OpenCL.dll
del OpenVideo64.dll
del OVDecode64.dll
@Cd C:\Windows\SysWOW64
del SlotMaximizerAg.dll
Del SlotMaximizerBe.dll
del amdocl.dll
del OpenCL.dll
del OpenVideo.dll
del OVDecode.dll
@rmdir C:\ProgramData\AMD\KDB /S /Q

-Reinstall ATI 13.1 drivers.

thanks