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

stewdk

newbie

Activity: 46

Merit: 0

Quote from: Trance104 on December 12, 2013, 05:10:39 PM

Quote from: stewdk on December 12, 2013, 09:55:26 AM

Quote from: Trance104 on December 10, 2013, 12:11:27 PM

After using BFG miner on my SC Single, it eventually errored out. When I restarted it, it now only picks my graphics cards.

Has anyone experienced this? Is there any way I can trouble shoot it? I didn't alter anything. I can't figure it out.

I tried using bfgminer for my Jalapeno, and it would only detect it like every fifth time I started bfgminer. I've found that unplugging and replugging both the power and USB cable from my Jalapeno will help it get back online. However, cgminer detects my jalapeno pretty much every time. Just sayin'. I think the initialization code in cgminer is much more robust compared to bfgminer. I did flash the firmware on my jalapeno though, so I can't rule that out as being the issue.

Who woulda thought?? Unplugging it and plugging it back in got it to work! My hats off to you sir!

Thank you very much!

Tech support: level 99. I don't think it helps any that there are over 750 warnings when compiling the BitForce_SC firmware... I would just be worried about bfgminer detecting the BitForce devices properly after a power failure or reboot, especially if you need to reboot remotely.

xzempt

hero member

Activity: 504

Merit: 500

bfgminer 3.3.0 has been working great for a couple weeks now..... but last night it just quit recognizing my blades....

i can access the blades and point them to a getwork pool and they mine.....

switch them to point to pc running bfgminer.... they quit mining and bfgminer wont even show them on the network?

any ideas?

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: dadach on December 13, 2013, 06:03:23 AM

why is cgminer so retarded that he cannot distinguish between 2 different cards in a computer?

Why are you so retarded the you cannot post in the correct thread? Huh

dadach

sr. member

Activity: 365

Merit: 250

why is cgminer so retarded that he cannot distinguish between 2 different cards in a computer?

asjfdlksfd

full member

Activity: 128

Merit: 100

Hi, is there a way to see the chips stats in the same way for Chilly as it is possible to see the stats for Jally/(Little) Single?

Cheers...

HellDiverUK

hero member

Activity: 1246

Merit: 501

My Jalapeno needs a hard reboot the odd time too, or it just falls off the USB bus. Usually after the host has rebooted.

Trance104

full member

Activity: 206

Merit: 100

Quote from: stewdk on December 12, 2013, 09:55:26 AM

Quote from: Trance104 on December 10, 2013, 12:11:27 PM

After using BFG miner on my SC Single, it eventually errored out. When I restarted it, it now only picks my graphics cards.

Has anyone experienced this? Is there any way I can trouble shoot it? I didn't alter anything. I can't figure it out.

I tried using bfgminer for my Jalapeno, and it would only detect it like every fifth time I started bfgminer. I've found that unplugging and replugging both the power and USB cable from my Jalapeno will help it get back online. However, cgminer detects my jalapeno pretty much every time. Just sayin'. I think the initialization code in cgminer is much more robust compared to bfgminer. I did flash the firmware on my jalapeno though, so I can't rule that out as being the issue.

Who woulda thought?? Unplugging it and plugging it back in got it to work! My hats off to you sir!

Thank you very much!

stewdk

newbie

Activity: 46

Merit: 0

Quote from: Trance104 on December 10, 2013, 12:11:27 PM

After using BFG miner on my SC Single, it eventually errored out. When I restarted it, it now only picks my graphics cards.

Has anyone experienced this? Is there any way I can trouble shoot it? I didn't alter anything. I can't figure it out.

I tried using bfgminer for my Jalapeno, and it would only detect it like every fifth time I started bfgminer. I've found that unplugging and replugging both the power and USB cable from my Jalapeno will help it get back online. However, cgminer detects my jalapeno pretty much every time. Just sayin'. I think the initialization code in cgminer is much more robust compared to bfgminer. I did flash the firmware on my jalapeno though, so I can't rule that out as being the issue.

Btc-Go

newbie

Activity: 14

Merit: 0

@stewdk, static binary is redistributable cause it doesn't require libraries.

stewdk

newbie

Activity: 46

Merit: 0

Quote from: Btc-Go on December 12, 2013, 04:18:46 AM

@stewdk, I use debian with libmicrohttpd ver 0.9
But that's not the point.

The application fails to compile statically, into single binary with all libraries bundled.

Ah, sorry for the confusion, my other post wasn't necessarily directed towards you, just in general... I took a stab at trying to compile it statically on my setup anyway, and was not successful. I don't use GPUs or scrypt, so I ran ./configure without any options:

Code:

LDFLAGS=-static ./configure

The configure succeeds, but the make fails. If I rerun ./configure without the static link flag, then the make succeeds. I'm guessing if you really want a static binary then you might have to get dirty with the build setup and that'll likely take a lot of work. What were you hoping to achieve with a static binary anyway?

Btc-Go

newbie

Activity: 14

Merit: 0

@stewdk, I use debian with libmicrohttpd ver 0.9
But that's not the point.

The application fails to compile statically, into single binary with all libraries bundled.

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

also can i use set device with NFY@Serial#:osc6_bits=##

i cant find code to indicate either way

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

so i got my BBB up and running with my 2 NFY 1 BPMC and 5 BES but:

im having an issue that if all the devices are plugged in at same time and in one instance of bfgminer one "random" of my NFY will hang at initializing.... while the other goes on just fine.

but in this image i got everything running for a short while in 2 different instances but then one of the NFY errors/hangs/stops hashing.

lsusb -t output:

Code:

miner@arm:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=HID, Driver=usbhid, 480M
|__ Port 2: Dev 46, If 0, Class=HID, Driver=usbfs, 12M
|__ Port 4: Dev 38, If 0, Class=HID, Driver=usbfs, 12M
|__ Port 5: Dev 4, If 0, Class=hub, Driver=hub/5p, 480M
|__ Port 1: Dev 5, If 0, Class=HID, Driver=usbhid, 480M
|__ Port 2: Dev 47, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 47, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 55, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 56, If 0, Class=vend., Driver=cp210x, 12M
|__ Port 2: Dev 57, If 0, Class=vend., Driver=cp210x, 12M
|__ Port 3: Dev 58, If 0, Class=vend., Driver=cp210x, 12M
|__ Port 4: Dev 59, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 60, If 0, Class=vend., Driver=cp210x, 12M
|__ Port 2: Dev 61, If 0, Class=vend., Driver=cp210x, 12M

i can get everything working if i remove the last 2 BES (devs 60 and 61)

poor ascii art of layout: BBB---DLINK---7port
| | | || || |
N N B EEEEE

N=NFY
B=BPMC
E=Erupter

each hub is powered by a separate [email protected] wall supply

HellDiverUK

hero member

Activity: 1246

Merit: 501

Luke-Jr, back in November I was asking about getting the BlueFurys running on OpenWRT. I finally got round to testing the BlueFury again on OpenWRT, and it's still showing 100% errors.

I don't remember what you said back then, and I can't find it on this thread.

What are your thoughts?

stewdk

newbie

Activity: 46

Merit: 0

If you're using Ubuntu 12.04 Precise and want to compile bfgminer with blade/cube functionality via libmicrohttpd, chances are you'll have a bad time because the libmicrohttpd version included with 12.04 is out of date. You can work around this by installing the libmicrohttpd packages from the 12.10 Quantal release. Sure you could just download the .deb files from http://packages.ubuntu.com/quantal/libmicrohttpd-dev and install them manually, but there's a fancier way (inspired by and portions copied from http://blog.sleeplessbeastie.eu/2012/10/08/ubuntu-precise-install-youtube-dl-package-using-quantal-repo/).

First things first, uninstall the old versions of libmicrohttpd5 and libmicrohttpd-dev and do a sudo apt-get update.

Check your available package versions:

Code:

apt-cache policy libmicrohttpd5 libmicrohttpd10 libmicrohttpd-dev

Note that libmicrohttpd5 is the 12.04 runtime package and libmicrohttpd10 is the quantal runtime package.

Create file /etc/apt/apt.conf.d/00release with contents:

Code:

APT::Default-Release "precise";

Append the quantal repository to /etc/apt/sources.list:

Code:

deb http://us.archive.ubuntu.com/ubuntu/ quantal universe

Code:

sudo apt-get update

As you defined default release as precise there should not be any packages to update (unless updates were released between the time that you started and now, something that I actually encountered while writing this up):

Code:

sudo apt-get upgrade --simulate

Check that the new version (0.9.20-1) of libmicrohttpd is available:

Code:

apt-cache policy libmicrohttpd5 libmicrohttpd10 libmicrohttpd-dev

Now, apt won't actually choose the new version of libmicrohttpd-dev yet, so create file /etc/apt/preferences.d/libmicrohttpd-dev with contents:

Code:

Package: libmicrohttpd-dev
Pin: release a=quantal
Pin-Priority: 990

Check the pinned priorities for good measure (Candidate should be version 0.9.20-1) :

Code:

apt-cache policy libmicrohttpd-dev

Code:

sudo apt-get install libmicrohttpd10 libmicrohttpd-dev

Double check the installed versions

Code:

dpkg --list | grep libmicrohttpd

Finally, compile bfgminer by the usual means.

Btc-Go

newbie

Activity: 14

Merit: 0

I want to statically link libraries so that I have single all-in binary.
That's what I do:

Code:

LDFLAGS=-static ./configure --disable-avalon --disable-largefile --enable-cpumining --enable-opencl --disable-bigpic --disable-bitfury --disable-bfsb --disable-bigpic --disable-littlefury --disable-nanofury --disable-hashbuster --disable-hashbuster2 --disable-bitforce --disable-icarus --disable-klondike --disable-modminer --disable-x6500 --disable-ztex --enable-scrypt --without-sensors --without-curses --without-libusb --without-libudev --disable-twinfury

But I get error on make:

Code:

bfgminer-driver-opencl.o: In function `load_opencl_symbols':
/usr/local/src/bfgminer/driver-opencl.c:222: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
bfgminer-miner.o: In function `main':
/usr/local/src/bfgminer/miner.c:11017: warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

I'm not a C programmer, could someone help me to understand what is going on?

bitcoinmining

sr. member

Activity: 381

Merit: 250

I've gained a lot with this method I would recommend to anyone to start winning start already miner

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: E-TARD on December 10, 2013, 08:15:46 PM

@Luke-Jr I can't get my USB block erupters to work on bfgminer.
I run Gentoo & they never show up in /dev/ttyUSB0 the way you keep saying it does, I have done everything I can think of & than some.

Well, there's something broken with your install, because they should appear as /dev/ttyUSB* - they do on any Linux/linux-based OS I've seen, even on OpenWRT.

Do you have the VCP drivers installed?

poplolnman

legendary

Activity: 1442

Merit: 1008

thanks for your hard work!!!

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

just curious for an explaination of this snippet of code from driver-bitfury.c:

in bitfury_init_oldbuf

Code:


        if (tried > 3)
        {
                applog(LOG_ERR, "%"PRIpreprv": %s: Giving up after %d tries",
                       proc->proc_repr, __func__, tried);
                bitfury->desync_counter = 99;
                return false;
        }

i have one NF1 that seems to throw it incessantly after a period of time if i set the osc6 above 52. this is on a BBB(independantly powered) linked into a dlink DUB-H7/B powered with a 2.5A supply.

also on the hub is another NF1(runs fine at 54 bits) and a pencil modded BPMC BF1.

for shits and giggles ive changed the supply to the dlink to a 3.5A to see if theres a difference.

TL;DR

is that tidbit of code an indication the chip is power starved for the frequency it is set at?

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