Quote
clDevicesNum returned error, no GPUs usable
I'm trying to mine litecoins with it. the nvidia gpus are temporary until my 7900's get here. help please
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 88. (Read 1193364 times)
November 24, 2013, 02:58:46 PM
I have a machine with a quadcore and 2 nvidia video cards and I cant get bfgminer to run i get this error
I'm trying to mine litecoins with it. the nvidia gpus are temporary until my 7900's get here. help please
I'm trying to mine litecoins with it. the nvidia gpus are temporary until my 7900's get here. help please
November 24, 2013, 02:07:53 PM
Is the Klondike K16 supported now in BFG? I can't be sure looking at the readmes.
The driver is pretty poor code (almost verbatim import from cgminer), so I'll probably rewrite it when/if they get back to me with protocol specs (or maybe reverse engineer it from this code), but it should work as of 3.6.0...Cheers.
I was bidding on a K16 on Fleabay, but it went for Silly Moneytm - someone was pretty keen to pay £280 for the thing...
November 24, 2013, 02:06:13 PM
Is the Klondike K16 supported now in BFG? I can't be sure looking at the readmes.
The driver is pretty poor code (almost verbatim import from cgminer), so I'll probably rewrite it when/if they get back to me with protocol specs (or maybe reverse engineer it from this code), but it should work as of 3.6.0... November 24, 2013, 12:52:04 PM
Is the Klondike K16 supported now in BFG? I can't be sure looking at the readmes.
November 24, 2013, 07:16:13 AM
README
November 24, 2013, 06:31:43 AM
I have a question i could not find so easely, so that's why im posting here. Sorry for bad English.
I'm using bfgminer 3.6.0 at this moment to mine some BTC.
Well, when i'm mining, i see this:
1: xx/xx/xxMh/s
OCL 0: xx/xx/xxMh/s
I'm mining with my GPU, were is the 1 for and were is the OCL 0 for?
What XX's do i need to look for what my actual MH/s's are?
Thank you! God Bless
I'm using bfgminer 3.6.0 at this moment to mine some BTC.
Well, when i'm mining, i see this:
1: xx/xx/xxMh/s
OCL 0: xx/xx/xxMh/s
I'm mining with my GPU, were is the 1 for and were is the OCL 0 for?
What XX's do i need to look for what my actual MH/s's are?
Thank you! God Bless
November 23, 2013, 11:12:53 PM
Is there anything BFGMiner could do to fix these errors on BFSB hardware without restarting?
BSB 1e: bitfury_init_oldbuf: Giving up after 4 tries
I've noticed that a chip's frequency sometimes drops considerably and it starts spamming that error. Restarting BFGMiner fixes it, unlike when a whole card goes down. Since a simple BFGMiner restart is enough in this case, I'm wondering if this could be fixed automatically when it happens, without even having to restart?
BSB 1e: bitfury_init_oldbuf: Giving up after 4 tries
I've noticed that a chip's frequency sometimes drops considerably and it starts spamming that error. Restarting BFGMiner fixes it, unlike when a whole card goes down. Since a simple BFGMiner restart is enough in this case, I'm wondering if this could be fixed automatically when it happens, without even having to restart?
i get this occasionally with a nanofury NF1 that i pencil modded. lowering the osc6 bits restarts it. i changed the volt mod slightly and it became stable again at the higher bits
November 23, 2013, 09:52:30 AM
Is there anything BFGMiner could do to fix these errors on BFSB hardware without restarting?
BSB 1e: bitfury_init_oldbuf: Giving up after 4 tries
I've noticed that a chip's frequency sometimes drops considerably and it starts spamming that error. Restarting BFGMiner fixes it, unlike when a whole card goes down. Since a simple BFGMiner restart is enough in this case, I'm wondering if this could be fixed automatically when it happens, without even having to restart?
BSB 1e: bitfury_init_oldbuf: Giving up after 4 tries
I've noticed that a chip's frequency sometimes drops considerably and it starts spamming that error. Restarting BFGMiner fixes it, unlike when a whole card goes down. Since a simple BFGMiner restart is enough in this case, I'm wondering if this could be fixed automatically when it happens, without even having to restart?
November 22, 2013, 10:09:28 PM
Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.
In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine... 
Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.)
November 22, 2013, 09:49:49 PM
Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.
In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine... Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.)
November 22, 2013, 08:41:24 PM
Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.
In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine... Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.)
November 22, 2013, 06:21:09 PM
I have a problem i will mine on a cpu pool and he is automatic mining whit gpu and i will get nothing.
How can i stop gpu and start whit cpu?
How can i stop gpu and start whit cpu?
November 22, 2013, 06:02:17 PM
For CPU or scrypt problems, especially on Mac: patches welcome.
November 22, 2013, 03:48:48 PM
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 :
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 :
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
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 :
Code:
...
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 :
Code:
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
November 22, 2013, 09:55:05 AM
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
trying now 3.2.6...
later ill try 3.0.9
November 22, 2013, 09:23:36 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.
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
November 22, 2013, 08:58:32 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.
its not mining
edit:
disabled avalon support and its mining
edit2:
its mining at a fraction of the speed that was on 3.0
November 22, 2013, 06: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.
November 22, 2013, 02: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:autothe 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 :<
November 22, 2013, 02: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 Jump to: