 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
The blades are already around 3.3 I think (from SSB if you buy 9) and USB miners are now around 0.12 from couple of resellers here. So given that and some delay with Canary's new GB, I think we'll see closer to 0.1 for the USB miners and 3.2-3.4 for the blades.
Under .1, is a great buy for something in-hand in couple of days. Even if it has a negative ROI, it is still better than the "promises" of the other pre-order miners. Plus for $10 or so this is a great xmas tree ornament! (if you decide to quit mining)...or a stocking stuffer, heck... use it for Halloween instead of candy!
I'm usually quite positive... But, this statement just doesn't give me very happy thoughts. |
|
|
|
|
I still don't understand..... Why not just store the datadir and swap on a thumb drive or on an external usb drive (w powered hub)? Isn't the solution really that simple?
|
|
|
|
wat u doin with dem bad miners?
Not sure. They do run, but cause restart/lockups.. Might try swapping oscillators and resistors to see what happens. Anybody out there successfully overclock the USB's? |
|
|
|
My only issue at this point is for some reason 3 out of my 25 sticks show up as BES instead of ICA and are giving me sick/dead restart problems. Before I changed to this version, I have been stable since I set it up. Impressive to say the least. I definitely want my blade connected through BFGminer... So I have isolated the 3 erupters that show up differently and pulled them, now BFG is running like a champ. Not a big deal since my windows machine is always running with my node and so I can just put the 3 "BES"sticks on there. Just thought I would add that information in case someone else is having a similar issue. This is pretty odd. They really should all show up as BES (Block Erupter Sapphire), but I'm curious as to why that is creating problems for you. What options are you using? Can you try with just -S erupter:all and not any --icarus-* options, in the same instance? Temporary workaround in any case: -S erupter:noauto will disable the autodetection of autodetect-capable Erupters (likely the 3 that show up as BES for you). I have tried -S erupter:all and --scan-serial erupter:* * is not a special character with --scan-serial, and will be ignored. Thanks for getting back so quick Luke. Whenever I try with -S erupter:all NO --icarus -I start getting sick/dead within 10-20 minutes. Whenever I try -S erupter:noauto - then only the blade shows up ----No erupters I got --scan-serial erupter:* from the ASIC readme -I guess I misunderstood the usage. The only way I've been able to get them running close to as stable as before is by using a similar command to the one I have been using since I started setting up these AsicMiner devices on BFGminer...... bfgminer.exe -o 127.0.0.1:8332 -u worker99 -p pass -o gbt.mining.eligius.st:9337 -u ITSYOURS -p pass --failover-only -G -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100 --coinbase-addr 14qi3gVPuDzcuTiJpdHCoTETFFFvG4SeD3 --coinbase-sig "BUYER99 SOLO MINE" |
|
|
|
I am assuming the new blades have a gigabit network connection. Does anyone know how to force them to 100mb full duplex?
They have a 10MB connection. Thanks, been trying to make a WIFI bridge work with it..... I'll put a little switch in-between as the bridge doesn't like talking directly to the blade. Need another switch anyway as I plan on ordering more blades very soon. |
|
|
|
My sticks never come up as ICA - they either come up as BEE or BES. BES works best, I usually expect them to stop working when they report as BEE, and when they do it's almost always cured by changing the USB port the hub is plugged in to.
Under Ubuntu 13.04 Server, the hubs worked best plugged in to the USB3 ports - under Windows best in USB2 ports. Same hubs, same machine.
The staged underrun thing seems normal, I get that here too. Mine usually ends up queuing 4 or 8.
Which switch are you using? "-S all" or "-S erupter:all" or "--scan-serial erupter:*" Icarus flags or no? Now that I moved the 3 problem children to the windows box and using -S all they do show up as ICA on there and have given me zero problems.. It has always showed me 3 as BES and the rest as ICA on the pi. Now that I have moved the 3 "oddballs" off of the pi everything has been rolling smootly but then, all of sudden about 15 of them went to ERR at the same time and all restarted.. They did ALL restart fine though. I realize it could be power or hubs or cooling or one bad erupter or a driver or etc etc... Just trying to find out more if I can since it has been so rock solid up until this point. I have been swapping ports & hubs & power adapters & erupters. Maybe running the getwork server and the erupters is a little too much for the pi? As for the queue they both (win7 miner and pi miner) have queued up, but only a little 2-4. |
|
|
|
|
I am assuming the new blades have a gigabit network connection. Does anyone know how to force them to 100mb full duplex?
|
|
|
|
I got my blades today!  Most of them are perfect... but I think one of them has a dead chip. Chip: OOOOOOOOOOOOOOOOOOOxOOOOOOOOOOOO Any way to fix that? If not, does that qualify for warranty replacement? Could just be a power issue.. |
|
|
|
That worked. Pleased to announce BFG is happily mining away with 11 Block Erupters on a TL-WR703N with a 4GB USB stick. RAM is a bit tight, but I think it'd run the HTTP proxy thingymabob for the Blades, too, if a nice developer could compile it in.  Very cool, I've been reading your posts hoping it would work out. Congratulations HellDiver! Luke, I want to thank you for what you have done and have sent a small donation your way. I recently rebuilt BFGminer on my pi with 3.2.0 and now with the new getwork option I have my USB's and my blade all happy together in one interface! My only issue at this point is for some reason 3 out of my 25 sticks show up as BES instead of ICA and are giving me sick/dead restart problems. Before I changed to this version, I have been stable since I set it up. Impressive to say the least. I definitely want my blade connected through BFGminer... So I have isolated the 3 erupters that show up differently and pulled them, now BFG is running like a champ. Not a big deal since my windows machine is always running with my node and so I can just put the 3 "BES"sticks on there. Just thought I would add that information in case someone else is having a similar issue. FYI... I have tried with -G switch and without. I have tried with the icarus timings and without I have tried -S erupter:all and --scan-serial erupter:* -S all with the icarus timings seems to give me the best results, but after a while the 3 sticks which show up as BES go to sick and sometimes dead, also randomly causing problems with other sticks in the process of restarting themselves etc. Staged work underrun will not increase automatically pass 36 keeps coming up every 2-3 min.. So far since I have removed those 3 from the equation, no messages about staged overrun and it looks like all is well. Hardware errors are also very low... Thanks for everything you do! Edit: Still no issues, stable like it always was but just got this message "staged work underrun; increasing queue minimum to 2" Doesn't seem to be a problem, I'm sure it has said this many times before (but it's been running so good I haven't been watching it at all) and sorry for being such a newb but google doesn't want to tell me what it means. |
|
|
|
god, the public, ya blame him? He sold items with the terms that future upgrades would be included. He is still yet to honour that promise, while putting new money customers first. Also very dissapointing.  |
|
|
|
When will he send out the new blades to batch 1-3 auction winners Waiting still Very dissapointing to read this... |
|
|
|
Why not put a usb on the back-plane? I was excited to hear there was a usb port on the boards and bummed to find out there isn't.
That is totally stupid. This is a standalone unit. Why would anyone be stupid and wish it to be not a stand alone unit? It's doesn't seem that stupid. Why is it better to configure each one individually? Why not USB? Not really standalone when it still needs another system to run the stratum proxy or internal getwork server... |
|
|
|
Question:
Is it okay to connect wires from two molex from the PSU than just getting a splitter? Do you HAVE to have a splitter? If not then what is the alternative. I didnt seem to find any here.
You can cut the wires on your PSU and connect them directly to the green plug. It's cleaner to do with the splitters though, and gives you a little more length to work with. |
|
|
|
|
I guess I missed something. What is the timer for?
|
|
|
|
Sounds good. Never used BFGminer before, so looking forward to the next learning curve. Will it cope with my FPGA's and USB asics as well? I guess this question belongs on another thread. As I said before I was using minepeon on the pi as it ran the usb asics from boot. I spent some time pissing about with drivers trying to get CGminer to recognise them on raspbian. minepeon is light and has no apt-get to install so I haven't spent any time trying to tweak it yet.
Running USB asics and getwork server through one instance of BFGminer on the pi right now.. All of my hardware connects as one 20GH miner. BFGminer definitely has support for FPGA. Will it run in the same instance as the blades and USB? You are probably right about that being a question for another thread..Perhaps this one? https://bitcointalk.org/index.php?topic=168174.0I say give it a shot. It will probably work.. Just gonna have a shitload of flags to set I'm sure, but thats no biggie. Here is the readme for running ASIC w/ BFGminer https://github.com/luke-jr/bfgminer/blob/bfgminer/README.ASICHere is the readme for running FPGA w/ BFGminer https://github.com/luke-jr/bfgminer/blob/bfgminer/README.FPGA |
|
|
|
YES! Hello world! I have hashes! Local stratum proxy is the answer. Thank you all for your help. Got to set-up a stratum proxy on a pc now. Late night looming.
Why not just run BFGminer on the pi? You got it running already, and could easily just compile BFGminer and use the getwork option. Just my 2 cents... |
|
|
|
BTC Guild is offically at 300,323Gh!  Funny looking back, was so happy at the first 30 GH/s, and 300 GH/s  . 300 GH/s was one of the first big bottlenecks for the old pool software! .............................. |
|
|
|
Thanks Pistachio. Tried as you suggested using gwp on bitparking and bitminter. Still no hashes.
Settings:
Ports = 8332,8332
Server addresses = mint.bitminter.com,mint.bitminter.com
user:pass = enginehead_blade:pass,enginehead_blade:pass
also keeps restarting every minute or so!
user and pass are correct.
I haven't tried a stratum proxy yet. Will try that next.
Since you are running linux you can use the latest version of BFGminer and it has an internal getwork server. Was easy to set up and has been working flawlessly. It's nice to control all of my ASIC's from one "miner." Slushs mining proxy is also very easy to set up. Either way it's going to work best to run something local on your network as a "bridge" between your getwork blade and a stratum server. |
|
|
|
|
