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

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: purelithium on November 29, 2013, 07:34:13 PM

I get this output when running the git you linked to with my optimal scrypt settings that worked with 3.2.1, then it immediately crashes:

One thing maybe worth trying is changing your -d 0 -d 1 etc to -d OCL0 -d OCL1 etc. Just a thought as I know some code changed there.

purelithium

hero member

Activity: 504

Merit: 500

I get this output when running the git you linked to with my optimal scrypt settings that worked with 3.2.1, then it immediately crashes:

Code:

C:\Users\BigMiner\Desktop\New folder>bfgminer.exe --scrypt  -I 13,19,19,19 --thr
ead-concurrency 16384,22400,22400,22400 --gpu-engine 1045,1150,1050,1050 --gpu-m
emclock 1450,1420,1425,1425 -w 256,256,256,256 --auto-fan --failover-only --gpu-
powertune 0,20,20,20 --scan-serial all --scan-serial opencl:auto -o pool1.us.mul
tipool.us:3345 -u user -p "" -d 0 -d 1 -d 2 -d 3 -T
 [2013-11-29 19:30:51] Started bfgminer 3.7.0
 [2013-11-29 19:30:51] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-29 19:30:51] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-29 19:30:51] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-29 19:30:51] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-29 19:30:51] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-29 19:30:51] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-29 19:30:51] Failed to get PortName registry key value in lowl-vcom.c
_vcom_devinfo_scan_windows__hubport():443: The system cannot find the file speci
fied.

 [2013-11-29 19:30:51] Failed to ioctl (1) in lowl-vcom.c windows_usb_get_root_h
ub_path():497: The operation completed successfully.

 [2013-11-29 19:30:53] Twinfury: Not a valid response from device (-1)

 [2013-11-29 19:30:54] klondike_lowl_probe: Matched "(null)" serial "(null)", bu
t lowlevel driver is not usb!
 [2013-11-29 19:30:56] x6500_lowl_probe: Matched "(null)" serial "(null)", but l
owlevel driver is not ft232r!
 [2013-11-29 19:30:56] ztex_lowl_probe: Matched "(null)" serial "(null)", but lo
wlevel driver is not usb!
 [2013-11-29 19:31:00] Read of fd 3 returned 0
 [2013-11-29 19:31:00] nanofury_lowl_probe: Matched "(null)" serial "(null)", bu
t lowlevel driver is not mcp2210!
 [2013-11-29 19:31:00] hashbuster_lowl_probe: Matched "(null)" serial "(null)",
but lowlevel driver is not hid!
 [2013-11-29 19:31:00] hashbuster2_lowl_probe: Matched "(null)" serial "(null)",
 but lowlevel driver is not usb_generic!
 [2013-11-29 19:31:02] Probing for an alive pool
 [2013-11-29 19:31:03] Pool 0 http://pool1.us.multipool.us:3345 alive

 [2013-11-29 19:31:03] Network difficulty changed to 1 (13.44Mh/s)

 [2013-11-29 19:31:03] Stratum from pool 0 detected new block

 [2013-11-29 19:31:03] Pool 0 is hiding block contents from us

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: noct on November 29, 2013, 06:01:10 PM

Same here. Windows 7 x64.
bfgminer -D -d? finds this:

[2013-11-30 00:47:06] lowlevel_scan: Found hid device at hid:\\?\hid#vid_fa04&p
id_0011#6&11d06e40&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (path=\\?\hid#v
id_fa04&pid_0011#6&11d06e40&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vid=f
a04, pid=0011, manuf=StarFury Laboratories, prod=HashBuster.nano Project, serial
= )

But i only get "waiting for devices: press m+ to add, or q to quit."
Can anyone help?

I need the whole output from -D -d?

Quote from: purelithium on November 29, 2013, 06:05:37 PM

Quote from: purelithium on November 27, 2013, 08:38:31 PM

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?

Code:


C:\Mining\bfgminer-3.7.0-win64>bfgminer.exe --scrypt -T
 [2013-11-27 20:36:26] Started bfgminer 3.7.0
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] Failed to get PortName registry key value in lowl-vcom.c
_vcom_devinfo_scan_windows__hubport():443: The system cannot find the file speci
fied.

 [2013-11-27 20:36:26] Failed to ioctl (1) in lowl-vcom.c windows_usb_get_root_h
ub_path():497: The operation completed successfully.


C:\Mining\bfgminer-3.7.0-win64>

I used WeBisect session "purelithiumNov29" to try and bisect the problem. This is what it gave me once I bisected all I could:

Code:

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
e61f3a480388cfabe4dd7ddcbd643c6d7390c751
745bd11dc27a745f42fdb2361da60e0ca5bc5fa6
dd43825dbb5300d8509e7da8bba4d4599a98f719
ebf66582ace0fe5b7162f2d896a5b59043707a85
fd7d89dfef7398bedfd7d6f00ac6601a441a2d28
a651e94616c4c3c5eb9aefc7b2c350e8793e6628
ce4eba9042cdd3070a9770699987cd3d4005fc2f
f84c1a473f8618c46750701c249eddbf940d240f
We cannot bisect more!

The build I got before that message didn't have the error I described in my quoted message, but It did have another issue of crashing almost immediately on connecting to a pool. Not sure how I could bisect that one... As of right now 3.2.1 is the only functional build for my machine.

Please test the latest git: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

purelithium

hero member

Activity: 504

Merit: 500

Quote from: purelithium on November 27, 2013, 08:38:31 PM

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?

Code:


C:\Mining\bfgminer-3.7.0-win64>bfgminer.exe --scrypt -T
 [2013-11-27 20:36:26] Started bfgminer 3.7.0
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-27 20:36:26] Failed to get PortName registry key value in lowl-vcom.c
_vcom_devinfo_scan_windows__hubport():443: The system cannot find the file speci
fied.

 [2013-11-27 20:36:26] Failed to ioctl (1) in lowl-vcom.c windows_usb_get_root_h
ub_path():497: The operation completed successfully.


C:\Mining\bfgminer-3.7.0-win64>

I used WeBisect session "purelithiumNov29" to try and bisect the problem. This is what it gave me once I bisected all I could:

Code:

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
e61f3a480388cfabe4dd7ddcbd643c6d7390c751
745bd11dc27a745f42fdb2361da60e0ca5bc5fa6
dd43825dbb5300d8509e7da8bba4d4599a98f719
ebf66582ace0fe5b7162f2d896a5b59043707a85
fd7d89dfef7398bedfd7d6f00ac6601a441a2d28
a651e94616c4c3c5eb9aefc7b2c350e8793e6628
ce4eba9042cdd3070a9770699987cd3d4005fc2f
f84c1a473f8618c46750701c249eddbf940d240f
We cannot bisect more!

The build I got before that message didn't have the error I described in my quoted message, but It did have another issue of crashing almost immediately on connecting to a pool. Not sure how I could bisect that one... As of right now 3.2.1 is the only functional build for my machine.

noct

newbie

Activity: 11

Merit: 0

Quote from: Badonkadonk on November 29, 2013, 07:34:07 AM

anyone that could help me to figure out how to run these hashbuster nano bords?
been trying for hours and now im ready to start banging my head to the wall x)

im on win 8.1, and installed the drivers with zadig.
i have reconnected all 5 of the boards a billion times, both usb cable and power cable.
i have rebooted countless times. i think i have tried pretty much everything in every post i have found that has made any kind off sense to me.

these where working fine until yesterday using virtualbox and the custom cgminer that hashbuster released.
then i rebooted and it all went to hell.

all i get now is "waiting for devices: press m+ to add, or q to quit.

any help is appreciated
thanks

edit: i tried version 3.5.1, 3.2.7, 3.5.3 and 3.7.0

Same here. Windows 7 x64.
bfgminer -D -d? finds this:

[2013-11-30 00:47:06] lowlevel_scan: Found hid device at hid:\\?\hid#vid_fa04&p
id_0011#6&11d06e40&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (path=\\?\hid#v
id_fa04&pid_0011#6&11d06e40&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vid=f
a04, pid=0011, manuf=StarFury Laboratories, prod=HashBuster.nano Project, serial
= )

But i only get "waiting for devices: press m+ to add, or q to quit."
Can anyone help?

elrock

newbie

Activity: 41

Merit: 0

I mine on Ubuntu not Mac so I don't use homebrew for bfgminer. (I just use a Mac to check status.)

Anyway, problem solved -- I was running the older version by mistake.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: elrock on November 29, 2013, 11:29:41 AM

I use a Macbook to ssh into an Ubuntu rig, and I'm still seeing this bug in the Mac's display, even after building from the latest git. Not a big deal since it's still hashing away. Is there a way to rebuild *with* unicode support?

How did you build from Git? I just double-checked myself on OS X 10.9 and the issue seems fixed to me.

To install the latest bfgminer from Git using Homebrew you can do:

Code:

brew tap nwoolls/xgminer
brew install bfgminer --HEAD

elrock

newbie

Activity: 41

Merit: 0

Quote from: Luke-Jr on November 27, 2013, 03:29:18 PM

Quote from: jedimstr on November 27, 2013, 03:26:41 PM

Running 3.7.0 compiled using Homebrew.

The running stats log on the second half of the terminal window does not have any line breaks. It updates as one continuous string that just fills the bottom of the screen:

Bug when compiled without unicode support. Already fixed in git.

I use a Macbook to ssh into an Ubuntu rig, and I'm still seeing this bug in the Mac's display, even after building from the latest git. Not a big deal since it's still hashing away. Is there a way to rebuild *with* unicode support?

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Badonkadonk on November 29, 2013, 07:34:07 AM

any special drivers i should be using?

The default, standard USB HID driver.

Badonkadonk

hero member

Activity: 560

Merit: 500

Quote from: jedimstr on November 29, 2013, 07:17:36 AM

Quote from: Badonkadonk on November 29, 2013, 06:55:53 AM

anyone that could help me to figure out how to run these hashbuster nano bords?
been trying for hours and now im ready to start banging my head to the wall x)

im on win 8.1, and installed the drivers with zadig.
i have reconnected all 5 of the boards a billion times, both usb cable and power cable.
i have rebooted countless times. i think i have tried pretty much everything in every post i have found that has made any kind off sense to me.

these where working fine until yesterday using virtualbox and the custom cgminer that hashbuster released.
then i rebooted and it all went to hell.

all i get now is "waiting for devices: press m+ to add, or q to quit.

any help is appreciated
thanks

edit: i tried version 3.5.1, 3.2.7, 3.5.3 and 3.7.0

That's your problem right there... Zadig. BFGMiner doesn't use Zadig last I checked. That's for CGMiner.

well, i uninstalled the minsers in device manager. no change.
any special drivers i should be using?

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: Badonkadonk on November 29, 2013, 06:55:53 AM

anyone that could help me to figure out how to run these hashbuster nano bords?
been trying for hours and now im ready to start banging my head to the wall x)

im on win 8.1, and installed the drivers with zadig.
i have reconnected all 5 of the boards a billion times, both usb cable and power cable.
i have rebooted countless times. i think i have tried pretty much everything in every post i have found that has made any kind off sense to me.

these where working fine until yesterday using virtualbox and the custom cgminer that hashbuster released.
then i rebooted and it all went to hell.

all i get now is "waiting for devices: press m+ to add, or q to quit.

any help is appreciated
thanks

edit: i tried version 3.5.1, 3.2.7, 3.5.3 and 3.7.0

That's your problem right there... Zadig. BFGMiner doesn't use Zadig last I checked. That's for CGMiner.

Badonkadonk

hero member

Activity: 560

Merit: 500

anyone that could help me to figure out how to run these hashbuster nano bords?
been trying for hours and now im ready to start banging my head to the wall x)

im on win 8.1, and installed the drivers with zadig.
i have reconnected all 5 of the boards a billion times, both usb cable and power cable.
i have rebooted countless times. i think i have tried pretty much everything in every post i have found that has made any kind off sense to me.

these where working fine until yesterday using virtualbox and the custom cgminer that hashbuster released.
then i rebooted and it all went to hell.

all i get now is "waiting for devices: press m+ to add, or q to quit.

any help is appreciated
thanks

edit: i tried version 3.5.1, 3.2.7, 3.5.3 and 3.7.0

HellDiverUK

hero member

Activity: 1246

Merit: 501

Does the new version's scanning system mean it's possible to run BlueFuzzies, Block Erupters and other USB miners without having to manually input device names?

I'm running various different USB miners off MinePeon/BFG 3.6.0 and it's a total pain in the hole having to manually configure device names. I'd rather go back to running BFGMiner on Linux or Windows than mess with all that shit every time I move a USB device or reboot.

drewage

member

Activity: 262

Merit: 10

Quote from: albon on November 28, 2013, 06:51:29 PM

Quote from: Luke-Jr on November 28, 2013, 06:31:10 PM

Quote from: albon on November 28, 2013, 06:27:57 PM

Quote from: Luke-Jr on November 28, 2013, 06:24:46 PM

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

Every time I run it.

Can you send me your current firmware?

Would love to but how the F'@K do you shot them out.

I have tried silver paper and selotape and nothing just shows up again as BiFury Huh

Luke-Jr can you use a pencil mod to short them? I was wondering the same thing.

crazyearner

legendary

Activity: 1820

Merit: 1001

How to get gpu mining working in the new version ? on windows 7 plz

albon

legendary

Activity: 1932

Merit: 1549

Quote from: Luke-Jr on November 28, 2013, 06:31:10 PM

Quote from: albon on November 28, 2013, 06:27:57 PM

Quote from: Luke-Jr on November 28, 2013, 06:24:46 PM

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

Every time I run it.

Can you send me your current firmware?

Would love to but how the F'@K do you shot them out.

I have tried silver paper and selotape and nothing just shows up again as BiFury Huh

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: albon on November 28, 2013, 06:27:57 PM

Quote from: Luke-Jr on November 28, 2013, 06:24:46 PM

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

Every time I run it.

Can you send me your current firmware?

albon

legendary

Activity: 1932

Merit: 1549

Quote from: Luke-Jr on November 28, 2013, 06:24:46 PM

Quote from: cxboyminer on November 28, 2013, 05:22:26 PM

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

Cant mine...

Need a backtrace or bisect.

Quote from: odinhf on November 28, 2013, 05:11:43 PM

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

Need output from

Code:

bfgminer -D -d?

Quote from: drewage on November 28, 2013, 02:19:03 PM

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.

Need a backtrace or bisect.

Quote from: albon on November 28, 2013, 03:16:42 PM

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>

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

Every time I run it.

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

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: cxboyminer on November 28, 2013, 05:22:26 PM

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

Cant mine...

Need a backtrace or bisect.

Quote from: odinhf on November 28, 2013, 05:11:43 PM

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

Need output from

Code:

bfgminer -D -d?

Quote from: drewage on November 28, 2013, 02:19:03 PM

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.

Need a backtrace or bisect.

Quote from: albon on November 28, 2013, 03:16:42 PM

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>

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

cxboyminer

hero member

Activity: 896

Merit: 500

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

Cant mine...

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