Author

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

legendary
Activity: 1066
Merit: 1098
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.
hero member
Activity: 1246
Merit: 501
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?
legendary
Activity: 1066
Merit: 1098
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 ".  Then you will have the whole GUI at your disposal if you want.  But that was not the original question.
hero member
Activity: 574
Merit: 501
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...
legendary
Activity: 1066
Merit: 1098
& 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 &

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.
legendary
Activity: 2576
Merit: 1186
Personally, I would use GNU screen.
If you really want to background it the classical way:
Code:
bfgminer -T &>some.log &
disown
hero member
Activity: 574
Merit: 501
& 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 &

But screen is much easier to work with than a backgrounded process and allows you to reconnect to your bfgminer console session at will.
legendary
Activity: 1066
Merit: 1098
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 &
hero member
Activity: 574
Merit: 501
screen bash
run your bfgminer command
CTL-A d to disconnect
logout
screen -r to reconnect when you log back in
hero member
Activity: 1246
Merit: 501
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.
hero member
Activity: 1246
Merit: 501

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. Smiley 

The author of the "other" miner says that you MUST run the BitFury chips off a RPi.  Herp Derp.  Roll Eyes
legendary
Activity: 2576
Merit: 1186
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.

Your video is inverted in both dimensions btw O.o
legendary
Activity: 2576
Merit: 1186
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.
legendary
Activity: 2058
Merit: 1005
this space intentionally left blank
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?
hero member
Activity: 1246
Merit: 501
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?
hero member
Activity: 658
Merit: 500
CCNA: There i fixed the internet.
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
hero member
Activity: 518
Merit: 500
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.
legendary
Activity: 922
Merit: 1003
Huh, odd that I've never had bfgminer crash, ever, in about a year of mining.   Huh  That's on home-built machines (Asus boards), or on OEM Asus PC. 
Maybe your machines aren't as stable as you think?
There are many variables in play here, hardware and software; I don't have the tools necessary to determine the root cause and there's little point in speculating. If some software crashes once in a blue moon I don't worry about it much. Especially when it can be easily mitigated.

The reason I say that it isn't the machine (hardware), is that (1) I have 4 different machines on which I have encountered bfgminer crashes and (2) enough other people have reported crashes. It has happened often enough in the past that I have sometimes watched the crash first-hand as it happened. On those occasions there was always a network/pool issue associated with it: either my pool (bitminter) crashed, or my wireless went down. Luke and I have worked together to debug some of these crashes in the past with some success.

The quoted batch file is for Windows machines. Do you run Windows as well, or Linux? Anecdotally it seems that bfgminer is more stable running on Linux. My understanding is that bfgminer is developed on Linux and has been 'ported' to Windows; it isn't what would be normally considered a 'native' Windows app. And I run Windows.
newbie
Activity: 17
Merit: 0
The machine is 100% stable, Epoch explained it well Wink

Thx again for the loop Wink

I registered at butterflylabs forums only to say thank you, couldnt pm before 5 posts though Tongue really helped me out as non coder
hero member
Activity: 1246
Merit: 501
Huh, odd that I've never had bfgminer crash, ever, in about a year of mining.   Huh  That's on home-built machines (Asus boards), or on OEM Asus PC. 

Maybe your machines aren't as stable as you think?
Jump to: