and when a card shows 0 hashing, what's next? decrease voltage with a quarter counterclockwise turn of the trimpot?
Have you already tried turning the speed down to 52 or 51? A few of my cards won't stay running at 53 or higher. how is this done? |
|
|
|
what's the recommended procedure for doing this as in "stop miner" or "shut down completely" or "power off" before adding another card?
a) stop miner b) shutdown -h now c) power off PSU d) PS no hot-swapping  I just do sudo poweroff, wait for all but the red light on the rPi to go off, and then shut off the PSU. sounds reasonable to me as Chainminer seems broken. i'd much rather work from the CLI. |
|
|
|
can someone explain the concept of the Banks and how they apply to v2.2 H boards and v3 M boards?
Dave said that the Banks are obsolete and that the H boards are just numbered 0-9, A-F. however, on 3 of my M boards i have one entire bank at zero; 2 Bank 1's, and 1 Bank 4. there must be some relationship btwn the 4 adjacent cards in those Banks.
any suggestions to revive those Banks?
Even v3 M-boards have 4 banks of 4 slots each. Try reseating cards, or rotate the 4 cards within a bank. If you think the problem is related to VRM thermal/current overload, try disabling a chip or two on each card, or turn down the voltage with the trimpots. i have heatsinks and multiple fans so hopefully it isn't thermal. i know the GUI shows 4 banks but do they have a function? Dave did say they didn't mean anything. Can you please post a screenshot of your bitfury webpage? Can you enable remote login to your rig for a few mins?  Since Bank1 and 2 are kaput, You will have to a) Unplug all but first card from Bank 1 and Bank 2 b) Check if the cards on Bank 1 and Bank 2 are mining c) Add one more card to each Bank d) Repeat b through c what's the recommended procedure for doing this as in "stop miner" or "shut down completely" or "power off" before adding another card? a) stop miner b) shutdown -h now c) power off PSU d) PS no hot-swapping and when a card shows 0 hashing, what's next? decrease voltage with a quarter counterclockwise turn of the trimpot? |
|
|
|
can someone explain the concept of the Banks and how they apply to v2.2 H boards and v3 M boards?
Dave said that the Banks are obsolete and that the H boards are just numbered 0-9, A-F. however, on 3 of my M boards i have one entire bank at zero; 2 Bank 1's, and 1 Bank 4. there must be some relationship btwn the 4 adjacent cards in those Banks.
any suggestions to revive those Banks?
Even v3 M-boards have 4 banks of 4 slots each. Try reseating cards, or rotate the 4 cards within a bank. If you think the problem is related to VRM thermal/current overload, try disabling a chip or two on each card, or turn down the voltage with the trimpots. i have heatsinks and multiple fans so hopefully it isn't thermal. i know the GUI shows 4 banks but do they have a function? Dave did say they didn't mean anything. Can you please post a screenshot of your bitfury webpage? Can you enable remote login to your rig for a few mins? Since Bank1 and 2 are kaput, You will have to a) Unplug all but first card from Bank 1 and Bank 2 b) Check if the cards on Bank 1 and Bank 2 are mining c) Add one more card to each Bank d) Repeat b through c what's the recommended procedure for doing this as in "stop miner" or "shut down completely" or "power off" before adding another card? |
|
|
|
can someone explain the concept of the Banks and how they apply to v2.2 H boards and v3 M boards?
Dave said that the Banks are obsolete and that the H boards are just numbered 0-9, A-F. however, on 3 of my M boards i have one entire bank at zero; 2 Bank 1's, and 1 Bank 4. there must be some relationship btwn the 4 adjacent cards in those Banks.
any suggestions to revive those Banks?
Even v3 M-boards have 4 banks of 4 slots each. Try reseating cards, or rotate the 4 cards within a bank. If you think the problem is related to VRM thermal/current overload, try disabling a chip or two on each card, or turn down the voltage with the trimpots. i have heatsinks and multiple fans so hopefully it isn't thermal. i know the GUI shows 4 banks but do they have a function? Dave did say they didn't mean anything. Can you please post a screenshot of your bitfury webpage? Can you enable remote login to your rig for a few mins? |
|
|
|
can someone explain the concept of the Banks and how they apply to v2.2 H boards and v3 M boards?
Dave said that the Banks are obsolete and that the H boards are just numbered 0-9, A-F. however, on 3 of my M boards i have one entire bank at zero; 2 Bank 1's, and 1 Bank 4. there must be some relationship btwn the 4 adjacent cards in those Banks.
any suggestions to revive those Banks?
Even v3 M-boards have 4 banks of 4 slots each. Try reseating cards, or rotate the 4 cards within a bank. If you think the problem is related to VRM thermal/current overload, try disabling a chip or two on each card, or turn down the voltage with the trimpots. i have heatsinks and multiple fans so hopefully it isn't thermal. i know the GUI shows 4 banks but do they have a function? Dave did say they didn't mean anything. |
|
|
|
|
can someone explain the concept of the Banks and how they apply to v2.2 H boards and v3 M boards?
Dave said that the Banks are obsolete and that the H boards are just numbered 0-9, A-F. however, on 3 of my M boards i have one entire bank at zero; 2 Bank 1's, and 1 Bank 4. there must be some relationship btwn the 4 adjacent cards in those Banks.
any suggestions to revive those Banks?
|
|
|
|
...
...
***ERROR: Block previously main branch, now orphan!?081e107ab0468d867937221970d87cd5101b5b0691c4502b4600000000000000
***ERROR: Block previously main branch, now orphan!?081fd344b0a6ce419cc79621abe2a3e6344635ef6296c39f7400000000000000
***ERROR: Block previously main branch, now orphan!?081fd344b0a6ce419cc79621abe2a3e6344635ef6296c39f7400000000000000
...
...
Definitely the corrupted blk*.dat files that used to happen all the time. I don't know how you got there after a fresh install, but this was definitely the issue that was always resolved when I told people to remove their blk*.dat files and redownload the chain. Also, this can happen if you start mainnet Armory on the testnet blockchain, or vice versa. But I assume that's not the issue here. I have no othe recommendation other than to nuke your Bitcoin-Qt dir (except wallet.dat) and let it redownload. Even if Bitcoin-Qt can read it, Armory can't for some reason. I spent time trying to figure it out, but new it would be obsoleted soon by the new version. the only hint i can give you is that for the first time, i let Armory handle the Bitcoin download since this was a fresh install. |
|
|
|
so, in your opinion, is BFGminer definitely a better choice than Chainminer?
Chainminer kept conking out on me. Sometimes it'd take a few tries to get it running stably, and even once it appeared to be stable, sometimes it'd die for no good reason. Hashrate kept fluctuating. It (or the stratum proxy) also didn't like BTCGuild. bfgminer has been far less troublesome, so I'd have to say that it is the better choice. That it'll also handle my BFL miners plugged into the RPi over USB is a bonus (was able to get rid of the power-hungry P4 that was running all my mining hardware). I've not applied any hardware tweaks yet. I've not tried backing off the voltage from the regulator, and I'm waiting for heatsinks to arrive (ordered this 100-pack last week). of course you're right. i've been experiencing the same problems with chainminer. not looking forward to the effort of switching over. |
|
|
|
Although the shelves are metal, they are coated in a plastic/epoxy material. I have ran Mobos for GPU rigs directly on the shelves for over a year now with no problems, so I'm not that worried about it. I really like these shelves for mining equipment.. I got them at target. The wire racks allow for optimal air flow.  hmmm, mine are awfully similar. i laid plastic sheet down. but it causes the M board to torque a bit due to the yellow video port lifting up the raspi end. may have to try w/o the plastic. |
|
|
|
I got my unit running with bfgminer, the only thing I could get chainminer to do was output
"M-Board version 2 detected
INIT: 256 chips detected"
Now I'm having issues with bfgminer outputting this, and the hashrate dropping.
[2013-11-12 00:05:02] BSB 2bm: bitfury_init_oldbuf: Giving up after 4 tries
[2013-11-12 00:05:02] BSB 2bn: bitfury_init_oldbuf: Giving up after 4 tries
[2013-11-12 00:05:02] BSB 2bo: bitfury_init_oldbuf: Giving up after 4 tries
[2013-11-12 00:05:02] BSB 2bp: bitfury_init_oldbuf: Giving up after 4 tries
...
I'd get those errors if I let bfgminer initialize the cards with the clock set to 53. I turned it down to 52 and it's been running without issue for nearly 3 days:  See this post for details. so, in your opinion, is BFGminer definitely a better choice than Chainminer? |
|
|
|
silverbox, i know you're out there. you're on your way to making a new low. get out NOW:  |
|
|
|
|
Gold collapsing. Bitcoin UP.
|
|
|
|
Hrm. This is not exactly how I envisioned this going. This is very frustrating.. my Avalons and KNCminers I was able to setup and get hashing within minutes. Add the assembly time of a full rig, plus the fact they're both not working.... I got two full rigs today. One is running at 225 Gh and the other is running at 0 Gh. Rig 1:
Bank 1
1: 33.415GH/s
2: 33.443GH/s
3: 20.702GH/s
4: 21.79GH/s
Bank 2
5: 4.223GH/s
6: 0GH/s
7: 0GH/s
8: 0GH/s
Bank 3
9: 15.677GH/s
10: 10.107GH/s
11: 11.167GH/s
12: 13.758GH/s
Bank 4
13: 9.621GH/s
14: 9.893GH/s
15: 10.165GH/s
16: 20.916GH/s
Rig 2:
Bank 1
1: 0GH/s
2: 0GH/s
3: 0GH/s
4: 0GH/s
Bank 2
5: 0GH/s
6: 0GH/s
7: 0GH/s
8: 0GH/s
Bank 3
9: 0GH/s
10: 0GH/s
11: 0GH/s
12: 0GH/s
Bank 4
13: 0GH/s
14: 0GH/s
15: 0GH/s
16: 0GH/s
I'm certain everything is hooked up correctly. I have checked several times. I tried replacing the PSU and that didn't do anything. I am using a 1200w to run both full rigs. I'm sorry if this is covered... (I'm going to go back and read through this thread now.) Any quick suggestions though? This thread is so long.. I'm not sure if this matters, but it seems the two rigs might have different firmware versions. One says this on the main admin screen the other does not: "Attention! Please set pool difficulty on your pool to 32-512 depending on your hashrate. Low difficulty setting will result in work queue overload, and drop your hashrate substantially. If running a full unit, please make sure all cards are installed in slots written on the back side of the card. Due to SPI bugs, the miner may need to be stopped and restarted using the buttons above." (I don't take credit for these fixes, some of them I found out on my own and some of them I read from other user's experiences.) I needed to find a way to keep the cards stable, they come with crappy 1x PCI connectors and are really wobbly, especially when being blasted by fans (which is necc. to keep them cool and stable). The movement in the cards was causing the rig to slow down slowly over time until the affected cards eventually ended up at 0 Gh. To fix this I used two rows of electrical tape along the top of the cards to hold them in place better. Cooling may or may not have been an issue. I added an extra box fan in front (two box fans now) and also two computer fans blowing air down on top of them for added air flow. I was under the impression that two full rigs would run on one 1200 watt power supply. It turns out that seemed to be overloading the PSU (a nice gold rated ASUS). I ended up using a separate PSU for each rig and that got them both mining. I think this is the main reason why the one was getting 0 Gh and wouldn't mine. As soon as I put it on its own PSU it started working fine. I put slower H cards in the last slot of each bank to keep them from interfering with other H cards. If you have one bank that is not working but all the rest are, this is likely the issue. If the card in the first slot of each bank is not seated properly, the rest of the bank will not work. I hope this helps someone and saves them the 16 hours of their life that I just wasted. Now... I wish I would of realized all this before spending all night messing with firmwares... flashing sdcards... installing a different OS... trying BFGminer... trying cgminer... etc. :rolleyes: My phone messed up while uploading, but a couple pics: http://imgur.com/a/9vDAm#apBFVy5are you laying the M boards down directly onto a wire frame rack? aren't you worried about an electrical short? |
|
|
|
But after it was working and when i saw it reach 640 for a brief moment on this same psu and not shut down...it gave me that boost in morale to "keep calm and carry on"
was this 640 from the pool or in Chainminer? i'm consistently getting higher readings from the pool. |
|
|
|
reading the last few pages makes me feel not so bad.  I'm happy for you, HashFast shill. no, more from the standpoint that i have been having alot of trouble with my BF's as well. |
|
|
|
reading the last few pages makes me feel not so bad. |
|
|
|
why do i seem to be stuck at 98% "scanning transaction history" after a fresh install of 0.88.1 onto Ubuntu 13.10 with bitcoind in the background?
16GB RAM, 64 bit, 750 GB SSD.
i tried closing Armory, starting bitcoind -daemon, then reopening Armory, but still get stuck on 98% "scanning transaction history"! Log file please! I'm not sure what would be causing that, besides the dreaded corrupt blockchain database in Bitcoin-Qt. I haven't heard of that happening a while... i think the core devs must've cleaned that up pretty well. If you don't mind spending the time and bandwidth, maybe you could try it for me... just let bitcoind redownload the blockchain. THough you did say it was a fresh install, so I doubt it... Either way, please send a logfile to support@bitcoinarmory.com! bitcoind getinfo returns fully synced blockchain. log on its way. |
|
|
|
why do i seem to be stuck at 98% "scanning transaction history" after a fresh install of 0.88.1 onto Ubuntu 13.10 with bitcoind in the background?
16GB RAM, 64 bit, 750 GB SSD.
i tried closing Armory, starting bitcoind -daemon, then reopening Armory, but still get stuck on 98% "scanning transaction history"! |
|
|
|
|
Show Posts
