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

Can you send me your current firmware?

Every time I run it.

I read in the readme how to update firmware but where can I get a copy?
Thanks

Need a backtrace or bisect.

Need output from
Need a backtrace or bisect.

This feels like stack corruption. How often does it happen? Are you running the latest firmware?

3.7.0 bug: [2013-11-28 22:21:58] Started bfgminer 3.7.0Segmentation fault: 11

Cant mine...

3.6.0 Is not detecting my bitfury redfury ASIC anymore, how do I fix this?

OK I have a problem

OP Windows 7

BFGMiner 3.7.0

BiFURY running by itself on a usb 3 hub with a fan

I can get it running and the temp is at about 48C
But after a few miner BFGMiner crashes

Can anyone help

0x4898c8 : C:\Users\Douglas Seager\Desktop\bfgminer-3.7.0-win32\bfgminer.exe : /
home/luke-jr/Projects/Education/Tonal/BitCoin/bfgminer/make-release-tmp/bfgminer
-3.7.0-tmp/driver-bifury.c (467) : in function (bifury_poll)
0x42c9ac : C:\Users\Douglas Seager\Desktop\bfgminer-3.7.0-win32\bfgminer.exe : /
home/luke-jr/Projects/Education/Tonal/BitCoin/bfgminer/make-release-tmp/bfgminer
-3.7.0-tmp/deviceapi.c (641) : in function (minerloop_queue)
0x42ccb3 : C:\Users\Douglas Seager\Desktop\bfgminer-3.7.0-win32\bfgminer.exe : /
home/luke-jr/Projects/Education/Tonal/BitCoin/bfgminer/make-release-tmp/bfgminer
-3.7.0-tmp/deviceapi.c (688) : in function (miner_thread)
Failed to init bfd from (C:\Users\Douglas Seager\Desktop\bfgminer-3.7.0-win32\pt
hreadGC2.dll)
0x6248671b : C:\Users\Douglas Seager\Desktop\bfgminer-3.7.0-win32\pthreadGC2.dll
 : pthread_create
Failed to init bfd from (C:\Windows\syswow64\msvcrt.dll)
0x77221287 : C:\Windows\syswow64\msvcrt.dll : itow_s
Failed to init bfd from (C:\Windows\syswow64\msvcrt.dll)
0x77221328 : C:\Windows\syswow64\msvcrt.dll : endthreadex
Failed to init bfd from (C:\Windows\syswow64\kernel32.dll)
0x76ce336a : C:\Windows\syswow64\kernel32.dll : BaseThreadInitThunk
Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll)
0x779a9f72 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain
Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll)
0x779a9f45 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain

C:\Users\Douglas Seager\Desktop\bfgminer-3.7.0-win32>

They don't seem to like to play together.  3.7 starts and recognizes the Jalapeno, Blue Fury and BiFury but if I try to add the erupters it crashes quickly.  After dinner I'll try running the BEs on a separate hub and see if that makes any difference.

and then it crashed.  

Edit:  LOL

I know this has to be something stupid that I'm missing but I'm running Ubuntu 12.04 on a 32bit MacMini.  It's up to date.  I just compiled BFGMiner 3.7.0 on it and it runs and recognizes my BEs, my BF and my Jalapeno.  My Bi-Fury will not start no matter which driver I try.  I've tried bifury, twinfury, bitfury and bigpic and none of them discovers it.  It is showing up in /dev as /ttyACM1 but even probing that doesn't produce any results.  I was able to get it discovered in 3.6.0 using bigpic but it only produced 100% HW errors.  Any ideas?

Edit: changed /ttyUSBACM1 to /ttyACM1

Solved my own problem.  Just had to apply my edit here to what I input in BFGMiner

Any chance we'll see a new scan flag that says either "scan all except dev:port" or "scan range dev:port-port" ?  Would be great for systems where non-mining devices like a keyboard that never moves needs to be protected from scan data while miners are frequently being added or moved around in the usb chains, which currently mean lots of config file changes to limit scan to the mining ports.

It's a shame not so many people are aware of the BeagleBone Black - only marginally more expensive than the RaspberryPi, has 2GB flash memory on board, USB that works, and is a bit faster. 

I do run a RPi myself, only because I happened to have one.  If I were starting again, I'd run a BeagleBone.

At the price of the Pi, It's not worth the grief that comes with trying to mix devices.
Just buy another one and run as a separate rig. That way when something DOES go wrong, you keep some mining capacity.
Everything is on the SD card, so it only takes seconds to switch Devices around and swap cards.

hmm, alright, I'll see if I can reach out to Barntech some, as most people have already received their Drillbit thumbs and all the boards have been mailed out (personally hoping to see mine Friday or Saturday). At the request of some others I made a MinePeon image with CGMiner compiled with the drillbit drivers and a few other drivers (apparently the drillbit drivers don't seem to play with with the bitfury drivers, can't say for sure yet, as I just had one person with some thumbs test the compile I made, I am shooting in the dark all the same).

I've still not had any interaction with Drillbit in a while...
Most cgminer drivers are not really usable outside of cgminer, unfortunately.
I could try to reverse engineer the code, but until I receive my sample unit to test with, it's difficult to write bug-free code.
Plus, there's a possibility when Drillbit does finally contact me, they'll have some protocol documentation which would save a lot of time so I don't need to reverse engineer it.
So overall, it makes more sense to just wait for Drillbit to follow through IMO.

Just curious, how are bifury/twinfury being detected on 3.7.0?

@Luke-Jr - Any releases with drillbit bitfury drivers coming?

I know the drillbit boards needed their own drivers aside from the bitfury drivers in CGMiner, but I would personally rather use BFGMiner as it just seems to be more stable on the RaspberryPi's, CGMiner seems to be having issues with libusb regarding timing lately, but I've never had an issue with BFGMiner.

If you need the drives being used in CGMiner let me know, happy to provide them.

I'm baffled as to why bfgminer keeps crashing on this system. Why is it looking for USB devices when I'm trying to mine scrypt?

-S opencl:auto

How are GPUs detected now? How do I pass specific settings per device via command flags? (thread-concurrency, gpu-engine, etc)