I've posted a note in the Bi*fury thread and linked back to this post to show it wasn't an isolated case.
Topic: BFGMiner 3.7.0 Segmentation Fault with Bi•Fury (Read 1208 times)
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.
I've posted a note in the Bi*fury thread and linked back to this post to show it wasn't an isolated case.
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
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
Jump to: