Re: Problems booting XP1000

From: Albert Chin-A-Young (china_at_foo.com)
Date: 12/10/03 

Date: Wed, 10 Dec 2003 14:49:03 -0600

Albert Chin-A-Young <china@foo.com> wrote:
> Trying to get a used XP1000 to boot. The unit has a 21264 667Mhz EV6 CPU
> with 640MB installed. The firmware 6.3 CD is in the CD-ROM drive and I
> removed the SCSI cable. A terminal is connected to the serial port. This
> is all I see when it boots:
> OpenVMS PALcode V1.78-24, Digital UNIX PALcode V1.71-20
>
> FF.FE.FD.FC.FB.FA.F9.F8.F7.F6.F5.F3.F2.F1.F0.EF.EE.EC.EB.EA.E9.F4.*** no
> timer interrupts on CPU 0 ***
>
> Any ideas? I've already reseated the motherboard and memory. I don't
> hear any beeps.

I removed the video card and things are looking better. I've upgraded to
the latest firmware (5.9) and am now trying to boot the 5.1B
installation CD with a SCSI drive at id #1. I get the following error:
  (boot dqb0.0.1.207.0)
  block 0 of dqb0.0.1.207.0 is a valid boot block
  reading 15 blocks from dqb0.0.1.207.0
  bootstrap code read in
  base = 200000, image_start = 0, image_bytes = 1e00
  initializing HWRPB at 2000
  initializing page table at 27fee000
  initializing machine state
  setting affinity to the primary CPU
  jumping to bootstrap code

  UNIX boot - Wednesday October 16, 2002

  Loading vmunix ...
  Loading at 0xffffffff00000000

  Sizes:
  text = 7922752
  data = 2044560
  bss = 2433008
  Starting at 0xffffffff00011d70

  bcm: DEGXA driver V1.0.6 NUMA lanlog
  failed configuring ev7_ocla subsystem
  Alpha boot: available memory from 0x1fee000 to 0x27fec000
  Compaq Tru64 UNIX V5.1B (Rev. 2650); Wed Oct 16 17:45:54 EDT 2002
  physical memory = 640.00 megabytes.
  available memory = 607.99 megabytes.
  using 798 buffers containing 6.23 megabytes of memory
  Firmware revision: 5.9-1
  PALcode: UNIX version 1.83-22
  COMPAQ Professional Workstation XP1000
  config_cpus: Could not find config tree entry for CPU0
  pci1 (primary bus:1) at nexus
  tu0: DECchip 21143: Revision: 4.1
  tu0: auto negotiation capable device
  tu0 at pci1 slot 3
  tu0: DEC TULIP (10/100) Ethernet Interface, hardware address: 08-00-2B-87-23-15
  tu0: auto negotiation on: will advertise 100BaseTX (UTP) port: full duplex
  isp0 at pci1 slot 6
  isp0: QLOGIC ISP1040C
  isp0: Firmware revision 5.57 (loaded by console)
  DDR - Warning: Device has no "name" - for
    Vendor ID : Product ID: Revision: S7Z0
  scsi0 at isp0 slot 0 rad 0
  pci2 (primary bus:1 subordinate bus:2) at pci1 slot 8
  pci0 (primary bus:0) at nexus
  isa0 at pci0
  gpc0 at isa0
  gpc1 not probed
  ace0 at isa0
  ace1 at isa0
  lp0 at isa0
  fdi0 at isa0
  fd0 at fdi0 unit 0
  ata0 at pci0 slot 107 (slot 7, function 1)
  ata0: CYPRESS 82C693
  scsi1 at ata0 slot 0 rad 0
  ata1 at pci0 slot 207 (slot 7, function 2)
  ata1: CYPRESS 82C693
  scsi2 at ata1 slot 0 rad 0
  usb0 at pci0 slot 307 (slot 7, function 3)
  kernel console: ace0
  panic (cpu 0): init_rootdev: boot device translation failed

  DUMP: Warning: no disk available for dump.

  DUMP: first crash dump failed: attempting memory dump...
  DUMP: compressing 49488KB into 574927KB memory...
  DUMP: Starting Address Ending Address Size(MB)
  DUMP: ------------------ ------------------ --------
  DUMP: 0xfffffc0027c40000 - 0xfffffc0027febfef 3.6 (indicator)
  DUMP: Writing data.. [2MB]
  DUMP: crash dump complete.

  halted CPU 0

  halt code = 5
  HALT instruction executed
  PC = ffffffff00300d70

How do I fix the "init_rootdev: boot device translation failed" message? 

-- 
albert chin

Relevant Pages

  • Problems installing 5.1A on XP1000
    ... The drive I'm attempting an install to is an IBM ... 640 MBytes of System Memory ... isa0 at pci0 ... DUMP: Warning: no disk available for dump. ...
    (Tru64-UNIX-Managers)
  • Booting 4.0 on XP1000
    ... available memory from 0x2ef8000 to 0x7ffec000 ... isp0 at pci1 slot 6 ... gpc0 at isa0 ... DUMP: No primary swap, no explicit dumpdev. ...
    (Tru64-UNIX-Managers)
  • SUMMARY: Problems installing 5.1A on XP1000
    ... The drive I'm attempting an install to is an IBM ... 640 MBytes of System Memory ... isa0 at pci0 ... DUMP: Warning: no disk available for dump. ...
    (Tru64-UNIX-Managers)
  • SUMMARY: installing Tru64 5.1B on PW500au, moving system disk to DS20E
    ... Best regards, Bob ... boot with genvmunix to get access to all the device drivers and then ... DUMP: A dump found in memory will tie up 3940352 bytes until released. ...
    (Tru64-UNIX-Managers)
  • Re: media of old VMS versions
    ... obviate recollection from a weak memory. ... The size restriction is on the boot disk when the system does a crash ... at risk if the system crashes, and the firmware mislocates the dump ... Perhaps there was a reason that I suggested a 1GB disk, ...
    (comp.os.vms)