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

[Taugeran]

I'm trying to set up my friends new 60gh bfl unit remotely. It connects fine to the pool  but I don't get any accepted, rejected shares. No HW errors either. I've tried it on two of his pc's. A windows 7 and a windows 8. The speed just sits at zero. I tried easyminer as well. Anyone seen something similar or have time to login and try to fix it? The only thing else out of the ordinary is a device that was showing up like another miner, called MMQ. I had to use -s COM4 so it would stop picking up the other device. He said there was nothing else hooked to the pc though.

I would recommend -S bfl:all if it is the only USB miner hooked up to the box

And windows com ports need to be of the form \\.\COMx where x is the number

[HellDiverUK]

Luke-Jr, have you heard anything about the BitFury USB miners?  Someone says they need to be plugged in to a RPi, which sounds like bollocks to me.  USB is USB is USB...and the Pi has a shitty USB implementation if we're being fair to it.

Surely it's just a case of drivers?

[2weiX]

I get this error, both in cgminer and BFGminer for my 30gh/s Little SC:


BitForceSC detected (5:1) invalid s-link count: '--DEVICES IN CHAIN: 00x00'


Here's a vid: https://www.dropbox.com/s/y5adr1ae4okzilk/VID-20130910-WA0004.mp4


Can anyone point me to a solution?

[Luke-Jr]

Luke-Jr, have you heard anything about the BitFury USB miners?  Someone says they need to be plugged in to a RPi, which sounds like bollocks to me.  USB is USB is USB...and the Pi has a shitty USB implementation if we're being fair to it.

Surely it's just a case of drivers?

No mining chips support USB themselves. USB devices require an additional controller chip.
RPi-based Bitfury devices (Metabank and c-scape) are using SPI and GPIO to communicate directly to the chip(s).
There is also the LittleFury, which has a MCU that does (among other things) USB interfacing - this should work on any USB system.

Note that the code for handling BitFury is still immature, and I plan to rewrite a lot of it before merging it into mainline for BFGMiner 3.3.

[Luke-Jr]

I get this error, both in cgminer and BFGminer for my 30gh/s Little SC:

BitForceSC detected (5:1) invalid s-link count: '--DEVICES IN CHAIN: 00x00'

This error is completely impossible with BFGMiner.
I would suspect it is due to cgminer's attempt to reinvent their own non-standard drivers.

If it doesn't work with BFGMiner, using the official FTDI drivers (ie, NOT winusb/zadig), please post the error you get.

Here's a vid: https://www.dropbox.com/s/y5adr1ae4okzilk/VID-20130910-WA0004.mp4

Your video is inverted in both dimensions btw O.o

[HellDiverUK]

There is also the LittleFury, which has a MCU that does (among other things) USB interfacing - this should work on any USB system.

Note that the code for handling BitFury is still immature, and I plan to rewrite a lot of it before merging it into mainline for BFGMiner 3.3.

The LittleFury is what I was talking about.  

The author of the "other" miner says that you MUST run the BitFury chips off a RPi.  Herp Derp. 

[HellDiverUK]

Stupid linux-noob question here.  How do I run bfgminer so it doesn't stop mining when I log out? 

I want to be able to SSH in to my linux box, run BFGMiner, and log out and have it run on.  Currently when I do, an close my SSH session, the miner stops.

[-Redacted-]

screen bash
run your bfgminer command
CTL-A d to disconnect
logout
screen -r to reconnect when you log back in

[xyzzy099]

Stupid linux-noob question here.  How do I run bfgminer so it doesn't stop mining when I log out?  

I want to be able to SSH in to my linux box, run BFGMiner, and log out and have it run on.  Currently when I do, an close my SSH session, the miner stops.

You can use an ampersand after the command to make it execute in a background process.  You may need to redirect stdin and/or stdout to allow ssh to exit cleanly, depending on exactly how you start BFGMiner.

If you have a script that starts BFGMiner with your favorite arguments, you could do this:

% ./bfg_miner_script </dev/null >/dev/null &

[-Redacted-]

& doesn't help, it would still terminate after you logged out.  You would need to use nohup to keep it running the background. So:

nohup <your bfgminer command> &

But screen is much easier to work with than a backgrounded process and allows you to reconnect to your bfgminer console session at will.

[Luke-Jr]

Personally, I would use GNU screen.
If you really want to background it the classical way:

Code:

bfgminer <your options> -T &>some.log &
disown

[xyzzy099]

& doesn't help, it would still terminate after you logged out.  You would need to use nohup to keep it running the background. So:

nohup <your bfgminer command> &

But screen is much easier to work with than a backgrounded process and allows you to reconnect to your bfgminer console session at will.

I just tried it from a Windows machine to my Ubuntu 13.04 machine, and it worked fine.  Screen might be a better solution, but & works fine as long as you make sure stdin and stdout are not attached to the ssh terminal.

[-Redacted-]

True, but then you can't look at the befminer console.  I tend to switch pools every once in a while, or do other things, like look at accepted share counts in the console...

[xyzzy099]

True, but then you can't look at the befminer console.  I tend to switch pools every once in a while, or do other things, like look at accepted share counts in the console...

If the machine has an X server, you could just make sure XDMCP is enabled, then use "X -query <hostname/ip>".  Then you will have the whole GUI at your disposal if you want.  But that was not the original question.

[HellDiverUK]

Thanks for the advice, I'll try that later.  I should have realised about screen - I used that when setting up p2pool.

I've got my TP-Link 703N up and running with OpenWRT, and a 4GB USB stick as / - plenty of space.  Got bfgminer installed.  When I run it, I get the "All Devices Disabled, Cannot Mine!" error.  I assume I'm missing the VCP drivers?  Any pointers on how to get Erupters mining on this thing?

[xyzzy099]

Thanks for the advice, I'll try that later.  I should have realised about screen - I used that when setting up p2pool.

I've got my TP-Link 703N up and running with OpenWRT, and a 4GB USB stick as / - plenty of space.  Got bfgminer installed.  When I run it, I get the "All Devices Disabled, Cannot Mine!" error.  I assume I'm missing the VCP drivers?  Any pointers on how to get Erupters mining on this thing?

Did you try using the '-S erupter:all' switch?  I don't know much about OpenWRT, but that works on Linux.

[Luke-Jr]

Thanks for the advice, I'll try that later.  I should have realised about screen - I used that when setting up p2pool.

I've got my TP-Link 703N up and running with OpenWRT, and a 4GB USB stick as / - plenty of space.  Got bfgminer installed.  When I run it, I get the "All Devices Disabled, Cannot Mine!" error.  I assume I'm missing the VCP drivers?  Any pointers on how to get Erupters mining on this thing?

opkg install kmod-usb-serial-cp210x

[HellDiverUK]

That worked.  Pleased to announce BFG is happily mining away with 11 Block Erupters on a TL-WR703N with a 4GB USB stick.

RAM is a bit tight, but I think it'd run the HTTP proxy thingymabob for the Blades, too, if a nice developer could compile it in. 

[bwstacker]

  I run bfgminer and cgminer on new install and when i start it it comes up with bfgminer has experince an error and needs to close any idea on why this is, I have install bitminter and it runs fine. Cards run fine on linux just can't get them to work with windows. windows will give me a 120 k/h increase in hash rate. cards have worked before with windows. no way i flashed pcb board to only function with linux is there?

[buyer99]

That worked.  Pleased to announce BFG is happily mining away with 11 Block Erupters on a TL-WR703N with a 4GB USB stick.

RAM is a bit tight, but I think it'd run the HTTP proxy thingymabob for the Blades, too, if a nice developer could compile it in.  

Very cool, I've been reading your posts hoping it would work out.

Congratulations HellDiver!


Luke, I want to thank you for what you have done and have sent a small donation your way. I recently rebuilt BFGminer on my pi with 3.2.0 and now with the new getwork option I have my USB's and my blade all happy together in one interface!

My only issue at this point is for some reason 3 out of my 25 sticks show up as BES instead of ICA and are giving me sick/dead restart problems. Before I changed to this version, I have been stable since I set it up. Impressive to say the least. I definitely want my blade connected through BFGminer... So I have isolated the 3 erupters that show up differently and pulled them, now BFG is running like a champ. Not a big deal since my windows machine is always running with my node and so I can just put the 3 "BES"sticks on there. Just thought I would add that information in case someone else is having a similar issue.

 FYI...

I have tried with -G switch and without.
I have tried with the icarus timings and without
 I have tried -S erupter:all   and   --scan-serial erupter:*  

-S all   with the icarus timings  seems to give me the best results, but after a while the 3 sticks which show up as BES go to sick and sometimes dead, also randomly causing problems with other sticks in the process of restarting themselves etc.  Staged work underrun will not increase automatically pass 36 keeps coming up every 2-3 min..  So far since I have removed those 3 from the equation, no messages about staged overrun and it looks like all is well. Hardware errors are also very low... Thanks for everything you do!

Edit: Still no issues, stable like it always was but just got this message "staged work underrun; increasing queue minimum to 2" Doesn't seem to be a problem, I'm sure it has said this many times before (but it's been running so good I haven't been watching it at all) and sorry for being such a newb but google doesn't want to tell me what it means.