solarion
|
|
March 19, 2014, 07:52:35 AM Last edit: March 23, 2014, 05:28:09 PM by solarion |
|
Is there anyway to use a different stratum proxy with chain miner? Resetting it every 10 or 60 min still leads to issues after several days. Anyway to put slush's proxy in it, or is that what it is using? I tried bfgminer as the proxy and though the shares make it to bfgminer, they're all discarded as hw errors. Not sure where the problem lies as I've encoded credentials into jobconnect. Perhaps I'll throw the question at Luke-jr at some point. Update: Nevermind THAT ^^^ CGMiner works a treat now on bitfury rigs. Bye Bye chainminer and the lamo proxy. Thanks ckolivas for the awesome miner! Finally got some cgremote action on bitfury rigs. Huge thanks to Kano, who apparently did the bulk of the work to the bab driver. https://bitcointalk.org/index.php?topic=28402.msg4726840#msg4726840
|
|
|
|
|
|
|
|
|
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
ndonnard
Member
Offline
Activity: 109
Merit: 10
|
|
March 20, 2014, 02:03:23 PM |
|
The goal of this thread has been reached with success! A lot of info!
|
|
|
|
adib
|
|
March 20, 2014, 06:11:30 PM |
|
Is there anyway to use a different stratum proxy with chain miner? Resetting it every 10 or 60 min still leads to issues after several days. Anyway to put slush's proxy in it, or is that what it is using? I tried bfgminer as the proxy and though the shares make it to bfgminer, they're all discarded as hw errors. Not sure where the problem lies as I've encoded credentials into jobconnect. Perhaps I'll throw the question at Luke-jr at some point. Update: Nevermind THAT ^^^ CGMiner works a treat now on bitfury rigs. Bye Bye chainminer and the lamo proxy. Thanks ckolivas for the awesome miner! Finally got some cgremote action on bitfury rigs. How did you get Cgminer to work with bitfury h-cards? I only managed with bfgminer, cgminer only wants usb stuff
|
TIPS - 19JLxDkCfn5x667xCeSgmYNop4WLR3ci27
|
|
|
solarion
|
|
March 21, 2014, 12:48:57 AM Last edit: March 23, 2014, 05:43:07 PM by solarion |
|
Is there anyway to use a different stratum proxy with chain miner? Resetting it every 10 or 60 min still leads to issues after several days. Anyway to put slush's proxy in it, or is that what it is using? I tried bfgminer as the proxy and though the shares make it to bfgminer, they're all discarded as hw errors. Not sure where the problem lies as I've encoded credentials into jobconnect. Perhaps I'll throw the question at Luke-jr at some point. Update: Nevermind THAT ^^^ CGMiner works a treat now on bitfury rigs. Bye Bye chainminer and the lamo proxy. Thanks ckolivas for the awesome miner! Finally got some cgremote action on bitfury rigs. How did you get Cgminer to work with bitfury h-cards? I only managed with bfgminer, cgminer only wants usb stuff I compiled cgminer with --enable-bab (black arrow bitfury). It autodetected all of my v2.2 cards properly. I can't speak to how this works with v1 cards, though I know it tries to detect those first. I've gotten cgminer to match chainminer top end performance with similar settings, which is a huge win given cgminer's wealth of features. The real advantage to running cgminer on bitfury rigs wasn't immediately obvious however. I let a rig with 14 h cards run overnight with stock cgminer parameters and it tuned out so many hardware errors that efficiency improved by over 11%(.8622 vs .7747). Aside from potential uses to diagnose problems I've no further use for chainminer.
|
|
|
|
spegelius
Newbie
Offline
Activity: 52
Merit: 0
|
|
March 26, 2014, 07:12:30 PM |
|
Yeah cgminer does work with these cards, ive been testing it now and then, but have always returned to chainminer. The reason is that even though the speed looks very good after a while it tunes itself to max speed (385GH/s vs. 420GH/s max speeds, chainminer vs cgminer), after a day or so it goes below chainminer speeds. I guess restarting cgminer daily would fix that, haven't really bothered as chainminer just rolls on on autotune. And cgminer does have some options to tune bitfury cards manually, but currently i just want my rigs to run without constant tuning .
|
|
|
|
solarion
|
|
March 27, 2014, 11:43:43 AM |
|
Put a meter on that rig. You'll find that power consumption is dropping off a cliff. Cgminer is tuning out hw errors and chainminner is happily gobbling up power without regard to hw errors. The difference in efficiency is not small.
You can make cgminer behave the same way by just changing the tune up/down values. That's an optional value you can pass directly to cgminer without changing the code.
|
|
|
|
daddyfatsax
|
|
March 27, 2014, 04:20:23 PM |
|
Put a meter on that rig. You'll find that power consumption is dropping off a cliff. Cgminer is tuning out hw errors and chainminner is happily gobbling up power without regard to hw errors. The difference in efficiency is not small.
You can make cgminer behave the same way by just changing the tune up/down values. That's an optional value you can pass directly to cgminer without changing the code.
What options are you starting cgminer with?
|
|
|
|
spegelius
Newbie
Offline
Activity: 52
Merit: 0
|
|
March 27, 2014, 06:37:19 PM |
|
Put a meter on that rig. You'll find that power consumption is dropping off a cliff. Cgminer is tuning out hw errors and chainminner is happily gobbling up power without regard to hw errors. The difference in efficiency is not small.
You can make cgminer behave the same way by just changing the tune up/down values. That's an optional value you can pass directly to cgminer without changing the code.
Hmm, seriously? I'll have to test the power draw. With chainminer it sucks about ~300W on the wall @380GH/s, i haven't tried it with cgminer. Tuning... somehow that doesn't sound as fun it sounded few months ago . Oh well, it'll be propably worth it.
|
|
|
|
solarion
|
|
March 27, 2014, 09:45:30 PM Last edit: March 27, 2014, 10:09:12 PM by solarion |
|
Put a meter on that rig. You'll find that power consumption is dropping off a cliff. Cgminer is tuning out hw errors and chainminner is happily gobbling up power without regard to hw errors. The difference in efficiency is not small.
You can make cgminer behave the same way by just changing the tune up/down values. That's an optional value you can pass directly to cgminer without changing the code.
What options are you starting cgminer with? I've been altering these lines in driver-bab.c #define BAB_MAXSPEED 57 #define BAB_DEFMAXSPEED 55 #define BAB_DEFSPEED 53 #define BAB_MINSPEED 52 #define BAB_ABSMINSPEED 32 #define BAB_TUNEUP 1.0 #define BAB_TUNEDOWN 10.0 https://github.com/ckolivas/cgminer/blob/master/driver-bab.cThese are also the values that can be passed to cgminer on startup. The format was posted by kano in the cgminer thread...somewhere around pg 700 I believe. Actually 710: https://bitcointalk.org/index.php?topic=28402.msg4726840#msg4726840From asic-readme: --bab-options <arg> Set BaB options max:def:min:up:down:hz:delay:trf https://github.com/ckolivas/cgminer/blob/master/ASIC-README
|
|
|
|
Gyrsur
Legendary
Offline
Activity: 2856
Merit: 1520
Bitcoin Legal Tender Countries: 2 of 206
|
|
March 30, 2014, 07:53:53 AM Last edit: March 30, 2014, 08:25:23 AM by Gyrsur |
|
6 of my 16 bitfury v1.2 H-CARD died over the time. October 2013 batch. no overclocking and no overheating! did someone face the same experience??
EDIT: seems to me quality of the bitfury v1.2 H-CARD (October 2013 batch) is not good enough to work with it 24/7 for a half year. some component on the card died. cards did not work again if I changed the slot on the bitfury v2.3 M-CARD.
|
|
|
|
eestimees
|
|
April 02, 2014, 08:47:18 PM |
|
I need some help.. I have M-board 2.3 and 16x H-card v1.2 today I had to shutdown (sudo halt) miner to move it. After blowing away some dust and starting it again, is started hashing fine.. approx 15min later it stopped.. webserver responds The requested URL / was not found on this server. and no ssh connectivity at all.. next time I stayed in with my ssh connection. now I cant do a thing in shell all commands are dissapeared.. Do I have faulty SD-card that has unmounted itself? pi@bitfury ~ $ pwd /home/pi pi@bitfury ~ $ ls -bash: ls: command not found pi@bitfury ~ $ ps -bash: ps: command not found pi@bitfury ~ $ df -h -bash: /bin/df: No such file or directory pi@bitfury ~ $
|
— eestimees
|
|
|
bobcaticus
|
|
April 02, 2014, 09:08:07 PM |
|
I need some help.. I have M-board 2.3 and 16x H-card v1.2 today I had to shutdown (sudo halt) miner to move it. After blowing away some dust and starting it again, is started hashing fine.. approx 15min later it stopped.. webserver responds The requested URL / was not found on this server. and no ssh connectivity at all.. next time I stayed in with my ssh connection. now I cant do a thing in shell all commands are dissapeared.. Do I have faulty SD-card that has unmounted itself? pi@bitfury ~ $ pwd /home/pi pi@bitfury ~ $ ls -bash: ls: command not found pi@bitfury ~ $ ps -bash: ps: command not found pi@bitfury ~ $ df -h -bash: /bin/df: No such file or directory pi@bitfury ~ $
I'd recommend a new image and SD card
|
|
|
|
eestimees
|
|
April 02, 2014, 09:16:32 PM |
|
I'd recommend a new image and SD card
got a link to image? OP links does not work... EDIT: found it, prev page
|
— eestimees
|
|
|
arorts
|
|
April 08, 2014, 11:23:53 AM Last edit: April 08, 2014, 11:35:44 AM by arorts |
|
As you might know, openssl libraries based on 1.01 and 1.02 beta releases are apparently infected with the heartbleed bug. This is the bug that allows snooping and steeling of information over SSL connections. Does anyone know whether it's safe to upgrade/recompile the openssl libraries that came with the Raspberry PI distributed by Bitfury??? What's the simplest/safest method to do so?? I just typed openssl version -v and it definitely shows version 1.0.1e, which seems to carry the bug as explained here!!!: Check out http://heartbleed.comThis is a CRITICAL topic!!! Please advise!!!
|
|
|
|
|
bobcaticus
|
|
April 08, 2014, 06:14:49 PM |
|
As you might know, openssl libraries based on 1.01 and 1.02 beta releases are apparently infected with the heartbleed bug. This is the bug that allows snooping and steeling of information over SSL connections. Does anyone know whether it's safe to upgrade/recompile the openssl libraries that came with the Raspberry PI distributed by Bitfury??? What's the simplest/safest method to do so?? I just typed openssl version -v and it definitely shows version 1.0.1e, which seems to carry the bug as explained here!!!: Check out http://heartbleed.comThis is a CRITICAL topic!!! Please advise!!! I've passed this info along to our devs and will get a response shortly. -Jason
|
|
|
|
arorts
|
|
April 09, 2014, 01:31:13 AM |
|
As you might know, openssl libraries based on 1.01 and 1.02 beta releases are apparently infected with the heartbleed bug. This is the bug that allows snooping and steeling of information over SSL connections. Does anyone know whether it's safe to upgrade/recompile the openssl libraries that came with the Raspberry PI distributed by Bitfury??? What's the simplest/safest method to do so?? I just typed openssl version -v and it definitely shows version 1.0.1e, which seems to carry the bug as explained here!!!: Check out http://heartbleed.comThis is a CRITICAL topic!!! Please advise!!! I've passed this info along to our devs and will get a response shortly. -Jason Well I did update my overall Raspbian using this command line, which apparently does include any OpenSSL updates as well: sudo apt-get update && sudo apt-get dist-upgrade However, now when I run cat /run/shm/.stat.log it's now showing even the slots where there are no H-Cards with tons of errors from B-F. speed:13325 noncerate[GH/s]:328.450 (1.283/chip) hashrate[GH/s]:441.082 good:22942 errors:26313 spi-err:1757 miso-err:1191 jobs:283 cores:11% good:246 bad:2 off:8 (best[GH/s]:0.000) Tue Apr 8 18:28:18 2014 0: 871 32.484 35.038 2269 82 0 1 16 0 0 (2.030/chip) 17% 1: 758 30.050 33.125 2099 102 0 0 15 1 0 (1.878/chip) 16% 2: 817 33.959 35.123 2372 49 1 0 15 1 0 (2.122/chip) 18% 3: 869 34.260 34.880 2393 49 1 0 16 0 0 (2.141/chip) 18% 4: 809 31.496 31.191 2200 34 0 0 16 0 0 (1.969/chip) 17% 5: 704 28.318 28.580 1978 28 0 2 13 0 3 (1.770/chip) 15% 6: 822 25.240 27.534 1763 69 0 1 15 0 1 (1.578/chip) 13% 7: 872 34.245 34.700 2392 34 0 0 16 0 0 (2.140/chip) 18% 8: 768 26.028 27.101 1818 43 0 2 14 0 2 (1.627/chip) 14% 9: 767 24.925 25.642 1741 31 0 2 14 0 2 (1.558/chip) 13% A: 868 27.445 31.032 1917 654 35 30 16 0 0 (1.715/chip) 15% B: 880 0.000 19.385 0 5037 345 225 16 0 0 (0.000/chip) 0% C: 880 0.000 19.448 0 5025 343 236 16 0 0 (0.000/chip) 0% D: 880 0.000 19.501 0 5026 351 224 16 0 0 (0.000/chip) 0% E: 880 0.000 19.268 0 5030 331 239 16 0 0 (0.000/chip) 0% F: 880 0.000 19.533 0 5020 350 229 16 0 0 (0.000/chip) 0% Previously, this file simply ended at A and didn't gave me all those errors. Any thoughts? UPDATE: It seems the problem went away by itself so no more nasty extra lines in that file. :-)
|
|
|
|
Stanford
Member
Offline
Activity: 314
Merit: 10
|
|
April 09, 2014, 10:19:51 AM |
|
The goal of this thread has been reached with success! A lot of info!
Totally agree with you! I have already found here answers to the problems I have faced with!
|
|
|
|
arorts
|
|
April 10, 2014, 01:34:42 AM |
|
Anyone has seen the repeating message "New proxy version available Please update!" when checking their proxy process in the miner?
Any process to back it up and update it to a new version?
|
|
|
|
bobcaticus
|
|
April 10, 2014, 01:46:31 AM Last edit: April 10, 2014, 02:38:40 AM by bobcaticus |
|
As you might know, openssl libraries based on 1.01 and 1.02 beta releases are apparently infected with the heartbleed bug. This is the bug that allows snooping and steeling of information over SSL connections. Does anyone know whether it's safe to upgrade/recompile the openssl libraries that came with the Raspberry PI distributed by Bitfury??? What's the simplest/safest method to do so?? I just typed openssl version -v and it definitely shows version 1.0.1e, which seems to carry the bug as explained here!!!: Check out http://heartbleed.comThis is a CRITICAL topic!!! Please advise!!! I've passed this info along to our devs and will get a response shortly. -Jason Well I did update my overall Raspbian using this command line, which apparently does include any OpenSSL updates as well: sudo apt-get update && sudo apt-get dist-upgrade Thanks - either that or this will do the trick: sudo apt-get update sudo apt-get install openssl libssl-dev
This information was added to the blog as well: https://www.megabigpower.com/blog/?p=60Arorts - I will look into that.
|
|
|
|
|