I came home last night to one of my older style blades not powered on.
After some testing with a multi meter, it looks like the diode d9 is not conducting and the coil isn't powered.
Does anyone know if asicminer will provide a warranty for it?
Topic: [Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 32. (Read 580761 times)
is it possible to add two ports to the http-port option? The reason I ask is that my 2 blades show up all as SGW 0, and I`d like them to show up seperately.
Thanks
Thanks
need to make sure you use different usernames for each blade
is it possible to add two ports to the http-port option? The reason I ask is that my 2 blades show up all as SGW 0, and I`d like them to show up seperately.
Thanks
Thanks
Regarding proxy software (stratum) I have to reccomend BFGMiner over Slush's proxy. I've used both for awhile now and BFG comes out much better. The blades don't have near as many issues, and the work shares are more consistent.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
Is this the Windows or Linux BFGMiner? What code do you use in BFG so it sees the Blades?
Both Windows and Linux. You use the --http-port flag to set the getwork port. By default it's 8332 I believe, but you could use anything as long as the blade uses the same.
Basically start BFG as you normally would, add --http-port 8332, and point your blades to the server running BFG using 8332 and they'll connect up. For blade setup make sure each blade has a unique worker name, password doesn't matter.
ok, I'm sett5ing up an old style blade. I have this issue:
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
Quote
Also, a bit of a tip for fresh asic Blade Runners (heh):
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
If you have a crossover cable around you can plug the blade straight into your network card in your pc. You will manually have to set the pc's Ip to match the blades current configuration for the ip subnet.
Then navigate to the blade settings, change them to work with your router configuration. Then disconnect the blade and plug it into the router, it should find it by then. Restore your pc original Ip setting and you should be up an running
Is a crossover cable really needed? i thought that i read somewhere that network cards autosense. or was that something else?
ok, I'm sett5ing up an old style blade. I have this issue:
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
Quote
Also, a bit of a tip for fresh asic Blade Runners (heh):
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
If you have a crossover cable around you can plug the blade straight into your network card in your pc. You will manually have to set the pc's Ip to match the blades current configuration for the ip subnet.
Then navigate to the blade settings, change them to work with your router configuration. Then disconnect the blade and plug it into the router, it should find it by then. Restore your pc original Ip setting and you should be up an running
Is a crossover cable really needed? i thought that i read somewhere that network cards autosense. or was that something else?
ok, I'm sett5ing up an old style blade. I have this issue:
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
Quote
Also, a bit of a tip for fresh asic Blade Runners (heh):
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
If you have a crossover cable around you can plug the blade straight into your network card in your pc. You will manually have to set the pc's Ip to match the blades current configuration for the ip subnet.
Then navigate to the blade settings, change them to work with your router configuration. Then disconnect the blade and plug it into the router, it should find it by then. Restore your pc original Ip setting and you should be up an running
ok, I'm sett5ing up an old style blade. I have this issue:
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
Quote
Also, a bit of a tip for fresh asic Blade Runners (heh):
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch.
I finally got my bade going.
When I initially set it up I was using 10.0.1.60/255.255.255.0 as my IP address for the blade behind a PIX 515E firewall. It would start to get work right away but then within two minutes the blade would reboot due to not receiving any more work.
What I had to do was put a Linksys router between my pix 515E and the blade and use an IP of 192.168.1.x in order for it the blade to work as it should.
Just throwing that out there.
When I initially set it up I was using 10.0.1.60/255.255.255.0 as my IP address for the blade behind a PIX 515E firewall. It would start to get work right away but then within two minutes the blade would reboot due to not receiving any more work.
What I had to do was put a Linksys router between my pix 515E and the blade and use an IP of 192.168.1.x in order for it the blade to work as it should.
Just throwing that out there.
I tried zet mining with my blade. Ive been getting equal shares and rejects from Zetpool in a 4 hour period
3440 Accepted Rejects 215+3123 HW 2%
Is there a cause for this? I switched to zeta.dsync.com and received 3100 shares in 8 hours.
Similar issues is Asic Coin, I have high "Job Not found" errors
I use Bfgminer, since Mining Proxy, looses connection to my Blade often
3440 Accepted Rejects 215+3123 HW 2%
Is there a cause for this? I switched to zeta.dsync.com and received 3100 shares in 8 hours.
Similar issues is Asic Coin, I have high "Job Not found" errors
I use Bfgminer, since Mining Proxy, looses connection to my Blade often
Regarding proxy software (stratum) I have to reccomend BFGMiner over Slush's proxy. I've used both for awhile now and BFG comes out much better. The blades don't have near as many issues, and the work shares are more consistent.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
Is this the Windows or Linux BFGMiner? What code do you use in BFG so it sees the Blades?
i use raspberry pi
raspian + newest bfg
git clone, automake, configure (tricky), make and done
Regarding proxy software (stratum) I have to reccomend BFGMiner over Slush's proxy. I've used both for awhile now and BFG comes out much better. The blades don't have near as many issues, and the work shares are more consistent.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
Is this the Windows or Linux BFGMiner? What code do you use in BFG so it sees the Blades?
Regarding proxy software (stratum) I have to reccomend BFGMiner over Slush's proxy. I've used both for awhile now and BFG comes out much better. The blades don't have near as many issues, and the work shares are more consistent.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
+1.
Less hassle all round.My bfg 3.2.1 been going for 4 days straight no issues
Regarding proxy software (stratum) I have to reccomend BFGMiner over Slush's proxy. I've used both for awhile now and BFG comes out much better. The blades don't have near as many issues, and the work shares are more consistent.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
In addition to making sure the blades work like a charm, it's nice being able to see aggregate stats on the blade farm in one spot without using html. I'm convinced that html request processing on the blade's part causes network issues for the blades.
Anyhow, 3 thumbs up to luke-jr and bfgminer.
For this thread to be considered 'comprehensive', I suggest the OP provide software proxy info on the first post, as the thread has had folks inquiring about it. I suggest BFGminer as the primary focus, Slush's should also be mentioned. Just a suggestion.
do you know how to run blades with raspberry pi (raspian) ?
bfgminer 3.2.90
to reproduce
git clone https://github.com/luke-jr/bfgminer.git
./autogen.sh
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-microhttpd
make
./bfgminer --http-port 8332
./bfgminer: --http-port: unrecognized option
thanks
try: (difference with "lib" in --with)bfgminer 3.2.90
to reproduce
git clone https://github.com/luke-jr/bfgminer.git
./autogen.sh
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-microhttpd
make
./bfgminer --http-port 8332
./bfgminer: --http-port: unrecognized option
thanks
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-libmicrohttpd
Question:
Does my 100mbps network switch have enough throughput to cope with 2 blades at 10.3 gh and 2 other miners (on the way) using ethernet (rated at 32gh each)?
The reason I ask is because I seem to be getting a lot of rejected/stale shares with my blades. my total hash rate currently is approx 22.5gh with the blades.
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
Does my 100mbps network switch have enough throughput to cope with 2 blades at 10.3 gh and 2 other miners (on the way) using ethernet (rated at 32gh each)?
The reason I ask is because I seem to be getting a lot of rejected/stale shares with my blades. my total hash rate currently is approx 22.5gh with the blades.
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
I'm having odd behaviours with the three I have running through BFGMiner - they'll hash fine for hours on end, then "sulk" for a few hours, not accepting the work provided, then carry on working.
Very similar to what I get. my 2 do about 2000 shares then bash out 5 rejected then continue hashing. bfg shows my rejected rate at 4%. That just seems high to me.
Question:
Does my 100mbps network switch have enough throughput to cope with 2 blades at 10.3 gh and 2 other miners (on the way) using ethernet (rated at 32gh each)?
The reason I ask is because I seem to be getting a lot of rejected/stale shares with my blades. my total hash rate currently is approx 22.5gh with the blades.
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
Does my 100mbps network switch have enough throughput to cope with 2 blades at 10.3 gh and 2 other miners (on the way) using ethernet (rated at 32gh each)?
The reason I ask is because I seem to be getting a lot of rejected/stale shares with my blades. my total hash rate currently is approx 22.5gh with the blades.
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
The Microchip ethernet adapter on the blades is 10Mbps adapter.This is plenty for the traffic the blade could generate (tops of about 60kpbs I think).
I'm having odd behaviours with the three I have running through BFGMiner - they'll hash fine for hours on end, then "sulk" for a few hours, not accepting the work provided, then carry on working.
And I've got my handy HTML page to watch them all side by side, and auto refresh the stats (I've got BFGminer on 8330, and mining_proxy on 8331. the blades sulk with both of them at the same time, so is supect I've got problems with access to BTCGuild (the pool I use), I suppose I should add a different pool instead...)
Does my 100mbps network switch have enough throughput to cope with 2 blades at 10.3 gh and 2 other miners (on the way) using ethernet (rated at 32gh each)?
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
Yes it does. Mining uses a few kb/s, a 100Mb switch is plenty. Are you using a local proxy?
I'm using bfg 3.2.1 on a win 7 laptop. bbxx, I dont have a clue about linux! I'd love to get a pi and mess about to get it to work, but I'm not sure I have the patience. I know windows 7, so decided to stick with it.
do you know how to run blades with raspberry pi (raspian) ?
bfgminer 3.2.90
to reproduce
git clone https://github.com/luke-jr/bfgminer.git
./autogen.sh
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-microhttpd
make
./bfgminer --http-port 8332
./bfgminer: --http-port: unrecognized option
thanks
bfgminer 3.2.90
to reproduce
git clone https://github.com/luke-jr/bfgminer.git
./autogen.sh
./configure --disable-opencl --disable-bitforce --disable-adl --disable-modminer --disable-ztex --disable-avalon --disable-icarus --disable-modminer --disable-x6500 --with-microhttpd
make
./bfgminer --http-port 8332
./bfgminer: --http-port: unrecognized option
thanks
Does my 100mbps network switch have enough throughput to cope with 2 blades at 10.3 gh and 2 other miners (on the way) using ethernet (rated at 32gh each)?
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
Does anyone know what how much network throughput Blades use per second? surely its Kb and not Mb?
Yes it does. Mining uses a few kb/s, a 100Mb switch is plenty. Are you using a local proxy?
Jump to: