[weblacky]

Thanks Jwhat,
I feel this is something incredibly fundamental. I’ve never seen a failure like this and I don’t think anyone else has either. I think, just like anything else, covering your fundamentals is probably going to solve the situation.

Of course there are new occurrences of issues, based on the history of each system, but I feel like if that’s the case we still need to be using correct parts (or as close as we can get to them today) for at least proper troubleshooting.

Just like an automobile, you don’t want to end up learning that the sensor you bought from a third party never worked right to begin with and that was the cause of all your issues versus having just bought the OEM part. Now in this case you have no real choice but to purchase third-party but we’re trying to steer you to third-party solutions that should conform well enough to the original to be called a functional replacement.

Once that’s addressed we can then move on.


Kokoboi,
Seeing is how you’ve tried two different I09 cards and have exactly the same symptoms I would agree that it has to be the mainboard. Well the L1 is responsible for setting all the hardware states and values and then bootstrapping the PROM.

Various users, including Jwhat, have proven that you need a fully compatible working and clean L1 RTC to work. You definitely can’t work without the RTC and you definitely can’t work with a corrupted RTC that the system doesn’t detect as wrong and is able to clear/initialize itself.


You can fully get by with a dead clock on both the RTC‘s due to dead batteries. Everything else is not negotiable.

However for both Tezro and Fuel it’s been shown that if you did have dead batteries but working RTC‘s, you normally need a double reboot on power on to have them properly initialize and then reboot and go through default initialization. That is to say that normally the first stage is the self programming by the station if they’re blank than normally they assume you have working batteries they tell you to reboot deep in the logs. If you don’t have a working battery you can keep power on by just using the soft reset on the front of a lot of the systems or issuing a reset through the L1 terminal. Then the system board is still providing power to the RTC so it still has the memory initialized in the previous boot and will start correctly. It’s only when external powers cut off that the RTC memory fades and eventually erases.

Knowing this if you had two working RTC‘s with dead batteries you should’ve been able to successfully boot using a series of soft reboots one after the other until successful start of the operating system. Since that hasn’t happened yet I’m still going to assume we have a basic RTC problem at the L1.