|
Hello,
I've been mining on p2pool @ 6.5GH/s for a couple of weeks, and I haven't seen any payouts yet. Is this normal? Is there a better pool I can use (one resistent to ddos attacks)?
|
|
|
|
Hmm,
I have to say, the response is somewhat underwhelming.
Sure there are a few people who want it but the amount of effort required to do this seems unwarranted and I would be better off just putting all of my effort into MinePeon ARM.
Neil
+1 for this. I would prefer you continue to work on th ARM version. |
|
|
|
|
Done.
I now have a table summarising my expenditure, balance, and hashrate on the first page.
The table looks fine in preview mode, but the columns aren't rendering nicely on the live page. Oh well.
|
|
|
|
LogicalUnit, what is your current GH/s? I'm considering a 100 GH/s unit for now and possibly the BFL 600 GH/s in the short future. April / May looks like a huge drop off in profitability for everyone - regardless of your setup - big or small, it seems difficulty is driving profitability way down.
My 3 Blue Fury units average about 6.5 GH/s (I sold my ten block erupters). I'm a little disappointed with their performance -- they are below the 2.2 to 2.6 advertised range. If you can get your hands on one of the Black Arrow Prospero X-1 units for $400, I would jump on it. I'm planning on selling my rig and getting one of those myself. |
|
|
|
|
Stability Improvements
I've been having some issues with instability, and I'm pretty sure it's related to my wireless connection. I've rejigged my home network and the RPi now has a wired connection. Hooray!!
|
|
|
|
Hi all, I just removed the Block Erupters from my rig, leaving me with 3 Blue Fury ASICs connected to my MinePeon. I reset the command line to "default bfgminer" and now the miner starts and connects to my pools, but it does not detect the mining hardware.
What command parameters do I need to make Blue Fury ASICs work with bfgminer 3.3.0?
Thanks
Update your MinePeon Just installed MinePeon 0.2.4.1 with bfgminer 3.4.0, and it's not automagically detecting my Blue Furies. |
|
|
|
|
Hi all, I just removed the Block Erupters from my rig, leaving me with 3 Blue Fury ASICs connected to my MinePeon. I reset the command line to "default bfgminer" and now the miner starts and connects to my pools, but it does not detect the mining hardware.
What command parameters do I need to make Blue Fury ASICs work with bfgminer 3.3.0?
Thanks
|
|
|
|
|
Sell, sell, sell
Just sold my 10 block erupters for 0.035 BTC each plus shipping. I'm left with 3 Blue Fury ASICs, mining at 6,427 MH/s.
|
|
|
|
|
I was right
BitCoin just hit AUD$870. If I had not reinvested, I would have made a profit. Not as much as if I'd just bought and held BTC, but all the naysayers about never achieving ROI have been -- suddenly -- proven wrong. My original prediction that the price of BTC would go up as more people adopted it was spot on.
|
|
|
|
|
Woohoo, I think I've got it all working. The trick was to put only 3 ASICs in the daisy-chained hub.
|
|
|
|
Grrr, I'm having lots of stability issues running three hubs from the RPi's two USB ports. I've removed one hub, so now I'm running 5x USB Erupters and 3x Blue Fury ASICs (+1 wireless dongle)
The pi's USB out is from a hub anyway. Try plugging the hub that will be daisy chained into the very first port of one of the hubs. Good suggestion but I still get two unstable Block Erupters when this happens. |
|
|
|
I have been able to get Block Erupters working concurrently with Blue Fury ASICs on MinePeon with bfgminer 3.3.0  Sadly, some of the ASICs become unstable when I try to daisy-chain more than 1 hub per usb port on the Pi. Only four Blue Fury units will fit on a DUB-H7 due to their large profile. Here's what I put in my Miner Startup Setting: #!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S ICA:/dev/ttyUSB0 -S ICA:/dev/ttyUSB1 -S ICA:/dev/ttyUSB2 -S ICA:/dev/ttyUSB3 -S ICA:/dev/ttyUSB4 -c /opt/minepeon/etc/miner.confNote that I do not manually specify the Blue Fury units. Doing this caused MinePeon to crash when I plugged in a second hub. |
|
|
|
|
Grrr, I'm having lots of stability issues running three hubs from the RPi's two USB ports. I've removed one hub, so now I'm running 5x USB Erupters and 3x Blue Fury ASICs (+1 wireless dongle)
|
|
|
|
Sorry I wasn't clear: how do I identify which ports are Block Erupters, and which ports are Blue Fury ASICs? Currently with just the Blue Fury units there are no ttyUSB devices on my MinePeon: [minepeon@minepeon ~]$ ls /dev/tty*
/dev/tty /dev/tty19 /dev/tty3 /dev/tty40 /dev/tty51 /dev/tty62
/dev/tty0 /dev/tty2 /dev/tty30 /dev/tty41 /dev/tty52 /dev/tty63
/dev/tty1 /dev/tty20 /dev/tty31 /dev/tty42 /dev/tty53 /dev/tty7
/dev/tty10 /dev/tty21 /dev/tty32 /dev/tty43 /dev/tty54 /dev/tty8
/dev/tty11 /dev/tty22 /dev/tty33 /dev/tty44 /dev/tty55 /dev/tty9
/dev/tty12 /dev/tty23 /dev/tty34 /dev/tty45 /dev/tty56 /dev/ttyACM0
/dev/tty13 /dev/tty24 /dev/tty35 /dev/tty46 /dev/tty57 /dev/ttyACM1
/dev/tty14 /dev/tty25 /dev/tty36 /dev/tty47 /dev/tty58 /dev/ttyACM2
/dev/tty15 /dev/tty26 /dev/tty37 /dev/tty48 /dev/tty59 /dev/ttyAMA0
/dev/tty16 /dev/tty27 /dev/tty38 /dev/tty49 /dev/tty6 /dev/ttyprintk
/dev/tty17 /dev/tty28 /dev/tty39 /dev/tty5 /dev/tty60
/dev/tty18 /dev/tty29 /dev/tty4 /dev/tty50 /dev/tty61
|
|
|
|
You will need to manually assign the com ports.
Any info on this? |
|
|
|
Try;-
#!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S bigpic:all -c /opt/minepeon/etc/miner.conf
In your startup.
Disconnected the Block Erupters and tried that, but now bfgminer doesn't even start. Fixed it! Blue Fury units are running!! Now, how do I identify the Block Erupters so I can get everything working simultaneously? |
|
|
|
Try;-
#!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S bigpic:all /opt/minepeon/etc/miner.conf
In your startup.
Disconnected the Block Erupters and tried that, but now bfgminer doesn't even start. |
|
|
|
|
Show Posts
