I havent kept up with P2pool for so long. Way back when i tried it with GPUs more than a year ago, its very resource hungry and variances were so high.
Still resource hungry, still high variance. I was really keen to use P2Pool, and ran it for several months, but to be honest it was just too much - it needed a fast machine to run it, and payouts were pretty woeful. Half of any mining profits (if I got any at all) was wasted on power to run the i3 machine needed to make P2Pool perform anywhere near well enough. I tried to run it on a Sempron dual core 2.5GHz CPU, and it struggled with a measly 5GH/s. Someone said they ran P2Pool on a Celeron 847, but I think they were huffing glue. Now I'm up to 35GH/s, I gave up on P2Pool. I get far better returns with less bother on a 'real' pool. |
|
|
|
The readme that I have says nothing about blades, jsut thats they have been added to the support of BFGminer. Anyhow I don't run win32... so I don't know what I'm going to do to fix this bullshit...
Well, I copied that straight out of the README.ASIC - it's not my fault you can't download some files properly. You asked for help, I told you how to get it working. If you'd spent 5 minutes reading the BFGMiner thread, you'd see why it's only Win32 and Linux, but apparently you prefer posting a new thread then complaining bitterly when the solution doesn't suit you. Next time, you can stick it up your ass.  My bad, wasn't even angry at you. And all I read was the README not the .asic version. I'm mad because these blades have been nothing but up's and down's and its only been on the networking end. I figured the electrical work would be the hard part but that wasn't the case at all. I just want to get these things up and running. As I have no experience running BFG miner outside of minepeon on my Raspberry pi... Could someone show me what I would type in for the command to run a blade on BFGminer? Yeah, I have two of them, one has been running perfectly, the other is up and down like a cheap whore's knickers. You need to: bfgminer.exe -G --http-port 8330 BFG should start and ask you for pool details etc. Set those up and save the config as usual. Once BFG is running, point the Blade to the IP address of the PC and port as 8330. Eac Blade must have a unique and non-important username and password. I've found BFG crashes first time the Blade connects, just running BFG again allows the Blade to connect OK. Luke-Jr is aware of the crashing issue. Once it's running it works OK. |
|
|
|
The readme that I have says nothing about blades, jsut thats they have been added to the support of BFGminer. Anyhow I don't run win32... so I don't know what I'm going to do to fix this bullshit...
Well, I copied that straight out of the README.ASIC - it's not my fault you can't download some files properly. You asked for help, I told you how to get it working. If you'd spent 5 minutes reading the BFGMiner thread, you'd see why it's only Win32 and Linux, but apparently you prefer posting a new thread then complaining bitterly when the solution doesn't suit you. Next time, you can stick it up your ass. |
|
|
|
LilGhost
Use Google translator to view in english
Or if you use a decent browser (Chrome) it does it automatically. |
|
|
|
so u say the ica timing not needed? mmmm
ed. tried it getting this BES 2: Work division autodetection failed (assuming 2): got 00000000 ?
BES 4: Work division autodetection failed (assuming 2): got 00000000
Never seen that Work Division thing. The ICA timing isn't needed. |
|
|
|
It is open source, rewrite it to do what you want it to do.
I'm not a coder. But I know inefficient code when I see it. Point some out in there that you see ... You seem to think you have all the answers, why don't you? Your the one who said "I know inefficient code when I see it" Or where you taking medication at the time? When it runs like shit on anything less than a 3.3GHz i3, and still pegs a core at 100%, then it's OBVIOUSLY inefficient code. Because code makes a program. If the program runs like shit, then it's obviously the code that's crap. Bitcoind doesn't do much, there's no reason for it to need so many CPU cycles and half a gig of RAM. It's just sloppy. I might not know how a car engine works, but I know when an engine runs like crap. You're just being obtuse, you know what I'm talking about (see how I used 'you're' and not 'your'?) |
|
|
|
Is there a specific order I have to add the -S opencl:noauto?
Yeah, you don't put it in at all. -G is the option you need. The one you're using was depreciated long ago. |
|
|
|
You need to read README.ASIC. Info is there.  Basically you need to add --http-port 8330 to the end of your command line, then point your Blade to the IP of the machine running BFG. Each Blade needs to have a unique username (it doesn't matter what, anything will do as long as it's unique). Note this option is only available on Win32 version, and under Linux. OpenWRT and Win64 don't have it. Here's the section in README.ASIC if you couldn't be bothered reading it yourself: BLOCK ERUPTER BLADE
-------------------
Blades communicate over Ethernet using the old but simple getwork mining
protocol. If you build BFGMiner with libmicrohttpd, you can have it work with
one or more blades. First, start BFGMiner with the --http-port option. For
example:
bfgminer --http-port 8330
Then configure your blade to connect to your BFGMiner instance on the same port,
with a unique username per blade. It will then show up as a SGW device and
should work more or less like any other miner. |
|
|
|
C:\miner\bfgminer321\bfgminer.exe -o pool -u worker1 -p password1 -L log.txt -G -S erupter:all
Fixed.  |
|
|
|
|
Run it at "Low" speed. If that works, and you get failures at "High" speed, then you need to crank up the voltage.
I have two Blades, one is perfectly stable at 1.15v, the other isn't so much and will need a bit more. The second one intermittently reboots, and some of the chips X out.
I'm running mine off a Corsair CX750 - I was using an older Zalman 1000W unit before which didn't seem to like running with no 5v/3.3v load. The new Corsair runs perfectly.
|
|
|
|
It is open source, rewrite it to do what you want it to do.
I'm not a coder. But I know inefficient code when I see it. Point some out in there that you see ... You seem to think you have all the answers, why don't you? |
|
|
|
|
Huh, I now read it as Blue PCB and Red LED. I'm sure it said Blue LED earlier...
|
|
|
|
Hello, i personally use CGminer as it easy to setup. you can run cgminer with no GPU and change no settings. if you would like me to type a little guild just say Totally useless post. He asked how to work bfgminer with 50BTC, he didn't ask how easy you thought a different program was to use. OP, you need to use: bfgminer.exe -G -S erupter:all Then go to Pool Management menu, Add Pool, then put in when asked: pool.50btc.com:8332 Your bitcoin addressAnything as PasswordThen go to Settings Menu, then key W which saves your configuration. Simple. |
|
|
|
fI you are tired of the problems with windows then it is time to try linux.
There's as many problems with ATI's retarded drivers under linux as there are under Windows. |
|
|
|
|
Please reserve a 2nd one for me, OC3k. I'll send payment tomorrow/Tuesday (waiting for Bitcoin-Qt downloading the blockchain again, time passes FFS)
|
|
|
|
I know you're busy with the BitFury code, Luke-Jr, but any ETA on the stratum proxy support on BFGMiner? I'd love to run my rig off an OpenWRT box, save running a PC in the house all the time...or even the http getwork server for OpenWRT.  I want to get every little bit of use out of that little TP-Link. |
|
|
|
i keep getting HW errors 100% on some of the usb erruptors. when i test them on another pc they test fine. i tried uninstalling(delete driver) a reinstalling(reinstall driver)
Almost always power issues. |
|
|
|
Poor language fallacy Google Translate it is. |
|
|
|
my miner went idol
American Idol? Idle is the word you're looking for. Any router worth using will restart the connection if it dies. |
|
|
|
|
Keep them red. Please. Don't be sucked in to the "Blue LED" bullshit - everything has blue LEDs on it now, and they're a blight.
|
|
|
|
|
Show Posts
