Topic: BFGMiner 5.5.0: CPU/GPU/FPGA/ASIC mining software, GBT+Stratum, RPC, Linux/Win64 - page 39. (Read 834507 times)

Wow! That's surely a big help to fix bugs!

Just few questions:

Why would there be "cd" just before using sudo wget?
Do we need having access to root to do what you did?

I recall reading your post earlier stating press m or + to detect those drivers, so there no need in doing this anymore? I also saw you using chmod 777 and I assume we don't need to!

To make bfminer.conf with sudo nano, don't I need permission before saving? I assume this where I need using chmod 777 but on what and where?

again you've a been greater help!

Anyone?  Am I supposed to be running the Bitmain Antminer U1/2 as Compaq's now?

updated to BFGMINer 5.3 cleaned it up some

sudo apt-get update
sudo apt-get upgrade

sudo apt-get -y install git-core build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin


sudo wget http://luke.dashjr.org/programs/bitcoin/files/bfgminer/5.3.0/bfgminer-5.3.0.zip
sudo unzip bfgminer-5.3.0.zip
sudo rm -r bfgminer-5.3.0.zip
sudo mv /home/pi/bfgminer-5.3.0 /home/pi/bfgminer

cd /home/pi/bfgminer
 
sudo chmod +x ./configure  
sudo ./configure CFLAGS="-O3" --enable-scrypt --enable-broad-udevrules

sudo make

sudo ldconfig
lsusb

./bfgminer --version

bfgminer 5.3.0
  Lowlevel: ftdi pci pci:uio spi usb vcom
  Drivers: antminer avalon avalonmm bfx bifury bigpic bitforce bitforce:pci bitfury cairnsmore cointerra drillbit dualminer erupter gridseed hashbusterusb hashfast icarus klondike littlefury modminer proxy proxy:getwork proxy:stratum rockminer twinfury x6500 zeusminer ztex
  Algorithms: SHA256d scrypt
  Options: ncursesw5

will it hurt adding --enable-gridseed in addtion   no  it won't . I don't because it is on by default im not saying don't, if you feel better doing it, then do it   . it may even help thu i have yet to see were it does . for sure add it if your having issue with any grindseed miner ..

Few members and including Luke reported a bug with recent version!

In fact a member did built this in raspberry PI:


Try executing code above to see if is version 5.3.

If you can see current version, I suggest sharing with us how you did it, if you see different version, I suggest wait until bug is fix as Luke explain few posts above!

Don't know, I have a feeling it has something to do with GPU!

https://github.com/luke-jr/bfgminer/blob/bfgminer/README.GPU

Search for temperature, you might find settings you might want using with bfgminer executable or by re-building using linus.

I don't think this applies to asic miner as they don't produces as much heat.
However, if heat causing raspberry device, few suggested putting device on top of gridseed 80 chip device which cool down or you can purchase raspberry pi fan on ebay.

Caution: the a bug on recent version while we build it, if you planning re-building it from source, I suggest waiting until that's fix!

You already mention --enable-broad-udevrules just few post above, I'm wondering, will it hurt adding --enable-gridseed in addtion?

I understand luke mentions about a bug and I quess I'll wait alse!

Upgraded successfully to 5.3.0 on the machine I run bfg on, sticks are mining away happily. 

Hi all,

I always get this log when my temperature is above 85.


Is there a way I can set bfgminer to sleep until a certain temperature is met before it is being re-enabled again like when temp is 80 and above, disable it. when it cools down to 70, re-enable it. can this be done ?

thanks in advance.

Hey the link for 5.3 for Mac os is not working.

IM gettting  5.2 as the biuld to but then up a few post luke said that's a bug so we wait i guess .


so i need to learn cross comping or use it on my PC as zip file and go that route and compile to my PI that way.

I built bfgminer from source today on a Raspberry Pi and the version returned from the resulting binary is 5.2 instead of 5.3:


This was a completely clean checkout and the usual configure, make, make install pattern:


Is this just a cosmetic problem with the version number, or is 5.3 not really on the git trunk?

chmod +x:


you need no matter what that, i know from testing, it won't run or work unless you use that command .


Never tried


chmod 777  so can't say but may try now.



all you need from this line is

sudo ./configure CFLAGS="-O3" --enable-scrypt --enable-broad-udevrules --enable-gridseed

IS

--enable-scrypt


 the read me says this is on
--enable-gridseed by default which is part of this --enable-scrypt  tested that as well . .

I did it with only --enable-gridseed it stopped at some point and told me i need --enable-scrypt to use --enable-gridseed .
I have used it with these lines --enable-scrypt --enable-gridseed i think adding --enable-gridseed  makes sure all grindseed are added even thu they are with --enable-scrypt , by Default.

I add this --enable-broad-udevrules

encase, it doesn't have be a miner to stop BFG from working if your PI has software that needs those rules  . i just add it encase it's  also added in minera as well the miners UI, check that out  btw  .. .it is really nice

https://bitcointalksearch.org/topic/minera-v090-your-next-mining-dashboard-s9l3d3cpuminercgminerbfgminer-596620


as far as i know you need all these line

code:
sudo git clone https://github.com/luke-jr/bfgminer.git
cd /bfgminer
sudo ./autogen.sh

sudo chmod +x ./configure

you crossed out and modified it which make sense i think using just +x is so no one else can access it or a rights thing which i don't care much about either. I also Use WinSCP  or  http://winscp.net/eng/index.php?#utm_source=winscp&utm_medium=app&utm_campaign=5.7.5 and looked at the BFG Properties one time to see what chmod does , it adds the excutable code 0775 i think it is so bfg can be used other wise if you don't use chmod in some form it adds another code i forget what and BFG doesn't work . but I'm still learning and next up when i take the time to do it is cross compiling.

sudo ./configure CFLAGS="-O3" --enable-scrypt
sudo make
sudo make install


maybe not this one:

sudo make install

some say they have made it with using only  sudo make, i have yet to get it to work without using  sudo make install , after using sudo make . .

I tested to see it wouldn't compile other wise or didn't for me .

this line:
sudo apt-get -y install git-core build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin


if sudo ./autogen.sh doesn't work  or it asks for autoconf or any of those packages .


depends if BFG has a line added to one of the files when its updated to a new version, i forget which one off hand .


this line is to test the USB drivers or driver to make sure you see  your miner : , some times the driver don't enable right and sudo ldconfig may help it do it and all lsusb does  is show you a list of all your drivers.

sudo ldconfig
lsusb

This need i say why  ": ) Jk


bfgminer --scrypt -S all -o your pool -u user -p PW
 


HOPE this helps some . but tested it to see what works . let us know, I'm all ways willing to try less to do more .


PS : I set up three PI's the other day with three Proxy's  wish i had done that sooner .


cya hope all this help

Were U1 and U2's supposed to change from AMU to CBM in 5.3.0?

This is what I was running 5.0.0 on a PC that I use for lottery:

again sorry you want it for a mac , yea id ask  nwoolls i have no idea how mac works sorry never owned one even thu my first PC was a apple that's about as far as I went with apple/Mac etc .

Im not being a smart ass  i would ask

 nwoolls hes pretty cool to. if your using his miner, i think hes only dropping support for the remote software part of his miner not the miner it self .

but you can try . it can't hurt any thing . expect the time you waste doing it .

The way I do it works every time with minera or without it . I haven't used multi miner that much so can't say.

if you look at the BFG read me is says gridseed is enabled by default .

--disable-gridseed      Compile support for GridSeed (default enabled)




PS  you may need this, this  time around : it seems 5.3 didn't pick it up nor did  sudo apt-get update
sudo apt-get upgrade, just did a new SD install had to do that as well .

sudo apt-get -y install git-core build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin

something like this ,

sudo git clone https://github.com/luke-jr/bfgminer.git
cd /bfgminer
sudo ./autogen.sh
sudo chmod +x ./configure  
sudo ./configure CFLAGS="-O3" --enable-scrypt --enable-broad-udevrules
sudo make
sudo make install
sudo ldconfig
lsusb

bfgminer --scrypt -S all -o your pool -u user -p PW

for my Gblade this is all i use

bfgminer --scrypt -o your pool -u user -p PW -S gsd:all --set gsd:clock=800


it stys at a steady stable 27 MH with low HW errors.

which i use every time there is a new BFG so far it works and adds supports for all my miners , if you watch at the end it tells you what is disabled and enabled and how to do it if it's not .

I do it inside a PI,  haven't tried in  windows yet but plan to. or know how to in windows with other software

cross compiling, I believe it's called .

I'm guessing at why you want those I know why just don't know the detailed way of explaining it were it makes sense .

this is not needed any more

build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev hidapi

 if you  do this

sudo apt-get update
sudo apt-get upgrade


BFG does the rest unless you use a custom made bfg or fork of BFG then you may need to add some stuff inside the BFG folder for it to compile right which I know how to. but see no need right now for a custom fork , it seems really stable for any thing you throw at it + there has been no real hard ware that has needed a BFG fork or they dislike BFG.
I added --enable-broad-udevrules

 just encase after looking at the read me

Include udev rules for ambiguous devices which may not be miners

Thanks pekatete

Ok toptek,

I think I understand  CFLAGS!

I took a double at that and I seems to suspect that some string shouldn't be in:

If I am using Git from above code, I can replace with: https://github.com/luke-jr/bfgminer ?
However, setting on that same line I wondering:

-b feature/gridseed-support
Should the complete above string be included

--enable-gridseed that include those of 40 chips blade correct?


by default using ./configure CFLAGS="-O3" --enable-scrypt when you compile it  should add support for all Grindseeds, at least it did for me for my G back and my 80 chip 5.2 MH speed GS when i had it. I even tested adding in --enable-gridseed either way it worked , i think adding that makes sure it enables support for all grindseeds, but it's not needed from what Ive done .but

 --enable-scrypt is no matter what if you want any kind of Scrypt support in BFG enabled.

I think CFLAGS is used for GCC optimization or any kind of optimization and  there is diff levels of speed you can set it at O2 O3 etc but I'm still learning how it all works and  can very well be wrong and first to admit it.