Just Amazon them

Hmm i can try but i have it in the roome where is only one notebook with proxy one cube and one fridge (icebox).
Problem is in the power or can be in the lan subnet ?. If only power circuit i try it change.

Thanks

Hi miners. I have this problem.

My cube run good when i am in work. When i am not at home.

When come home parrents and me and turn on computers or TV or i dont know what cube stop hashing and start next day on morning.

I dont know where is problem. Can any pc or TV with lan interrupt my cube?

Please if have anybody any solution send me any settings for cube.
Here or on email donkezz@gmail.com

Maybe set two different subnets? All devices in first subnet and notebook with proxy and cube to second subnet ?

I try setup different dns, web port, IPs i dont know how can i fix it.

Here is when is hashing very slow.
http://i.imgur.com/R0rr5Wu.jpg

Here is when hashing good.
http://i.imgur.com/DvnZkbH.jpg

I try it setup about 20 days but not working 24 hours nonstop. Max 10-12 hours.

Thanks

Your Gateway is blank....Needs to be your router IP address....

I don't know how to use the -cu or -cp switch.  Can you give me an example?  Thanks!




Thanks, Gents!  One or both of these got me mining!  Cheers!

Wait, I'm going to take a longshot here, -cu is and -cp ?  I'll try that...

EDIT:  Well, I tried that as in: -cu username -cp password but the mining did not register on the site.  If I use my username/password in the settings panel, it works.  But I'd like the functionality of using a command line version.  If someone can give me an example in syntax.  Thanks.

I have 1 card that is half full of x's in low clock mode (x x x x x x x x o o o o o o o o). If I switch to high clock mode and restart, it goes to all o's. But when I switch back to low and restart, the x's return.

Anyone know what's going on or how to fix it?

Also, is it normal to always get these "WARNING proxy getwork_listener._on_submit" messages? I seem to be getting a lot of work accepted (27 gh/s on slush's pool), but I'm getting lots of WARNING spam.

After several hours of running with a Scythe Gentle Typhoon AP-15 (58.x CFM), I saw a performance slowdown of roughly 8%. While I had thought the airflow coming from the front of the Cube was similar to the stock fan, it was noticeably warmer air coming out.

So, I used twist ties to attach another fan to the front. The result is hideously ugly, louder, but still much quieter than the stock fan, and is definitely putting out more air flow. It still feels warm, but I'm not using thermometers to measure this stuff.

There is also zero back flow out of the back where the fan is supposed to go. With both the stock fan and my Scythe replacement by itself, I was getting some back flow.

So far, my missing performance is back.

I'd appreciate anyone's insight on all this.

I'm thinking it's a proxy issue - part of the programming makes it so the devices (v2 blades and cube) restart when they don't get any work. All three restart simultaneously and the problem is most assuredly not heat related.

Hello,

I have two V2 blades and a cube connected to Slush's stratum proxy. The hardware itself seems to be in good shape, all three devices achieve the desired hashrate but after about five minutes - they restart. Every time this happens they need a few moments to get back up to speed and in the process I lose tons of hashes. The blades average out at only about 7.5Gh/s (out of 10Gh/s) while the cube averages only 25Gh/s (out of 38Gh/s), I'm guessing since it takes longer to reach its target rate upon restart.

So far I've tried different pools and exchanged the power supply to see if those could be the problem, but the results were the same. Honestly any information would be greatly appreciated and I'll tip whoever can make this go away. I feel like a noob for not being able to figure this out, but I'm treading in the dark.

I have also seen reports that a failing fan (not drawing enough power, I suppose) will cause random restarts - it's worth trying if you're out of other ideas.

somewhere in this forum is a reference to certain corsair psu's having a power saving mode that cause's issues similar to this. I believe it was an AX model but may include the CS model as well. I know for a fact the GS800 works fine.

I think you misunderstood my question
I'm not trying to solo mine bitcoin. I'm trying to solo mine other coins like Tigercoin or Zetacoin or something like that.

Do we know how to get a cube to solo mine something like Zetacoin without using BFG Miner?

You seem "in the know".

So far, I've only been able to solo mine other SHA-256 coins with a cube by using BFG Miner and the --http-port #### option.

Is it even possible to use stratum proxy for solo mining?

Also, I've tried just using the cube by itself but it won't communicate with the wallet by setting the "Pool ports" to the rpcport in the wallet .conf file. Any suggestions? (I've probably asked this question about 3-5 times on this thread and once in its own thread, but people just said "point the cube at the wallet" which obviously so far has not worked.)

Found my problem, it was the power supply.

The Corsair GS 800 has this annoying attribute where it will go into "power saving" mode randomly and stop supplying power to the cube.

I bought another Corsair HX 850 yesterday and hooked it up this morning and I've had no issues so far.

Also, you're going to get a lot faster hashrate if you use stratum mining proxy with the following:

mining_proxy.exe -o stratum.btcguild.com -p 3333 -gp 8333 -q

For Primary and Secondary DNS I would recommend using OpenDNS instead.
Primary DNS: 208.67.220.220
Secondary DNS: 208.67.222.222

Also is your Gateway really 0.0.0.0?

run ipconfig in a command prompt and make sure your Default Gateway actually says 0.0.0.0.

I ended up building a small Ubuntu VM per Cube for a proxy; it actually doesn't use much ram or disk space so it's not too much of a big deal.  It is a pain in the ass since I'd like a single instance to cover all cubes and direct them all to slush's pool.  Anyway, with 4 cubes, I have 4 proxies and they will fail over to one of the other cubes should their primary fail.  I noticed when I was sharing one proxy, even with different ports and workers - I was getting ~25Gh/s, but once it's on a dedicated proxy it jumped over 30Gh/s.  I may have to alter things once again when I start adding more cubes.

Hi Shaker242, I read through your post but my problem is not only slow mining it simply does reboot all the time. After 2 min. reboot.Actually you do not tell how you solved the problem.

The LED stays red on some powersupply. On the other it goes off but also after 2 min restart it connects to my windows binary proxy. And also I tried to compile the slush proxy on ubuntu which connects now the same way, but no luck getting this brick to mine.