If R1 and R2 Baby Jets don't arrive by Dec. 31, I'm immediately filing for a refund at 10PM Hawaii Standard Time on Dec. 31 (which corresponds to midnight on the West Coast where HF is located) so that we're at the front of any refund queue.
If they do manage to get this shipped before year's end, let's hope the MPP chips aren't far behind because those MPP chips were *originally* scheduled for the beginning of February (assuming Batch 1 was in our hands at the beginning of November).
No miner in hand, no trucking number, no emails. Jan 1st 2014 so lets hope they send a refund and don't skip town. |
|
|
|
Ok, I finally got my whole batch of 14 working and they are running at ~1.7GH each.  Using cgminer 3.8.5 (ant version) with the following command line -> C:\my_file_location\cgminer.exe -o stratum.bitcoin.cz:3333 -u my.worker -p my_password --bmsc-options 115200:20 --bmsc-freq 0881 The process of getting them all online is a PITA. This is what worked for me: 1) Start cgminer with one stick already in a hub, the zadig winusb already installed for that port. Cgminer recognizes the stick and loads AMU0. 2) Mount next stick in hub 3) Choose next device (com port) in zadig and install winusb for that device  4) Wait for driver to finish install 5) Remove the new device, wait 2 seconds and re-mount, cgminer recognizes the stick and loads next AMU Rinse and repeat. A tedious process for sure, but that's what worked for me - if anyone has a better way to get these mounted please let me know  Q: Does anyone know if one can run cgminer in a separate instance on a pi running minepeon? Cheers good can you check your mining site hashrate against your cgminer hashrate for a few times over the next day. I seem to get a big mis-match with a lot of sticks and correct numbers with 1 hub and 8 sticks. also what hubs do you use to get that many sticks? I am running bfg miner with ice furies and the custom cg miner with the ant miners. Maybe I should only run the custom cg miner. BTW your method is how I got 15 sticks on two hubs mining. but 21gh on cgmining and 11-13 gh on the mining sites. |
|
|
|
You had a 40amp fuse on a 30a circuit. Why it did not blow, and burnt wires/holder.
You would need 50a P/S to run that 40a fuse with room to blow on sudden surge.
At 40a fuse with a 30-35a P/S you get burn rather than blow...
48 asics @.6A would be spec with some room on top, some of the newer asics pull more much more for some, way out of USB spec. That is what that hub is for, setup right it will work properly.
So your P/S says 35a 5v get real give it some breathing room load it no higher than 30a 5v.
Safe for up to 30 35 miners before you are pushing things. I would use 25a fuse till it blows to see where your load is really at, could be a bad miner or ?
this is correct. use a 25 amp or 30 amp fuse with 40 sticks tops = no worries |
|
|
|
I prefer Mindy to the zombies. THAT is funny. Well back to the sticks. When running six of them on 1 hub it gets me an avg hash at 8.3 on the cg miner screen that is around 1.4gh a stick and bitminter is reporting them at about 6.9 - 9.1 which comes to 8.0 . I can live with small unreporting like 8 instead of 8.3 but at the larger stick counts of 8 or more the numbers are much worse. It would be nice if someone else gets 8-10 on 1 hub running windows 7. and gets the big drop in hash rate. I am going to run the 6 for the whole day and check back on and off. |
|
|
|
Please move all talk not related to asic or fpga hardware to the alternate currency sub forum. Cgminer doesn't support gpu mining after 3.7.2
Thanks
Thank you and I mine LTC using an older cgminer version. But I want to talk about the new ant miner sticks. there is a custom 3.8.5 version on github designed to run the new sticks. I am having a funny problem I can get up to 13 sticks to run using this custom version but on 2 different mining sites I get very bad underreporting of hashrate when I use more then 6 sticks. when I had the 13 sticks up and running at stock speeds of around 1.5-1.6 for a total of 21gh on the cgminer screen after 4 or 5 hours running at cex.io my avg hash rate was around 11-12gh. The same problem happened running on bit minter. The when I reduced sticks to 6 and used 1 hub vs 2 hubs my rates are closer to correct. 6 sticks avg 8.3 and report as 8.2. So it seems like once I get to 8 or more sticks on either hub even though the cgminer reads okay The mining sites under report the hashing. At 10 sticks at an avg of 14.7gh which is about 1.47 a stick. at no time does either mining site read close to the 14.7 more like 10.1. I am running 5 nano -ice fury sticks on a different hub the read about 12 and 12 which is accurate. I am also mining 11 of them on a different pc and getting good numbers. Now in my case i have more then 50 ant miner sticks and can only run 6 per pc with good rates. I know the cg build is custom but I thought I would point this out. |
|
|
|
http://imageshack.us/photo/my-images/36/vp5a.JPG/okay I have been playing around with them and got 15 to work on 1 pc but 2 went zombie. I have found some type of hash rate bug.. lets say you are running 6 at 1.6 or 9.6 gh with windows 7 and the custom cg 3.8.5 build both cex.io and bitminter seem to under report the rate by a lot. the 6.9 gh on bitminter reading is for 8 sticks this shows a big difference in hash rate for the antminers using a custom build and the ice fury using bfgminer 3.9 I know that bitminter reporting rate varies but I had the same under reporting with cex.io . If someone can get more then 6 on a hub to work please see if you have this error in rate reporting
|
|
|
|
Will these work with a Raspberry Pi running MinePeon?
I have regular erupters on d-link hubs working on it now, would these just plug in and work? or would I need to download updates or change settings?
Short answer: NO Longer answer: It *MAY* be possible in the future but it is not possible now. Nor is is possible to run a mixture of AntMiner and Erupters in the same machine. you can mix ants with furies. I got 15 ants and 5 furies on 1 machine. they have been running for about 10 hours. |
|
|
|
Yes, well posting ANY DETAILS should put the pressure on KnC to patch up their firmware.
To the person claiming i hacked their rig, i bruteforce 28 miners under 20 minutes, that's about 50 seconds/miner.
What are you complaining about 3 hours non activity for you miner?
Second of all, your http is seperated from the mining activity itself. Even if i bruteforce your miner for 24h, you'll never notice this.
Third of all, POST SOME LOGS THEN!!! That's why logs are made for anyway.
Last but not least, if i DID hacked your machine, it would not even be visible to you.
I am not a 15yr old scriptkiddie trying to hack into every account i see.
I'm a 30+ professional security penetration tester.
But fine to me, next time, i'll post nothing, and get your rigs hacked then.
Underground is already offering me +150 BTC for all details, be glad i keep it to myself instead of thinking i would hack your lame rig with almost no profit according to your blockchain....
Bitcoin is about the community. That's why i keep this public and not underground, so all users can patch up before massive attacks start!
Or are you so naive to think i'm the only one who can discover this...
Okay I call myself jaded and suspicious . Thanks for your efforts to warn us. |
|
|
|
http://bitcoinwisdom.com/bitcoin/difficulty diff is set to jump about 18% from 1180 to 1393 although this site thinks it will jump from 1180 to 1374 that is about 16% http://bitcoincharts.com/why the good news hashfast failed to ship. so we may get a second low jump in 12 days if they are the bs artists many people think that of them. no real jump is due for the next 12 days so 1374 may go to 1580 in 12 days this would be helpful to us here a 16% followed by a 15% is good for this round. was far too busy the last 14 days to track what the btc loss is here. but we lost ground from the last payout due to the power strip issue. we had an average under 3.3 for the 15 days.
|
|
|
|
I download the custom windows build from github for ant miner says it is cg 3.8.5
it would not run said I was missing zlib.dll I dragged the zlib.dll from 3.9 and put it into 3.8.5
this works. I have 1 stick running at over 1.7gh so the next adventure is getting 2 plus sticks to run.
so far a no go on that.
Hey phil, I was having a problem running 6 of these on one win7 machine, I read somewhere about start up new cgminer with 1, then hot plug the others in 1 at a time, that worked, now have all 6 running....hope that helps. iluvpcs, will prob. order some from you later today, anymore in stock?? PS, windows xp can still be as stupid as it was with asicminer usbs yeah I will try that tomorrow. these case a second problem my pc was running 5 ice/nano furies using bfg miner 3.9 and running a ltc miner using guy/cg miner running the custom cg miner for the ant miner is crashing my ltc mining. i think the gear does not want to run 2 versions go cg miner at the same time. since all my pc's are running guiminer- cg miner I will need to set up a mac mini with vm ware to run these sticks. I don't have any parallels but I do have a vm ware fusion with windows 7 pro on a quad core mac mini. I NOW HAVE 4 RUNNING THANKS!!!! and the caps were me shouting for joy. update I now have an entire hub of 10 running at 12gh using about 20 watts. these sticks are really good. now as to what they are worth less then a red fury or a nano fury. but furies are selling at 225 on ebay these are around 100 on ebay. |
|
|
|
|
like I said in usd I lost 192-200 on this. 1 share and a upgrade. so my say is small. but this company has been classic bfl all the way. which means we will lose no matter what we do. So for my small share I rather get this over as soon as possible and move on to other things. but if you have 10 shares and missed out on r5+r6 yeah I hear you.
whatever you guys want to do go for it.
|
|
|
|
|
I download the custom windows build from github for ant miner says it is cg 3.8.5
it would not run said I was missing zlib.dll I dragged the zlib.dll from 3.9 and put it into 3.8.5
this works. I have 1 stick running at over 1.7gh so the next adventure is getting 2 plus sticks to run.
so far a no go on that.
|
|
|
|
|
I have 1 stick working so far it is doing about .6gh I am using cg3.9 with a windows 7 build. I changed the driver with zadig. it now reads amu not icarus. I am running a lot on this pc
1 bfg miner with 5 nano/ice furies scores are 2.5 each with a 53 for over clock
1 gui miner with a hd7970 about 660 kh
1 cgminer 3.9 with 1 ant miner usb 1 .gh i will tweak more but it is hashing.
to iluvpcs I owe you a positive trust I will post it later.
|
|
|
|
|
you are wrong they use less power then a block erupter. under 2 watts vs 2.5-2.7 watts unless you are trying to do over clock
|
|
|
|
what do you expect me to think?
That you should have some evidence beyond pure circumstance before slinging around legal threats? Would you somehow have been better off if OP had been intimidated by legal liabilities into never discovering and posting this information? P.S. If you don't want people "attacking" your gear through a public IP interface, simply configure it to not fulfill requests so promptly and politely. Is it that difficult? first off I am not the op. i did not brute force 28 knc machines he did. now when he did the brute force on the 28 machines he did not tell us he had permission to do it. so stop defending him for doing something that is not legal. did his brute force attack hurt this person? https://bitcointalk.org/index.php?topic=31163.msg4140767#msg4140767maybe I do not know but time wise it matches. was he off line for 3 or 5 hours extra due to the password attack ? do not know. I ask you this. would you want someone coming to the front door of your home and testing your door knob to see if it opens easily ? so to the op did you have permission to attack the 28 machines? yes or no? my apologies if you informed those miners. before you attacked them |
|
|
|
I did think about it. I found it to be bad timing on your part to announce you did this and that the announcement matches very odd behaviour of our miners. What I would like to know is how many miners other then the two mention have this problem which is why I posted this here. You have admitted you viewed 1100 plus miners. if only the two I mention have this problem after being viewed by you then most likely this has nothing to do with your testing.
Holy shit the entitlement here! no not about entitlement. he admits to attacking passwords of 28 miners. and in no place does he say he had permission. the 2 miners I own 9.5 % of had a hashing issue during the time he was brute forcing miners. if I go to a gym locker and try a 3 digit combo lock 20 times a day until it clicks open I am breaking the law in most counties. even if I push it locked again. the op admits to doing this with knc passwords. so dude this is not about entitlement. this is about the op admitting to attacking passwords on valuable gear. I am not the op. I am a part owner of 2 machines that the op may have attacked. so 28/1100 = 2.5% chance but I have 2 machines so about 5% chance he tried on my gear. my gear had a loss unexplained loss of hash power. what do you expect me to think? |
|
|
|
I did think about it. I found it to be bad timing on your part to announce you did this and that the announcement matches very odd behaviour of our miners. What I would like to know is how many miners other then the two mention have this problem which is why I posted this here. You have admitted you viewed 1100 plus miners. if only the two I mention have this problem after being viewed by you then most likely this has nothing to do with your testing.
Well, just wait until the post goes public then! Hurry up and push KnC to patch up. Can you imagine the horror once i post the full details? For your information; the +1100 miners are public available on the net, everybody can scan and see them. I bruteforced 28 logins, but i never actually logged in. Dont you know your KnC has a log? CHECK YOUR LOG BEFORE THROWING MUD!!! So you attacked 28 logins of the 1100 plus miners and you were successful with them. your words not mine . you claim to own 2 machines so at best 26 miners are not yours. did you get permission to try them? so I do I know if one or both of the machines I own shares in were not damaged by you? causing them to lose about .5btc each in hash. look If no one comes to the thread other then me then maybe the 28 machines you hacked were not injured in terms of hash power. but announcing to the world that you hacked /brute forced 28 machines puts you at risk for damages. Any one including me and my 9.5 percent share of 2 Jupiter's (about 100gh) can say your actions caused them harm. Frankly I am posting this here to say that brute forcing some ones password with out permission is not to clever in terms of liability . Can you prove the 28 machines that were brute forced were not damaged? Can you prove you did not attack the machines I own a piece of? Most people do not realize that for civil damage the proof is not as high as it is for criminal damage. So I am not slinging any mud I am pointing out that you may have set yourself up for problems. you should have asked for 30 knc owners to be testers. If you had permission to do a brute force attack on the 28 machines you should have told us that right up front. |
|
|
|
|
I did think about it. I found it to be bad timing on your part to announce you did this and that the announcement matches very odd behaviour of our miners. What I would like to know is how many miners other then the two mention have this problem which is why I posted this here. You have admitted you viewed 1100 plus miners. if only the two I mention have this problem after being viewed by you then most likely this has nothing to do with your testing.
|
|
|
|
Hi all, So, what else to do in my spare time while mining some BTC? Exploiting security holes in my hardware. It turns out that every KnC miner can be hacked within 5-10 minutes, making it possible to control the CGMiner remotely. I've submitted a higly detailed report to KNC, explaining how i did it, and how they can patch it with a new firmware upgrade. To avoid a huge breach, i will not reveal all details, but i give you a short summary [proof of concept]. 1: Scan the internet, using a special tool, for the default KnC Miner header response WWW-Authenticate: Digest realm="KnC Miner configuration", nonce="f76e06a34c00b5fec1da6749d4ed0bfc", qop="auth" EVERY miner uses this header, so in 10 seconds, i found about 1180 responses vulnerable to my attack. 2: Cricial information remains hidden for public, but the http digest can be bypassed with ease. 3: Run basic HTTP bruteforce. Since the digest is bypassed, i can run unlimited bruteforce attempts. Within a timespan of 20 minutes, i managed to bruteforce 28 miners !! (Most of them poor passwords tough) Now comes the fun part...Login using SSH. If the SSH port is not enabled, simply login to the web console and enable it. The source code of tells us exactly what we need. VI (edit) the default factory files, as found in the factory reset code, making a second login inside the factory reset files. The digest file requires you a special hash to create the password. This can be done using special tools, but for safety reasons, i will not go further on this part in public. Alter these files to gain access after factory reset /etc/lighttpd.htdigest.user Now remove all the default credentials in the factory files, making it impossible to login using the default admin:admin for the owner RUN THE FACTORY RESET... And enjoy your personal miner, that just became unusable to the owner, since he can no longer login. Disclaimer: I intend to do no harm. No miner has ever been in my control, or ever will be. I just expose this threat to put pressure on KnC to hurry their firmware upgrade. Do not ask or PM me for information about this hack, it will not be provided !! Only KNC has the entire manual !
Note to all KnC miners out there: Please change your passwords to long, safe password!
If needed, simply hashing your firstname to MD5 will do the trick to scare away hackers.
PLEASE USE A ROUTER INSTEAD OF DIRECT INTERNET ACCESS !!!
Greetings!! EDIT: Email to KnCHello KnC team,
As you might picked up on bitcointalk.org, i managed to successfully scan and exploit KnC Miner configuration software running on all your miners.
Attachted is my HowTo, showing you how i managed to succeed in this hack.
I feel, as a software developer and penetration tester, that you do not take user security in account with your services.
The only thing you care about, is selling hardware. What happens with it, seems to be the least of your concerns.
You should now that the user is always the weakest security, but instead of anticipating on that, you go with that flow.
I did not post exactly how i did it on the forum for security reasons, but however, i urge you to push a new firmware closing up those holes.
Holidays or not, i will expose the detailed howto on bitcointalk.org on January 1st 2014 at 12h00.
Once this exploit go public, you will receive a lot of complaints and behalf of your clients, and loose lots of trust in the general public.
If you have not patched your firmware, this will confirm my statement that you do not carry about user security.
I can only imagine all blogs picking up that posts just before Neptune delivery...
I just created a custom firmware patching all the security flaws, it took me about one hour.
So surely, your developers can do the trick also.
For the sake of the general public, who have put their trust and funds in you, please patch up your firmware!! Quite frankly after read this I think you owe coins to us on this thread: https://bitcointalk.org/index.php?topic=334360.0I believe you screwed up our 2 miners we have a 2-3 day coin less gap https://blockchain.info/address/19NAwha8LGpRFEBwRgjH5ZMB9YyXeqyY9Vhttps://blockchain.info/address/13fGQGmb6Xi576ppJTkeXk34yDDRmvxjm4 (Eleuthria ) this direct appeared on both out payout addresses and we lost coins.. the timing matches to your playing around with out 2 miners along with 1100 other miners. |
|
|
|
Guys/Gals: bobsag3 had to take the miners down for 12-18 hours. It could be as many as 24-28 hours, but should be in the lower range.
I'm sorry, I'm apologizing now on behalf of the team. We were planning for an early Jan. move but plans became accelerated and we're moving to the bigger/better location right now.
We'll have word of some compensation worked out with Miner Hosting LLC once they're back online. On the bright side...we're going to have much more capacity and pro employees that are miners and/or IT experts manning the new facility.
hey read this https://bitcointalk.org/index.php?topic=392166.0 this smells like a theft to me. |
|
|
|
|
Show Posts
