Evening All,
I received my cube over the weekend and have just found the time to set it up.
I've used the default settings and have connected successfully to slush's pool.
My cube is being powered by a Corsair 500W CX500 PSU and I have set the clock on the device to high, for the first few minutes the Efficiency is in the 80 percentile but then it drops to the 20% region and stays around there. I've noticed eight X's in ASIC row 49-64 and my MHS is around 13374. I am only hosting the 1 cube using my 500W power supply.
ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: x x x x x x x x O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O
Can anyone tell me why my efficiency is so low and what I might be able to do to remedy this?
Thanks in advance for your time and help.
Topic: [Guide] Dogie's Comprehensive ASICMiner Cube Setup [HD] - page 77. (Read 187363 times)
Well nuts. Unless there's something screwy with network topology, I'm out of ideas. Did you double-check the IP of your proxy machine?
Yeah I went and changed the IPs of everything again and tried it once more. Same results. I'm just going to blame it on AT&T UVerse and sell this thing to a sucker on CL or eBay.
Sticking with scrypt mining for now... thanks for all of the help!
Well nuts. Unless there's something screwy with network topology, I'm out of ideas. Did you double-check the IP of your proxy machine?
The word "port" doesn't need to be in there. -gp 8335 or something
Tried that and there was no change...
The word "port" doesn't need to be in there. -gp 8335 or something
Hm, yeah that all seems to make sense. The only thing I can think of, which is sorta unlikely unless for some reason you have a local bitcoind instance running, is something's already got 8332 tied up?
Had the Wallet-qt open, but I closed it... no different results.
Trt adding a "-gp port" option to your mining_proxy.exe and changing the "Pool ports" to the same port specified.
Adding "-gp port" or "-gp port 8332" to the command line only caused it to immediately crash.
I'm all out of ideas. Already changed the PSU, fuse, took apart the Cube, made sure everything was in there correctly (for the second time), tried changing the IP for it, tried two different pools, tried shutting off the WiFi and disconnecting all other devices from the router, tried restarting the router... tried blowing into the fan while I touched my nose with my left hand...
Would power issues manifest by having about 3 rows (3 boards) consistently at less than 100 on chips?
so the cube runs at ~20 Gh/s (symptom). 3 rows of chips show "expected" speeds. next 3 rows show sub 100 Mh/s speed with a few chips actually at zeros.
power?
so the cube runs at ~20 Gh/s (symptom). 3 rows of chips show "expected" speeds. next 3 rows show sub 100 Mh/s speed with a few chips actually at zeros.
power?
Hm, yeah that all seems to make sense. The only thing I can think of, which is sorta unlikely unless for some reason you have a local bitcoind instance running, is something's already got 8332 tied up?
Trt adding a "-gp port" option to your mining_proxy.exe and changing the "Pool ports" to the same port specified.
Trt adding a "-gp port" option to your mining_proxy.exe and changing the "Pool ports" to the same port specified.
What is your:
a) router IP address
b) Cube config
c) proxy-machine IP address
d) proxy command line
a) router IP address
b) Cube config
c) proxy-machine IP address
d) proxy command line
a) 192.168.1.254
b) Cube Config:
IP 192.168.1.201
Mask 255.255.255.0
Gateway 0.0.0.0
WEB Port 8000
Primary DNS 192.168.1.254
Secondary DNS 8.8.8.8
Pool ports 8332, 8332
Pool addresses 192.168.1.76, 192.168.1.76
Miners user:pass Damnsammit:x, Damnsammit:x
c) 192.168.1.76
d) C:\proxyminer\mining_proxy.exe -o stratum.bitcoin.cz -p 3333
Thanks in advance!
What is your:
a) router IP address
b) Cube config
c) proxy-machine IP address
d) proxy command line
a) router IP address
b) Cube config
c) proxy-machine IP address
d) proxy command line
Thank you!!! As soon as my WiFi was turned off on my droid, both units started going full steam at the proxy! Been driving me crazy for 4 days.
Wish that would work for me! I shut my wireless down and the only two things connected to the router are my computer and the Cube... still not working, and it is getting reset every ~2 minutes.
I have an all X problem which I'm assuming is power related.
At first it was hashing away nicely for about 8 hours... then it stopped. After restarting, and then doing a full factory reset.... it will only run for about 1 hr before stopping.
power supply is a new Corsair CX750M with nothing else plugged in. Before I ran the cube on it... it was powering a 49 port USB erupter setup with no issues. :/
At first it was hashing away nicely for about 8 hours... then it stopped. After restarting, and then doing a full factory reset.... it will only run for about 1 hr before stopping.
power supply is a new Corsair CX750M with nothing else plugged in. Before I ran the cube on it... it was powering a 49 port USB erupter setup with no issues. :/
I will bet your all xs problem is due to one flaky board.
Try running one board alone and then add back one by one to identify the offending board.
I'm doing this now. Thanks for the suggestion. So far, 2 boards running with no problems. I'm adding a new board every 2 hours. I did notice when I took the boards out that a few of them had loose heat sinks. Hopefully tightening them will solve all my issues!
I found the faulty board. After putting in each board one at a time, I finally found one that crashed all the others. I made sure it was the board by testing on different slots as well. I pulled the bad board and the cube has been running at 28 gh/s all night with no issues.
So after 5 hrs, my "overclocked" cub has climbed to 33.9 gh/s (87.21% efficiency), while my standard/low clocked cube is operating at 31.6 gh/s (96.14% efficiency).
Any idea why it won't get anywhere near the 38 gh/s?? voltages all test out correctly too. Can Cubes be too cold? the outer case is cold, and the air exiting it is pretty cool as well (feeding it freezing air from a window).
Any idea why it won't get anywhere near the 38 gh/s?? voltages all test out correctly too. Can Cubes be too cold? the outer case is cold, and the air exiting it is pretty cool as well (feeding it freezing air from a window).I'm also unable to break 95% efficiency on the cube, any tips??
Take it out of its case and put another fan on it. I run over 38.2gh/s on both of my 2 cubes.
The air exiting the Cube is already cold... what would adding more airflow do? The cube already feels like a cold plate. It's 36F ambient outside, from which the air blown at my Cubes are from. I don't think heat is an issue. (yes, all the heatsinks have been property tightened).
Quote
Also, your miningproxy port does not have to be identical to the pool ports on the cube.
Actually, yes it does. The -p port refers to the stratum port on the pool; the -gp port refers to the getwork listen port which must be the same as the "Pool port" on the Cube. If you don't specify a getwork port in mining_proxy, it defaults to 8332. If you need to run multiple proxies, like a secondary/failover pool, you need to specify a different getwork port in the second proxy instance, and match that port in the secondary pool config on the Cube.
So in my case, what happens when the cube is defaulted to 8332 and the port specified in the batch file is 3334? It hasn't shown any problems that I can see in this configuration.
Wait, answered my own question. The cube getwork pool port is 8332, and since I don't have a -gp specified on my miningproxy it defaults to 8332, while the -p refers to the stratum port 3334. So technically that means I'm right, even though my thinking was incorrect lol, since the port (-p) is in fact different than the ports listed in the cube.
So after 5 hrs, my "overclocked" cub has climbed to 33.9 gh/s (87.21% efficiency), while my standard/low clocked cube is operating at 31.6 gh/s (96.14% efficiency).
Any idea why it won't get anywhere near the 38 gh/s?? voltages all test out correctly too. Can Cubes be too cold? the outer case is cold, and the air exiting it is pretty cool as well (feeding it freezing air from a window).
Any idea why it won't get anywhere near the 38 gh/s?? voltages all test out correctly too. Can Cubes be too cold? the outer case is cold, and the air exiting it is pretty cool as well (feeding it freezing air from a window).I'm also unable to break 95% efficiency on the cube, any tips??
Take it out of its case and put another fan on it. I run over 38.2gh/s on both of my 2 cubes.
So after 5 hrs, my "overclocked" cub has climbed to 33.9 gh/s (87.21% efficiency), while my standard/low clocked cube is operating at 31.6 gh/s (96.14% efficiency).
Any idea why it won't get anywhere near the 38 gh/s?? voltages all test out correctly too. Can Cubes be too cold? the outer case is cold, and the air exiting it is pretty cool as well (feeding it freezing air from a window).
Any idea why it won't get anywhere near the 38 gh/s?? voltages all test out correctly too. Can Cubes be too cold? the outer case is cold, and the air exiting it is pretty cool as well (feeding it freezing air from a window).I'm also unable to break 95% efficiency on the cube, any tips??
Quote
Also, your miningproxy port does not have to be identical to the pool ports on the cube.
Actually, yes it does. The -p port refers to the stratum port on the pool; the -gp port refers to the getwork listen port which must be the same as the "Pool port" on the Cube. If you don't specify a getwork port in mining_proxy, it defaults to 8332. If you need to run multiple proxies, like a secondary/failover pool, you need to specify a different getwork port in the second proxy instance, and match that port in the secondary pool config on the Cube.
Having difficulty getting my new cubes set up. I am fairly confident I have everything set correctly but it is not connecting to my proxy and not hashing.
What do the LEDs on the back mean? I have a solid RED one for status. (I assume it just means it is offline and not working)
ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_17-32: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_33-48: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
Jobs:0000000000 Accepted:0000000000 Rejected:0000000002 (0:0) F1 F2 F3
MHS:00000 Utility:000 Efficieny:000.00%
Started before: 0d,00h,00m,51s
Current pool: 192.168.1.129 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: inactive
IP 192.168.1.200
Mask 255.255.255.0
Gateway 192.168.1.1 (have also tried 0.0.0.0)
WEB Port 8000
Primary DNS 192.168.1.1
Secondary DNS 8.8.8.8
Pool ports 8332,8332
Pool addresses 192.168.1.129,192.168.1.129
Miners user:pass asicminer_test:x,asicminer_test:x
I am just using default setup right now, but I did change ports to 8332 because the proxy showed this is the port it is listening to.
I have have a 1000W 80 plus gold power supply - Plenty of juice and nothing else on it.
I have turned off all software firewalls on proxy host and in router. Also disabled antivirus settings.
I am not using WIFI...everything is over cat5.
I can ping cube & proxy machine both directions
I received two cubes, and have tried both. And only trying to get one going right now on power supply. They both seem to be properly functioning. Same lights/indicators
I can log into web interface and make changes with no problem
I quickly tried "getwork" on OZ pool to bypass stratum proxy, but no luck either. (But I was pretty hammered/frustrated by now!)
Ok guys, any ideas???
What do the LEDs on the back mean? I have a solid RED one for status. (I assume it just means it is offline and not working)
ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_17-32: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_33-48: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
Jobs:0000000000 Accepted:0000000000 Rejected:0000000002 (0:0) F1 F2 F3
MHS:00000 Utility:000 Efficieny:000.00%
Started before: 0d,00h,00m,51s
Current pool: 192.168.1.129 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: inactive
IP 192.168.1.200
Mask 255.255.255.0
Gateway 192.168.1.1 (have also tried 0.0.0.0)
WEB Port 8000
Primary DNS 192.168.1.1
Secondary DNS 8.8.8.8
Pool ports 8332,8332
Pool addresses 192.168.1.129,192.168.1.129
Miners user:pass asicminer_test:x,asicminer_test:x
I am just using default setup right now, but I did change ports to 8332 because the proxy showed this is the port it is listening to.
I have have a 1000W 80 plus gold power supply - Plenty of juice and nothing else on it.
I have turned off all software firewalls on proxy host and in router. Also disabled antivirus settings.
I am not using WIFI...everything is over cat5.
I can ping cube & proxy machine both directions
I received two cubes, and have tried both. And only trying to get one going right now on power supply. They both seem to be properly functioning. Same lights/indicators
I can log into web interface and make changes with no problem
I quickly tried "getwork" on OZ pool to bypass stratum proxy, but no luck either. (But I was pretty hammered/frustrated by now!)
Ok guys, any ideas???
I've been seeing a lot of people setting their DNS to the same thing as the Gateway and setting the secondary DNS to 8.8.8.8.
Try using Open DNS as someone suggested earlier, I did this and it's been working fantastically:
Primary DNS 208.67.220.220
Secondary DNS 208.67.222.222
Run ipconfig on the machine running the miningproxy.exe just to make 100% sure that your IPv4 Address is exactly the same as what you're setting both of your pool addresses to.
Also, your miningproxy port does not have to be identical to the pool ports on the cube. I'm running 8332,8332 on both of my cubes with the following as a miningproxy.exe batch file and its running just fine:
mining_proxy.exe -o nl1.ghash.io -p 3334
Insert whatever pool above you're using.
For ozcoin try this:
mining_proxy.exe -o stratum.ozco.in -p 3333
Allright...now working.....Not sure why....
Cube was delivered in deep freeze stage. maybe it needed to thaw! LOL
Cube was delivered in deep freeze stage. maybe it needed to thaw! LOL
Having difficulty getting my new cubes set up. I am fairly confident I have everything set correctly but it is not connecting to my proxy and not hashing.
What do the LEDs on the back mean? I have a solid RED one for status. (I assume it just means it is offline and not working)
ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_17-32: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_33-48: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
Jobs:0000000000 Accepted:0000000000 Rejected:0000000002 (0:0) F1 F2 F3
MHS:00000 Utility:000 Efficieny:000.00%
Started before: 0d,00h,00m,51s
Current pool: 192.168.1.129 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: inactive
IP 192.168.1.200
Mask 255.255.255.0
Gateway 192.168.1.1 (have also tried 0.0.0.0)
WEB Port 8000
Primary DNS 192.168.1.1
Secondary DNS 8.8.8.8
Pool ports 8332,8332
Pool addresses 192.168.1.129,192.168.1.129
Miners user:pass asicminer_test:x,asicminer_test:x
I am just using default setup right now, but I did change ports to 8332 because the proxy showed this is the port it is listening to.
I have have a 1000W 80 plus gold power supply - Plenty of juice and nothing else on it.
I have turned off all software firewalls on proxy host and in router. Also disabled antivirus settings.
I am not using WIFI...everything is over cat5.
I can ping cube & proxy machine both directions
I received two cubes, and have tried both. And only trying to get one going right now on power supply. They both seem to be properly functioning. Same lights/indicators
I can log into web interface and make changes with no problem
I quickly tried "getwork" on OZ pool to bypass stratum proxy, but no luck either. (But I was pretty hammered/frustrated by now!)
Ok guys, any ideas???
What do the LEDs on the back mean? I have a solid RED one for status. (I assume it just means it is offline and not working)
ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_17-32: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_33-48: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
Jobs:0000000000 Accepted:0000000000 Rejected:0000000002 (0:0) F1 F2 F3
MHS:00000 Utility:000 Efficieny:000.00%
Started before: 0d,00h,00m,51s
Current pool: 192.168.1.129 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: inactive
IP 192.168.1.200
Mask 255.255.255.0
Gateway 192.168.1.1 (have also tried 0.0.0.0)
WEB Port 8000
Primary DNS 192.168.1.1
Secondary DNS 8.8.8.8
Pool ports 8332,8332
Pool addresses 192.168.1.129,192.168.1.129
Miners user:pass asicminer_test:x,asicminer_test:x
I am just using default setup right now, but I did change ports to 8332 because the proxy showed this is the port it is listening to.
I have have a 1000W 80 plus gold power supply - Plenty of juice and nothing else on it.
I have turned off all software firewalls on proxy host and in router. Also disabled antivirus settings.
I am not using WIFI...everything is over cat5.
I can ping cube & proxy machine both directions
I received two cubes, and have tried both. And only trying to get one going right now on power supply. They both seem to be properly functioning. Same lights/indicators
I can log into web interface and make changes with no problem
I quickly tried "getwork" on OZ pool to bypass stratum proxy, but no luck either. (But I was pretty hammered/frustrated by now!)
Ok guys, any ideas???
Jump to: