My recollection is that the error LED for for a few seconds during cold boot is normal. If it stays on you have an issue.
My first thought is that you have a speed mismatch on the serial line. Perhaps it didn't stay the same speed after the reboot, or you restarted the terminal emulation and it defaulted back to 9600. That's one reason I always go into CommBIOS first thing and set it to 9600, which is the default for the rest of the world. Many less problems that way. After that, power supplies are a frequent issue, as the other poster mentioned. I'm on my third. Soekris replaced the first one under warranty and when it went, I bought something completely different. If you boot off the CF or HDD can you ping it on the network? Does the HDD even act like it's booting? -Jed On Feb 18, 2011, at 11:37 AM, Andrea Gronchi <[email protected]> wrote: > Hi, > I've been experimenting with a net5501 board for some days. > > The board run Linux (2.6.36) and worked quite nicely botting from PXE+NFS and > CF. > This same board also spent some time running as a test firewall appliance, > without apparent problems. > > After a clean hard reboot (correct system shutdown followed by power supply > disconnection), the board stopped working: > - no POST with CF inserted, > - no POST with SATA drive connected. > - no POST even with a clean, unconnected board. > > Other than the power led on, the only recognizable sign of activity is the > "error" led, which happens to stay on for the first 6-8 seconds after > powering on. > > I'd like to have some insight in this specific condition, possible fixes and > what is causing this. > > Thank you in advance. > > Andrea. > > ---- > Andrea Gronchi > [email protected] > _______________________________________________ > Soekris-tech mailing list > [email protected] > http://lists.soekris.com/mailman/listinfo/soekris-tech _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
