Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
November 21, 2013, 10:17:57 AM |
|
I've noticed a number of things in README have fallen out of date. If you see any of these and feel like helping out, please just pastebin your modified version and PM me a link to it. Please include in your PM a name and email address for attribution. Thanks, Luke
|
|
|
|
Notanon
|
|
November 21, 2013, 10:52:55 AM |
|
How far off until BFGMiner supports the Drillbit thumbs? Just got mine today and want to start running them on my Pi with BFGMiner as soon as possible to keep power consumption down, as CGMiner is too unstable on the Pi at the moment.
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
November 21, 2013, 11:03:18 AM |
|
How far off until BFGMiner supports the Drillbit thumbs? Just got mine today and want to start running them on my Pi with BFGMiner as soon as possible to keep power consumption down, as CGMiner is too unstable on the Pi at the moment.
I've not heard anything from Drillbit in a while...
|
|
|
|
jedimstr
|
|
November 21, 2013, 11:25:07 AM |
|
How far off until BFGMiner supports the Drillbit thumbs? Just got mine today and want to start running them on my Pi with BFGMiner as soon as possible to keep power consumption down, as CGMiner is too unstable on the Pi at the moment.
I've not heard anything from Drillbit in a while... Per James the Drillbit firmware guy, you should get contacted "soon": http://drillbitsystem.com/forum/index.php?topic=184.msg625#msg625
|
|
|
|
Trance104
|
|
November 21, 2013, 06:22:30 PM |
|
BFG miner is no longer recognizing my Jally. It only picks up my SC single.
How do I make it recognize both?
*edit*
Easy miner is garbage.
|
|
|
|
bog1111
Newbie
Offline
Activity: 10
Merit: 0
|
|
November 21, 2013, 07:44:00 PM |
|
Hi, I have a new blade, and I'm having an issue getting it to work with BFGMiner. When I add the --http-port 8332 bit to my existing command line, BFGMiner won't start, and gives an unrecognised option message. Running on Raspbian for a while with no issues, got some BEs and Blue fury already. When I built 3.5.1 on the Pi, I used the commands below. ./autogen.sh ./configure make Do I need to add anything after the configure command...? Do I need to run a apt-get install for anything beforehand? I'm a bit confused by the read-me file - see link below https://i.imgur.com/z0HL8hW.jpgThanks.
|
|
|
|
xyzzy099
Legendary
Offline
Activity: 1065
Merit: 1077
|
|
November 21, 2013, 08:01:36 PM |
|
Hi, I have a new blade, and I'm having an issue getting it to work with BFGMiner. When I add the --http-port 8332 bit to my existing command line, BFGMiner won't start, and gives an unrecognised option message. Running on Raspbian for a while with no issues, got some BEs and Blue fury already. When I built 3.5.1 on the Pi, I used the commands below. ./autogen.sh ./configure make Do I need to add anything after the configure command...? Do I need to run a apt-get install for anything beforehand? I'm a bit confused by the read-me file - see link below Thanks. As long as you have libmicrohttpd-dev installed it should enable the proxy support by default. Maybe you need to install that package.
|
Libertarians: Diligently plotting to take over the world and leave you alone.
|
|
|
bog1111
Newbie
Offline
Activity: 10
Merit: 0
|
|
November 21, 2013, 08:08:27 PM Last edit: December 11, 2013, 10:24:48 PM by bog1111 |
|
./bfgminer: --http-port: unrecognized option This means libmicrohttpd wasn't found when you ran configure. I'm an arse - doing it now!
|
|
|
|
shawtux
Newbie
Offline
Activity: 57
Merit: 0
|
|
November 21, 2013, 11:11:51 PM |
|
hi! i was on bfgminer 3.0.2 (if my memory serves me right) and i started my jalapeño and icarus with no problem... as an update freak that i am, i updated to 3.6 and not my jalapeño is not detected as BFL but as AVA0 and AVA1... is there anything that i can do to fix this problem?
|
|
|
|
crazyearner
Legendary
Offline
Activity: 1820
Merit: 1001
|
|
November 22, 2013, 02:45:50 AM |
|
Whats the best settings to use on bfg miner to use with blue furys and usb erupters as cant seem to get them working together on one instance of bfg miner having to use 2 different versions.
|
|
|
|
RicRock
|
|
November 22, 2013, 03:04:29 AM |
|
Whats the best settings to use on bfg miner to use with blue furys and usb erupters as cant seem to get them working together on one instance of bfg miner having to use 2 different versions.
I list them all out on command line. For example: -S erupter:/dev/ttyUSB0 -S BF1:/dev/ttyACM0 etc. etc.
|
|
|
|
Taugeran
|
|
November 22, 2013, 07:17:25 AM |
|
how would one hot plug a nanofury NF1 through device manager on a windows 7 x32 machine. or can it only be located at startup with hidapi?
|
Bitfury HW & Habañero : 1.625Th/s tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1 Come join Coinbase
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
November 22, 2013, 07:31:32 AM |
|
how would one hot plug a nanofury NF1 through device manager on a windows 7 x32 machine. or can it only be located at startup with hidapi?
Plug it in, hit D M and type in nanofury:auto
|
|
|
|
Taugeran
|
|
November 22, 2013, 07:52:46 AM |
|
how would one hot plug a nanofury NF1 through device manager on a windows 7 x32 machine. or can it only be located at startup with hidapi?
Plug it in, hit D M and type in nanofury:auto the simplicity; it hurts my caffeine stuffed, sleep deprived brain! ty luke. troubleshooting a stubborn NF1 who doesn't like running at 52+ bits. it keeps bitfury_init_oldbuf: giving up after X tries and does this until i drop it to under 52 :<
|
Bitfury HW & Habañero : 1.625Th/s tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1 Come join Coinbase
|
|
|
HellDiverUK
|
|
November 22, 2013, 11:13:47 AM |
|
i updated to 3.6 and not my jalapeño is not detected as BFL but as AVA0 and AVA1... is there anything that i can do to fix this problem?
Is it mining? If it is, it's not a problem.
|
|
|
|
shawtux
Newbie
Offline
Activity: 57
Merit: 0
|
|
November 22, 2013, 01:58:32 PM Last edit: November 22, 2013, 02:17:28 PM by shawtux |
|
i updated to 3.6 and not my jalapeño is not detected as BFL but as AVA0 and AVA1... is there anything that i can do to fix this problem?
Is it mining? If it is, it's not a problem. its not mining edit: disabled avalon support and its mining edit2: its mining at a fraction of the speed that was on 3.0
|
|
|
|
OleOle
|
|
November 22, 2013, 02:23:36 PM |
|
i updated to 3.6 and not my jalapeño is not detected as BFL but as AVA0 and AVA1... is there anything that i can do to fix this problem?
Is it mining? If it is, it's not a problem. its not mining edit: disabled avalon support and its mining edit2: its mining at a fraction of the speed that was on 3.0 Would it kill you to go back to version 3.0 to get back to your full mining performance? Maybe do that then try to work out why you're not getting the full hash rate on 3.6. Or you can just dump it in the ocean if you like? - http://www.timeslive.co.za/world/2013/11/22/caterpillar-probed-for-dumping-train-parts-into-sea
|
|
|
|
shawtux
Newbie
Offline
Activity: 57
Merit: 0
|
|
November 22, 2013, 02:55:05 PM |
|
hahaha tried going back to 3.0.10 but i get only segmentation faults when running and no errors on build...
trying now 3.2.6...
later ill try 3.0.9
|
|
|
|
3KyNoX
Member
Offline
Activity: 81
Merit: 10
|
|
November 22, 2013, 08:48:48 PM Last edit: November 22, 2013, 09:01:09 PM by 3KyNoX |
|
Hello Luke-Jr, Got some problem to compile bfgminer correctly inside a macbook-pro (core i7 2.5Ghz & Radeon 6770M) and gladly would appreciate some help please : 1. When yasm is installed (with macports) ... "./configure CFLAGS="-I$PWD" --enable-scrypt --enable-cpumining" works "make" returns this error : ... Making all in x86_64 /opt/local/bin/yasm -f macho64 -o sha256_sse4_amd64.o sha256_sse4_amd64.asm sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. sha256_sse4_amd64.asm:238: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. make[2]: *** [sha256_sse4_amd64.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 It looks like specific yasm mac error but can't find out where the problem is located. 2. Anyway, uninstalled yasm and build passing now but when launching bfgminer, I have to select manually cpu's with Management Devices and typing "auto" to detect cpu's (not possible to use it auto at startup ?) and bfgminer interface looks like this : bfgminer version 3.6.0 - Started: [2013-11-22 21:35:31] - [ 0 days 00:00:32] [M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit Connected to xxxxxxxxxxxx diff 64 with stratum as user XXXXXXXXXXXXXX Block: ...217e8051 #464923 Diff:1.43k (10.23Gh/s) Started: [21:35:31] ST:3 F:0 NB:1 AS:0 BW:[ 27/ 8 B/s] E:0.00 I: 0.00 BTC/hr BS:0 0 | 224.0/120.5/ 0.0kh/s | A:0 R:0+0(none) HW:0/none -------------------------------------------------------------------------------- CPU 0: | 29.4/ 51.5/ 0.0kh/s | A:0 R:0+0(none) HW:0/none CPU 1: | 29.3/ 51.4/ 0.0kh/s | A:0 R:0+0(none) HW:0/none CPU 2: | 29.5/ 51.7/ 0.0kh/s | A:0 R:0+0(none) HW:0/none CPU 3: | 29.4/ 51.5/ 0.0kh/s | A:0 R:0+0(none) HW:0/none CPU 4: | 29.4/ 51.4/ 0.0kh/s | A:0 R:0+0(none) HW:0/none CPU 5: | 29.6/ 51.9/ 0.0kh/s | A:0 R:0+0(none) HW:0/none CPU 6: | 29.4/ 51.5/ 0.0kh/s | A:0 R:0+0(none) HW:0/none CPU 7: | 29.6/ 51.9/ 0.0kh/s | A:0 R:0+0(none) HW:0/none -------------------------------------------------------------------------------- Still at 0.0kh/s and cpu doesn't looks like to work ... Any idea why cpu's looks like idle-ing ? 3. AMD OPENCL drivers and bfgminer gpu dependencies are installed on this mac but no GPU are found under Management devices. It looks like also GPU specific start options are not recognized (like "-I 9 --auto-fan --auto-gpu"). Any reason why ? Thanks for help. 3Ky
|
Donate : 1MmSvVtcZMLtCbk6RcEXRei91K8VrgPxoC
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
November 22, 2013, 11:02:17 PM |
|
For CPU or scrypt problems, especially on Mac: patches welcome.
|
|
|
|
|