 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
I had a shutdown issue for over a month with my Cube. I thought it was total carbage. I wrote someplace back around page 29 a couple months ago and never got a response.
In the interim I discovered a couple things and got my cube to run stably for several weeks at a time:
1) I pulled out the stock fan that came with the unit. I replaced it with a smaller 90mm higher RPM fan at about 2700RPM. The smaller fan works fine for cooling and I used some scotch tape to hold it in place. The fans that shipped with the Cubes were garbage. Mine started failing after a few days. The fan connects right to the voltage sensor, so this causes a lot of trouble. The high RPM fan solves this issue. Half the reason why it shuts down so often is that the sensor senses that the stock fan is too slow.
2) The Cube doesn't like ANY thing else broadcasting to it on the network. It can handle your pool software: BFGminer, or XPTproxy, but that's about it. If you put your unit on a network SWITCH - not a hub, but a switch, it will cut off any network contention that shuts the unit off.
After these two changes, my unit runs for at least a week at a time without issue.
Yep, I've got four on switches without any problem. I have two that don't like to overclock. One shuts all chips off, the other just flips the clock, but these two both run fine in Low clock at ~32ghs. The other two run for weeks at a time overclocked at 38+ghs. Mine has never overclocked unless I removed at least 2 cards. |
|
|
|
Is there a way to setup BFGMiner instead of using the proxy? I've been trying but have had no success. I've got BFG 3.10/x64. Have it working fine with CPU, GPU and an Antminer U1 but can't get it to work with my cube.
Don't use the 64bit version. go to the 32. I did try that one as well and it failed indicating it could not connect to the proxy port xxxx and no devices were found. Tried to manually add them using all and auto and all it found was my graphics card. Update. I think I managed to get it working. Not sure why they weren't communicating before but ..... Shut everything down and made sure the cube was up and running. No other devices/miners were running and started 32bit version of BFG with the http-port option and it just sat there for a while and declared the proxy as dead  Verified my pools and ports and restarted BFG from within rather than quitting and restarting and it started requesting work and the cube is showing that it's processing. Yeah!!! Thanks for the help guys! WAIT!!! I wanna know.....how did you do this? I'd like to switch from Slushs proxy to BFGMiner so I can run a different pool. I can't seem to get it to see the Cube. Not sure if it needs a driver or what. Explain plz. I had the same issue with my unit early on, and help was sparse. BFGMiner 32 bit version. I'll copy you my conf: {
"pools" : [
{
"url" : "stratum+tcp://us-west.multipool.us:8888",
"user" : "XXXX.xxx",
"pass" : "x",
"pool-priority" : "0"
},
{
"url" : "stratum+tcp://stratum.coinex.pw:9044",
"user" : "xxxxx",
"pass" : "x",
"pool-priority" : "0"
},
{
"url" : "stratum+tcp://us-east.multipool.us:8888",
"user" : "xxxx.xxx",
"pass" : "x",
"pool-priority" : "0"
}
]
,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"expiry-lp" : "3600",
"gpu-dyninterval" : "7",
"log" : "5",
"failover-only" : true,
"no-pool-disable" : true,
"no-show-processors" : true,
"no-show-procs" : true,
"no-unicode" : true,
"queue" : "1",
"scan-time" : "60",
"skip-security-checks" : "0",
"submit-stale" : false,
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "C:\\Program Files\\BFGMiner\\/share/bfgminer",
"http-port" : 8332
}
|
|
|
|
Is there a way to setup BFGMiner instead of using the proxy? I've been trying but have had no success. I've got BFG 3.10/x64. Have it working fine with CPU, GPU and an Antminer U1 but can't get it to work with my cube.
Don't use the 64bit version. go to the 32. |
|
|
|
|
I had a shutdown issue for over a month with my Cube. I thought it was total carbage. I wrote someplace back around page 29 a couple months ago and never got a response.
In the interim I discovered a couple things and got my cube to run stably for several weeks at a time:
1) I pulled out the stock fan that came with the unit. I replaced it with a smaller 90mm higher RPM fan at about 2700RPM. The smaller fan works fine for cooling and I used some scotch tape to hold it in place. The fans that shipped with the Cubes were garbage. Mine started failing after a few days. The fan connects right to the voltage sensor, so this causes a lot of trouble. The high RPM fan solves this issue. Half the reason why it shuts down so often is that the sensor senses that the stock fan is too slow.
2) The Cube doesn't like ANY thing else broadcasting to it on the network. It can handle your pool software: BFGminer, or XPTproxy, but that's about it. If you put your unit on a network SWITCH - not a hub, but a switch, it will cut off any network contention that shuts the unit off.
After these two changes, my unit runs for at least a week at a time without issue.
|
|
|
|
|
tried your pool, but for some reason I'm getting lots of reject errors.
Is this sha, rather than script? I'm I using my wrong rig?
Derp. It's sha-256. Changing rigs. Never mind. Duh.
|
|
|
|
|
Here's my getpeerinfo from the console, only 2 of the above nodes are connected.

[
{
"addr" : "5.249.152.30:9771",
"services" : "00000001",
"lastsend" : 1393354533,
"lastrecv" : 1393354536,
"conntime" : 1393354286,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
},
{
"addr" : "115.28.56.217:9771",
"services" : "00000001",
"lastsend" : 1393354529,
"lastrecv" : 1393354529,
"conntime" : 1393354303,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
},
{
"addr" : "84.200.84.93:9771",
"services" : "00000001",
"lastsend" : 1393354529,
"lastrecv" : 1393354528,
"conntime" : 1393354331,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
},
{
"addr" : "38.64.135.55:9771",
"services" : "00000001",
"lastsend" : 1393354528,
"lastrecv" : 1393354528,
"conntime" : 1393354455,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
}
]
|
|
|
|
The client is not and has never pointed to the Litecoin chain. There was issue a few months ago with the Litecoin alert key, but was corrected last year. This effected many coins not just JKC. The issue had nothing to do with the block chain. The issue now is lack of miners vs. difficulty. I could band-aid a fix in that might or might not work depending if users install it. However it would be a hard fork and could cause more problems then it solves. The next time difficulty goes up and miners drop off, the same situation would occur again. A more permanent fix would involve completely rewriting the difficulty algo. to a different type of algo. In essence changing the coin into something else. Network Hash rate is ~4 MH @ 8.672 difficulty. This means the network is going to crawl along until the next difficulty drop. At block 161280 the difficulty jumped from 2.5 to 8.6. Just before the jump the network was running too fast, after the jump you can see the heavy hasher that was running up the difficulty calculation before the adjustment, dropped out of the network. This leaves the chain in the lurch it is in. Difficulty re-targets every 2040 blocks, so at block 163,320 the difficulty will adjust back down again. You claim the coin is so successful, yet the issue is lack of hash rate. The community abandoned me long ago, then became encouraging when they wanted something. As soon as they got it, crickets again. I continue to develop in the sense of maintaining the software and keeping it running, but the issue here is not the software. It is the lack of mining outside of a heavy hitter or two who jump on the chain when the difficulty is low and jump off when it adjusts back up. If one needs a node, I also run and maintain the block explorer jkc.cryptocoinexplorer.com.. One can use it as a node. I've made this junkcoin.conf file. Is this workable? The dif is the changes to the ports - none set to LTC any longer as noted on the previous page: listen=1
daemon=1
server=1
rpcuser=blah
rpcpassword=blah
rpcport=9772
port=9771
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
addnode=5.249.152.30:9771
addnode=192.241.216.151:9771
addnode=94.254.7.39:9771
addnode=72.213.130.251:9771
addnode=115.28.56.217:9771
addnode=89.178.192.93:9771
addnode=72.78.100.12:9771
addnode=128.199.238.183:9771
addnode=84.250.6.190:9771
addnode=78.221.228.44:9771
addnode=jkc.cryptocoinexplorer.com |
|
|
|
The client is not and has never pointed to the Litecoin chain. There was issue a few months ago with the Litecoin alert key, but was corrected last year. This effected many coins not just JKC. The issue had nothing to do with the block chain. The issue now is lack of miners vs. difficulty. I could band-aid a fix in that might or might not work depending if users install it. However it would be a hard fork and could cause more problems then it solves. The next time difficulty goes up and miners drop off, the same situation would occur again. A more permanent fix would involve completely rewriting the difficulty algo. to a different type of algo. In essence changing the coin into something else. Network Hash rate is ~4 MH @ 8.672 difficulty. This means the network is going to crawl along until the next difficulty drop. At block 161280 the difficulty jumped from 2.5 to 8.6. Just before the jump the network was running too fast, after the jump you can see the heavy hasher that was running up the difficulty calculation before the adjustment, dropped out of the network. This leaves the chain in the lurch it is in. Difficulty re-targets every 2040 blocks, so at block 163,320 the difficulty will adjust back down again. You claim the coin is so successful, yet the issue is lack of hash rate. The community abandoned me long ago, then became encouraging when they wanted something. As soon as they got it, crickets again. I continue to develop in the sense of maintaining the software and keeping it running, but the issue here is not the software. It is the lack of mining outside of a heavy hitter or two who jump on the chain when the difficulty is low and jump off when it adjusts back up. If one needs a node, I also run and maintain the block explorer jkc.cryptocoinexplorer.com.. One can use it as a node. I appreciate your detailed reply, and your frustration over this coin. I didn't realize that there was such a lack of interest when its value is up and up. How big a rig is a "heavy hitter"? Would it be 60 mh/s +? There's no way I could help with that. But I may be able to offer some help for a little while. |
|
|
|
This thing still doesn't work... I left it running all night, and it had reset it self twice before then and again during the night. I get up this AM and it's stuck around 8000 remaining. Close it, it reopens at 700000. Now it's stuck at 356049. This is the 5th time I've done this. 1) Is this wallet still pointing at LiteCoin instead of JKC? 2) Does JKC really only have 1 node after all this time? 3) How many DAYS does it take to synch one wallet? I'm approaching a week (2?) and many attempts. As this coin has grown in popularity, a little better support may be in order? My JKC have gone up over 500% in value and I can't even get to them in several weeks. (-JKC - LTC clone. 0 starting diff with superblocks, random superblocks.) https://bitcointalk.org/index.php?topic=134179.0Edit: closed and reopned a couple times, goes to 8682, then back to 300k, then back to 8682... etc. Edit: closed and reopened a again. Stuck at 92800k or so, then at 8685, then back to 356052, then down to 8000k, then back to 356052. OVER AND OVER AND OVER AND OVER. Here is my getpeerinfo, it maybe helpful: [ { "addr" : "192.241.216.151:11345", "services" : "00000001", "lastsend" : 1392933634, "lastrecv" : 1392933635, "conntime" : 1392401723, "version" : 60002, "subver" : "/DGC:1.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 687959, "banscore" : 0 }, { "addr" : "94.254.7.39:9336", "services" : "00000003", "lastsend" : 1392933674, "lastrecv" : 1392933667, "conntime" : 1392872708, "version" : 60003, "subver" : "/Satoshi:0.8.5/", "inbound" : false, "releasetime" : 0, "startingheight" : 169878, "banscore" : 0 }, { "addr" : "89.178.192.93:24242", "services" : "00000001", "lastsend" : 1392933675, "lastrecv" : 1392933657, "conntime" : 1392889636, "version" : 60001, "subver" : "/42:0.6.4.6/", "inbound" : false, "releasetime" : 0, "startingheight" : 26826, "banscore" : 0 }, { "addr" : "72.78.100.12:4588", "services" : "00000001", "lastsend" : 1392933635, "lastrecv" : 1392933602, "conntime" : 1392895512, "version" : 60080, "subver" : "/Satoshi:1.1.0/", "inbound" : false, "releasetime" : 0, "startingheight" : 80260, "banscore" : 0 }, { "addr" : "128.199.238.183:24242", "services" : "00000001", "lastsend" : 1392933634, "lastrecv" : 1392933638, "conntime" : 1392924222, "version" : 60001, "subver" : "/42:0.6.4.6/", "inbound" : false, "releasetime" : 0, "startingheight" : 26952, "banscore" : 0 }, { "addr" : "84.250.6.190:24242", "services" : "00000001", "lastsend" : 1392933660, "lastrecv" : 1392933606, "conntime" : 1392924507, "version" : 60001, "subver" : "/42:0.6.4.6/", "inbound" : false, "releasetime" : 0, "startingheight" : 26953, "banscore" : 0 }, { "addr" : "78.221.228.44:9336", "services" : "00000003", "lastsend" : 1392933635, "lastrecv" : 1392933674, "conntime" : 1392931264, "version" : 60003, "subver" : "/Satoshi:0.8.5/", "inbound" : false, "releasetime" : 0, "startingheight" : 89423, "banscore" : 0 }, { "addr" : "72.213.130.251:9336", "services" : "00000000", "lastsend" : 1392933707, "lastrecv" : 0, "conntime" : 1392933707, "version" : 0, "subver" : "", "inbound" : false, "releasetime" : 0, "startingheight" : -1, "banscore" : 0 } ] Hi, thanks. I've created this in the conf file based on your IPs. I don't know how else to do it: listen=1
daemon=1
server=1
rpcuser=blah
rpcpassword=blah
rpcport=9772
port=9771
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
addnode=5.249.152.30:9771
addnode=192.241.216.151:11345
addnode=94.254.7.39:9336
addnode=89.178.192.93:24242
addnode=72.78.100.12:4588
addnode=128.199.238.183:24242
addnode=84.250.6.190:24242
addnode=78.221.228.44:9336
addnode=72.213.130.251:9336
addnode=115.28.56.217:9771 it connects, seems to synch up, but my coins withdrawn from Cryptsy 2 weeks ago aren't there. I just deleted the roaming files again (not the wallet) to allow it to resynch fully with these addresses. So why is the wallet pointing to the wrong block chain? Does the dev. not know how to do the proper updates? Why let a coin die that's starting to do well? |
|
|
|
so CENT is not dead, it's just weired cryptsy? it's weired they didn't tweet about it, I found out by accident. Is the community still alive, is there development going on here? I posted something on the main forum like a month ago, but got like 3 views and not a single reply..
Something tells me that Cryptsy owns most of it and made a load of money by selling it on LTC and then dropping it to XPM so no one could make their money back. They drive the market down, make it impossible for you to withdraw and sell on other sites, and then they close the trade. Others have suggested that Cryptsy hoarded nearly all of the CENT to make a market below XPM that doesn't seem to have manifested, or maybe they decided to crash it the whole way and cash out. I've seen some pretty weird stuff on Cryptsy myself, and their delays with withdrawals, not being able to sell at peak moments etc - sales not going through at the right time, as if you're not in the "in club" or something. Much I'm speculating here, but I've not seen this behavior on other trade sites. CoinEx, for instance, you'll normally receive your withdrawals in 2 seconds or less. |
|
|
|
|
Ugh, so after weeks of trying, I finally got HALF my CENT from Cryptsy - the other 15 mil is missing in the ether, and cryptsy has done nothing after weeks of complaining to them. By the time I got my other 2nd half from Cryptsy, BTER had shut down deposits for it. So now I can't move them to BTER to at least make my money back.
Such a fucking scam. I don't know what's worse - Cryptsy, or this coin.
|
|
|
|
This thing still doesn't work... I left it running all night, and it had reset it self twice before then and again during the night. I get up this AM and it's stuck around 8000 remaining. Close it, it reopens at 700000. Now it's stuck at 356049. This is the 5th time I've done this. 1) Is this wallet still pointing at LiteCoin instead of JKC? 2) Does JKC really only have 1 node after all this time? 3) How many DAYS does it take to synch one wallet? I'm approaching a week (2?) and many attempts. As this coin has grown in popularity, a little better support may be in order? My JKC have gone up over 500% in value and I can't even get to them in several weeks. (-JKC - LTC clone. 0 starting diff with superblocks, random superblocks.) https://bitcointalk.org/index.php?topic=134179.0Edit: closed and reopned a couple times, goes to 8682, then back to 300k, then back to 8682... etc. Edit: closed and reopened a again. Stuck at 92800k or so, then at 8685, then back to 356052, then down to 8000k, then back to 356052. OVER AND OVER AND OVER AND OVER. |
|
|
|
I still can't get the wallet to synch. Think I downloaded the latest, but it's hard to say with these threads. I've included the addnodes - it connects - gets near the end, doesn't synch fully. Been waiting for two weeks to see if a transaction went though.
I've also deleted the files from roaming and redownloaded everything - still the same.
The website is crud, not even updated. The info old there. Is the most up to date wallet from December?
Hi, as I understand, the December release is the current file. What addnodes are you using? Try 5.249.152.30 as this one I just checked is currently up to date at latest block 161530. If it doesn't completely synchronize, I usually close it, and wait a minute and open it again - with other wallets, this might need to be done a few times. Hi, thank you. I've done that a number of times. I've just deleted all the files again except wallet and the junkcoin.conf. I JUST added the last node, so we'll see. Here's what's in my conf: addnode=24.210.42.161
addnode=86.40.95.128
addnode=46.65.55.189
addnode=123.16.98.117
addnode=113.167.117.173
addnode=88.182.13.77
addnode=113.162.171.83
addnode=107.3.186.55
addnode=62.163.9.155
addnode=138.130.128.133
addnode=188.81.21.200
addnode=5.249.152.30:9771 |
|
|
|
|
I still can't get the wallet to synch. Think I downloaded the latest, but it's hard to say with these threads. I've included the addnodes - it connects - gets near the end, doesn't synch fully. Been waiting for two weeks to see if a transaction went though.
I've also deleted the files from roaming and redownloaded everything - still the same.
The website is crud, not even updated. The info old there. Is the most up to date wallet from December?
|
|
|
|
|
I started having these issues in windows when I tried to change a simple setting. Everything went haywire and cost me 36 hours. I switched to SMOS BAMT and all seems to be running just fine, but only with 5 cards.
I've not tried the 6th yet.
otherwise the board seems fine. It may be a driver issue and not the board. Others are reporting similar problems on different boards.
|
|
|
|
I've been told that Linux BAMT works better than windows with the R9 290 graphics card.
Maybe that is something to give it a try.
Got this up and running in 5 minutes - all 5 cards working, no issues. .. it is BY FAR easier and better equiped for 290 cards. I had downloaded it two days ago, but was reluctant for having to learn one more Linux system.. .but there was nothing to learn. edit the config, start it... it even finds and installs your cards for you. |
|
|
|
|
I'm getting the same here. Running Windows 7 64 Ult., I went from 1 to 2 to 3 cards, then a forth - no problem. Added #5 and all hell breaks lose. Down for a day and a half, the CGMiner sees the cards as something else, the standard settings that I've used for my R9s suddenly stopped working properly. I reinstalled Windows twice / three times since this is a dedicated mining machine - there's NOTHING else on it, but the drivers, CGminer and some bat files - and still it doesn't want to work - even back down to one card.
It's the AS Rock H81 BTC Pro mining board - 2 R9 290x's - red vacuum cleaners, and 3 tri-x R9 290x silent dream cards - all Saphire. 8GBs of ram, low end Pentium Dual core - perfect for the job. Flew like a dream for a week until I added that 5th card, now no matter of reinstall or anything else is bringing it back. Pentium barely gets to 2-4%. RAM is hardly used. I've swapped the ram already - no change.
Oh, same here also on the BSOD hitting Q with the R9 290x's - works fine on all other cards on other systems - i.e., my 7970s have no problems.
What the hell would make a bat file work one day and not the next? Why 4 cards work and not one, or 5 - on a board that's made just for this job?
|
|
|
|
Hi everyone, I just want to warn you all that Bitcoinrigs.org is a rip off company. I'll start off by saying that after threatening and complaining to this guy, I did receive my unit, almost two weeks late. 1) He created bogus tracking numbers to pretend that he'd shipped the unit. He didn't ship the unit for nearly two weeks later (after numerous threats and complaints) and then sent updated, or real tracking numbers at that time. 2) The unit I received began to fail immediately and the owner of the company has refused to respond. 3) These units are guaranteed at 32Gh/s, and mine won't even run with all 6 cards in it, and additionally it's never once overclocked with all 6 cards. My machine only runs with 5 cards, and will only overclock with 4 cards. 4) The fan went out after 3 days. 5) The guy linked me to the wrong power supply that wasn't near strong enough to power the unit, waisting several additional days - I bought the PSU 2 weeks before the unit got here. 6) I've used no less than 6 PSU's, from the Corsair TX850, to Fractal Design 1000w Platinum, to Thermaltake 850 Gold, to Corsair CX 650, to Rosewill 650 gold, etc. All of them have the same results. 7) All the reviews on his site are positive - that's because he approves all comments and only approves positive ones. There are no comments about how he's defrauded people, nor the 1 star reviews. Another customer recently told me that he ripped them off too, and they had to go through bitpay to get their coins back - nearly $4k worth. 8.) It's a new company, his business address is masked on WhoIS. There's no phone number. The address on the box (once it came - weeks late) is a UPS store: 3434 Edwards Mill Rd., STE 112-138 Raleigh, NC 27612 - https://maps.google.com/maps?oe=utf-8&client=firefox-a&q=3434+Edwards+Mill+Rd.,+STE+112-138+Raleigh,+NC+27612&ie=UTF-8&hq=&hnear=0x89acf687e1a68c27:0x49623e0b0fcec5f7,3434+Edwards+Mill+Rd+%23112,+Raleigh,+NC+27612&gl=us&ei=qujWUu-YJdLzoATK-4HICQ&ved=0CCoQ8gEwAAThe owner of the company is a liar, a poor businessman, a rip off and a scammer. His business location is a UPS store. BE WARNED to NEVER DO BUSINESS WITH THIS INDIVIDUAL! |
|
|
|
|
The only thing I note is that they mention REV 0, and REV 2... was there also a REV 1 that didn't work well?
|
|
|
|
http://hashfast.com/hashfast-customer-update/ - found on their website from Dec. 27: 3PM PST (GMT-8), DECEMBER 27TH, 2013 Dear Customers, Our apologies for not communicating more often these past days. We have been going all-out on production in order to ship Batch 1 units by December 31.We have enough GN chips in hand for all Batch 1 orders. We also have enough hardware (boxes, cooling systems, power supplies, etc.) on hand for all Batch 1 orders. We are in the final stages of production. Our initial modules (Rev 0) had reliability issues due to the PCB layout (Printed Circuit Boards). We received Rev 2 PCBs this morning and they are currently being assembled.We expect these Rev 2 PCBs to work well, and to begin bulk production and be on track to ship Batch 1 orders December 31.The remaining steps (assembling the modules into the Sierra or Baby Jet chassis, packaging and shipping) are quick and generally very predictable processes.
Please know we are doing everything possible to get you your orders as soon as we can.We will update you with our progress as it happens. Stay tuned to Twitter and our HashFast Blog for the most up to date news. Many Thanks & Happy Holidays, The HashFast Team
|
|
|
|
|
