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

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: pengoau on December 09, 2013, 01:44:46 AM

I have that specified.

Its reporting correctly with the stable release but not with the latest release. Is this due to cgminer dropping gpu support after 3.7.2? Or something else?

I've also tried v3.5.0 with the same command line as the stable release and it reports in Gh/sec. So only the stable release of v3.2.8 reports correctly for me.

Am I missing something for the latest version?

My command line is:

bfgminer --scrypt -o stratum+tcp://ctompo.dyndns.org:3332 -u pengo.0 -p x -I 20 --auto-fan --temp-overheat 80 --temp-cutoff 85 --temp-target 70

tldr: Reports correctly in kH/sec in v3.2.8, newer versions tested v3.5.0 and latest release it reports in gH/sec (same cmd line)..

Thanks for your help if you can assist.

I don't really care about scrypt.
If you (or anyone else) can bisect it, debug it, or provide a patch, I'll look into it...
If you use Windows, you can easily bisect by starting a new session on http://luke.dashjr.org/tmp/code/webisect/webisect.php

pengoau

full member

Activity: 208

Merit: 100

I have that specified.

Its reporting correctly with the stable release but not with the latest release. Is this due to cgminer dropping gpu support after 3.7.2? Or something else?

I've also tried v3.5.0 with the same command line as the stable release and it reports in Gh/sec. So only the stable release of v3.2.8 reports correctly for me.

Am I missing something for the latest version?

My command line is:

bfgminer --scrypt -o stratum+tcp://ctompo.dyndns.org:3332 -u pengo.0 -p x -I 20 --auto-fan --temp-overheat 80 --temp-cutoff 85 --temp-target 70

tldr: Reports correctly in kH/sec in v3.2.8, newer versions tested v3.5.0 and latest release it reports in gH/sec (same cmd line)..

Thanks for your help if you can assist.

Beastlymac

hero member

Activity: 630

Merit: 501

Miner Setup And Reviews. WASP Rep.

you need to add in the --scrypt tag.

pengoau

full member

Activity: 208

Merit: 100

I'm using 3.8.1
and I get work but bfgminer is reporting in Gh/sec and Mh/sec when I mine scrypt (unless I'm reading wrong; probably)?

This is my command line (copied from cgminer bat modified for bfgminer):

bfgminer.exe --scan opencl:auto --scrypt -E 15 -Q 0 -o stratum+tcp://ctompo.dyndns.org:3332 -u xxxxxxx -p xxxxxx -s 5 --gpu-fan 83-100 --temp-hysteresis 1 --temp-overheat 80 --temp-cutoff 85 --temp-target 70 --intensity 19 --thread-concurrency 24576 --gpu-threads 1 --worksize 256 --auto-fan --no-submit-stale

When I go to manage devices its reporting correctly in Kh/sec.

Tho the top reports this:
OCL 0: 78.0C | 0.00/ 0.00/ 1.76Gh/s | A:327 R:66+55(none) HW:0/none

Whats it reporting in Gh/sec? How do I get it to display my gpu's hash rate?

edit: read the readme for gpus, still reporting in Gh/sec I have a 7950 and it maxes out at 580-600kh/sec with cgminer.
edit 2: Got it reporting in Kh/sec via the stable release: v3.2.8

If anyone can help, thank you.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

NEW VERSION 3.8.1, DECEMBER 9 2013

Human readable changelog:

Bug fixes only.

Full changelog:

bfgminer-rpc: Catch error when server host fails to resolve to an IP
RPC: Remove unnecessary delay from RPC server startup
Call WSAStartup for our own needs independently of libcurl etc
hashbusterusb: Give more meaningful errors before serial number is known
hashbusterusb: Populate device_path with USB devid
Rename hashbuster2 to hashbusterusb (only a-z allowed in driver names)
Include libusb in options list, since it is no longer tied to specific drivers
Make hashbuster serial number output match formatting on physical board
Fix for hashbuster first init after power up
Workaround Microsoft's non-standard swprintf
vcom: Fabricate vcom devinfo for any existing paths specified to --scan, in case enumeration fails
Bugfix: hashbuster2: Check for errors setting up libusb handle
Bugfix: Draw statuswin in line order to ensure overflow is cutoff properly
Fixed one byte stack overflow in mcast recvfrom.
Bugfix: Let libc do any translation for %lc before adding wide characters to curses
Specifically handle mining.get_transactions failures so they get logged at the lower debug loglevel
Bugfix: lowlevel: Use LL_DELETE2 when cleaning up secondary list

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: gump on December 08, 2013, 02:44:46 PM

Quote from: jedimstr on December 08, 2013, 02:39:25 AM

Why run in the Ubuntu VM instead of running the Mac compiled versions directly? Both precompiled binaries and Homebrew formula are available.

Because I can't get the native OSX version to work. It crashes "Bus error 10" -- I've re-installed with a fresh Homebrew, etc. No luck.

I have a small netbook I will move bfgminer to (under Ubuntu) and see if that solves the issue. It could be I have a general hardware problem on the Mac Pro, which is causing this.

Would be neat if these little ASIC boxen could be networked so you could connect a remote miner to them.

I've had the same problems in the past with my Mac Pro. Try these binaries here:
https://github.com/nwoolls/xgminer-osx/releases

gump

newbie

Activity: 7

Merit: 0

Quote from: jedimstr on December 08, 2013, 02:39:25 AM

Why run in the Ubuntu VM instead of running the Mac compiled versions directly? Both precompiled binaries and Homebrew formula are available.

Because I can't get the native OSX version to work. It crashes "Bus error 10" -- I've re-installed with a fresh Homebrew, etc. No luck.

I have a small netbook I will move bfgminer to (under Ubuntu) and see if that solves the issue. It could be I have a general hardware problem on the Mac Pro, which is causing this.

Would be neat if these little ASIC boxen could be networked so you could connect a remote miner to them.

ehmdjii

sr. member

Activity: 351

Merit: 250

Quote from: Mudbankkeith on December 08, 2013, 01:22:51 PM

Quote from: ehmdjii on December 08, 2013, 12:30:16 PM

Quote from: HellDiverUK on December 08, 2013, 11:53:17 AM

I'm pretty sure CPU mining is long gone...

then why is my cpu at 100% since i upgraded from 3.7 to 3.8 ?

my command line :

bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1HZKrZiUQvLMWnee2uPKvYJk5H7hZZvayT -p x -S all -t 0

This line works great with 3.7.0
bfgminer.exe -o http://stratum.bitcoin.cz:3333 -O worker:pasword -S Erupter:all

thanks but that still drives it to 100% cpu usage.
can someone explain what is the exact syntax of this -S flag? thanks!

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: ehmdjii on December 08, 2013, 12:30:16 PM

Quote from: HellDiverUK on December 08, 2013, 11:53:17 AM

I'm pretty sure CPU mining is long gone...

then why is my cpu at 100% since i upgraded from 3.7 to 3.8 ?

my command line :

bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1HZKrZiUQvLMWnee2uPKvYJk5H7hZZvayT -p x -S all -t 0

This line works great with 3.7.0
bfgminer.exe -o http://stratum.bitcoin.cz:3333 -O worker:pasword -S Erupter:all

ehmdjii

sr. member

Activity: 351

Merit: 250

Quote from: HellDiverUK on December 08, 2013, 11:53:17 AM

I'm pretty sure CPU mining is long gone...

then why is my cpu at 100% since i upgraded from 3.7 to 3.8 ?

my command line :

bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1HZKrZiUQvLMWnee2uPKvYJk5H7hZZvayT -p x -S all -t 0

HellDiverUK

hero member

Activity: 1246

Merit: 501

I'm pretty sure CPU mining is long gone...

ehmdjii

sr. member

Activity: 351

Merit: 250

has the option --disable-gpu gone? if yes, how else can i avoid gpu/cpu mining. the bfgminer process is taking 100% cpu now.

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: gump on December 07, 2013, 11:55:44 PM

I am running bfgminer-3.8.0 under Ubuntu 13.x (current) in a VMware Fusion image. For a while, it had been working fine, until today it literally causes the Mac to crash and reboot. I looked in the logs and didn't see anything that stood out, but I wonder if anyone else is experiencing this annoying problem.

OSX 10.9 Mavericks is the version of the OS.

Thanks.

Why run in the Ubuntu VM instead of running the Mac compiled versions directly? Both precompiled binaries and Homebrew formula are available.

gump

newbie

Activity: 7

Merit: 0

I am running bfgminer-3.8.0 under Ubuntu 13.x (current) in a VMware Fusion image. For a while, it had been working fine, until today it literally causes the Mac to crash and reboot. I looked in the logs and didn't see anything that stood out, but I wonder if anyone else is experiencing this annoying problem.

OSX 10.9 Mavericks is the version of the OS.

Thanks.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: sly5am on December 06, 2013, 10:00:34 PM

Quote from: Beave162 on December 06, 2013, 01:32:49 AM

Why is my bfgminer closing immediately after I open it? I have been using it for months and didn't have this problem...

Same problem here.. BFL gear working fine with version 3.6.0 bfgminer, as soon as I upgraded to 3.8.0 the program opens then immediately closes and doesn't run. Same OS and environment, Win 7. hope there is a fix in the newer version.

Can you show us your batch/input line?

If you have -G ..........then remove it.

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: sly5am on December 06, 2013, 10:00:34 PM

Quote from: Beave162 on December 06, 2013, 01:32:49 AM

Why is my bfgminer closing immediately after I open it? I have been using it for months and didn't have this problem...

Same problem here.. BFL gear working fine with version 3.6.0 bfgminer, as soon as I upgraded to 3.8.0 the program opens then immediately closes and doesn't run. Same OS and environment, Win 7. hope there is a fix in the newer version.

I've got BFL, BlueFury, Block Erupter all working together on windows 7 no problems. Even got 2 Blades on it too, all running off a Celeron NUC. 3.8.0 works as well as 3.6.0 and 3.7.0 did. I'm running the Win32 version on 7 Ultimate x64.

Zich

legendary

Activity: 1190

Merit: 1000

Quote from: Luke-Jr on December 03, 2013, 10:33:59 AM

Quote from: HellDiverUK on December 03, 2013, 10:27:31 AM

Quote from: Luke-Jr on December 03, 2013, 10:10:05 AM

Quote from: HellDiverUK on December 03, 2013, 10:08:37 AM

Seems I'm getting a Nanofury to replace a dead Bluefury. Anything I need to be aware of as regards getting the Nanofury working on BFGMiner on Linux (or indeed OpenWRT)?

You'll have to build hidapi for OpenWrt and recompile BFGMiner to use it.

Cheers Luke-Jr. I think I'll stick to the RPi then. Wink

I hear there are significant problems with Nanofury on the RPi's buggy USB stack...
I plan to be looking into this in the upcoming weeks, but it may be a hardware issue I can't workaround.

Good news thanks to derjanb Grin

Quote from: derjanb on December 05, 2013, 03:10:27 PM

Working fine here after hours of trying... Grin

At least I get ~2.3 GH/s out of the Nanofury.

I'm using bfgminer 3.8.0 (latest git version) and all you have to do (after compiling) is to enforce the USB 2.0 low speed mode to make the USB communication stable. Note: this will also limit the network speed of your Raspi!

The slowdown can be achieved by putting dwc_otg.speed=1 into /boot/cmdline.txt. Note: all statements need to be at one line.

See this page for more infomation: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=53832#sig411106 (the last section at the bottom.

Question: what does

Quote

NFY 0: Frequency drop over 50% detected, reinitialising

mean? I see a lot of these messages.

sly5am

hero member

Activity: 582

Merit: 500

Quote from: Beave162 on December 06, 2013, 01:32:49 AM

Why is my bfgminer closing immediately after I open it? I have been using it for months and didn't have this problem...

Same problem here.. BFL gear working fine with version 3.6.0 bfgminer, as soon as I upgraded to 3.8.0 the program opens then immediately closes and doesn't run. Same OS and environment, Win 7. hope there is a fix in the newer version.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Xer0 on December 06, 2013, 11:50:38 AM

Quote from: Luke-Jr on December 03, 2013, 10:10:05 AM

Quote from: HellDiverUK on December 03, 2013, 10:08:37 AM

Seems I'm getting a Nanofury to replace a dead Bluefury. Anything I need to be aware of as regards getting the Nanofury working on BFGMiner on Linux (or indeed OpenWRT)?

You'll have to build hidapi for OpenWrt and recompile BFGMiner to use it.

is this a git-source-and-cross-compile task or does it require intensive tinkering?

It requires writing code.

Xer0

hero member

Activity: 826

Merit: 1000

°^°

Quote from: Luke-Jr on December 03, 2013, 10:10:05 AM

Quote from: HellDiverUK on December 03, 2013, 10:08:37 AM

Seems I'm getting a Nanofury to replace a dead Bluefury. Anything I need to be aware of as regards getting the Nanofury working on BFGMiner on Linux (or indeed OpenWRT)?

You'll have to build hidapi for OpenWrt and recompile BFGMiner to use it.

is this a git-source-and-cross-compile task or does it require intensive tinkering?

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