Topic: [Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 61. (Read 580775 times)
I have experimented a bit, and it seems "normal" (at least not shockingly bad) that sometimes, some chips appear as 'x' instead of 'O' right away after reconfiguring + restarting. Waiting for a minute and restarting (sometimes multiple restarts are needed) seems to get rid of the 'x' and turn them back to 'O'. Fair enough for me as long as it says under control...
I also had 3 x'es within the O's just after a reconfiguration + restart.
Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
I do not think cooling is concerned. Otherwise I do not understand much criticism for cooling. My blade is cooled with a single ASUS fan of 12 cm forward. The fan blows cold air on the right side of the blade. The blade is in the vertical position (standing on their part with the cooler). BLADE is overclocked cool as a cucumber. I can not believe that such a stable made.I think even my overclocked BLADE can operate without a fan.Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
I'll hit mine with a Infrared thermometer tomorrow, and I can get you some rough numbers to compare against. I can test with no cooling, 1x200mm, 1x200mm+1x120mm, and 1x200mm+2x120mm.
I also had 3 x'es within the O's just after a reconfiguration + restart.
Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
I do not think cooling is concerned. Otherwise I do not understand much criticism for cooling. My blade is cooled with a single ASUS fan of 12 cm forward. The fan blows cold air on the right side of the blade. The blade is in the vertical position (standing on their part with the cooler). BLADE is overclocked cool as a cucumber. I can not believe that such a stable made.I think even my overclocked BLADE can operate without a fan. Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
I also had 3 x'es within the O's just after a reconfiguration + restart.
Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
For me, my "x" didn't start until after a reconfiguration also. The first time it happened it was after the initial setup. Then today it happened when I switched pools. Both times I "fixed" it by changing the clock to low again, and possibly another reset (can't remember it was fixed after the reset or the change in clock). Then it works fine again on high.
The cooling setup is the same for this blade as my first, which has never displayed an "x" but also has firmware 0.2 (not sure if that's relevant or not).
I also had 3 x'es within the O's just after a reconfiguration + restart.
Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!
I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?
Not easily. Need specialist equipment.
.....aaaaand the "x" is back. My chips look like this:
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
I have one X as well. That means that the particular chip is not receiving sufficient voltage.!
As friedcat mentioned.. Unless you have 3 or more X, it should be a concern.. you can try resetting the board or may be increase the voltage of that power line.!
btw.. on the config page, does it have any version number in the footer..?
I was just going to post about this. My first blade says "BE Blade Rev 0.2" but the blade with the "x" doesn't have anything (no version number) listed at the footer. Why is that? Do I need to upgrade the firmware somehow?
Same here.. my first blade which was brought in Auction 3 says "BE Blade Rev 0.2" but i have an "X" in this blade..
The second blade that i brought later (can say Auction 3.5) doesnot have anything on it.!
I also noticed something.. When my first blade (the one WITH BE Blade Rev 0.2) restarts, it goes on High Clock automatically..
However when the second blade restarts (the one WITHOUT BE Blade Rev 0.2), it goes into LOW clock even though it was running High clock before restart.
I have to manually switch the clock.
So there is some difference in both..!! Anyone advise / suggestions.?
Without .2 is the old firmware.
.....aaaaand the "x" is back. My chips look like this:
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
I have one X as well. That means that the particular chip is not receiving sufficient voltage.!
As friedcat mentioned.. Unless you have 3 or more X, it should be a concern.. you can try resetting the board or may be increase the voltage of that power line.!
btw.. on the config page, does it have any version number in the footer..?
I was just going to post about this. My first blade says "BE Blade Rev 0.2" but the blade with the "x" doesn't have anything (no version number) listed at the footer. Why is that? Do I need to upgrade the firmware somehow?
Same here.. my first blade which was brought in Auction 3 says "BE Blade Rev 0.2" but i have an "X" in this blade..
The second blade that i brought later (can say Auction 3.5) doesnot have anything on it.!
I also noticed something.. When my first blade (the one WITH BE Blade Rev 0.2) restarts, it goes on High Clock automatically..
However when the second blade restarts (the one WITHOUT BE Blade Rev 0.2), it goes into LOW clock even though it was running High clock before restart.
I have to manually switch the clock.
So there is some difference in both..!! Anyone advise / suggestions.?
Just to update on my "x"... I switched the clock from low back to high, restarted, and the x went away again.
I definitely would like to upgrade to 0.2 if anyone knows how to do this. The first blade also seems to get up to the peak hash rate a lot quicker than this one (like 30 minutes faster).
.....aaaaand the "x" is back. My chips look like this:
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
I have one X as well. That means that the particular chip is not receiving sufficient voltage.!
As friedcat mentioned.. Unless you have 3 or more X, it should be a concern.. you can try resetting the board or may be increase the voltage of that power line.!
btw.. on the config page, does it have any version number in the footer..?
I was just going to post about this. My first blade says "BE Blade Rev 0.2" but the blade with the "x" doesn't have anything (no version number) listed at the footer. Why is that? Do I need to upgrade the firmware somehow?
Same here.. my first blade which was brought in Auction 3 says "BE Blade Rev 0.2" but i have an "X" in this blade..
The second blade that i brought later (can say Auction 3.5) doesnot have anything on it.!
I also noticed something.. When my first blade (the one WITH BE Blade Rev 0.2) restarts, it goes on High Clock automatically..
However when the second blade restarts (the one WITHOUT BE Blade Rev 0.2), it goes into LOW clock even though it was running High clock before restart.
I have to manually switch the clock.
So there is some difference in both..!! Anyone advise / suggestions.?
.....aaaaand the "x" is back. My chips look like this:
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
I have one X as well. That means that the particular chip is not receiving sufficient voltage.!
As friedcat mentioned.. Unless you have 3 or more X, it should be a concern.. you can try resetting the board or may be increase the voltage of that power line.!
btw.. on the config page, does it have any version number in the footer..?
I was just going to post about this. My first blade says "BE Blade Rev 0.2" but the blade with the "x" doesn't have anything (no version number) listed at the footer. Why is that? Do I need to upgrade the firmware somehow?
.....aaaaand the "x" is back. My chips look like this:
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
I have one X as well. That means that the particular chip is not receiving sufficient voltage.!
As friedcat mentioned.. Unless you have 3 or more X, it should be a concern.. you can try resetting the board or may be increase the voltage of that power line.!
btw.. on the config page, does it have any version number in the footer..?
.....aaaaand the "x" is back. My chips look like this:
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
Chip: OOOOOOOOOOOOOOOOxOOOOOOOOOOOOOOO
It came back when I switched pools and hit the restart button. I am just gonna let it be and see if it goes away unless any of you can think of anything else. So I'm guessing, not a big deal? It's still hashing at the normal rate. It's just annoying like a zit I want to pop.
I noticed some weird behaviour today with my blade. I am running stratum proxy on bitparking to feed my blade. Today the pool went down and my gpu miners running cgminer switched to its backup pool, where the blade just stayed on the proxy with 0mhs and resetting every 2 minutes. It does have a backup pool set up and the switch server button makes the blade work fine on the second pool, but this did not happen automatically.
Anyone know how this can be fixed? It seems like whatever algorithm cgminer uses to switch pools is better than what the blade has built in. Is there any way to update the firmware or any of the parameters?
This is what stratum proxy is showing while the blade is trying to get work:
Anyone know how this can be fixed? It seems like whatever algorithm cgminer uses to switch pools is better than what the blade has built in. Is there any way to update the firmware or any of the parameters?
This is what stratum proxy is showing while the blade is trying to get work:
Quote
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
File "twisted\web\server.pyo", line 156, in process
File "twisted\web\server.pyo", line 191, in render
File "twisted\web\resource.pyo", line 216, in render
File "mining_libs\getwork_listener.pyo", line 163, in render_POST
--- ---
File "twisted\internet\defer.pyo", line 134, in maybeDeferred
File "mining_libs\worker_registry.pyo", line 37, in authorize
File "stratum\socket_transport.pyo", line 93, in rpc
stratum.custom_exceptions.TransportException: Not connected
2013-05-24 20:32:51,382 ERROR proxy # Connection to upstream pool timed out
Unhandled Error
Traceback (most recent call last):
File "twisted\web\server.pyo", line 156, in process
File "twisted\web\server.pyo", line 191, in render
File "twisted\web\resource.pyo", line 216, in render
File "mining_libs\getwork_listener.pyo", line 163, in render_POST
---
File "twisted\internet\defer.pyo", line 134, in maybeDeferred
File "mining_libs\worker_registry.pyo", line 37, in authorize
File "stratum\socket_transport.pyo", line 93, in rpc
stratum.custom_exceptions.TransportException: Not connected
2013-05-24 20:32:51,382 ERROR proxy # Connection to upstream pool timed out
Saw this the other day too, do you have more than one blade? I have a more than one and I had to put them on one worker each on BTCguild and I was able to get it going.
I have each worker on a separate instance of the proxy (each on different ports). I found if I was running one instance of the proxy and two workers that the work units leaked between the two workers in the pool. Two instances seem to work best. The issue is that the cgminer was able to deal with a bad pool connection and switched to backup, but the blade just sat there on the main pool and didnt switch.
One x in itself is not the end of the world, I have one chip (#32) which spent an entire week displaying the x and then just decided to cooperate. Your user experience may vary.
Well it's been hashing at 12,900 for about an hour and the x disappeared. Weird. Thanks for the response.
One x in itself is not the end of the world, I have one chip (#32) which spent an entire week displaying the x and then just decided to cooperate. Your user experience may vary.
I read through the troubleshooting and this thread, but it seems it only addresses when there are multiple "x"s on the chip section of the configuration menu. I just got a second blade today, and after reaching 12,800 or so (high clock), one of the chips displayed "x". Does this mean one chip is bad? Do I need to tune the voltage? Or is it nothing to worry about? I restarted it and all the chips read 0 again after hashing on high for 15 minutes so far, but that is what it did the first time so I am continuing to monitor it. I never saw this with the other blade as all the chips read "0" always. Thanks!
I do what you suggest, there is no echo replies after plug cable to the blade. 
I'd suggest you to try cross-cable to connect it to your PC. I have old notebook (2008) which don't have autosense capability in its Ethernet adapter, used X-cable and it worked fine to me. And for what are two pins 1-2 normal ?
Best Guess:
Putting a jumper between 1-2 resets the hardware without overwriting user settings.
Putting a jumper between 2-3 overwrites user settings with factory settings, then resets the hardware.
EDIT: Dude, I really feel for you if you can't get it working again. Tonight I moved my blade from office back home, and I had a heart attack for about 30 seconds, when I saw:
Chip: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (hashing at 0 Mhash/s)
So, I decided it was a **** nightmare, and I cut the power off the PSU.
Then, closed my eyes, opened again, and put the power back on:
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Allright. It was a nightmare indeed. Back to reality...
I hope it will turn out good for you too. Good luck!
For what reasons are other pins for example 1-2 ?
I am away from my Blade at the moment but if I remember well, there was a DEBUG connector on the Ethernet board. If it is two pins (I think it is), it is probably an I2C interface. But this is not something you may easily work with unless you are in a lab with HW dev equipment.
EDIT: It's actually 3 pins, GND, Tx, Rx. It might just a well be a serial interface (console?). If you have any RS-232 port at hand, maybe you could attach a terminal, and get the settings from friedcat (or just try 8N1 at 2400, 9600 or 19200 bps? best guess...). At any rate, if I were you, I would (be pissed off but anyway) wait for an answer from him.
And for what are two pins 1-2 normal ?
Jump to: