Topic: Block Erupter with BFGMiner on Ubuntu (Read 2945 times)
I believe you need some specific Icarus arguments in there and maybe a com argument in there in order to tell BFGMiner that you are using an Icarus device and what com port to use.
Also...I found a forum post where I tried
bfgminer starts just fine but shows I'm mining CPU
Code:
bfgminer -o-u -p -S all
bfgminer starts just fine but shows I'm mining CPU
Greeting BTC Community!!
I am trying to mine on my new USB Block Erupted but having some difficulty getting started. After searching the forum for a bit I figure it's time to ask for some help.
I have BFGMiner 3.1.1 running on Ubuntu 12.04 64bit
The output of bfgminer -D -T -d? is
the output of dmesg | grep tty is
The command string I've been using to start bfgminer is
since it seems that the computer recognizes the hardware, and it is supported in BFGMiner I conclude that I'm likely doing something wrong when starting the miner. Any help would be greatly appreciated.
KL
I am trying to mine on my new USB Block Erupted but having some difficulty getting started. After searching the forum for a bit I figure it's time to ask for some help.
I have BFGMiner 3.1.1 running on Ubuntu 12.04 64bit
The output of bfgminer -D -T -d? is
Code:
[2013-06-27 15:16:41] setrlimit: Increased soft fd limit from 1024 to hard limit of 4096
[2013-06-27 15:16:41] ft232r_scan: Found 8087:0024 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 8087:0024 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 1d6b:0002 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 1d6b:0002 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 413c:8187 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 0c45:6433 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 10c4:ea60 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 8086:0188 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 413c:8194 - not a ft232r
[2013-06-27 15:16:41] ft232r_scan: Found 0a5c:5801 - not a ft232r
[2013-06-27 15:16:41] Started bfgminer 3.1.1
[2013-06-27 15:16:41] Failed to load OpenCL library, no GPUs usable
[2013-06-27 15:16:41] Not a ZTEX device 8087:0024
[2013-06-27 15:16:41] Not a ZTEX device 8087:0024
[2013-06-27 15:16:41] Not a ZTEX device 1d6b:0002
[2013-06-27 15:16:41] Not a ZTEX device 1d6b:0002
[2013-06-27 15:16:41] Not a ZTEX device 413c:8187
[2013-06-27 15:16:41] Not a ZTEX device 0c45:6433
[2013-06-27 15:16:41] Not a ZTEX device 10c4:ea60
[2013-06-27 15:16:41] Not a ZTEX device 8086:0188
[2013-06-27 15:16:41] Not a ZTEX device 413c:8194
[2013-06-27 15:16:41] Not a ZTEX device 0a5c:5801
[2013-06-27 15:16:41] Devices detected:
[2013-06-27 15:16:41] 0. CPU 0 (driver: cpu)
[2013-06-27 15:16:41] 1. CPU 1 (driver: cpu)
[2013-06-27 15:16:41] 2. CPU 2 (driver: cpu)
[2013-06-27 15:16:41] 3. CPU 3 (driver: cpu)
[2013-06-27 15:16:41] 4 devices listed
the output of dmesg | grep tty is
Code:
kernellinux@ark:~$ dmesg | grep tty
[ 0.000000] console [tty0] enabled
[ 0.581363] 0000:00:16.3: ttyS4 at I/O 0x40e0 (irq = 17) is a 16550A
[ 3.058429] usb 2-1.6: Qualcomm USB modem converter now attached to ttyUSB0
[ 3.062260] usb 2-1.6: Qualcomm USB modem converter now attached to ttyUSB1
[ 3.065045] usb 2-1.6: Qualcomm USB modem converter now attached to ttyUSB2
[ 5283.888034] PM: resume of drv:qcserial dev:ttyUSB0 complete after 298.222 msecs
[ 5283.888093] PM: resume of drv:qcserial dev:ttyUSB2 complete after 298.192 msecs
[ 5283.888106] PM: resume of drv:qcserial dev:ttyUSB1 complete after 298.250 msecs
[ 5284.902673] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 5284.903271] qcserial ttyUSB1: Qualcomm USB modem converter now disconnected from ttyUSB1
[ 5284.903796] qcserial ttyUSB2: Qualcomm USB modem converter now disconnected from ttyUSB2
[ 5285.300272] usb 2-1.6: Qualcomm USB modem converter now attached to ttyUSB0
[ 5285.302484] usb 2-1.6: Qualcomm USB modem converter now attached to ttyUSB1
[ 5285.304232] usb 2-1.6: Qualcomm USB modem converter now attached to ttyUSB2
[44944.081625] usb 2-1.2: cp210x converter now attached to ttyUSB3
The command string I've been using to start bfgminer is
Code:
bfgminer -o stratum.btcguild.com:3333 -O MyUserName:MyPassword--rotate 2 --temp-target 70 --temp-overheat 72 --temp-cutoff 74 --auto-fan --auto-gpu
since it seems that the computer recognizes the hardware, and it is supported in BFGMiner I conclude that I'm likely doing something wrong when starting the miner. Any help would be greatly appreciated.
KL
Jump to: