ssinc suggested in a PM and I agreed to that he mine with my 6 units for me until they can safely be sent to me at a later date. Now waiting for them to show some signs of life on my designated address on Eligius. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) For the record, I offered ssinc 3% of the total proceeds from this "hosted" mining. Setting up a separate pc for them right now actually ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Also, if anyone has a DOA unit or a unit performing way under spec PM me or e-mail me to setup an exchange as limited replacements will be available later this week. What's being considered way under spec? I know Beastlymac made a comment about being under 2GH/s I've got two that seem to end up as 'DEAD' in bfgminer after 5-10 hours, and they are also the same two that are under 2GH/s (one sits at 1.21GH/s apparently atm the other is at 1.75GH/s, they've been on for 3hr 19min thus far), it's always the same two as well.
|
|
|
I can't get the sticks to work on OSX - always time out in Bitminter.
When plugging a stick in, it comes up as a modem in networking
Am I doing something obviously wrong or is the Bitminter beta not actually functioning right yet
I believe the last that was reported from Bitminter was that they were still working on it (can't remember who it is that maintains the bitminter code atm).
|
|
|
just a dummy question. do we talk here about RED fury or BLUE fury ? Why is it named blue when no one talk/write about blue light. Maybe i forgot ( the years are here) , but i have in memory that BLUE furys will have blue light ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) hehe, could always do what I'm doing, replacing the LED's with a 3528 bi-color blue/yellow LED (PN# OSYBS4S2C1A) and I'm considering anodizing the heatsinks blue as well...
|
|
|
Yes I just got a promising email from Luke so we should have a firmware update out soon that will fix the error rate and improve the hash rate. Also people who are getting bellow 2ghs are you using windows?
Awesome news! I have 1 of 8 running on Arch Linux (MinePeon) that constantly gets below 2GH/s, but right at, it's usually at 1.95/196 GH/s, it has the same behavior on Ubuntu 13.
|
|
|
I actually built one of those using 5 Pi's! Totally useless for what we are discussing but totally cool! Neil hehe, yea, it's a neat show piece though... ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) need to make a life-size Cray-2 replica with nothing but RaspberryPi's filling it... haha
|
|
|
I am playing around with some other hardware (cubieboard 2 & beaglebone black) and while they are better off for CPU they are still not enough (and they still use SD for IO's).
I thought the beagle-bone blacks had a 2GB flash/solid state storage on them with an optional SD slot for extra storage? Yep it does. I could also use a USB HDD for storage, but it still does not solve the CPU requirement problem. Neil very true on the CPU... wait, I know... cluster 40 beagle-bone blacks! yeaaaa! lol (I had to) I'd be interested to see if something like this is possible, more from the perspective of this being more common in the future. Lots of people hosting tiny chunks of the blockchain, bonus points if none of them have to trust each other and don't have to transmit whole blocks back and forth. Probably something for another thread though if anyone wanted to get serious about it. http://www.youtube.com/watch?v=i_r3z1jYHAc
|
|
|
I am playing around with some other hardware (cubieboard 2 & beaglebone black) and while they are better off for CPU they are still not enough (and they still use SD for IO's).
I thought the beagle-bone blacks had a 2GB flash/solid state storage on them with an optional SD slot for extra storage? Yep it does. I could also use a USB HDD for storage, but it still does not solve the CPU requirement problem. Neil very true on the CPU... wait, I know... cluster 40 beagle-bone blacks! yeaaaa! lol (I had to)
|
|
|
I am playing around with some other hardware (cubieboard 2 & beaglebone black) and while they are better off for CPU they are still not enough (and they still use SD for IO's).
I thought the beagle-bone blacks had a 2GB flash/solid state storage on them with an optional SD slot for extra storage?
|
|
|
@zyk0 & @ssinc
What OS? As I've seen this before but after I recompiled BFG using 3.2.0, I haven't seen the issue since, so, I'm curious what OS you're using these on.
Ubuntu 12.04 - BFGminer 3.0.99 Personally I had shit luck on a fresh install of 12.04, but 13.10 worked like a charm within minutes with no issues. If you want I'll load up 12.04 and see if I can make a build of BFGMiner 3.2.0 (as that's what I'm using with the best success rate thus far).
|
|
|
Is there a way to log in to minepeon web page remotely? I have the port forwarded in my router, I enter my ip and then the username/password, but then nothing happens (if I was in my home network, it would ask me username/password again and then display the page)
You need to redirect the port 443... SSL connection... https://... Can I change port 443 to another (5-digit) port? I don't want bots/hackers to try bruteforcing my credentials... Changing the port isn't going to do much anything if someone was trying to "hack" your your raspberryPi, that's why they have port scanners... an open port is an open port regardless of how safe you *think* it is. It being on SSL (whether valid or not) encrypts traffic (to an extent) where you're not sending straight clear text all the time. And as far as brute-force hacks go, if you're password is so weak that one can be brute-force hacked (in any given time frame of your life) then I hate to be the bearer of bad news, but you should consider using a different password. I good thing I like to tell people is, find a phrase that means something to them, go to an online md5 tool, type in the phrase and get the hash, whola password, for extra fun, find a split point in the hash, then take from that split point on and put it to the front, or get really fun with shit and mix in different hash strings ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
60%ish hardware errors seem to be about normal
but... [2013-11-05 09:03:46] BPM0 | 5s: 2.31 avg: 2.30 u: 0.54 Gh/s | A:66 R:0+0(none) HW:2252/ 89% [2013-11-05 09:03:46] BPM1 | 5s: 1.99 avg: 1.99 u: 1.89 Gh/s | A:237 R:1+1(.84%) HW:1398/ 59% [2013-11-05 09:03:46] BPM2 | 5s: 2.29 avg: 2.29 u: 2.16 Gh/s | A:287 R:2+0(.52%) HW:1607/ 59% [2013-11-05 09:03:46] BPM3 | 5s: 2.21 avg: 2.21 u: 2.05 Gh/s | A:261 R:2+0(.76%) HW:1567/ 60%
seems like I got a couple duds.
@zyk0 & @ssinc What OS? As I've seen this before but after I recompiled BFG using 3.2.0, I haven't seen the issue since, so, I'm curious what OS you're using these on.
|
|
|
looks nice, may pick one up from you here shortly.
|
|
|
Try cgminer 3.7.0 that issue with detection should be fixed now.
CGMiner 3.7.0 is working as far as detecting the devices finally, going to let it run for an hour or so to see what numbers I get... so far the averages a looking pretty low (compared to bfgminer), but it's only been up for 4min. Here's 15 hours of using BFGMiner (3.2.0, as it's the only version I could get to compile on the rPi without causing tons of HW errors) ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Ftk1337.com%2Fimages%2Fbfgminer_320_bf_results.png&t=663&c=tu4333MyGZFi-Q) I compiled CGMiner 3.7.0, worked fine at detecting the devices (unlike previous versions of CGMiner), but the hashing numbers were a bit different, granted I only let it run for about an hour, also right before I was about to take a screenshot, libusb hit a write error which caused one of the devices to drop dramatically in hash rate. Screen shot of error: ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Ftk1337.com%2Fimages%2Fcgminer_370_bf_error.png&t=663&c=G4VDrL-AjnT_Ew) Screen shot of results: ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Ftk1337.com%2Fimages%2Fcgminer_370_bf_results.png&t=663&c=FYlUByIMaN2PaQ)
|
|
|
CGMiner seems to work much better in MinePeon than several of the previous versions (at least for me).
|
|
|
Try cgminer 3.7.0 that issue with detection should be fixed now.
CGMiner 3.7.0 is working as far as detecting the devices finally, going to let it run for an hour or so to see what numbers I get... so far the averages a looking pretty low (compared to bfgminer), but it's only been up for 4min.
|
|
|
If anyone is having high Hardware Errors while using BlueFury miners, I compiled a build of BFGMiner 3.2.0 (the same version Beastlymac suggests for Ubuntu 13.10) in MinePeon 0.2.4, just tried it out, getting ZERO hardware errors (just like I was on Ubuntu 13.10). wget http://256mining.com/downloads/minepeon_bfgminer-fury.tgz tar -xvf minepeon_bfgminer-fury.tgz cp bfgminer-fury /opt/minepeon/bin/bfgminer-fury
Then change your 'Miner Startup Settings' to: #!/bin/bash sleep 10 /usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer-fury -S bitfury:/dev/ttyACM0 -c /opt/minepeon/etc/miner.conf
^ If you are using only BlueFury miners, just having the single -S bitfury:/dev/ttyACM0 in that line, it will detect all BlueFury Miners, however, if you plan on running BlueFury Miners and Erupters, you will need to list each device individually like below. Example of 1x BlueFury Miner, 2x USB Erupter Miners: #!/bin/bash sleep 10 /usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer-fury -S bitfury:/dev/ttyACM0 -S ICA:/dev/ttyUSB0 -S ICA:/dev/ttyUSB1 -c /opt/minepeon/etc/miner.conf
(Again, you still have to specify each device...) To find your device names/list your devices: For Erupters: For BlueFury Miners:
|
|
|
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:
I'll make a post here for others (since we were chatting on MinePeon forums). The only way I could get both Erupters and BlueFuries to work together was by defining both the BlueFury and Erupters explicitly, for example my test configuration was 1x BlueFury, 2x Erupters: #!/bin/bash sleep 10 /usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S bitfury:/dev/ttyACM0 -S ICA:/dev/ttyUSB0 -S ICA:/dev/ttyUSB1 -c /opt/minepeon/etc/miner.conf
However, this really doesn't do much good, as upon boot up, while it will detect the BlueFury, it instantly goes into a panic with tons Hardware Errors. Just running the BlueFury by itself on MinePeon with BFGMiner 3.4.0 it does the same thing, I know I created a build of BFGMiner 3.2.0 on MinePeon last night, however I can't remember which box it's on at the moment (lol). EDIT: Found my build of BFGMiner 3.2.0 that I made last night for MinePeon, just tried it out, getting ZERO hardware errors, so if you are running MinePeon and getting a ton of hardware errors, here's a fix: wget http://256mining.com/downloads/minepeon_bfgminer-fury.tgz tar -xvf minepeon_bfgminer-fury.tgz cp bfgminer-fury /opt/minepeon/bin/bfgminer-fury
Then change your miner-start.sh script like so: #!/bin/bash sleep 10 /usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer-fury -S bitfury:/dev/ttyACM0 -S ICA:/dev/ttyUSB0 -S ICA:/dev/ttyUSB1 -c /opt/minepeon/etc/miner.conf
(Yes you still have to specify each device...)
|
|
|
You will need to manually assign the com ports.
Any info on this? Your answer: If your running them with eruptors though you need to identify everything seperetily like;-
#!/bin/bash sleep 10 /usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S bigpic:all -S ICA:/dev/ttyUSB0 -S ICA:/dev/ttyUSB1 -S ICA:/dev/ttyUSB2 -S ICA:/dev/ttyUSB3 -S ICA:/dev/ttyUSB4 -S ICA:/dev/ttyUSB5 -S ICA:/dev/ttyUSB6 -S ICA:/dev/ttyUSB7 -S ICA:/dev/ttyUSB8 -S ICA:/dev/ttyUSB9 -S ICA:/dev/ttyUSB10 -S ICA:/dev/ttyUSB11 -S ICA:/dev/ttyUSB12 -S ICA:/dev/ttyUSB13 -S ICA:/dev/ttyUSB14 -S ICA:/dev/ttyUSB15 -S ICA:/dev/ttyUSB16 -S ICA:/dev/ttyUSB17 -S ICA:/dev/ttyUSB18 -S ICA:/dev/ttyUSB19 -S ICA:/dev/ttyUSB20 -S ICA:/dev/ttyUSB21 -S ICA:/dev/ttyUSB22 -S ICA:/dev/ttyUSB23 -S ICA:/dev/ttyUSB24 -S ICA:/dev/ttyUSB25 -S ICA:/dev/ttyUSB26 -S ICA:/dev/ttyUSB27 -S ICA:/dev/ttyUSB28 -S ICA:/dev/ttyUSB29 -S ICA:/dev/ttyUSB30 -S ICA:/dev/ttyUSB31 -S ICA:/dev/ttyUSB32 -S ICA:/dev/ttyUSB33 -S ICA:/dev/ttyUSB34 -c /opt/minepeon/etc/miner.conf
|
|
|
On Ubuntu 12.04.3, I get the following error when running the 'sudo apt-get install bfgminer' command Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: bfgminer : Depends: libjansson4 but it is not installable E: Unable to correct problems, you have held broken packages.
I have searched on google but no luck. Any ideas? In the mean time, I have them running temporary on a windows 7 box and I am getting about 2.22 - 2.34 Ghps (per unit) with bfgminer 3.2.0. Anyone have any ideas? Use Ubuntu 13.10... best idea I got for you, since I couldn't get it working under 12.04, but 13.10 took me 2 minutes.
|
|
|
If you can't fix it, lmk I'll probably buy it I enjoy fixing things others can't ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
|