| Products > Test Equipment |
| Agilent E7495 linux root account |
| << < (38/91) > >> |
| lectrohamlincoln:
I tried plugging it into the network again no luck. AFAIK it never boots from the PCMCIA. If DIP switch 2&3 are set, it looks like it just boots from the 1Mib flash ROM (the AT29LV1024 chip). The screen is blank and I only get a Serial Menu with a few crappy option and no way of booting from the PCMCIA or getting an actual command line. Although, it does detect when a PCMCIA card is not inserted (it prints an extra line over Serial saying the PCMCIA card is missing). If DIP 1&2 are set, it gets part way through the Kernel boot then hangs. No command line, no option for firmware upgrade, no difference if the PCMCIA card is inserted. Is there some special formatting of the PCMCIA necessary for recovery? |
| kirill_ka:
--- Quote from: lectrohamlincoln on April 26, 2017, 06:36:37 am ---The filesystem is definitely corrupted. Most likely the ram disk is corrupted in a way that the kernel can't load it. The start-up log has the following, "RAMDISK: Couldn't find valid RAM disk image starting at 0" (I can copy the entire boot log if anyone is curious) --- End quote --- Does it mean something's changed from your first attempt? There's "no init" error on the screen shot you posted earlier. |
| kirill_ka:
--- Quote from: lectrohamlincoln on April 26, 2017, 11:01:14 pm ---Is there some special formatting of the PCMCIA necessary for recovery? --- End quote --- I'd try different cards formatted as FAT16. |
| kirill_ka:
--- Quote from: ve7xen on March 18, 2017, 04:05:15 am ---So this is quite odd, since Linux itself has no trouble with the current date, but the egServer process seems to be rolling it over zero to 'less than the minimum'. I guess egServer must be internally representing the time in a nonstandard way. Maybe just patching the comparison would make it work again? --- End quote --- No. What we see here is "GPS week rollover" problem. http://www.npl.co.uk/reference/faqs/when-and-what-is-the-gps-week-rollover-problem-(faq-time) The message doesn't show the time which is "less than minimum". I verified that it's current time minus 1024 weeks. So GPS subsystem adjusts system clock and then it's immediately reset to "minimum time". |
| kirill_ka:
Apply following patch to elgato binary to fix GPS time synchronisation: 0x0122880: replace 4b2585e2152882e2 with de2585e23f2882e2 |
| Navigation |
| Message Index |
| Next page |
| Previous page |