|
I have to agree, the U3 is a piece of crap... I'm sorry I bought them.
|
|
|
|
I'm kinda getting a feeling that the only problems arise when there's more than one U3 plugged in? Has anyone had the same problem with just one U3 running?
This is pretty much what I've encountered. I have 3 miners running for 7 days and 1 hour on three different computers, in that time, one slipped from port 0 to port 1, but it's still hashing fine. http://solo.ckpool.org/users/14LxDWtRRdQAbnJdd4Ew5jwag8Bx9UfNRd |
|
|
|
|
Huge fan of the SCAR, too bad I'm a NY resident and can't get them anymore...
|
|
|
|
|
Sorry then, I'm no help. Good luck.
|
|
|
|
|
Are you talking about the small USB R-Box? I think that mine only runs at 37 whether I run it at 270 or 290... Setting it to 270 has a lot less hardware errors.
I run the R-Box with BFG Miner, never tried CG Miner with it. maybe I'll do that tomorrow.
|
|
|
|
|
Have you tried swapping the compaqs around to different ports in the USB hub to see if you get the same errors on that stick?
|
|
|
|
|
I have a dumb question... Is the queue for the shipped or to ship public ally available? I'm not sure where I fall on the list.
|
|
|
|
|
Is this idea still a possibility once everyone gets their sticks?
|
|
|
|
Were U1 and U2's supposed to change from AMU to CBM in 5.3.0? This is what I was running 5.0.0 on a PC that I use for lottery: bfgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 14LxDWtRRdQAbnJdd4Ew5jwag8Bx9UfNRd -p x -S rockminer:all --set rockminer:clock=270 -S antminer:all --set-device antminer:clock=x0881 --api-listen --api-allow W:10.0.0/24 |
|
|
|
|
I can't wait to try mine once they arrive.
|
|
|
|
|
I have a couple of S5s each powered by their own EVGA 750 Gold units without issues. These units have been hashing since the S5 was released; I think mine are batch 2.
|
|
|
|
would you post your start mining batch file? I have the bitcoin.conf set up, and it seems happy with that part of the process. maybe I should upgrade to 4.9.2. I tried 4.9.1, but it didn't seem to act correctly.
Thanks,
Storm
This is a simple batch file: cgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 14LxDWtRRdQAbnJdd4Ew5jwag8Bx9UfNRd -p x --au3-volt 830 --au3-freq 225 --hotplug 600 --api-listen --api-allow w:10.0.0/24 pause |
|
|
|
I also posted this in the general mining software forum... Anyone have information to share?
Cgminer ( ver 4.9.0 ) never says accepted, it only tells me the block height changes. If I turn on verbose, I get lots of "share above target" notifications and an occasional Hashrate report ( same information that is in the header ). I am hashing at about 50 GH/s with an Antminer U3 so I am sure it needs to be optimized, however, I have seen it peak around 65 when I was mining in a pool.
My question is this: Is this reporting normal? I have tried to find a post about what solo reporting looks like online, but have not been able to find anything. I am okay with it not providing the information, as long as it is mining.
Cgminer is happy with the set-up ( no reported errors ) but not very informative..
Thanks,
Storm
I'm using 4.9.2 and by default it says when shares are accepted. |
|
|
|
|
All I use is EVGA modular power supplies. My Antminers and Zeus Miners hook up through the VGA ports.
|
|
|
|
Wonder how much BTC this guy has to burn  Much more than I do! Lol |
|
|
|
The problem with the U3 is what works for some does not work for others. Heck, even for me what works on one U3 does not work the same if I use another U3 in its place.
Agreed, it blows my mind that I literally mined for around 3 months with no issue at all with a single device and once I added multiple devices to the same PC, they all went Zombie in a few hours. |
|
|
|
I doubt that the "zombie" (not sure where this term came from) issue can be solved programatically. I have tried similar method in the last 3 weeks by stopping BFGMiner, reset usb port, wait 10 minutes and restart BFGMiner via cron job every 7 hours and 50 minutes, but it did not help if Antminer U3 is stuck. The only solution is to power cycle it. I have 2 Antminer U3' and both behave exactly the same. So unless you also programatically do the power cycle using Arduino relay for instance, I don't think your method works.
Were you running 1 or multiple U3's? I can tell you that I had one unit running for months on CGMiner 4.8.0 that was packaged by Bitmain (cgminer-run-windows-20150107), my ZOMBIE issue started when I introduced more U3's on a computer. Any PC that I run with a solo U3 has no issues. |
|
|
|
|
Are you talking about the 30Ghs model? I run mine with a clock of 290, i seems like these units are full of hardware errors. Right now in BGMiner 5.0.0 I have one running for 3 days and it's has 41,750 accepted, 880 rejected and 39,428 hardware errors.
It runs at 34.5Ghs and about 43.0C.
|
|
|
|
|
Show Posts
