Update: NOT >>> BOOT DVA0 to get ECU
> Thanks go to Emil Dragic, Tom Blinn, Mark Vallee, Sunil Kurupath, and
> John
> Francini all saying essentially the same thing. Update your EISA
> configuration by running your ECU floppy. Tom Blinn also supplied the
> additional perl of picking the ace devices out of GENERIC and plopping
> them
> in the current kernel config file.
>
> I tried to >>> boot dva0 and it failed, bootstrap failure... (the same
> floppy does the same thing on other AlphaStation 600s so perhaps it is a
> bad
> floppy).
>
> So then I put in devices scc0, ace_0 and ace_1 from the GENERIC config
> file
> and was able to build a new K.
>
In response to my first summary John Francini pointed out that the ECU
floppy
is a x86 format.
>>> runecu
starts the x86 emulator in the Alpha and it is a typical PC point and shoot
from
there.
> thanks to all
> \s\Rick
>
>
> ----------------------------------------------wrt-------------------------
> --
> ------------------------------------
> > I just upgraded an AS 600 5/266 from V4.0B to V4.0D and when it went to
> > build the
> > new K the build blew up. Right after device listing in /dev/MAKEDEV.log
> > the clip
> > from the .errs log was displayed. At the end of it was:
> >
> > ...
> > loading vmunix.sys
> > ld:
> > Error: Undefined:
> > ace_regbase
> > exit 1
> > chmod 700 a.out
> > (no such file ...)
> > exit 4
> > stop.
> >
> > This was on a new Kernel Config file mapped while booted on genvmunix?
> >
> > Does someone have a hint?
> >
> > thanks
> > \s\Rick
> >
> >
Received on Fri Feb 25 2000 - 17:15:36 NZDT