You need to stop confusing the working Avalon's with the non-working. That's now how to you do basic troubleshooting.
1. Is the Avalon that is having the problem setup on static IP or is it getting's its IP through DHCP? You can only be using one of them...
2. When you plug your PC into the network to test it are you plugging it into the same network cable you have plugged your Avalon at it's new location?
You can only SSH into the Avalon but you have to make sure SSH is enabled.
Oh trust me, I'm not confused by the working/not working Avalons. I know I want to take a hammer to the one that doesnt work! LOL!
1. Right now, its static. Its been DHCP as well but that did not change the fact that it wont hash. For the record, I know it can only be one or the other.
2. Yes, same cable plugged into my laptop (pulled out of the port on the Avalon) and it works fine. Yes, at its new location. (up a 10 foot ladder thank you very much
)
So... From my 30+ years of troubleshooting (albeit a completely different industry) I've deduced that there is something wrong with the network controller on the Avalon that wont connect. Since my other 3 are working I decided to give something a shot.
I unplugged the ribbon cables from the FPGA controller board in the BA (Bad Avalon) and plugged them into one of my GA's (Good Avalon). I also moved the fan connector from the BA to the controller in the GA. Obviously the temp sensors cant be fooled with but these units "should" heat up about the same so the GA should be able to keep the modules in the BA cooled down. The power supply from the BA is supplying current to the 2 hashing modules so theres no crazy load on the other units supply.
I think I have some tweaking yet to do in CGMiners setup as I'm not getting the 120ish GH's that I should be getting from 4 modules clocked at 375. FWIW when the BA was working I was getting right around 63GH's out of it.
Anyone know the tweaks needed for what would be a 4 module Avalon?