nice explanation

here we go:

[minepeon@minepeon ~]$ lsusb | grep hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 009: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 010: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 011: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 007: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 008: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
[minepeon@minepeon ~]$ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
        |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 2: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 9, If 0, Class=Hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 12, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 2: Dev 13, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 3: Dev 14, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 4: Dev 15, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
            |__ Port 3: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 10, If 0, Class=Hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 16, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 2: Dev 17, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 3: Dev 18, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 4: Dev 19, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
            |__ Port 4: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 20, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 2: Dev 21, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 3: Dev 22, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
                    |__ Port 4: Dev 23, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
        |__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=rtl8192cu, 480M

OK, now I'm confused.

On the one hand, you've managed to set up all your erupters such that they only sit on one logical hub per physical hub. (Looking at the D-Link, it seems that plugs 1, 3, 5, and 7 form one logical hub, and plugs 2, 4, and 6 are on the other logical hub.)

On the other hand, you have six logical hubs showing up -- something I haven't been able to accomplish.  Like you, I have the Wifi plugged directly into one of the Pi's ports, and my hubs are in a star config off the other port. Here's the same output from one of my Pis:


No matter what I do, I can't get the Pi to recognize any additional hubs; in fact, I can't get it to recognize erupters plugged into logical hub 2 on my last physical hub.  Anyone have any ideas?

Round 2!

Star configuration is the solution to my previous problem!  Thank you everyone who helped me out with that!

I now can get every miner recognized and when I start up my PI they all start mining shortly after the pi turns on!  Then the bad stuff happens... about 10-15 min later some of the miners, usually just 1 or two will go idle for a few seconds... and then after that find work and start mining.  Once that happens I know the whole rig is about to shut down.  After that more miners go idle, then after a bit come back on to mining.  Within a minute all my miners go idle, and the second all of them go idle, I can no longer access the webGUI and they never start mining on their own again.

If i powercycle the pi, they all come back on and work like there was never a problem, but the whole thing mines for less then an hour before it shuts down.

Hrum... seems when I set the correct time zone, the time is an hour off minepeon says it is 7:30 am when it is 8:30am...  I live in the same timezone as Chicago... So i set my timezone there.  I swore Chicago was on GMT -6 not -5 as stated in minepeon  The time is 1 hour off of what the actual time is here, but this may be due to me being retarded with timezones.

I noticed that I seem to be getting 30% hardware errors... I thought maybe things were overheating so I spread out my miners on the ports a bit more and moved it closer to the fan, no luck there, still the same problem.  And from my reading I have seen people put more miners closer together with less or no fans without issue... so i doubt that is my problem.  But 30% hardware errors...

I will go out and buy a new SD card, I have been force restarting this thing a lot and I imagine something on the card could be fucked up, thank you for pointing that out.  Still testing stuff!

I did change The cable, but no difference. I don't understand... The 2 usb asicminer work perfectly well if plugged individually either directly to the Pi or to the USB hub, but if I put them together (USB hub or PI port or one in the USB hub and one to the Pi that's what happens... Basically one the two gives errors, but is not always the same one...alone works perfectly!

Name   ID   Temp   MH/s   Accept   Reject   Error   Utility   Last Share Time
AMU   0   0   335.36   178   1   0   4.9   14:50:28
AMU   1   0   325.56   0   0   34   0   01:00:00
Totals   2      660.92   178   1   34   4.9   

Thank you for the help.

Now I understand. Thank you very much and I'll let you know if it works!

Thank you!  Looks like with my configuration now 0.2.3a had some issues... strange.  I upgraded to 0.2.3a when i had half as many miners, only when I added double the miners did I have an issue, but 0.2.2 is working fine now for over an hour with no issue.  Well, I cant say for sure 0.2.3a is the issue, maybe a clean install would have worked, but I wanted it working ASAP so i did clean install AND old version at the same time, and one of those two things solved my problem.

Mined the first full hour on the donate address, love this project!

So far I can't get 3.4.3 to run longer than an hour on Raspbian before locking up seems the same on Pidora
Putting it back to 3.4.2, so far still running. So I'm not sure about that...

Please Help:

I finally got my first Erupters up and running and excited to start hashing for first time.  Only problem is after Minepeon has been running for 5 min, by Miner Uptime goes to 15963 day 4 hr 36 min 54 sec.

I realize this it a date time issue, I've found threaded that have me SSH in reset time, but it seems to just do it again 5 minutes later.  What am I doing wrong?

Squeeky4711

Followed these instruction and after about 2min 3sec, the miner went back to 15963 day.  I believe they are still working as accept reject etc still move, however it would be nice to have it completely operationing.  

I changed to America/New_York timezone and the following ntp servers:
           server 0.north-america.pool.ntp.org
      server 1.north-america.pool.ntp.org
      server 2.north-america.pool.ntp.org
      server 3.north-america.pool.ntp.org

Any other ideas, I'd be more than happy to try.

*EDIT* Realized I missed iburst after each ntp server address.  Adjusted file and restarted cgminer fingers crossed.