Bitcoin Forum
May 10, 2024, 07:48:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: BFGMiner 3.7.0 Segmentation Fault with Bi•Fury  (Read 1196 times)
askhimthatsoon (OP)
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
November 29, 2013, 10:52:14 PM
 #1

I would post in the correct thread, but being a newbie...

I built the latest BFGMiner from Git repository, first under Mac OS X Mavericks, in order to run with a bunch of Bi•Fury sticks.
Upon starting the miner, everything seems to operate nicely for a few minutes - but then I get a "Segmentation Fault 11".
I thought it might be a Mac OS specific problem and tried the same thing with a single stick on a Raspberry Pi. Compiling again with default settings (with disabled hashbuster driver, as this throws an include error on the rpi), I had the same result, just a bit quicker (the stick wasn't even warm yet...) - Segmentation Fault.

Anyone an idea why this happens or an idea for a workaround? I am assuming it has nothing to do with the Bi•Furys themselves...

http://thatapp.de/ScreenShot2.png
"This isn't the kind of software where we can leave so many unresolved bugs that we need a tracker for them." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715370512
Hero Member
*
Offline Offline

Posts: 1715370512

View Profile Personal Message (Offline)

Ignore
1715370512
Reply with quote  #2

1715370512
Report to moderator
1715370512
Hero Member
*
Offline Offline

Posts: 1715370512

View Profile Personal Message (Offline)

Ignore
1715370512
Reply with quote  #2

1715370512
Report to moderator
1715370512
Hero Member
*
Offline Offline

Posts: 1715370512

View Profile Personal Message (Offline)

Ignore
1715370512
Reply with quote  #2

1715370512
Report to moderator
jedimstr
Hero Member
*****
Offline Offline

Activity: 798
Merit: 1000



View Profile
December 12, 2013, 03:58:05 PM
 #2

I'm seeing the same behavior, even after updating the firmware.

I've posted a note in the Bi*fury thread and linked back to this post to show it wasn't an isolated case. Smiley

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!