Luke Dashjr

Not sure, sorry. If you run it in strace, does it reveal anything interesting?

Sure, just post a link here.

If you would prefer to email me a private link, feel free to send the link (no attachments please) to [email protected]

See the HACKING file, and maybe reference one of the newer minerloop_queue drivers.

Look at the most recent driver additions, which should have a single commit for the basic build system stuff. Why would there be autogenerated code?

Build with debugging symbols and get a backtrace?

Sounds like a bug in your BIF firmware. Is it a real bi*fury, or some clone? Have you tried to use any of the firmware-bug workarounds in README.ASIC?

--set bifury:\* is global. If you have serial numbers, you can use --set bifury@serial:\* instead

If you set it globally, doing it per-serial shouldn't matter. A debug log would show this.

Another option you may be able to play with is --set bifury:max_queued=N - it defaults to (chips \* 5) + 6 Also note osc6_bits for clock speeds.