On 11/23/13, 6:07 AM, Jim Klimov wrote:
> Or how to
> reinstall the thing with proper import of data which is still regularly
> being backed up :\
You should make it perfectly clear to them that a backup you can't
restore is a backup you don't have.
Cheers,
--
Saso
_
On Sat, 11/23/13, Jim Klimov wrote:
If we do manage to replace the NVRAM chip, I guess the
eeprom settings
(boot-devices and so on) would also need to be recovered?
You'll need to copy all that down, particularly the CPU ID if the software is
locked to a particular host. That should be
On Fri, 22 Nov 2013, Jim Klimov wrote:
> Hello all,
>
> My attention was requested to an old UltraSPARC E450 machine with
> Solaris 8, whose clock was going slower and worse for the past few
> days, maybe weeks. Since about today it has practically stopped -
> or more precisely, loops over the
Sad, nice boxes, they were. Afaik some were refitted into zfs nases, maybe
keeping only the stylish case with different mobo's.
Still, may i ask to mail us the small spare components like the nvram chips or
ram modules? That setup is not in USA, but i guess we can figure something
about snail
Hi Jim!
> Still, may i ask to mail us the small spare components like the
> nvram chips or ram modules? That setup is not in USA, but i guess we
> can figure something about snail mail... thanks in advance =)
Don't bother. There is lots of stuff for E450s right here in Europe.
I have some, for
Hello Jim,
We've got a few of these old beasts around; the last of 'em still anxiously
awaiting its, uhhh... 'Retirement Party'.
Seems to me we had to replace a battery on at least one of these at some point,
but don't think it was the CR2032 'button' type, as I recall. Happy to send you
some
You can get replacement NVRAMs from here
http://www.memoryxsun.com/5251673.html.
I have hundreds of still in production Netra AX1105's and this is the only
source I've found for Sun NVRAM.
They come pre-programmed with MAC/Host ID so if you need the existing
config you'll have to program it yoursel
My understanding is that the time is read from the NVRAM chip only once
when booting, then the time is updated by the kernel clock() function by
interrupt 10 while running.
High interrupt rates could cause the clock interrupt to be missed,
slowing time. A lot of serial activity could cause it.
I a
The crystal oscillator may or may not be OK, but low voltage can still
cause the surrounding logic in the NVRAM chip to malfunction, or an IO
signal from low to high voltage to be interpreted as the wrong logic
level. Remember -- the claimed problem is not that the clock is slow
but that the t
