rekweam
Newbie
Offline
Activity: 37
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 07, 2013, 05:39:58 PM |
|
maybe you guys can point me in the right dirrection, i finally got the board hashing on a proxy by using mining proxy.exe with the "-o mint.bitminter.com -p 3333" argument according to the gui i am hashing about 8000MHS but bitminter is showing under 1gps so about 700 difference http://i146.photobucket.com/albums/r262/ertgunner/Untitled_zps3d0d4ff5.pngdo i have the port set right in the GUI? it is the only one i can get to work, i have tried 3333 and 5050 but it just stalls my proxy Bitminter also outputs an estimation based on number of proofs returned. So what you see on their site is a ruff idea of what your hashing. I have 10 blades running and most of the time bit minter shows me 105-120ghps when i am usually doing a solid 111ghps.
|
|
|
|
dogie (OP)
Legendary
Offline
Activity: 1666
Merit: 1185
dogiecoin.com
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 07, 2013, 08:05:54 PM |
|
Added pinout info to OP: My cables are braided or aren't color coded: See below diagram for pin-outs. ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi1279.photobucket.com%2Falbums%2Fy530%2Fdogiee%2Fth_5_zps00eb3a34.png&t=665&c=QgbE6BnoNtnlDA)
|
|
|
|
bliskars
Newbie
Offline
Activity: 20
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 07, 2013, 10:42:31 PM |
|
Hey dogie wondering if you could help me out.
I have a 6 pin PCI-e to 4 pin molex connecter. Looking at your guid and drawings I figured I need to plut in 2 yellow cables and 4 black cables. If I only have 3 black cables is that going to be a problem since its a 6 pin connector and not an 8?
Whats the best way to plug it in that way?
|
|
|
|
dogie (OP)
Legendary
Offline
Activity: 1666
Merit: 1185
dogiecoin.com
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 07, 2013, 11:22:44 PM |
|
Hey dogie wondering if you could help me out.
I have a 6 pin PCI-e to 4 pin molex connecter. Looking at your guid and drawings I figured I need to plut in 2 yellow cables and 4 black cables. If I only have 3 black cables is that going to be a problem since its a 6 pin connector and not an 8?
Whats the best way to plug it in that way?
6 pin isn't great, and especially STILL COMING FROM ONE MOLEX. Use your 4 pin ATX, they're designed for that current typically.
|
|
|
|
bliskars
Newbie
Offline
Activity: 20
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 07, 2013, 11:29:22 PM |
|
4 Pin atx has less cables right? I saw from you picture you did the following config: 1 yellow 1 yellow 2 black 2 black with 4 atx I can only do 1 yellow 1 yellow 1 black 1 black and with 6 pin to 4 molex 1 yellow 1 yellow 2 black 1 black Isn't 6 pin better? I guess I can just chop the power supply but it has 2 8 pins. Any idea how I should go about it? Heres the power supply I have. I have to power 3 blades http://www.amazon.com/Corsair-430-Watt-Certified-Compatible-Platforms/dp/B004W2T2TM
|
|
|
|
matt4054
Legendary
Offline
Activity: 1946
Merit: 1035
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 07, 2013, 11:32:32 PM |
|
Hey guys,
I have a couple of Blades running for the past few months and I've been tweaking them a bit when running into issues with the chips, i.e. when I was getting one or more X in the "Chip: ..." diagnostics line.
One single X (might be XX), or a couple of them scattered among O's:
Probably heat related. Try power down, 5 min cool down and restart. Your Blade may require more cooling.
XXXX or XXX (might be XX), sticky after power cycle
Probably voltage related. Locate the corresponding power lane, and use a multimeter to adjust the voltage to the required level (1.06 for low clock, 1.2 for high clock)
All XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
If 5 min cool down doesn't help,
- check PSU voltage under load (should be near 12V) - check power lanes voltage (should be 1.06 or 1.2V) - if low clock is OK but not high, your power lanes may need 1.2 instead of 1.06 V
|
|
|
|
sidehack
Legendary
Offline
Activity: 3360
Merit: 1859
Curmudgeonly hardware guy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 01:15:28 AM |
|
The only thing registered is the run time, which goes up to around 2min15secs before the blade automatically restarts.
I've sifted through most of this thread to find out what might be the issue but this has proved unfruitful.
Does anyone know what might be the issue?
Did you try hitting "Switch server"? Sometimes these guys get locked and won't connect until you tell it to look at the secondary. Happened to me several times.
|
|
|
|
|
pluMmet
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:35:05 AM Last edit: December 08, 2013, 12:23:47 PM by pluMmet |
|
My Blades (2 of them) stopped working 2 days ago and I have no idea why.
On the Config screen I have no "x"'s and it's been great until now.
My whole system is on a UPS system even the cooling so I know it's never gotten hot and I'm stuck on why this has happened.
I've been using them with getwork which I keep seeing people trash but that is why I bought them and the rest of my equipment is utilized anyway.
I had an issue a week or so ago due to eligius going down and me scrambling to get the blades on any getwork system. eventually I got it back on eligius and it had been fine until 2 days ago.
I now have to divert a cpu and finally got them working but only using proxy on Slushs pool and that was 2 days ago (would not work on my preferred pool or the 2 others I tried).. I just found out that after initially reporting my blades as generating shares slushes pool though accepting hashes from me the whole time is not reporting them as credit to me and though my Blades are working fine right now Slushes pool says 0/mh. They were reporting fine when I final got them running 2 days ago and it looks like within 2 or 3 hours the pool just started not noticing that my workers have been doing their work.
checking on my workers on eligius is a great process on slushes pool its a nightmare just logging in.
I'm at my wits end with these Blades... They only work on 1 pool now and that pool in my mind is just horrible.
Right now I can put them to hash on a getwork pool and they do nothing..I put them back to mine proxy on Slushes pool and they are hashing away... but are not showing up on slushes pool at all.
Resetting my proxy terminal might get slushes pool to recognize but this is the reason I left that pool to begin with.
The proxy for what ever reason will not accept my doing stratum on another pool it just ignores my "-"flags. I have no choice in the matter.
WTF do I do?
Oh and also they hashed @ 10-11/mh on getwork and now 8/mh with proxy so boooo to you getwork haters...
|
|
|
|
sidehack
Legendary
Offline
Activity: 3360
Merit: 1859
Curmudgeonly hardware guy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 03:22:25 PM |
|
What's your command line look like for the proxy?
|
|
|
|
pluMmet
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 04:11:35 PM Last edit: December 08, 2013, 04:42:04 PM by pluMmet |
|
What's your command line look like for the proxy?
I wanted it to use Eligius so I used (Dogies suggestion): mining_proxy.py -o mining.eligius.st -p 3334 -cu 1yourSweetCoinsComeToThisAddress -cp x Not only did it not work the terminal ignored that and was trying to connect to Slushs pool. I ended up just doing: mining_proxy.py which had the slushs stuff already going and the blades synced up right away. It looks like the proxy.py has been nurfed to just use slushes pool. I d/l'd two days ago for the slushes pool site and it's not .tar anymore but .zip. Still linux of course.. well py anyway. I have them running now even though slushs pool is not awarding me anything. Beyond that this is ridiculous. I had been using getwork just fine for months.. I obviously know how to do that but the blades just won't do it. v2 blades btw.
|
|
|
|
Theo1355
Newbie
Offline
Activity: 46
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 08:50:36 PM |
|
What's your command line look like for the proxy?
I wanted it to use Eligius so I used (Dogies suggestion): mining_proxy.py -o mining.eligius.st -p 3334 -cu 1yourSweetCoinsComeToThisAddress -cp x Not only did it not work the terminal ignored that and was trying to connect to Slushs pool. I ended up just doing: mining_proxy.py which had the slushs stuff already going and the blades synced up right away. It looks like the proxy.py has been nurfed to just use slushes pool. I d/l'd two days ago for the slushes pool site and it's not .tar anymore but .zip. Still linux of course.. well py anyway. I have them running now even though slushs pool is not awarding me anything. Beyond that this is ridiculous. I had been using getwork just fine for months.. I obviously know how to do that but the blades just won't do it. v2 blades btw. Dude, I'm having the same problem with getwork-- it's so frustrating, especially when I didn't change anything, the blades just stopped connecting. Let me know if you get it figured out; I'll reciprocate if I discover what's happening.
|
|
|
|
pluMmet
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:06:23 PM |
|
What's your command line look like for the proxy?
I wanted it to use Eligius so I used (Dogies suggestion): mining_proxy.py -o mining.eligius.st -p 3334 -cu 1yourSweetCoinsComeToThisAddress -cp x Not only did it not work the terminal ignored that and was trying to connect to Slushs pool. I ended up just doing: mining_proxy.py which had the slushs stuff already going and the blades synced up right away. It looks like the proxy.py has been nurfed to just use slushes pool. I d/l'd two days ago for the slushes pool site and it's not .tar anymore but .zip. Still linux of course.. well py anyway. I have them running now even though slushs pool is not awarding me anything. Beyond that this is ridiculous. I had been using getwork just fine for months.. I obviously know how to do that but the blades just won't do it. v2 blades btw. Dude, I'm having the same problem with getwork-- it's so frustrating, especially when I didn't change anything, the blades just stopped connecting. Let me know if you get it figured out; I'll reciprocate if I discover what's happening. Will do, thanks. It's a serious issue as I've tried lots of getwork pools and the blades don't work on any of them.
|
|
|
|
Theo1355
Newbie
Offline
Activity: 46
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:16:32 PM |
|
Will do, thanks.
It's a serious issue as I've tried lots of getwork pools and the blades don't work on any of them.
Totally-- the weird thing is they were designed for getwork. I even did a factory reset, reconfigged and it still doesn't work. I'll maybe restart my router, and then I'll go to stratum though I'm not optimistic.
|
|
|
|
sidehack
Legendary
Offline
Activity: 3360
Merit: 1859
Curmudgeonly hardware guy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:26:11 PM |
|
Have you tried configuring worker/pass in the blade config and not using -cu -cp? Have you tried changing the getwork port -gp in case something on your local machine is using it?
|
|
|
|
Theo1355
Newbie
Offline
Activity: 46
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:31:21 PM |
|
Have you tried changing the getwork port -gp in case something on your local machine is using it?
The 'Web Port' that's usually 8000?
|
|
|
|
sidehack
Legendary
Offline
Activity: 3360
Merit: 1859
Curmudgeonly hardware guy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:45:24 PM |
|
No, the getwork port that is usually 8332. The -gp option in mining_proxy changes this, and it needs to match the blade's "Pool ports" setting.
|
|
|
|
Theo1355
Newbie
Offline
Activity: 46
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:47:31 PM |
|
No, the getwork port that is usually 8332. The -gp option in mining_proxy changes this, and it needs to match the blade's "Pool ports" setting.
Okay, do you still have to input twice (I assume so?)
|
|
|
|
sidehack
Legendary
Offline
Activity: 3360
Merit: 1859
Curmudgeonly hardware guy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:50:54 PM |
|
Yeah, one for each pool\user:pass set.
|
|
|
|
Theo1355
Newbie
Offline
Activity: 46
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 08, 2013, 11:58:36 PM |
|
Got it. However, the port on the site is 8337 (just checked). Can I go ahead and use something else? I thought that was the port on their server? I'd give you a screenshot but I had trouble uploading. Sorry, I'm still (really) a noob at all this ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
|
|