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

[synf2n]

Hi.

I built bfgminer from source (git from  a couple of days ago)  for my ARM based QNAP NAS (linux). It's version  3.1.4.

I have my NAS connected to a dlink USB hub and 7 USB eruptors plugged into that. 

Code:

./bfgminer

with no options returns:

Code:

All devices disabled, cannot mine!

I have tried :

Code:

./bfgminer -S all  

Code:

./bfgminer -S /dev/usb/ttyUSBX  

as well as trying it with -G to turn off GPU mining but with no luck.

Here is the device output from bfgminer -D -T -d?

Code:

[/share/HDA_DATA/Qdownload/bfgminer] # ./bfgminer -D -T -d?                             
 [2013-08-22 01:19:09] setrlimit: Soft fd limit already identical to hard limit (1024)                    
 [2013-08-22 01:19:09] Timers: Using clock_gettime(CLOCK_MONOTONIC)                    
 [2013-08-22 01:19:09] Started bfgminer 3.1.4                    
 [2013-08-22 01:19:09] ft232r_scan: Found 1d6b:0002 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 05e3:0608 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 05e3:0610 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 05e3:0610 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 10c4:ea60 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 10c4:ea60 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 10c4:ea60 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 10c4:ea60 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 10c4:ea60 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 10c4:ea60 - not a ft232r                    
 [2013-08-22 01:19:09] ft232r_scan: Found 10c4:ea60 - not a ft232r                    
 [2013-08-22 01:19:09] DISPLAY not set, setting :0 just in case                    
 [2013-08-22 01:19:09] Failed to load OpenCL library, no GPUs usable                    
 [2013-08-22 01:19:09] Not a ZTEX device 1d6b:0002                    
 [2013-08-22 01:19:09] Not a ZTEX device 05e3:0608                    
 [2013-08-22 01:19:09] Not a ZTEX device 05e3:0610                    
 [2013-08-22 01:19:09] Not a ZTEX device 05e3:0610                    
 [2013-08-22 01:19:09] Not a ZTEX device 10c4:ea60                    
 [2013-08-22 01:19:09] Not a ZTEX device 10c4:ea60                    
 [2013-08-22 01:19:09] Not a ZTEX device 10c4:ea60                    
 [2013-08-22 01:19:09] Not a ZTEX device 10c4:ea60                    
 [2013-08-22 01:19:09] Not a ZTEX device 10c4:ea60                    
 [2013-08-22 01:19:09] Not a ZTEX device 10c4:ea60                    
 [2013-08-22 01:19:09] Not a ZTEX device 10c4:ea60                    
 [2013-08-22 01:19:09] Devices detected:                    
0 devices listed

THis is the configuration optins summary

Code:

------------------------------------------------------------------------
bfgminer 3.1.4
------------------------------------------------------------------------


Configuration Options Summary:

  curses.TUI...........: FOUND: ncursesw5
  scrypt...............: Disabled

  OpenCL...............: Enabled
    sensors.monitoring.: Disabled
    ADL.monitoring.....: Enabled
  Avalon.ASICs.........: Enabled
  BitForce.devices.....: Enabled
  Icarus.FPGAs.........: Enabled
  ModMiner.FPGAs.......: Enabled
  X6500.FPGAs..........: Enabled
  ZTEX.FPGAs...........: Enabled
  libudev.detection....: no

  CPU Mining...........: Disabled

Compilation............: make (or gmake)
  CPPFLAGS.............: -I/opt/include -I/opt/include/ncursesw -pthread
  CFLAGS...............: -g -O2 -I/share/HDA_DATA/.qpkg/Optware/bin/../lib/gcc/../../include/libusb-1.0 -pthread
  LDFLAGS..............: -pthread -lpthread
  LDADD................: -lrt -ldl -L/usr/local/lib/libcurl -ljansson -L/opt/lib -lncursesw -lm -lusb-1.0

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

and this is my dmseg | tail:

Code:

[/share/HDA_DATA/Qdownload/bfgminer] # dmesg | tail
[356363.150000] usb 1-1.3.1: new high speed USB device using orion-ehci and address 22
[356363.280000] hub 1-1.3.1:1.0: USB hub found
[356363.280000] hub 1-1.3.1:1.0: 4 ports detected
[356363.420000] usb 1-1.3.2: new full speed USB device using orion-ehci and address 23
[356363.630000] usb 1-1.3.3: new full speed USB device using orion-ehci and address 24
[356363.840000] usb 1-1.3.4: new full speed USB device using orion-ehci and address 25
[356364.050000] usb 1-1.3.1.1: new full speed USB device using orion-ehci and address 26
[356364.290000] usb 1-1.3.1.2: new full speed USB device using orion-ehci and address 27
[356364.500000] usb 1-1.3.1.3: new full speed USB device using orion-ehci and address 28
[356364.730000] usb 1-1.3.1.4: new full speed USB device using orion-ehci and address 29
[/share/HDA_DATA/Qdownload/bfgminer] # 

Any help/pointers from anyone on what I might be doing wrong would be greatly appreciated.
Is it something to do with libudev.detection?
I am finding it difficult to understand the correct way to configure the new auto-detection for USB BE's. Everyone seems to do it differently.
 I know if no mining devices are found it's a USB driver problem possibly? But how to fix that on linux? (not ubuntu(ipkg based system)) (I built most of the bfgminer dependencies from source)

Cheers!

[Luke-Jr]

Code:

[/share/HDA_DATA/Qdownload/bfgminer] # dmesg | tail
[356363.150000] usb 1-1.3.1: new high speed USB device using orion-ehci and address 22
[356363.280000] hub 1-1.3.1:1.0: USB hub found
[356363.280000] hub 1-1.3.1:1.0: 4 ports detected
[356363.420000] usb 1-1.3.2: new full speed USB device using orion-ehci and address 23
[356363.630000] usb 1-1.3.3: new full speed USB device using orion-ehci and address 24
[356363.840000] usb 1-1.3.4: new full speed USB device using orion-ehci and address 25
[356364.050000] usb 1-1.3.1.1: new full speed USB device using orion-ehci and address 26
[356364.290000] usb 1-1.3.1.2: new full speed USB device using orion-ehci and address 27
[356364.500000] usb 1-1.3.1.3: new full speed USB device using orion-ehci and address 28
[356364.730000] usb 1-1.3.1.4: new full speed USB device using orion-ehci and address 29
[/share/HDA_DATA/Qdownload/bfgminer] # 

This suggests you don't have the cp210x driver (part of Linux).

It should say:

Code:

[3551139.516400] usb 1-5.1.1: new full-speed USB device number 45 using ehci_hcd
[3551139.609866] usb 1-5.1.1: New USB device found, idVendor=10c4, idProduct=ea60
[3551139.609874] usb 1-5.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[3551139.609881] usb 1-5.1.1: Product: Block Erupter Sapphire (Silver)
[3551139.609886] usb 1-5.1.1: Manufacturer: Bitfountain
[3551139.609891] usb 1-5.1.1: SerialNumber: ljr0002
[3551139.610704] cp210x 1-5.1.1:1.0: cp210x converter detected

[ewibit]

what is this?
always after ~1 hour I get this with BFL LS and then nothing going on..


only restarting BFGMiner helps

[Luke-Jr]

Luke,

Is there a way for bfgminer to set the minimum difficulty?  I always thought pools decide what the minimum difficulty suppose to be and they tell miners what is the share difficulty.  But just wondering if there is a way to tell the pool, "hey, I'm fast, don't bother sending me shares lower than XXX".

Thanks,
af_newbie

See --request-diff (GBT only until 3.2.0, released any hour now...)

[af_newbie]

Luke,

Is there a way for bfgminer to set the minimum difficulty?  I always thought pools decide what the minimum difficulty suppose to be and they tell miners what is the share difficulty.  But just wondering if there is a way to tell the pool, "hey, I'm fast, don't bother sending me shares lower than XXX".

Thanks,
af_newbie

See --request-diff (GBT only until 3.2.0, released any hour now...)

Thanks Luke.  Much appreciated.

[ewibit]

 

[Luke-Jr]

 

It looks like a bad USB cable or something. :/

[dlasher]

^^^ happened to me today too. BFGminer complained about individual cores being "sick". Avg temps <60C.

Sorry BFGminer, back on the shelf, cgminer returns for now. Will wait another few months and try bfgminer again.

[HellDiverUK]

Sorry BFGminer, back on the shelf, cgminer returns for now. Will wait another few months and try bfgminer again.

Or fix your USB hub or cables?

[vulgartrendkill]

Luke,

Is there a way for bfgminer to set the minimum difficulty?  I always thought pools decide what the minimum difficulty suppose to be and they tell miners what is the share difficulty.  But just wondering if there is a way to tell the pool, "hey, I'm fast, don't bother sending me shares lower than XXX".

Thanks,
af_newbie

See --request-diff (GBT only until 3.2.0, released any hour now...)

Thanks Luke.  Much appreciated.

Does that mean that if the pool I use selects say difficulty 3 for me and I can use the request difficulty function to reduce difficulty and therefore increase my share percentage/increase btc income ?

[Taugeran]

Luke,

Is there a way for bfgminer to set the minimum difficulty?  I always thought pools decide what the minimum difficulty suppose to be and they tell miners what is the share difficulty.  But just wondering if there is a way to tell the pool, "hey, I'm fast, don't bother sending me shares lower than XXX".

Thanks,
af_newbie

See --request-diff (GBT only until 3.2.0, released any hour now...)

Thanks Luke.  Much appreciated.

Does that mean that if the pool I use selects say difficulty 3 for me and I can use the request difficulty function to reduce difficulty and therefore increase my share percentage/increase btc income ?

sorry bud, answer is no, while you could try, the pool would do 1 of two things:
    take requested difficulty, then jack it back up because of your aggregate hashrate
or  refuse it and keep requesting what it sent you.

LJR please correct if im mistaken:

--request-diff only works going up, not back down; and is used as a means to lower TCP/IP network chatter and bandwidth by Rasing the difficulty that your miner accepts as shares

[-Redacted-]

EMC uses GBT, so --request-diff should be working for you in the current version of bfgminer.

[af_newbie]

EMC uses GBT, so --request-diff should be working for you in the current version of bfgminer.

Just tried GBT, on port 8337.  Miner is not hashing.  What is "BW" in bfgminer?

"request-diff" : "400",

I get "Work stale due to block mismatch" errors.  After a while I get to 8GH/s rate for each single (getting 60GH/s on stratum).

The starting diff is at 2, even though I requested 400.

I don't know what it is doing but the hash rate slowly (after 40 minute run) went to 270 GH/s and diff 342

I think I'm done testing GBT 

[candoo]

win download link doesnt work

[Taugeran]

win download link doesnt work

http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.1.4/

browse and download from there

[vulgartrendkill]

Does that mean that if the pool I use selects say difficulty 3 for me and I can use the request difficulty function to reduce difficulty and therefore increase my share percentage/increase btc income ?

You'll not be making any more money.  If you submit diff 3 share, it is the same as submitting three diff 1 shares.
Dynamic diff implemented by most pools is to limit network traffic, detect fast miners and send them less but harder shares to solve.

What we are talking about here is the minimum difficulty the pool will offer. 

Problem I'm having with mini rigs is that when they connect to a pool that starts off with diff 2 (and does not allow me to raise the minimum difficulty), miner starts off hashing tons of diff 2 shares, then pool slowly adjusts diff to 300 or higher, and (somehow) all the diff 2 shares that were calculated become rejected (unknown work).  Not sure why, but that is what I see.  Sometimes a pool might drop the diff back to 2, due to a bug or network disconnects, and fast miners start the process again from diff 2 back up to 300-400s.

If I can set the minimum diff at the pool (using EMC at the moment, and it does not offer this option) or in the miner, I could avoid the problem of adjusting the difficulty level.

Telling a pool: "Please send only diff XXX or higher shares"  would manually speed up this negotiation.

I think this feature might become more important as more ASICs are deployed.

Gotcha.

Makes sense now I think about it.

Thanks

[bitcoinsucker1]

Link not working to download

[OgNasty]

Link not working to download

+1, anyone else got a working link?

[Hunyadi]

What is this error <job '2116' not found> ?

Also, download link doesn't work.

[WhiteBeard]

I just had 2 instances of "fragmentation fault. Core dumped."  On restart from the first instance I noticed a few [NULL] lines in the share submissions shortly before the second fragfault.  I rebooted at that point and have had no more dumps in the past hour.

Running Ubuntu 13.04 on 64 bit AMD quad core processor with 4 Gig of RAM.  BFGMiner is the only thing that has been running on this machine for the past week.  Maybe it was just time to re-boot.  The only thing different today is that I shut down bfgminer and added 4 more usb eruptors and a new usb hub then restarted.

Will see if I can find the core dump if that will be helpful...