Bitcoin Forum>Bitcoin>Mining>Mining software (miners)
Pages:
Author

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

deagel
member
Activity: 67
Merit: 10
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 04:37:35 PM
#2553
Quote from: Cassey on February 11, 2014, 04:33:18 PM
Congrats on getting 3.0 ghz stable - make sure you tell us, or the antminer thread, exactly how you did that!

Can you please share your command line?

hi,
i will do it if my setup is finished.
 i have to go know but i can share it tomorrow.

Cassey
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 04:33:18 PM
#2552
Congrats on getting 3.0 ghz stable - make sure you tell us, or the antminer thread, exactly how you did that!

Can you please share your command line?
deagel
member
Activity: 67
Merit: 10
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 04:13:18 PM
#2551
Quote from: Cassey on February 11, 2014, 03:45:48 PM
Ok.. suggest breaking this down into smaller pieces. 

Just plug in your antminers (which are generally pretty well behaved) and run with a line like:

./bfgminer -S antminer:all --set-device antminer:clock=x0981 -o

And lets see what happens.  That speed is pretty much the normal limit pre-mod, let make sure they all show up at that point.

hi,
ok more infos:

i use:
config one:
windows 8.1
1 x TeckNet® USB 3.0 10 Port Hub
6 x modified antminer

i testet hub, cable and antminer on my windows pc and they are working stable with 3ghs and no hw errors.

config two:
1 x minepeon
6 x modified antminer
3 x D-Link DUB-H7 with 2.2 ghs

working all fine but with less speed

Target configuration:
intel i5 mini pc // ubuntu server minimal install
hub and miner from config one

Code:
bfgminer version 3.10.0 - Started: [2014-02-11 21:58:37] - [  0 days 00:13:28]
 [M]anage devices [P]ool management [S]ettings [D]isplay options                                        [H]elp [Q]uit
 Connected to stratum.mining.eligius.st diff 8 with stratum as user xxxxx
 Block: ...20fe9450 #285323  Diff:2.62G (18.77Ph/s)  Started: [22:01:44]
 ST:6  F:0  NB:2  AS:0  BW:[115/  7 B/s]  E:0.00  I: 0.00 BTC/hr  BS:0
 0            |   0.0/  0.0/  0.0 h/s | A:0 R:0+0(none) HW:0/none
----------------------------------------------------------------------------------------------------------------------
 AMU 0: Initializing...
 AMU 1: Initializing...
 AMU 2: Initializing...
 AMU 3: Initializing...
----------------------------------------------------------------------------------------------------------------------
 [2014-02-11 22:01:25] Stratum from pool 0 requested work update
 [2014-02-11 22:01:44] Stratum from pool 0 detected new block
 [2014-02-11 22:01:47] Stratum from pool 0 requested work update
 [2014-02-11 22:02:17] Stratum from pool 0 requested work update


Cassey
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 03:45:48 PM
#2550
Ok.. suggest breaking this down into smaller pieces.  

Just plug in your antminers (which are generally pretty well behaved) and run with a line like:

./bfgminer -S antminer:all --set-device antminer:clock=x0981 -o

And lets see what happens.  That speed is pretty much the normal limit pre-mod, let make sure they all show up at that point.

Oh, and please let us know the exact line your using (shy your pool info) and exact errors your seeing.  Since you did a clone, I'm presuming your have 3.10.0 code.
deagel
member
Activity: 67
Merit: 10
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 03:29:45 PM
#2549
Quote from: Cassey on February 11, 2014, 03:08:12 PM
I know its bad practice but the first thing I would try is to run it as root.  If that works, at least you know its just a permission problem.

Regarding only a few of the antminers showing up, suggest just restarting a time or time.  They appear to adjust themselves a bit every time they are initialized.  Eventually they should all appear - or you can use the M-->"+" approach.

hi,
thanks for your hint. i try it and it did not work.
Cassey
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 03:08:12 PM
#2548
I know its bad practice but the first thing I would try is to run it as root.  If that works, at least you know its just a permission problem.

Regarding only a few of the antminers showing up, suggest just restarting a time or time.  They appear to adjust themselves a bit every time they are initialized.  Eventually they should all appear - or you can use the M-->"+" approach.
deagel
member
Activity: 67
Merit: 10
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 02:20:46 PM
#2547
Hi,
i have problems with bfgminer from git.

- I have a new installed ubuntu server (minimal + ssh server)
- installed git apt-get install build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev hidapi
- executed:
    git clone https://github.com/luke-jr/bfgminer.git
    ./autogen.sh
    ./configure
    make

and than run:
./bfgminer -S antminer:all --set-device antminer:clock=x4C81 (i have modified ant u1)
got an error like "you do not have the permissions to access /dev/ttyUSB.....

i found this help:
 sudo usermod -a -G dialout $USER

know i got this error
Failed to open Icarus on /dev/ttyUSB1

or
 [2014-02-11 20:16:18] AMU 0: Failed to reopen on /dev/ttyUSB0
 [2014-02-11 20:16:18] AMU 0: Comms error (werr=1)
 [2014-02-11 20:16:18] AMU 0: Failed to reopen on /dev/ttyUSB0
 [2014-02-11 20:16:18] AMU 0 failure, attempting to reinitialize
 [2014-02-11 20:16:18] Failed to open Icarus on /dev/ttyUSB2
 [2014-02-11 20:16:18] AMU 0: Failed to reopen on /dev/ttyUSB0
 [2014-02-11 20:16:18] AMU 0 failure, disabling!
 [2014-02-11 20:16:18] AMU 0 being disabled

and bfgminer did find only 2-3 antminer but i have six connected.

did anybody ave an idea?


Update:
i run:
bfgminer -d? -D -S antminer:all

Code:
miner@uminer-01:~/bfgminer$ ./bfgminer  -d? -D -S antminer:all
 [2014-02-11 20:24:32] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)                    
 [2014-02-11 20:24:32] Started bfgminer 3.10.0                    
 [2014-02-11 20:24:32] Loaded configuration file /home/miner/.bfgminer/bfgminer.conf                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:001:004: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:001:001: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:005:001: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:004:003: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:004:002: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:004:001: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:003:001: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:002:001: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:007:001: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] usb_devinfo_scan: Error opening device usb:006:001: LIBUSB_ERROR_ACCESS                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:006:001 (path=(null), vid=1d6b, pid=0002, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:007:001 (path=(null), vid=1d6b, pid=0003, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:003:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:004:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:004:002 (path=(null), vid=03f0, pid=0024, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:004:003 (path=(null), vid=0461, pid=4d20, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:005:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1d6b, pid=0002, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found usb device at usb:001:004 (path=(null), vid=105b, pid=0d7d, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:03:00.0 (path=0000:03:00.0, vid=1b21, pid=1042, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:02:00.0 (path=0000:02:00.0, vid=10ec, pid=8168, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:01:00.0 (path=0000:01:00.0, vid=8086, pid=0083, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1f.3 (path=0000:00:1f.3, vid=8086, pid=27da, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1f.2 (path=0000:00:1f.2, vid=8086, pid=27c1, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1f.0 (path=0000:00:1f.0, vid=8086, pid=27bc, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1e.0 (path=0000:00:1e.0, vid=8086, pid=2448, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1d.7 (path=0000:00:1d.7, vid=8086, pid=27cc, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1d.3 (path=0000:00:1d.3, vid=8086, pid=27cb, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1d.2 (path=0000:00:1d.2, vid=8086, pid=27ca, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1d.1 (path=0000:00:1d.1, vid=8086, pid=27c9, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1d.0 (path=0000:00:1d.0, vid=8086, pid=27c8, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1c.2 (path=0000:00:1c.2, vid=8086, pid=27d4, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1c.1 (path=0000:00:1c.1, vid=8086, pid=27d2, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1c.0 (path=0000:00:1c.0, vid=8086, pid=27d0, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:1b.0 (path=0000:00:1b.0, vid=8086, pid=27d8, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:02.0 (path=0000:00:02.0, vid=8086, pid=0be2, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] lowlevel_scan: Found pci device at pci:0000:00:00.0 (path=0000:00:00.0, vid=8086, pid=0bf3, manuf=(null), prod=(null), serial=(null))                    
 [2014-02-11 20:24:32] Devices detected:                    
0 devices listed

Update info after startup without running bfgminer:
miner@uminer-01:~$ sudo ls -la /dev/ttyUSB*
[sudo] password for miner:
crw-rw---- 1 root dialout 188, 0 Feb 11 20:41 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Feb 11 20:41 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Feb 11 20:41 /dev/ttyUSB2
crw-rw---- 1 root dialout 188, 3 Feb 11 20:41 /dev/ttyUSB3
crw-rw---- 1 root dialout 188, 4 Feb 11 20:41 /dev/ttyUSB4
crw-rw---- 1 root dialout 188, 5 Feb 11 20:41 /dev/ttyUSB5
miner@uminer-01:~$

Code:
[2014-02-11 20:45:21] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)
 [2014-02-11 20:45:21] Started bfgminer 3.10.0
 [2014-02-11 20:45:21] Loaded configuration file /home/miner/.bfgminer/bfgminer.conf
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:001:004: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:001:001: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:005:001: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:004:003: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:004:002: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:004:001: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:003:001: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:002:001: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:007:004: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:007:003: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:007:002: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:007:001: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:010: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:009: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:008: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:007: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:004: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:006: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:005: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:003: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:002: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] usb_devinfo_scan: Error opening device usb:006:001: LIBUSB_ERROR_ACCESS
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:001 (path=(null), vid=1d6b, pid=0002, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:002 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:003 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:005 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:006 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:004 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:007 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:008 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:009 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:006:010 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:007:001 (path=(null), vid=1d6b, pid=0003, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:007:002 (path=(null), vid=2109, pid=0812, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:007:003 (path=(null), vid=2109, pid=0812, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:007:004 (path=(null), vid=2109, pid=0812, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:003:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:004:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:004:002 (path=(null), vid=03f0, pid=0024, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:004:003 (path=(null), vid=0461, pid=4d20, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:005:001 (path=(null), vid=1d6b, pid=0001, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1d6b, pid=0002, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found usb device at usb:001:004 (path=(null), vid=105b, pid=0d7d, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:03:00.0 (path=0000:03:00.0, vid=1b21, pid=1042, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:02:00.0 (path=0000:02:00.0, vid=10ec, pid=8168, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:01:00.0 (path=0000:01:00.0, vid=8086, pid=0083, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1f.3 (path=0000:00:1f.3, vid=8086, pid=27da, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1f.2 (path=0000:00:1f.2, vid=8086, pid=27c1, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1f.0 (path=0000:00:1f.0, vid=8086, pid=27bc, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1e.0 (path=0000:00:1e.0, vid=8086, pid=2448, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1d.7 (path=0000:00:1d.7, vid=8086, pid=27cc, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1d.3 (path=0000:00:1d.3, vid=8086, pid=27cb, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1d.2 (path=0000:00:1d.2, vid=8086, pid=27ca, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1d.1 (path=0000:00:1d.1, vid=8086, pid=27c9, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1d.0 (path=0000:00:1d.0, vid=8086, pid=27c8, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1c.2 (path=0000:00:1c.2, vid=8086, pid=27d4, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1c.1 (path=0000:00:1c.1, vid=8086, pid=27d2, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1c.0 (path=0000:00:1c.0, vid=8086, pid=27d0, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:1b.0 (path=0000:00:1b.0, vid=8086, pid=27d8, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:02.0 (path=0000:00:02.0, vid=8086, pid=0be2, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found pci device at pci:0000:00:00.0 (path=0000:00:00.0, vid=8086, pid=0bf3, manuf=(null), prod=(null), serial=(null))
 [2014-02-11 20:45:21] lowlevel_scan: Found vcom device at dev_t:05bc000000000000 (path=/dev/ttyUSB5, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)               
 [2014-02-11 20:45:21] lowlevel_scan: Found vcom device at dev_t:04bc000000000000 (path=/dev/ttyUSB4, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)               
 [2014-02-11 20:45:21] lowlevel_scan: Found vcom device at dev_t:03bc000000000000 (path=/dev/ttyUSB3, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)               
 [2014-02-11 20:45:21] lowlevel_scan: Found vcom device at dev_t:02bc000000000000 (path=/dev/ttyUSB2, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)               
 [2014-02-11 20:45:21] lowlevel_scan: Found vcom device at dev_t:01bc000000000000 (path=/dev/ttyUSB1, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)               
 [2014-02-11 20:45:21] lowlevel_scan: Found vcom device at dev_t:00bc000000000000 (path=/dev/ttyUSB0, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)               
 [2014-02-11 20:45:21] Icarus Detect: Attempting to open /dev/ttyUSB5
 [2014-02-11 20:45:21] Icarus Detect: Attempting to open /dev/ttyUSB4
 [2014-02-11 20:45:21] Icarus Detect: Attempting to open /dev/ttyUSB3
 [2014-02-11 20:45:21] Acquired exclusive advisory lock on /dev/ttyUSB3
 [2014-02-11 20:45:21] Acquired exclusive advisory lock on /dev/ttyUSB4
 [2014-02-11 20:45:21] Icarus Detect: Attempting to open /dev/ttyUSB1
 [2014-02-11 20:45:21] Icarus Detect: Attempting to open /dev/ttyUSB2
 [2014-02-11 20:45:21] Icarus Detect: Attempting to open /dev/ttyUSB0
 [2014-02-11 20:45:21] Acquired exclusive advisory lock on /dev/ttyUSB5
 [2014-02-11 20:45:21] Acquired exclusive advisory lock on /dev/ttyUSB2
 [2014-02-11 20:45:21] Acquired exclusive advisory lock on /dev/ttyUSB0
 [2014-02-11 20:45:21] Acquired exclusive advisory lock on /dev/ttyUSB1
 [2014-02-11 20:45:21] Icarus Read: No data in 0.10 seconds
 [2014-02-11 20:45:21] Icarus Read: No data in 0.10 seconds
 [2014-02-11 20:45:26] Icarus Detect: Test succeeded at /dev/ttyUSB0: got 000187a2
 [2014-02-11 20:45:26] Found AMU 0 at /dev/ttyUSB0
 [2014-02-11 20:45:26] AMU 0: Init: baud=115200 work_division=0 fpga_count=0
 [2014-02-11 20:45:26] AMU 0: Init: mode=default read_count=19 limit=0ms Hs=4.761000e-10
 [2014-02-11 20:45:26] Icarus Detect: Test failed at /dev/ttyUSB4: get 00000000, should: 000187a2
 [2014-02-11 20:45:26] Icarus Detect: Test failed at /dev/ttyUSB5: get 00000000, should: 000187a2
 [2014-02-11 20:45:26] Icarus Detect: Test succeeded at /dev/ttyUSB1: got 000187a2
 [2014-02-11 20:45:26] Icarus Detect: Test succeeded at /dev/ttyUSB3: got 000187a2
 [2014-02-11 20:45:26] Icarus Detect: Test succeeded at /dev/ttyUSB2: got 000187a2
 [2014-02-11 20:45:26] Found AMU 1 at /dev/ttyUSB1
 [2014-02-11 20:45:26] Found AMU 2 at /dev/ttyUSB3
 [2014-02-11 20:45:26] AMU 2: Init: baud=115200 work_division=0 fpga_count=0
 [2014-02-11 20:45:26] AMU 1: Init: baud=115200 work_division=0 fpga_count=0
 [2014-02-11 20:45:26] AMU 2: Init: mode=default read_count=19 limit=0ms Hs=4.761000e-10
 [2014-02-11 20:45:26] AMU 1: Init: mode=default read_count=19 limit=0ms Hs=4.761000e-10
 [2014-02-11 20:45:26] Found AMU 3 at /dev/ttyUSB2
 [2014-02-11 20:45:26] AMU 3: Init: baud=115200 work_division=0 fpga_count=0
 [2014-02-11 20:45:26] AMU 3: Init: mode=default read_count=19 limit=0ms Hs=4.761000e-10
 [2014-02-11 20:45:26] Devices detected:
 [2014-02-11 20:45:26]  CP2102 USB to UART Bridge Controller by Silicon Labs (driver=antminer; procs=1; serial=0001; path=/dev/ttyUSB0)
 [2014-02-11 20:45:26]  CP2102 USB to UART Bridge Controller by Silicon Labs (driver=antminer; procs=1; serial=0001; path=/dev/ttyUSB1)
 [2014-02-11 20:45:26]  CP2102 USB to UART Bridge Controller by Silicon Labs (driver=antminer; procs=1; serial=0001; path=/dev/ttyUSB3)
 [2014-02-11 20:45:26]  CP2102 USB to UART Bridge Controller by Silicon Labs (driver=antminer; procs=1; serial=0001; path=/dev/ttyUSB2)
4 devices listed
Cassey
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 11:59:36 AM
#2546
Quote from: Cassey on February 10, 2014, 08:28:12 PM
Quote from: Cassey on February 10, 2014, 01:54:22 PM
Quote from: nwoolls on February 10, 2014, 01:37:05 PM

Try the 32-bit bfgminer to rule that out. I don't use the 64-bit binary (doesn't support HTTP proxy).

Great idea!  Unfortunately, didn't help.  Still seeing the "Failed to open Device Parameters registry key in lowl-vcom.c _vcom_devinfo_scan_windows__hubport(
):440: The system cannot find the file specified." after selecting Auto. 

Good news, bad news.  I cranked up GUIMiner and it is having the same issue of not accepting work.  At least bfgminer is giving us a hint with that error message.  Alas, I'm clueless what it means, other than my wifes machine is borked.  Down to running (3) different anti-virus programs on her machine now.

FYI:  I tried doing a logical uninstall of the video card via windows device manager.  That worked as expected, but after rebooting, the problem still shows up.  No viruses either.

Does the error message "Failed to open Device Parameters registry key in lowl-vcom.c _vcom_devinfo_scan_windows__hubport(
):440: The system cannot find the file specified." give us any clue?
HellDiverUK
hero member
Activity: 1246
Merit: 501
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 11:29:54 AM
#2545
Quote from: mfread on February 11, 2014, 02:13:29 AM

I then downloaded and ran bfgminer 3.2.1 win32.

Why did you start with such an ancient version?  What's wrong with 3.10.0,  the current version that's had many, many fixes and upgrades for ASIC miners including the pointless one you bought?
Mudbankkeith
hero member
Activity: 868
Merit: 1000
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 10:29:18 AM
#2544
Quote from: primer10 on February 11, 2014, 09:54:30 AM
Quote from: dbcmaster on February 09, 2014, 08:28:42 AM
Wondering if you can help.

I have five Antminer U1 and two Block Erupter USB. For some reason, the effective average on two of the Antminer is low:


Also, I think I have some erroneous info in my config file:


Any help is appreciated.

Should try to see if it is due to power issues first: best way to test if you do not have a good hub is to plug straight into PC usb port directly.

Anyway, recently I also bought a defective antminer .. hashing way low below 0.7gh/s ...

Try them one at a time, if they all work ok then you have a power problem
Xer0
hero member
Activity: 826
Merit: 1000
°^°
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 10:25:49 AM
#2543
Luke, that inbuilt proxy, is there a manual how to use it?

can i like set it up on the gateway router,
enter my pool credentials,
and point all (stratum) miners to the proxy instead of pool?
primer10
sr. member
Activity: 249
Merit: 250
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 09:54:30 AM
#2542
Quote from: dbcmaster on February 09, 2014, 08:28:42 AM
Wondering if you can help.

I have five Antminer U1 and two Block Erupter USB. For some reason, the effective average on two of the Antminer is low:



Also, I think I have some erroneous info in my config file:

{
"pools" : [
   {
      "url" : "xxxxxxxxxx",
      "user" : "xxxxxxxxxx",
      "pass" : "",
      "pool-priority" : "0"
   },
   {
      "url" : "xxxxxxxxxx",
      "user" : "xxxxxxxxxx",
      "pass" : "xxxxxxxxxx",
      "pool-priority" : "1"
   }
]
,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"expiry-lp" : "3600",
"failover-only" : true,
"gpu-dyninterval" : "7",
"log" : "5",
"no-pool-disable" : true,
"no-show-processors" : true,
"no-show-procs" : true,
"no-unicode" : true,
"queue" : "2",
"scan-time" : "60",
"skip-security-checks" : "0",
"submit-stale" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "C:\\Program Files\\BFGMiner\\/share/bfgminer",
"scan" : [
   "antminer:all",
   "icarus:all"
],
"set-device" : [
   "antminer:clock=x0981"
]
}


Any help is appreciated.

Should try to see if it is due to power issues first: best way to test if you do not have a good hub is to plug straight into PC usb port directly.

Anyway, recently I also bought a defective antminer .. hashing way low below 0.7gh/s ...
Mudbankkeith
hero member
Activity: 868
Merit: 1000
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 06:20:52 AM
#2541
Quote from: mfread on February 11, 2014, 05:03:47 AM
@nwoolls and @Mudbankkeith

Thank you for your prompt responses. I think you might be correct - the USB port needs to give out more power.

When I plug in the ASIC USB device, the green light stays on, but as soon as I start mining, the light goes off (a possible indicator that there isn't enough power?). I don't know how these ASIC devices are supposed to behave (is the green slight supposed to stay on even when mining? Or should it flicker as it sends/rcves data? or behave in a different way?).

I'm sure I read that ASIC USB erupters can be plugged into *any* USB port, but I think this isn't entirely accurate - I guess they should of said it can be plugged into any USB port (1, 2 or 3) but only some equipment/USB ports will provide enough juice the for the device to operate correctly, so you're better off using a powered external hub.

I have an external powered 4-port USB hub somewhere - I'll give that a go and see what happens.

Cheers.

Additional Info
Compaq Presario C!61-314TU notebook purchased new Dec 2009
3 x USB ports (as far as I can find on Google they are USB 2.0)


the light should go out and then flash randomly when it starts mining.
erupters can work on usb1.1 but usb2 is better, laptop ports are usually low on power, so a hub will be needed,(some desktops will drive 1 or 2 erupters)
try it in each port, not all ports are the same.
not all usb3 ports can communicate with erupters.(it depends on the motherboard)
powered usb3 hubs are usually ok if plugged into a usb2 port.(not true for rPi)
try this thread for suitable hubs:-  https://bitcointalksearch.org/topic/m.2700634
mfread
newbie
Activity: 42
Merit: 0
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 05:03:47 AM
#2540
@nwoolls and @Mudbankkeith

Thank you for your prompt responses. I think you might be correct - the USB port needs to give out more power.

When I plug in the ASIC USB device, the green light stays on, but as soon as I start mining, the light goes off (a possible indicator that there isn't enough power?). I don't know how these ASIC devices are supposed to behave (is the green slight supposed to stay on even when mining? Or should it flicker as it sends/rcves data? or behave in a different way?).

I'm sure I read that ASIC USB erupters can be plugged into *any* USB port, but I think this isn't entirely accurate - I guess they should of said it can be plugged into any USB port (1, 2 or 3) but only some equipment/USB ports will provide enough juice the for the device to operate correctly, so you're better off using a powered external hub.

I have an external powered 4-port USB hub somewhere - I'll give that a go and see what happens.

Cheers.

Additional Info
Compaq Presario C!61-314TU notebook purchased new Dec 2009
3 x USB ports (as far as I can find on Google they are USB 2.0)
Mudbankkeith
hero member
Activity: 868
Merit: 1000
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 04:31:13 AM
#2539

If its USB1 then the data rate may be too slow.

Asics work best in a usb2 socket

Asic devices also need power from the socket.

So a powered usb hub is needed.

Look for at least 3watts per device.

Quote from: mfread on February 11, 2014, 02:13:29 AM
Hoping someone can help. I'm quite new to mining (and definitely new to ASIC mining).

I've just purchased an ASIC USB Block Erupter (apparently overclocked to 433 MH/s according to the seller).

I'm using Windows 7 x86.

I followed some instructions that said download and install the CP210x_VCP_Windows drivers (which I did). I then plugged in my ASIC into the side of my Windows 7 notebook (I think it's a USB 1 port as it's an older Celeron Dual Core HP laptop). Windows said the driver was installed successfully. Devices & Printers showed the dive sitting on COM12.


I then downloaded and ran bfgminer 3.2.1 win32. Here's a screenshot:


I don't understand how to read the screen.

Code:
1            | 309.0/348.2/31.00Mh/s | A:1 R:0+0(none) HW:50/ 98%

I'm presuming this means "the first ASIC is processing at 31.00 MH/s" ??
I'll have to read up on what the 309.0 and 348.2 mean.

I don't get what ICA 0: and MMQ 0: are about. Is a 'dead' MMQ the casue of my issue?

Naturally I'm trying to figure out why BFGminer says this ASIC is only processing at 31 MH/s (instead of the claimed overclocked 433 MH/s, or even just the rated 333 MH/s).

Any help greatly appreciated.


Amendment: Sorry, when BFGminer was 1st started, it reported something like 700MH/s, which very quickly reduced to 245, then after around 1 to 2 minutes it was down around 31, and now as I look at my screen it's around 17 MH/s after running for some 5 minutes. The ASIC USB device remains dark and only flickers green every 60 secs or so.

nwoolls
hero member
Activity: 840
Merit: 1002
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 02:25:37 AM
#2538
Quote from: mfread on February 11, 2014, 02:13:29 AM
I don't understand how to read the screen.

Code:
1            | 309.0/348.2/31.00Mh/s | A:1 R:0+0(none) HW:50/ 98%

...

Naturally I'm trying to figure out why BFGminer says this ASIC is only processing at 31 MH/s (instead of the claimed overclocked 433 MH/s, or even just the rated 333 MH/s).

If you look on the far right you'll see that 98% of the work the ASIC is doing is resulting in errors. That is why the third hashrate is so low. What do you have it plugged into? It may need more power.
mfread
newbie
Activity: 42
Merit: 0
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 02:13:29 AM
#2537
Hoping someone can help. I'm quite new to mining (and definitely new to ASIC mining).

I've just purchased an ASIC USB Block Erupter (apparently overclocked to 433 MH/s according to the seller).

I'm using Windows 7 x86.

I followed some instructions that said download and install the CP210x_VCP_Windows drivers (which I did). I then plugged in my ASIC into the side of my Windows 7 notebook (I think it's a USB 1 port as it's an older Celeron Dual Core HP laptop). Windows said the driver was installed successfully. Devices & Printers showed the dive sitting on COM12.

http://i58.tinypic.com/necl7m.png

I then downloaded and ran bfgminer 3.2.1 win32. Here's a screenshot:

http://i60.tinypic.com/a4c208.png

I don't understand how to read the screen.

Code:
1            | 309.0/348.2/31.00Mh/s | A:1 R:0+0(none) HW:50/ 98%

I'm presuming this means "the first ASIC is processing at 31.00 MH/s" ??
I'll have to read up on what the 309.0 and 348.2 mean.

I don't get what ICA 0: and MMQ 0: are about. Is a 'dead' MMQ the casue of my issue?

Naturally I'm trying to figure out why BFGminer says this ASIC is only processing at 31 MH/s (instead of the claimed overclocked 433 MH/s, or even just the rated 333 MH/s).

Any help greatly appreciated.


Amendment: Sorry, when BFGminer was 1st started, it reported something like 700MH/s, which very quickly reduced to 245, then after around 1 to 2 minutes it was down around 31, and now as I look at my screen it's around 17 MH/s after running for some 5 minutes. The ASIC USB device remains dark and only flickers green every 60 secs or so.
Cassey
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 11, 2014, 02:04:25 AM
#2536
Quote from: JBT on February 10, 2014, 11:27:58 PM

try uninstalling the video card then reinstall it.... and/or test it in another pc if possible.

It has previously run in another mobo before being added to this machine as a replacement for an even old Nvidia card.  I have completely removed (per "uninstall all AMD product") the drivers and reinstalled.  Would physically removing it be any different?    The card works for normal graphics - its the only video card in the box.
JBT
full member
Activity: 165
Merit: 100
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 10, 2014, 11:27:58 PM
#2535
Quote from: Cassey on February 10, 2014, 08:28:12 PM
Quote from: Cassey on February 10, 2014, 01:54:22 PM
Quote from: nwoolls on February 10, 2014, 01:37:05 PM
Quote from: Cassey on February 10, 2014, 01:34:25 PM
Doing Pooled mining Bradley.  We are finding blocks every many many times a day and I see my other miners accepting shares within seconds.  But appreciate the thought.  Fixated on the error message right now.

Try the 32-bit bfgminer to rule that out. I don't use the 64-bit binary (doesn't support HTTP proxy).

Great idea!  Unfortunately, didn't help.  Still seeing the "Failed to open Device Parameters registry key in lowl-vcom.c _vcom_devinfo_scan_windows__hubport(
):440: The system cannot find the file specified." after selecting Auto. 

Good news, bad news.  I cranked up GUIMiner and it is having the same issue of not accepting work.  At least bfgminer is giving us a hint with that error message.  Alas, I'm clueless what it means, other than my wifes machine is borked.  Down to running (3) different anti-virus programs on her machine now.
try uninstalling the video card then reinstall it.... and/or test it in another pc if possible.
Cassey
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Re: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB
February 10, 2014, 08:28:12 PM
#2534
Quote from: Cassey on February 10, 2014, 01:54:22 PM
Quote from: nwoolls on February 10, 2014, 01:37:05 PM
Quote from: Cassey on February 10, 2014, 01:34:25 PM
Doing Pooled mining Bradley.  We are finding blocks every many many times a day and I see my other miners accepting shares within seconds.  But appreciate the thought.  Fixated on the error message right now.

Try the 32-bit bfgminer to rule that out. I don't use the 64-bit binary (doesn't support HTTP proxy).

Great idea!  Unfortunately, didn't help.  Still seeing the "Failed to open Device Parameters registry key in lowl-vcom.c _vcom_devinfo_scan_windows__hubport(
):440: The system cannot find the file specified." after selecting Auto. 

Good news, bad news.  I cranked up GUIMiner and it is having the same issue of not accepting work.  At least bfgminer is giving us a hint with that error message.  Alas, I'm clueless what it means, other than my wifes machine is borked.  Down to running (3) different anti-virus programs on her machine now.
Pages:
Bitcoin Forum>Bitcoin>Mining>Mining software (miners)
Jump to: