Thanks goes out to: Emil Dragic, Bryaln Lavelle, Rick Hummers, and Adrija
Pantovic.
ECU(EISA COnfiguration Utility), this is used to configure the IO and
Interupts for EISA bus devices. These need to be configured with this disk
on older machines like the Alphastation 500. Newer machines like PWs and
XP1000's don't need them because they use PCI busses.
I called DEC(1-800-digital) and you can a new ECU disk for my AlphaStation
500. It only cost ~$11(as of 03/31/2000). Thanks everyone for answering.
-grant
---Original Message---
Ok. I just hit this exact same problem. When I do a build of the kernel, it
fails with the ace_regbase problem.
But I have no ECU floppy. I'm not sure what one is. I have been working
with DEC's for very long and was "given" the job of managing a bunch of
older DEC machines. The previous admin didn't keep much in the way of
manuals or disks. Not that I can find anyways.
So what is this ECU disk? And do I really have to have one to do this? I
have a V4.0d, V4.0e, and V4.0f media kit. Don't see any floppy disks in them.
Help... Thanks!
-grant
--Original Message Strain---
At 12:14 PM 2/25/00 -0500, Hummers, Rick \(Frederick\) wrote:
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
> >
> >
---------------------------------------------------------------------------
Grant Schoep, grant_at_storm.com
System/Network Administrator
L3 Communications Telemetry & Instrumentation
San Jose,CA
Received on Fri Mar 31 2000 - 15:13:23 NZST