Upgraded to 3.12.3, and seems to be running fine now.
|
|
|
I've been round them all in my year of mining, and I keep on coming back to Eligius and BTCGuild. I started off on Slush's (most people used it back then), then used itzod.ru until it had it's Gibson hacked, and the spent a long time on BTCGuild. Tried p2pool for a while, and ended up trying Eligius when it hit the heady heights of 200GH. Sort of been there ever since, because it Just Works(tm).
|
|
|
"Whaa, whaa, whaa. " ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) What's that noise? Oh, it's the Whaaaambulance.
|
|
|
The fuse wasn't in correctly, so the high resistance in the connection heats up the legs. They're just normal automotive blade fuses, just get another one and it might have a better connection. A box of 10 is about £2.
|
|
|
But they're still mining right? So the die - zombie - hotplug is just an ugly cosmetic issue, not that they have failed and stopped mining indefinitely. I've been running mine at 275 (2.2GH) which has been stable but I doubt they're all stable at that speed.
Yeah, they are still mining OK, it's just filling up the API with zombie miners. I'll try upgrading to the latest version and see if it's any better. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
WARNING: There may be a problem with cgminer 3.12.1 that makes it stop retrieving work. I will investigate further and possibly release a fix in the next 24 hours. In the meantime I suggest users do not upgrade.
Sigh.
The Antminer U1 support isn't very stable either, mine all crapped out after an hour or so, I ended up with 50-odd as they dropped out and came back on. I have 10 of them on a Anker hub, running off a PC running Debian Wheezy. I'll update the error messages when they happen again, I'm on an intermittent SSH connection through my phone from work at the moment. Hmm I can try reinstating the attempted reset but I'm not sure it's going to fix that... How much were you overclocking them? Sorry, only got back to this thread. 2GH, which they've been stable with. They do run basically OK with BFG at 2.2GH (one or two of them run at 10% HW error as reported by BFG), but I tried knocking them down to 2GH to see if that would help. Overnight I now have 20 ANU devices reported by the API, when I actually only have 10.
|
|
|
And when i will start bfgminer with options : bfgminer -c /home/pi/bfgminer.conf –set-device antminer:clock=x0981
i become only this error: Unexpected extra commandline arguments What is wrong here? You're missing a dash. It's --set-device, not -set-deviceSimple. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
WARNING: There may be a problem with cgminer 3.12.1 that makes it stop retrieving work. I will investigate further and possibly release a fix in the next 24 hours. In the meantime I suggest users do not upgrade.
Sigh.
The Antminer U1 support isn't very stable either, mine all crapped out after an hour or so, I ended up with 50-odd as they dropped out and came back on. I have 10 of them on a Anker hub, running off a PC running Debian Wheezy. ANU7: Comms error (werr=-9 something something) Then it disables, and a few seconds later the miner reappears using Hotplug and gets a new number. Then I get a load of ANUxx Re-estimate: blah blah spam. Same hardware runs the U1 on bfg perfectly for weeks on end. I'll update the error messages when they happen again, I'm on an intermittent SSH connection through my phone from work at the moment.
|
|
|
Which is fine until air temp increases quicker than the cold parts of the miner. I've seen server cases rusting when the aircon went wrong and was cycling the temp, leading to condensation on the server cases, despite the servers being on and outputting 40C air from the exhaust.
|
|
|
"The Future of Mining". You have pictures of Block Erupter Cubes. Buzzztt...wrong. They are firmly in the past those things...
|
|
|
Is it just me, or is there something odd with the variable difficulty today? I've got 35GH mining here on one instance of cgminer and it's sitting at Diff16. Usually it runs around Diff64. Edit: 90 minutes after connect, and 2 minutes after I posted this, it changed to 32. Edit2: It's flip-flopping back and forward between 16 and 32 now. ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
Yes it's supposed to go back in failover mode.
Yes, it is, isn't it? Except quite often it never does, it just sits thee like a twat mining on the backup pool. I see the same problem on 3.11.0 on Linux and on the dodgy patched 3.11.0 for the HEX16A2 on OpenWRT.
|
|
|
Eligius also keeps shares done by people mining with invalid addresses - say you connect your miner with a gibberish work name, work you do will go to the pool's coffers.
|
|
|
You mean, which is less slow? Probably no difference. It's not like Linux makes the CPU run faster, and OS overhead is so insignificant now, there's probably little difference.
|
|
|
Like the fans they fit, they're the cheapest shite they can get out of China.
|
|
|
1) Join bitcointalk forums. 2) Peruse briefly the custom hardware forums 3) Pick the first new mining hardware that claims to achieve some new standard in performance available "soon" and fork out thousands of dollars for it as a preorder before doing any more research. 4) ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) 5) Loss I rarely agree with ck, but I have to say what he's said here is right on the money.
|
|
|
Any idea on power use? Also, is UK shipping included? ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
I ran a pair of 7950s as my last GPU miners. They were good, paid for themselves in no time, and then I sold them for what I bought them for after 6 months. I still run a 7770 and a 7850 for scrypt, they're pulling BTC0.01 a day. Half what my 120GH of ASICs does on pure BTC mining. Yep, 400kH/s is making half of what 120GH is. I just picked up a R9 280X to get more scrypt hashing power, and I might even play some games with it too! ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
bfgminer still does CPU mining. Again, you must compile it yourself as it's not enabled on the Windows binary.
|
|
|
|