 Show Posts
|
|
Pages: [1]
|
wonder if someone could help me. I've compiled from github to enable bit fury devices. 3.9.0 on ubuntu against a bi*fury device. bfgminer will find it, cgminer won't.
------------------------------------------------------------------------
cgminer 3.9.0
------------------------------------------------------------------------
Configuration Options Summary:
libcurl(GBT+getwork).: Enabled: -lcurl
curses.TUI...........: FOUND: -lncurses
Avalon.ASICs.........: Disabled
BlackArrow.ASICs.....: Disabled
BFL.ASICs............: Disabled
BitForce.FPGAs.......: Disabled
BitFury.ASICs........: Enabled
which cgminer
/usr/local/bin/cgminer
[2013-12-30 15:27:12] Started cgminer 3.9.0
[2013-12-30 15:27:12] No devices detected!
[2013-12-30 15:27:12] Waiting for USB hotplug devices or press q to quit
[2013-12-30 15:27:12] Need to specify at least one pool server.
where do i start troubleshooting this one? just to prove it does see the device. sudo ../bfgminer/bfgminer -d? -S bifury:all
[2013-12-30 15:30:57] Started bfgminer 3.9.0
[2013-12-30 15:30:59] Devices detected:
[2013-12-30 15:30:59] bi•fury by c-scape (driver=bifury; procs=2; path=/dev/ttyACM0)
1 devices listed
[/code/] |
|
|
|
|
id noticed that in the output, but it was working fine until 3.9.0
that said, this box has now had so many installs and uninstalls of the bfg and cg miners any one of them could have removed it.
whats the actual package name? edit: libncurses5-dev
|
|
|
|
ok , fixed my own issue by surprise, googling the error message. needed to install autoconf uthash-dev and lib tool packages. then used ./autogen.sh && ./configure --enable-bitfury
make
bfgminer is streaming output rather than holding it in a block of text, but i think this might be bacuase i've ssh'd onto the ubuntu box. not sure why it won't show the desktop after login, need to fix that next. however this is worrying, is it not? BIF0 39.4C | 5s: 0.00 avg: 0.00 u:361.7 Mh/s | A:32 R:3+0(8.6%) HW:352/ 91%
looks to me like a busted chip... anyone agree or disagree? |
|
|
|
can anyone help me with my install of bfgminer on ubuntu? i can do it through apt-get but that only gets me 3.8.0 and i need 3.9.0 to use the new code fixes for bit fury. so i have done the following...
cd ~
mkdir bin
cd bin
sudo git clone https://github.com/luke-jr/bfgminer ~/bin/bfgminer
cd bfgminer
sudo ./autogen.sh
which runs but comes up with the following error ./autogen.sh: 20: ./autogen.sh: autoreconf: not found
which i take to mean its looking for an autoconf file, which isn't there. does it need to be? the next step is (from reading the help on github) sudo ./configure.ac --enable-bitfury
but this step also fails, 'command not found'. anyone else going through this and know what the fix is? and i know the obvious answer is to use the repos, but they aren't updated. thanks, |
|
|
|
Try running it using the latest 3.9.0 BFGMiner with sudo privileges. It was the only way I could run it without segmentation faults.
sudo apt-get install bfgminer
Reading package lists... Done
Building dependency tree
Reading state information... Done
bfgminer is already the newest version.
i know theres a 3.9.0 but apt-get doesn't seem to. i've got ppa as repo and i've done a 'sudo apt-get update'. so i guess i have to download it myself compile it and install it. linux hell, right there. |
|
|
|
been linked here by nwoolls, think i've got a hardware issue with a bi*fury stick. would you say the following results from a bi*fury left to run for 30 secondsish indicates an issue? so this is a bi*fury, in a usb 3 slot on a new macbook pro, running bfgminer --HEAD installed by home-brew Summary of runtime statistics:
[2013-12-29 13:15:39] Started at [2013-12-29 13:13:51]
[2013-12-29 13:15:39] Pool: http://pit.deepbit.net:8332
[2013-12-29 13:15:39] Runtime: 0 hrs : 1 mins : 47 secs
[2013-12-29 13:15:39] Average hashrate: 0.0 Megahash/s
[2013-12-29 13:15:39] Solved blocks: 0
[2013-12-29 13:15:39] Best share difficulty: 33
[2013-12-29 13:15:39] Share submissions: 32
[2013-12-29 13:15:39] Accepted shares: 32
[2013-12-29 13:15:39] Rejected shares: 0 + 0 stale (0.00%)
[2013-12-29 13:15:39] Accepted difficulty shares: 32
[2013-12-29 13:15:39] Rejected difficulty shares: 0
[2013-12-29 13:15:39] Hardware errors: 79
[2013-12-29 13:15:39] Network transfer: 153.0 / 67.9 kB ( 1.5 / 0.7 kB/s)
[2013-12-29 13:15:39] Efficiency (accepted shares * difficulty / 2 KB): 0.30
[2013-12-29 13:15:39] Utility (accepted shares / min): 18.81/min
[2013-12-29 13:15:39] Unable to get work from server occasions: 0
[2013-12-29 13:15:39] Work items generated locally: 0
[2013-12-29 13:15:39] Submitting work remotely delay occasions: 0
[2013-12-29 13:15:39] New blocks detected on network: 1
[2013-12-29 13:15:39] Summary of per device statistics:
[2013-12-29 13:15:39] BIF0 53.1C | 5s: 0.00 avg: 0.00 u: 1.27 Gh/s | A:32 R:0+0(none) HW:79/ 71%
[2013-12-29 13:15:39] BIF0a 53.1C | 5s: 0.00 avg: 0.00 u: 1.27 Gh/s | A:32 R:0+0(none) HW:73/ 70%
[2013-12-29 13:15:39] BIF0b 53.1C | 5s: 0.0 avg: 0.0 u: 0.0 h/s | A:0 R:0+0(none) HW:6/100%
[2013-12-29 13:15:39]
Shutdown signal received.
if i read it right, one of the two chips isn't hashing, hardware errors of 100%. the other one has a pretty terrible return of 70%. I know the temperature is sky high, was running it away from the fan briefly. I get very similar results from the device when i run it in an enclosure with a fan on it, on a ubuntu pc with latest bfgminer too. it did cause crashes in 3.8.0 every so often, segmentation faults. couldn't get it to run very long at all on the ubuntu box. any thoughts? |
|
|
|
been reading your blog and noticed the link here, so wondered if i could ask a question would you say the following results from a bi*fury left to run for 30 secondsish indicates an issue? so this is a bi*fury, in a usb 3 slot on a new macbook pro, running bfgminer --HEAD installed by home-brew from your excellent instructions. Summary of runtime statistics:
[2013-12-29 13:15:39] Started at [2013-12-29 13:13:51]
[2013-12-29 13:15:39] Pool: http://pit.deepbit.net:8332
[2013-12-29 13:15:39] Runtime: 0 hrs : 1 mins : 47 secs
[2013-12-29 13:15:39] Average hashrate: 0.0 Megahash/s
[2013-12-29 13:15:39] Solved blocks: 0
[2013-12-29 13:15:39] Best share difficulty: 33
[2013-12-29 13:15:39] Share submissions: 32
[2013-12-29 13:15:39] Accepted shares: 32
[2013-12-29 13:15:39] Rejected shares: 0 + 0 stale (0.00%)
[2013-12-29 13:15:39] Accepted difficulty shares: 32
[2013-12-29 13:15:39] Rejected difficulty shares: 0
[2013-12-29 13:15:39] Hardware errors: 79
[2013-12-29 13:15:39] Network transfer: 153.0 / 67.9 kB ( 1.5 / 0.7 kB/s)
[2013-12-29 13:15:39] Efficiency (accepted shares * difficulty / 2 KB): 0.30
[2013-12-29 13:15:39] Utility (accepted shares / min): 18.81/min
[2013-12-29 13:15:39] Unable to get work from server occasions: 0
[2013-12-29 13:15:39] Work items generated locally: 0
[2013-12-29 13:15:39] Submitting work remotely delay occasions: 0
[2013-12-29 13:15:39] New blocks detected on network: 1
[2013-12-29 13:15:39] Summary of per device statistics:
[2013-12-29 13:15:39] BIF0 53.1C | 5s: 0.00 avg: 0.00 u: 1.27 Gh/s | A:32 R:0+0(none) HW:79/ 71%
[2013-12-29 13:15:39] BIF0a 53.1C | 5s: 0.00 avg: 0.00 u: 1.27 Gh/s | A:32 R:0+0(none) HW:73/ 70%
[2013-12-29 13:15:39] BIF0b 53.1C | 5s: 0.0 avg: 0.0 u: 0.0 h/s | A:0 R:0+0(none) HW:6/100%
[2013-12-29 13:15:39]
Shutdown signal received.
if i read it right, one of the two chips isn't hashing, hardware errors of 100%. the other one has a pretty terrible return of 70%. I know the temperature is sky high, was running it away from the fan briefly. I get very similar results from the device when i run it in an enclosure with a fan on it, on a ubuntu pc with latest bfgminer too. it did cause crashes in 3.8.0 every so often, segmentation faults. couldn't get it to run very long at all on the ubuntu box. any thoughts? |
|
|
|
|
final post from me answering my own questions. seems the bit fury doesn't need to detect on ubuntu to hash. currently running along at 2.9Gh/s which isn't good enough, but if you saw how i'd cobbled it together, you'd be happy enough with that too.
gonna leave it over next couple of days and see what it comes up with.
|
|
|
|
|
ok, so issue found that i need help with. when i plug the a sic into the ubuntu box, the red led lights up on the board. next to the green one. what does this indicate? I can't find info on the device anywhere to explain what this LED indicates.
|
|
|
|
|
ok, partly solved my own issue, by restarting the mac and following the article to the letter. managed to get it to detect and even solved a block. but it thermalled, so I need to get it back into the ubuntu box and get the fan blowing on it again.
so maybe ignore this thread for an hour while i try and generate an actual error message on the ubuntu box.
|
|
|
|
hi all. i just bought a bit fury, which I can't get to detect on either os x or linux, more specifically ubuntu 13.10. I wondered if anyone could give me some clues, or at least let me know they've managed to get it working on either of the above. I have read just now that ubuntu isn't the friendliest of OS's to get them working on, but i've managed to get past the list of pre reqs. but the device just doesn't appear. I've tested the ports with other devices, moved the device, etc. I then moved the device to my 2013 Macbook pro, but it still doesn't detect. Im following this article http://blog.nwoolls.com/2013/12/19/bitcoin-mining-on-mac-os-x-bi•fury-asics/ the device itself is in good condition after its journey to me. it lights up with the green LED. I do sometimes see the red one which goes out after a while. I haven't yet found a guide which explains what the LEDs mean though. so anyone been successful with these devices? which OS, anyone on ubuntu? |
|
|
|
|
