Thanks Doc!  You're the greatest! After rebooting my computer and restarting the client, it did pick up the Antminer. Only problem now is that every 8-10 hours, I check and find everything stopped and the only error message is "Device already detected on ttyUSB0 - 7". Any suggestions? I plan on gradually replacing my Block erupters with Antiners. Is that with the regular version or the beta? Some things have changed in the beta that could help. It should be out as a regular release soon though. |
|
|
|
Need help with Antminer U1. I am running Xubuntu 12.04 with block erupters now, but I am switching to Antminers. I need help installing the driver as I want to use the Bitminter client. I need help with the command line commands. I have posted this question elsewhere on this forum and on the Ubuntu forums and have not gotten any replies. I have googled driver installation and all I find is how to install BFGminer, not the driver.
Thanks
You're sure it's not already there? Try the lsusb command after plugging the devices in, to see if they are recognized. You can laso have a look at /dev/ttyUSB* to see if the devices show up when you plug them in. |
|
|
|
|
Maintenance March 14, 18:00-22:00 UTC. Up to 5 mins mining downtime.
|
|
|
|
I have set up my namecoin wallet on mmc-wallet.com and I have pointed Bitminter there. They have loyally been sending the coins off to my wallet, but most of them are not showing up (we are only talking a little over 1 at the present time...oooohhhh...$3.50!!), but I want to understand how I can get this resolved.
Messages to the wallet web site have gone un-answered - you get what you pay for there I guess (free).
I'd recommend not using online wallets. You can download an NMC wallet from namecoin.info. Or you could send the coins directly to an exchange if you just want to sell them for bitcoins. I would immediately stop sending coins to nmc-wallet.com (I assume you meant that and not mmc-wallet.com). I'd also recommend moving whatever coins you are able from their site. If they are just taking your coins and not answering, using their site is a bad idea. Also they appear to not even use SSL...? Apparently it's a suspected scam site: https://bitcointalk.org/index.php?topic=497899.0http://forum.namecoin.info/viewtopic.php?f=2&t=1480There are a lot of scammers out there wanting to steal your coins, so be very careful where you send them. I hope you didn't lose much. |
|
|
|
|
2FA makes it a little harder for a hacker to get into just your account. It does nothing to prevent someone from hacking the entire pool.
|
|
|
|
|
Ok, have a look at the block at height 290021. blockchain.info says Bitminter mined it. But at the Eclipse pool they are saying they mined it. And they paid their miners for finding it.
So there are now two possibilities that can explain this...
Either
A) Bitminter is stealing and Eclipse is paying their members for blocks they didn't find
or
B) Data from blockchain.info is.. well.. useless.
Which one could it be? Hmmm.
I advise everyone who wants reliable information to stop using blockchain.info.
|
|
|
|
It seems like Bitminter is forgetting to list its found blocks. Where are the rewards for the 6 blocks from 2014-03-11  ? Are we being ripped off ? blockchain.info is lying, not Bitminter. I asked them to fix this, but they won't even reply. Please use this website instead: http://blockorigin.pfoe.be/Although you can't with 100% certainty attribute a block to a specific pool, at least this site is actually trying to do it right. |
|
|
|
10 blocks is very little. It will happen once in a while that there are a few bad luck blocks grouped together, just like it will happen with lucky blocks. Payouts over the last 500 shifts: https://bitminter.com/stats/rewardsWe are a small pool now and considering that fact the luck has been remarkably average. Sure we had a few lucky and a few unlucky rounds. But all in all it's very close to average. |
|
|
|
Is the problem with bitfury devices only sending in some of their proofs of work fixed? Was there a firmware update or something like that?
Or is it still necessary to set a high difficulty or other tricks?
Yes, I noticed 25GH higher work recently than the past few days. It was something the pool did. I'm back at 700GH. I think if you are affected by the bitfury bug then your hashrate on the website drops to almost nothing because the bitfury only sends in a small fraction of its work. I'm not that familiar with it though - I don't have any bitfury cards. Just noticed bitminter go down, but it's back up again, that's why I'm here.  My client has been connected 5 days without being disconnected at all. Maybe that was a problem somewhere out on the interwebs. |
|
|
|
|
Is the problem with bitfury devices only sending in some of their proofs of work fixed? Was there a firmware update or something like that?
Or is it still necessary to set a high difficulty or other tricks?
|
|
|
|
Great pool, I had fun jumping through the history of this thread. Should have read it before I bought a used Jalapeno, I would have seen the posts back in May 2013 explaining how with the difficulty increases and increases in overall hashing, 5GH would only earn good BTC rates for a while. Oh well, at least my miner contributes to the Bitcoin network in general  Did you seriously just make a non relevant comment to a non relevant 3 year old thread? You're a newbie, I get it, you want to get your activity up. But at least post your useless comments on active threads, if you're gonna spam at all. This is the Bitminter newbie thread - it's an active one (look at the posts). |
|
|
|
I actually really like this pool, I came to this pool from slush's pool, I like the support and the updates from the good Dr.
My earlier question still stands though, I am wondering if I should set up a mining proxy for my incoming blade, or if I should just connect to the getwork protocol....
what are the pros and cons of both, since I know getwork is the system, and stratum is the new hotness (relatively).
Getwork: easier to set up but the blade/cube runs slowly. Stratum proxy: more to set up, but the blade/cube runs at full speed. How to set up ASICMiner cubes and blades: https://bitcointalk.org/index.php?topic=27062.msg3046129#msg3046129 |
|
|
|
|
The income from a block is newly minted coins plus transaction fees.
The two are handled as one total and distributed to miners together. New coins nad transaction fees are not separated in any way.
|
|
|
|
Is there any way to overclock the ASIC block eruptors? Running at .336 mh/s is going to become useless, even with their low power consumption soon so I'd like to get everything out of them that I can while I can.
I don't know of any overclocking mechanism for those, sorry. |
|
|
|
BitMinter client v1.5.0beta2 is ready for testing. New: - Overclock support (click tune & tweak button) and identify button (click to flash LED) for Antminer U1
- Rewritten Red/Blue Fury support - should work much better now
- Bugfix: Chili ASIC would fail on first try and you'd need to start the device twice
- Bugfix: Fixed a bug where scanning for devices could stop working until you restarted the client
Please check it out:  Custom overclock support planned for next beta. For now there is a pre-defined list to choose from. |
|
|
|
I seem to be having trouble with the bitminter (1.4.3) communicating with my account on bitminter.com. I had someone else give it a try with a worker of mine to see if it works on their end and sure enough I can see their activity show up in my account. On my end the rate is ~120-150 gh/s. I am just learning this so the program is utilizing my GPU (GeForce GT 650M), and I'm glad I chose to take it slow because obviously I'm missing something. When I start bitminter client I enter my username and the number '2' for my worker and on my bitminter account page I have enabled to display worker '2'. Worker '1' is being tested by the other person and continues to show the correct hash rate and activity.
This is a bug in Apple OpenCL. You need to reboot your Mac and it will start working properly again. You will then see a sane speed for the slow GeForce, not 120-150 GH/s. You will also see it finding proofs of work, rather than never finding any. For some reason Apple OpenCL sometimes breaks and after that it "finishes" all work instantly, without ever getting any results. No not the entire app. I can still click the menus, and start and stop the "engine". What I mean by "freeze up" is after a while the miners will stop mining, the gauge will show whatever hash rate I was hashing at the time of the freeze but all stats will stop changing, so all of the numbers to the right of the gauge will stay the same indefinitely, and the temperatures will stop changing as well. I can audibly hear, if I'm in the room, as the fans in these rather noisy miners will drop from full speed to a way rpm (which they do when they're on and not mining, like if my computer is off but the miners are on). I can kind of gauge how long they mined before freezing by looking at my accepted packets and it varies, usually from less than an hour to half a day. Yesterday, on the Beta, I was able to get a whole day, night and it still looks good so far today (though I haven't done anything differently).
This seems to be because of the ASIC driver crashing. Some users reported reinstalling the driver and that fixing the issue. I don't know if its related or not but sometimes (most of the time) I have to start and close the app a couple times before the app will A- Recognize all of my miners and B - Start mining when I click the go button. Often I hit go and a temperature will show (at 32 degrees and never move) and no mining will take place. At which point, I'll close the app and start it up again. If it doesn't start working after a few tries I'll reboot both the miners and the computer but that doesn't seem to be a factor (blowing in my Nintendo cartridges)
Problems discovering the ASICs is usually because they don't get enough power. Laptop USB, weak USB hub, weak power supply. |
|
|
|
I just maximised my bitminter client and nothing is showing in it except a picture of my windows desktop .
The client quickly becomes unresponsive and I have to close with task manager
A couple users reported running on block erupters locked up the whole client, then they reinstalled the drivers and the problem went away. Could you try that? http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx |
|
|
|
Doc,
Thanks for the response. I tried the Beta and I'm having the same issue. It takes a couple start up, try, close, start up again attempts to get all three mining and then they only mine for a while before locking up, at which point I have to start the process over. This happened a few weeks back but it seems like it's happening with an increased frequency and that they are locking up faster.
The fix is for the entire app slowing down and eventually locking up so you can't even access menus or click anywhere. Is that the problem you had? Or is it that the devices stop mining, and you have to start them up again? Do you get any error messages? |
|
|
|
Ran until just after 6 AM and crashed: 2014.02.22 [06:51] IOReactor error java.lang.SecurityException: Trusted-Only loader attempted to load sandboxed resource from https://bitminter.com/beta/httpcore-nio-4.2.4.jar at com.sun.deploy.security.CPCallbackHandler$ParentCallback.check(Unknown Source) at com.sun.deploy.security.CPCallbackHandler$ParentCallback.access$1700(Unknown Source) at com.sun.deploy.security.CPCallbackHandler$ChildElement.checkResource(Unknown Source) at com.sun.deploy.security.DeployURLClassPath$JarLoader.checkResource(Unknown Source) at com.sun.deploy.security.DeployURLClassPath$JarLoader.getResource(Unknown Source) at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source) at java.net.URLClassLoader$1.run(URLClassLoader.java:358) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.addExceptionEvent(AbstractMultiworkerIOReactor.java:265) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.addExceptionEvent(AbstractMultiworkerIOReactor.java:274) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:396) at com.bitminter.gridnode.net.GridClientThread.run(SourceFile:309)
Hmm. This securityexception looks like a bug in older java 6 and java 7 releases that I have a workaround for. Basically a "should not happen" case. Which java version is this with? Can you try upgrading to the latest Java from java.com and see if this problem goes away? I wanna ask if my desktop is applicable for this one.
Is it working or something wrong?
That old nvidia GPU is slower than most CPUs. And even fast GPUs aren't profitable anymore for bitcoin mining. Try ASIC hardware: https://en.bitcoin.it/wiki/Mining_hardware_comparison#ASIChow's going work with overclock version? Almost done, just getting sidetracked by other things. Hi, I installed the driver and I also replaced them with zadig, but on my Windows 7 pc the antminers u1 are not recognized. I already tried to replace the driver again and restart my pc but nothing happend. Hope you can help me Use Zadig only for cgminer. For all other mining clients use normal drivers. For Antminer U1 use http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspxIs the Beta worth switching to now? My rig has been getting bumped off more and more often and its starting to annoy me. When it goes down I have to start the client, hope it finds all my asics, assuming it does, hit start, hope they all start and if not...... start all over again. Every time I restart my computer or it randomly stops mining it takes me a good 15-20 minutes of open, close, start, stop, restart, disconnect, reconnect, etc.. to get my the miners all going again. It wasn't like this 2 or 3 weeks ago but the frequency seems to be increasing.
If it helps to know, I'm running 3 Butterfly Labs 30 GH/s little singles. When they are running, they run great but I think it might be the client (or the pool) that I've having issues with. I love the simplicity of the interface and the DR. seems to be really proactive with the pool but I hate the constant stops and the issue mentioned above.
Yes, the beta should not have this issue. It would be very useful if you can try the beta and confirm that the issue goes away. The more BFL devices you are mining with, the faster the issue will occur. |
|
|
|
DR.
I think I'm having the same issue that was mentioned above with my BFL 30 gh/s little singles. Did I understand correctly when you said that this is an issue with the current version of the client, and that it should be solved with the version that is currently in Beta?
Since the Beta version is up and I'm trying to put these miners to work is there any reason why I wouldn't use the Beta version now? What are the concerns, outside of loosing mining time, that exist with the new version?
Yes, if you have the problem with slowdown and/or lockup when mining on BFL ASICs, then the beta should fix this issue for you. I believe the beta should be fine. But beta is always less tested than regular versions. So there is a higher risk that something doesn't work, than when going with the regular one. Of course if noone tests the beta versions, then the regular releases won't be any better than the beta releases.  |
|
|
|
|
Show Posts
