Many thanks to
Alan Rollow <alan_at_nabeth.cxo.dec.com>
For pointing out it was quite safe running on genvmunix but I would
loose such facilities as LAT CDFS Packetfilter etc that are not built
into genvmunix.
and special thanks to
Ray Bellis <rpb_at_psy.ox.ac.uk>
For pointing out he had had similar problems on some 200 4/166
machines and found the the cause of the crash during booting to be
incorrect "isacfg" information to do with the sound card.
He suggested trying
isacfg -init
isacfg -all
add_sound
After which the machine booted very happily on 3.2C kernel built by
doconfig.
Many thanks again
Tim.
Tim Janes | e-mail : janes_at_signal.dra.hmg.gb
Defence Research Agency | tel : +44 1684 894100
Malvern Worcs | fax : +44 1684 895103
Gt Britain | #include <std/disclaim.h>
Original question:-
> Hi,
>
> We run a "cluster" of about 40 Alphas all sharing the same filespace
> and all have a common /usr thus all have to run the same version of
> DU, currently 3.2C.
>
> Now we have just taken delivery of some more 250 4/266 machines but
> when we add them to our "cluster" I find that they will not boot with
> a 3.2C kernel either copied from an existing 250 4/266 or built on the new
> machine with doconfig.
>
> My guess is that 3.2C is incompatible with the newer firmware level of
> these machines. I tried to downgrade the firmware but they would not
> boot on the firmware disk supplied with 3.2C.
>
> At the moment we cannot afford the downtime of upgrading all machines
> - especially as DU 4.0 will be here very soon with will mean yet
> another upgrade.
>
> These machines however appear to run happily on genvmunix - apart
> from using a bit more memory what would be the disadvantage of running
> these machines on genvmunix for the 2-3 months until DU 4.0 appears.
>
> Any help suggestion would be very welcome.
>
> Thanks
>
> Tim.
Received on Fri Mar 22 1996 - 22:43:47 NZST