The trick was to run the isacfg utilty at the console level to ensure that the 
kernel picked up the right information about the isa bus configuration.
The first response I got was from Jason Bell, Digital CSC in the UK, who said
         try running the ISA bus configuration from system console as
         follows:
         >>> isacfg -init
         >>> init
         >>> add_sound
         >>> init
         Then try booting the system again.
                                                
Which did indeed clear the problem. Thanks also to both
"Dr. Tom Blinn, 603-884-0646" <tpb_at_zk3.dec.com>
and
Olle Eriksson <olle_at_cb.uu.se>
who each suggested simply
>>> isacfg -init
>>> init
This may well have been as good, but I had already put Jason's solution into practice. 
Thanks again to all respondents.
Richard
=====================================
Original query follows.
On Wed, 15 Apr 1998 09:19:48 +0100 Richard Rogers <R.M.Rogers_at_staffs.ac.uk> 
wrote:
> Hi -
> 
> I've just performed up update installation of DU 4.0 on an AlphaStation 4/166, 
> which previously had v3.2D-1 loaded. Prior to the upgrade, I updated to the 
> latest firmware (v6.6, from the v5.0 CD).
> 
> Now, when the system attempts to reboot, it fails with the following console 
> messages:
> 
> ----------
> Alpha boot: available memory from 0xc70000 to 0x3ffe000
> Digital UNIX v4.0 (Rev. 386); Mon May 20 04:23:35 EDT 1996
> physical memor = 64.00 megabytes
> available memory = 51.57 megabytes
> using 238 buffers containing 1.85 megabytes of memory
> DDR: WARNING: Unable to obtain Device Information Database
>       Unable to open file /etc/ddr.db
> DDR: WARNING: Basic Defaults will be used.
> -----------
>    ....and a little further on...
> -----------
> tz5 at scsi0 target 5 lun 0 (LID=3) (DEC TLZ09 (C)DEC 0173)
> isa0 at pci0
> panic (cpu0): rmalloc
> DUMP: No primary swap, no explicit dumpdev.
>      Nowhere to put header, giving up.
> halted CPU 0
> halt code = 5
> HALT instruction executed
> PC = fffffc000045f1d0
> >>>
> -----------------
> 
> Booting from v4.0 CD also gives the panic message, although booting from v3.2D 
> CD appears OK.
> 
> Has anyone seen this behaviour? Can you shed any light on it? Thanks for any 
> assistance.
> 
> Richard
> 
> -----------------------------------
> Richard Rogers
> Information Technology Services
> Staffordshire University
> Tel: 01785 (+44 1785) 353395
> E-mail: R.M.Rogers_at_staffs.ac.uk
>   ...Who knows where the time goes?...
> 
-----------------------------------
Richard Rogers
Information Technology Services
Staffordshire University
Tel: 01785 (+44 1785) 353395
E-mail: R.M.Rogers_at_staffs.ac.uk
  ...Who knows where the time goes?...
Received on Wed Apr 15 1998 - 15:56:47 NZST