wow thats luck! congrats with only 200th
We have become desensitized to hash rates I think, especially within the realm of solo mining. Have you seen what 200TH looks like in a warehouse? It's a large wall of miners! Compared to the multi-PH farms it may "only" be 200TH, but that's still a significant amount of hardware and investment. |
|
|
|
maybe we should do a GROUP hashrent ?
It has been not only discussed here before, but folks have done it. I think the consensus was it was too much work and you need a really trusted person to devote their time to run it and distribute funds. Probably the reasons it hasn't happened again. The current iteration would the the gekko stick solo club, a bit more simple that hashrent but still not without its complexities, need for trust, or time requirements. |
|
|
|
Or if you got 1A per port, Y-cable would put you to 2A.
This. My hub is rated at 1A per port and when I exceed 1A I see the voltage start to drop, so a Y cable will let me push it to 2A per stick. I also have 1 stick on an old laptop and those ports just barely provide 0.5A, so I'm using a cable there so the stick on that computer can run at 262freq for ~ 14GH/s. |
|
|
|
My stupid Y usb cable are 2 weeks late ... I guess i will never get them ...  Did you order them from Amazon? If so you probably got them from the same Chinese seller I did, and not realizing they ship via a super slow boat until weeks after I ordered I was pretty bummed that I didn't notice sooner. To top it off they only sent me 1 of the 4 Y cables I ordered, so I am currently waiting another ~3 weeks for the remaining cables to show up. |
|
|
|
I just want to power one, and I don't know what you mean 110v or 220v or expansion room.
I have a Corsair CX 500 Watt 80 PLUS PSU ( http://www.newegg.com/Product/Product.aspx?Item=N82E16817139027) that I bought new and used for about 2 weeks before getting a larger one to power more than one miner. I'd sell it to you for 0.1 BTC/$30 + shipping, pm me if interested. |
|
|
|
But maybe.. just maybe, there is a difference beetween one very fast device, versus 1000 slower devices.
Except that there's not: zip zero ziltch no difference. A hash is a hash, all that matters is how many calcs per second you can perform. As long as your 1000 devices are pointed to the same pool getting the same work it will result in the same chance at solving a block. |
|
|
|
--set compac:clock=x0b83
For bfg 5.4.0 I believe you can use numeric value for the clock speed instead of the hex value. -S compac is unnecessary. |
|
|
|
Compac and U3 both use CP2102 USB-UART adapters, for one thing. Bitfury sticks usually have a Microchip part for USB-SPI adapter.
So then logic would follow that there is something that some computers don't like when they see the CP2102 USB-UART configuration, and that causes the comm errors. If I knew anything about hardware other than how to plug it in I would dig deeper, but since it appears to be isolated to certain machines troubleshooting it is difficult. |
|
|
|
<snip>
When I'm running bfgminer 5.4, I get some strange hashrates...
-S all --set compac:210 --set antminer:voltage=x800 --set antminer:clock=250 --icarus-options 115200:1:1
<snip>
-S all --set compac:210 --set antminer:voltage=x800 --set antminer:clock=x982 --icarus-options 115200:1:1
<snip>
You have some errors: It should be --set compac:clock=210 --set antminer:clock=250 is correct for 5.4.0, per the readme use the numerical value, not the hex value. Besides, your hex value is wrong and should be x0982. --icarus-opions is old and not used or necessary |
|
|
|
Let's face it, someone running 6 S3s would have MUCH more than 1.2 TH/s on a pool with a legit cgm on their rigs...
They should check that all the chips are firing, no X's in the status screen. My S3+ averages about 490GH/s, I just turned it back on as a lottery machine a few days ago. "hashrate1m": "592G", "hashrate5m": "497G", "hashrate1hr": "486G", "hashrate1d": "484G" 6 S3s should be just under 3TH/s if they are configured correctly and not broken parts. |
|
|
|
I get the comm errors on my Win7 machine, but only this machine. I would agree it is hardware related, but exactly what on the hardware causes the error is a mystery. I get the same error if I try to run a U3 on this machine. My nanofury sticks hash just fine, though, so it is something that the U3 and compac stick share in common that the computer running them disagrees with. I have to restart the compacs every few hours to keep them hashing pool side, they always appear to be hashing from the bfg screen but after a while the hash drops off the pool.  |
|
|
|
|
I'm still in for round 2 (well, round 3 if you count the beta run, too). It will be cool to see the club hash rate grow a bit this time as more people join and point their sticks and donation hash this way.
Let's go, gekko club block!
|
|
|
|
We have 9 hours to go to hit a block before round 2, how sweet would that be?  I ordered 4 sets of 2-1 ubs pig tails so I could oc my sticks further, but the Chinese seller only sent me 1 and it took 19 days to get here! I bumped up one stick, now have to way for the Y cables before I can do the other 3. |
|
|
|
If a RasPi could reliably run as a full node... I would have been doing that at a remote site. Before 21co took over bitnodes, bitnodes offered a stand-alone node with a SSD drive for storing the block chain. When 21co took over, this became their "bitcoin computer", I think the SSD drive (and therefore full node capability) went away at that time.  (old address for device: http://getaddr.bitnodes.io/hardware/ now redirects to 21co bitcoin computer) |
|
|
|
Seems legit. This means that Bitmain actually advertises it as a 64GHs miner without telling that it's an overclocked mode.
Were that default settings taken from the hardware specs or found experimentally?
Yes, they advertise the maximum speed assuming everything works perfectly and you overclock it, which is a bit misleading if you ask me. Mine ran at 800v/250f for a while and saw about 60Gh, but it wasn't stable and actually melted two of my molex power plugs. The default setting is what you get if you launch it without specifying a volt or freq in your batch file. |
|
|
|
|
No, Verizon and AT&T use different antennae.
|
|
|
|
I tried countless combinations and found this to be the best:
--bmsc-voltage 0805 --bmsc-freq 1306
Hashrate: 53-60Gh/s
If you are still using --bmsc in your .bat file then you are using the old Bitmain cgminer fork. You should update to the latest 4.9.2 release, it had some changes made just for the U3. You can d/l it from https://github.com/ckolivas/cgminer, check readme.asic for update U3 commands, --au3-volt and --au3-freq The only settings that my U3 will run with <5% HW error is 785volt and 237.5freq, averages like 42GH/s. |
|
|
|
Just found this quote which relates to the power discussion: "The Canadian town of Mission, BC has a bylaw that allows the town's Public Safety Inspection Team to search people's homes for grow ops if they are using more than 93 kWh of electricity per day. There have allegedly been reports floating in IRC of two different cases of police showing up at a Bitcoin miner's residence with a search warrant. Ohio police and the DEA file at least 60 subpoenas each month for energy-use records of people suspected of running an indoor pot growing operation. DEA Agent Anthony Marotta said high electricity usage does not always mean the residence is an indoor pot farm and has surprised federal agents. 'We thought it was a major grow operation ... but this guy had some kind of business involving computers. I don't know how many computer servers we found in his home.'" source: http://idle.slashdot.org/story/11/05/24/1257229/increased-power-usage-leads-to-mistaken-pot-busts-for-bitcoin-minersI'm pretty sure there are ways to see when you are using power without a smart meter, but it definitely is not as straight-forward. So. Cal. Edison has switched all of its customers to smart meters. |
|
|
|
|
So I have found a common thread with my random crashes. It seems that (almost) whenever I receive a payment, core crashes without any error or indication of what happened in the log.
Can anyone think of what is happening, that receiving a payment causes the crash? Does core use a bunch more ram to process incoming payments or something?
|
|
|
|
|
Show Posts
