hwo do i perform a hardware reset? just tip the two pins? or is there something special??
That's correct, you'll see the LED come on.
Did you compile the proxy (midstate) C Extension in order to speed things up? ...
In English?
Topic: [Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 67. (Read 580775 times)
That's correct, you'll see the LED come on.
In English?
I was working with WinTame2012 this evening on where my performance has wandered off to, does anyone else's blade hop proxies every 90 seconds or so; I mean it switches from Pool-1 to Pool-2 automatically with no interaction from myself.
Yes I think I know which is the error you are talking about... you just have to edit the Makefile inside the midstate folder and change the -march compile flag so it looks like this:
-march=armv6
That worked for me... you'll need to indicate the proper architecture as well
Note: This is for Rasp B (512) using Raspbian. Check this out for more info: http://raspberrypi.stackexchange.com/questions/2046/which-cpu-flags-are-suitable-for-gcc-on-raspberry-pi
Thanks, that did it; back to the never ending stretch of troubleshooting. -march=armv6
That worked for me... you'll need to indicate the proper architecture as well
Note: This is for Rasp B (512) using Raspbian. Check this out for more info: http://raspberrypi.stackexchange.com/questions/2046/which-cpu-flags-are-suitable-for-gcc-on-raspberry-pi
1 Blade is the only thing attempting to use the proxy. Every time I tried "make" in the midstate folder it errors out under Wheezy, some complaint about the Arm processor. I can pull the log if need be.
Yes I think I know which is the error you are talking about... you just have to edit the Makefile inside the midstate folder and change the -march compile flag so it looks like this:
-march=armv6
That worked for me... you'll need to indicate the proper architecture as well
Note: This is for Rasp B (512) using Raspbian. Check this out for more info: http://raspberrypi.stackexchange.com/questions/2046/which-cpu-flags-are-suitable-for-gcc-on-raspberry-pi
My Pi for some reason couldn't feed the miner fast enough without work returns exceeding 100ms, and that was connected to the same router as the blades. I swear I am developing only hatred for my bad luck
How many blades/workers did you set up? Did you compile the proxy (midstate) C Extension in order to speed things up? ...
1 Blade is the only thing attempting to use the proxy. Every time I tried "make" in the midstate folder it errors out under Wheezy, some complaint about the Arm processor. I can pull the log if need be.
For all you fellow Blade Miners™: you really want to set the difficulty for your pool workers at least as high as 8 to minimize stale shares and network lags.
My Pi for some reason couldn't feed the miner fast enough without work returns exceeding 100ms, and that was connected to the same router as the blades. I swear I am developing only hatred for my bad luck
How many blades/workers did you set up? Did you compile the proxy (midstate) C Extension in order to speed things up? ...
has anyone had problems with BTCGuild? I have two proxies BTCGuild is primary and Slush is secondary and after about a minute all of my miners switch over to Slush automatically. I'm running two instances of the stratum proxy on one OSX machine (mac mini).
Sorry, no idea. Been on Slush's since powering up the blade and (probably) won't be testing other pools til next week
BTW, lil' Pi is more then enough for the stratum proxy! Htop shows just 46MB RAM and 15-30% CPU usage!!
My Pi for some reason couldn't feed the miner fast enough without work returns exceeding 100ms, and that was connected to the same router as the blades. I swear I am developing only hatred for my bad luck
has anyone had problems with BTCGuild? I have two proxies BTCGuild is primary and Slush is secondary and after about a minute all of my miners switch over to Slush automatically. I'm running two instances of the stratum proxy on one OSX machine (mac mini).
Yes, batch 3 is over clocked too so just change it to high. Cool Pi, time to put one of mine to good use.
Thanks! Yeah, the pi as a headless server does the work really well. You just have to get rid of all the X11 stuff and minimize the GPU RAM usage (with this script https://github.com/Hexxeh/rpi-update). Then autorun the mining_proxy with supervisord and you can forget about it....
I have much less impressive setup and blade works at HIGH clock like a charm. Just press the button and check the wires' temp after an hour of hashing. If it still cold or warm a little to touch then all is ok.
Thanks, I'll check the wires too. The setup is not that impressive
I just needed an extremely quiet config and I think I got it. I'm really happy with the fans (http://www.youtube.com/watch?v=XFi39czpsac blonde not included 
). Can't hear literally anything at 1m distance!Hi guys can anyone please confirm that in order to hash at ~13.000 I only have to change "Clock selected" to "High" (Switch Clock button)?
I have much less impressive setup and blade works at HIGH clock like a charm. Just press the button and check the wires' temp after an hour of hashing. If it still cold or warm a little to touch then all is ok. 
Hi guys can anyone please confirm that in order to hash at ~13.000 I only have to change "Clock selected" to "High" (Switch Clock button)?
BTW, lil' Pi is more then enough for the stratum proxy! Htop shows just 46MB RAM and 15-30% CPU usage!!
BTW, lil' Pi is more then enough for the stratum proxy! Htop shows just 46MB RAM and 15-30% CPU usage!!
Yes, batch 3 is over clocked too so just change it to high. Cool Pi, time to put one of mine to good use.
Hi guys can anyone please confirm that in order to hash at ~13.000 I only have to change "Clock selected" to "High" (Switch Clock button)?
I mean, right now I'm hashing at ~10000 since Clock seems to be set to "slow" by default. I just want to confirm if my blade (3rd batch) is providing the required 1.2V as dogie said in the first post...
I don't have a tester with me and I don't know if I should go and get one
and double-check.
BTW, lil' Pi is more then enough for the stratum proxy! Htop shows just 46MB RAM and 15-30% CPU usage!!
PS: My ugly setup
...
I mean, right now I'm hashing at ~10000 since Clock seems to be set to "slow" by default. I just want to confirm if my blade (3rd batch) is providing the required 1.2V as dogie said in the first post...
Batch 2+ blades come at 1.2V on stock, and you will be running them overclocked.
I don't have a tester with me and I don't know if I should go and get one
and double-check.BTW, lil' Pi is more then enough for the stratum proxy! Htop shows just 46MB RAM and 15-30% CPU usage!!
PS: My ugly setup
... 
hwo do i perform a hardware reset? just tip the two pins? or is there something special??
thanks a lot dogie!
Quote
You can use a PCI-E 6 pin but again you'll be overspec, although its the same as a molex. PCI-8 pin is best. There will be 3 12V cables, and 5 neutrals. Just wire them all up.
Hi dogie, I am confused
I bought another molex splitter but I doubt it will be any different than my previous melted one 
I rather use the PCI-E 6pin since I trust more the cables in my Corsair GS600 PSU
Can you please explain whether to use two yellows and blacks or only one of each for powering the board?
thanks!
i used 6 blacks and 6 yellows, all from 2 PCI-e connectors. With the usual molex i had overheating. No molex splitter, direct wires from PSU, that worked for me.
So you used 3 wires in each hole?
Quote
You can use a PCI-E 6 pin but again you'll be overspec, although its the same as a molex. PCI-8 pin is best. There will be 3 12V cables, and 5 neutrals. Just wire them all up.
Hi dogie, I am confused
I bought another molex splitter but I doubt it will be any different than my previous melted one I rather use the PCI-E 6pin since I trust more the cables in my Corsair GS600 PSU
Can you please explain whether to use two yellows and blacks or only one of each for powering the board?
thanks!
So just for future reference, upon further inspection my new molex splitter claims to be 18 AWG while the old (partially melted one) didn't say anything at all...
After compare them both, the new splitter's cables seem to be stronger as well. So I suggest to update the guide to check for the AWG inscription in the cables or use the PCI-e with 8 pins connector.Its a good tell if they're unmarked, but definitely a few of the burnt ones were also labelled 18 unfortunately.
Quote
You can use a PCI-E 6 pin but again you'll be overspec, although its the same as a molex. PCI-8 pin is best. There will be 3 12V cables, and 5 neutrals. Just wire them all up.
Hi dogie, I am confused
I bought another molex splitter but I doubt it will be any different than my previous melted one I rather use the PCI-E 6pin since I trust more the cables in my Corsair GS600 PSU
Can you please explain whether to use two yellows and blacks or only one of each for powering the board?
thanks!
So just for future reference, upon further inspection my new molex splitter claims to be 18 AWG while the old (partially melted one) didn't say anything at all...
After compare them both, the new splitter's cables seem to be stronger as well. So I suggest to update the guide to check for the AWG inscription in the cables or use the PCI-e with 8 pins connector. 
Quote
You can use a PCI-E 6 pin but again you'll be overspec, although its the same as a molex. PCI-8 pin is best. There will be 3 12V cables, and 5 neutrals. Just wire them all up.
Hi dogie, I am confused
I bought another molex splitter but I doubt it will be any different than my previous melted one I rather use the PCI-E 6pin since I trust more the cables in my Corsair GS600 PSU
Can you please explain whether to use two yellows and blacks or only one of each for powering the board?
thanks!
i used 6 blacks and 6 yellows, all from 2 PCI-e connectors. With the usual molex i had overheating. No molex splitter, direct wires from PSU, that worked for me.
Jump to: