I meant to try Eligius earlier, I haven't used it in a few weeks now... but I have made most of my btc there... anyhow..

Switched the pool, I see 4 at 2.6GH/s to 3GH/s, going to going to give it a little while, but I am seeing much better numbers off the bat with Eligius (still have yet to see a HW error!).

If this were true, why would Beastlymac stating 2.7GH/s on his own system, of course, I'm assuming he would use the same firmware (and I can't see he any reason why he wouldn't nor do I doubt he didn't use the same firmware to flash the chips).

Furthermore, I've seen one sit at 2.659GH/s - 2.8xxGH/s for about an hour, granted one out of eight and after I restarted the miner to add some api parameters for BFGMiner, I haven't seen anything that high yet again.

I'm up and running now on Win7, Ubuntu 13, Raspbian - Only on BFGMiner with all of them, eventually I gave up on CGMiner today...
(Of course being me, I just moved all the miners to the Ubuntu machine and enabled SSH... trying to work on a build of BFGMiner that will work with MinePeon atm.)

I tried the D-Link HUB-D7, including just using the 2 fast-charging ports, didn't see any rating increase (and even though these do generate little heat in comparison to other miners, I'm a cooling freak, so yea, there are fans). Still think there's some limiting factors in the software, I only say that because that's the world I come from and I damn well know nothing every goes right the first time, hell maybe not even the first few hundred times, no matter how good a programmer is, there are always some factors unaccounted for, overlooked, typo'ed (fking semi-colon), suddenly broken by something else (fking random updates) or just not thought of.

good catch, didn't even think about that, just went to grabbing off github.

I switched as I was using 12.04... after switching it appears the rep is having some issues (didn't on 12.04) of which won't let you install bfgminer (that way). I checked the server, the server connection is fine, just files aren't there.

Got one working on the Win7 box, cleaned up the zip file for installation. By cleaned up I mean I removed the 'Encrypt these files' option, so you could use the driver properly. Also removed the _MACOSX folder which had windows binaries in it. Not to mention, it's not on MediaFire (which since that is a fresh Win7 install it didn't have flash installed causing Chrome to loop-crash due to trying to forcefully install flash, thanks mediafire... you suck).

If anyone wants the cleaned up zip file: http://256mining.com/downloads/bf1_bfgminer_win7.zip & use the directions on on this thread after downloading.


Back to working on Ubuntu now...

Are you using Ubuntu 13 or 12.04.xx? Just curious.

I tried on Ubuntu, granted I can't stand what they've done with that distro over the years, however, I first tried a VM using VMWare Fusion, BFGMiner had issues finding the devices when they directly specified (which was awkward) I thought this was an issue due to the VM (however I see a few people that have it working as a VM). The irregular behavior between users and the variance of rates would definitely suggest software issues, at least that's the conclusion I took from it. I am going to attempt to do some more builds on Ubuntu, as I've got one on a windows box, one on my iMac with a Ubuntu VM, one on a linux asus laptop, then my 5 hashing on Raspbian.

Which I am impressed by still not seeing a single hardware error also noticed these barely generate any heat. I think if you took the 5 hashing for the last hour, combined their temps it still wouldn't equal to what one ASIC USB Erupter would in 5 minutes (temperature-wise).

Well...

I spent most of the day trying different OS's on different machines (Ubuntu 12.04.3, Raspbian, Arch Linux, Windows7, OSX), different USB Hubs (Rosewill RHB-500, D-Link DUB-H7, Sateshi 12-Port, a few Belkin 7-ports, GearHead 7-port), different physical machines (3 different laptops (Win/Linux/Apple),a iMac, a VM on iMac, a VM on Win7, raspberryPi).

From my experience:
On any platform, from a compiled build or a pre-compiled executable, CGMiner just doesn't work, it never detects the devices and shuts down.

Thus far, the *only* configuration that works for me is BFGMiner 3.0.99 on Raspbian (RaspberryPi). After doing all my testing on different machines, different hubs, different OS's, I ended up back at the RaspberryPi, upon starting BFGMiner up after all my testing, I'm seeing an average of 1.8GH/s per device (currently still 5 on the HUB, I've tried more/less it doesn't change).

Conclusion:
I'm fairly certain the most of the issues being seen are software related, either the firmware is just, well, not ready or there's some missing connection that everyone seems to be having.

As a developer (granted I moved away from os-apps long ago), I would highly suggest you releasing the firmware to the public so that other developers can assist on the issues. I'm not stating the people involved aren't doing everything they can (as I'm sure LukeJr & ckolivas are doing what they can to fix the issues from within their software), but "a different set of eyes" can usually always assist indirectly (sometimes directly). As usually questions get raised as to the methods being used (etc), which will cause the original developer to see the light on things that could be the cause of issues.

Either way, I stay optimistic these are software issues, not hardware issues.

@ssinc, received my order today thanks!

@Beastlymac, I am noticing some low rates, I will keep all my support issues in the support thread you opened up (as I feel most people should, as that's what it's there for).

Well...

I compiled the latest revision of CGMiner on MinePeon 0.2.4 w/options --disable-opencl --disable-adl --enable-bflsc --enable-bitforce --enable-icarus --enable-modminer --enable-ztex --enable-avalon --enable-bitfury (same options as the tutorial in Rasbian Wheezy). The devices were never detected, so I switched to Raspbian Wheezy, latest updated, first trying CGMiner per the .DEB package and instructions on the tutorial, results were the same, no devices were detected under CGMiner (they would show in lsusb).



I then uninstalled the CGMiner package (dpkg -r cgminer) and installed BFGMiner per tutorial instructions, after which the devices were detected. This is a hub that I can easily run 8 ASIC Erupters, so it should have no power issues running 8 BlueFuries, however I started off with 5 and decided to let them hash awhile to see what kind of rates I was getting...

Granted, I'm not getting any hardware errors (which is awesome),  but also not seeing GH/s rate I should be seeing. Now with this being said, I am going to try a few different pools and see what results I have. As well, I'm going to try to make a build on Raspbian of CGMiner (since I have yet to get CGMiner to work with the devices and apparently CGMiner so far, from what I've read has the best results...).



EDIT:
Just made a fresh build of CGMiner on Raspbian, still won't detect any devices, I also notice that CGMiner disables all the devices as I tried to use BFGMiner after (which was working seconds before trying CGMiner) and get 'All devices disabled, cannot mine!'. I thought that was semi-interesting...

Charging transaction fees based on the transaction amount would be a better alternative, as you said, it (definitely) will drive people away who want to use the service for mining. With the projected difficulty raises, trading let alone mining won't net profit for anyone other than CEX.io (which I'm sure they have no problem with that ) but then that kind of kills off their revenue at the same time, since people would stop using the service.

He got it working sort-of... had a few permission issues and the WebUI isn't reporting the device, however CGMiner is... I asked for screenshots so I could try to help troubleshoot, he'll be sending them tomorrow (as he already left the location his miner is at).

There's a lot of OS files that aren't in the repo. so while you updated some of the files, it didn't install the services, permissions, and other things that make 0.2.4 more stable. However it did update your /opt/minepeon/etc/version file, which contains the version (as that is in the repo), which doesn't do anything, you also got the update WebUI and a few other things (as they are in the repo). I would suggest you download the image and write it to a SD Card, to actually upgrade to 0.2.4, without properly doing this you more than likely will run into issues later on.

If it were .001 BTC instead of USD (lets hope it isn't a type-o on their site) then you definitely wouldn't make any money from buying GH/s, heck .001 BTC per hour per GH/s you wouldn't even make anything trading GH/s, unless you did it within the first hour.

Well, they are including spidevc as well as bitfury drivers... which my attempts yesterday to compile failed because of the spidevc, I'm trying to figure out if it's attempting to look for a spi device upon the build process or what, actually just had an idea.

If you're trying to update to 0.2.4, you will need to download the image and copy it to the SD card. There's a lot of things that got changed (OS-level) a simple git pull won't suffice.

interesting idea...

If you're interested in any of this, let me know:

3x 1GB DDR2 DIMMS, Corsair 800Mhz/1024MB #CM2X1024-6400
1x Intel Pentium 4 Processor 2.60GHz #SL6WH
1x Intel Pentium 4 Processor 1.8GHz #SL6QL
1x Intel Core 2 Duo Processor 2.66GHz #E7300
1x Samsung 3.5" Hard-drive, 400GB 7200RPM PATA #HD400LD - (tested fine/wrote zeros on drive 09/07/12, hasn't been used since)
1x Seagate 3.5" Hard-drive, Barracuda 7200.11, 160GB SATA #STX-720011 (B) -  (tested fine/wrote zeros on drive 09/07/12, hasn't been used since)
1x Seagate 3.5" Hard-drive, Barracuda 7200.10, 160GB SATA #STX-L3510 (B) - (would have to test, as I didn't mark is as tested)
1x Western Digital 3.5" Hard-drive, 160GB SATA #WD1600AAJS - (tested fine/wrote zeros on drive 09/07/12, hasn't been used since)
1x Fujitsu 2.5" Hard-drive, 160GB SATA, Mac Formatted #MJA2160BH - (tested fine, needs zeros to be written to drive)
1x Seagate 2.5" Hard-drive, Momentus 5400.6, 250GB SATA #STX-54006 (B) - (tested fine, needs zeros to be written to drive)
1x Dell Pentium 4 Workstation DHP S/N: BS2ZF81, Mfg Date: 090605
1x GeForce EVGA 7600GT 256MB PCI-E, P/N 256-P2-N554-AX

Everything has been stored in anti-static bags and that was just the draw to my left  
Last year I went through a phase and tested a lot, threw away anything that was extremely old or useless... lol

Just taking a stab in the dark here, but since just about all hosted mining services charge for maintenance/hosting/etc, this is how they are going to charge for it. But I notice it doesn't say BTC, it says dollars ($), so at the current exchange rate,  $0.001 = BTC0.000004998 (GH/s per Hour). According to the genesisBlock if you *started mining at the beginning of October*, you were looking at $0.24-$0.26/day profit, minus about $0.024 for fees, leaving you with around $0.21-0.22 profit (daily per GH/s).

At the current GH/s on CEX.io it would take you about a full month of mining to come close to ROI (at current exchange rate) per GH/s (unless of course you bought low, sold high ). But since we're hitting November in less than a day, you're really only going to have one month of mining before estimated diff. jump goes crazy, you wouldn't break ROI at the current market price on CEX.io after they implement fees or even if they don't.

*waits for market price to come down now*