Tru64 installation fails on DS20L

[Steven Schweda]

> [...] you MUST have an IDE system disk for
> that box ?!

Where "that box" is an API CS20, not a Compaq
DS20L (as I read it).

[Hein van den Heuvel]

Steven wrote>> > [...] you MUST have an IDE system disk for that box ?!
>Where "that box" is an API CS20, not a Compaq DS20L (as I read it).

I agree. I thought it odd, but just wanted an explanation.

For the console variable, I don't see anything odd, but that does not mean much. My gutfeel suspect ones would be
'heap_expand', set to none, can be set to 2mb or 4mb? and 'console_memory_allocation' set to new, alternative 'old'. Supposedly genvmunix (which the CD image surely is) can deal with either and the wrong setting would give an "bootstrap address collision" messages

Steven>>I can boot from that disk up
:
>> configuration of the boot disk is inconsistent with that of the ds20L.

Can you boot genvmunix from that disk?
-fi genvmunix
If that works... doconfig.

Hein.

[Pieter 't Hart]

suggestion : clear bootdef_dev before booting from the OS-CD.

the installation script on CD tries to read some hw_config from the default bootdisk (bootdef_dev)to "optimize" the process.

Pieter

[Vladimir Fabecic]

Just one question:
Did you try to boot with help of NHD5?
As far I can remember, I needed NHD5 to install v5.1A on DS20L.

[Rob Leadbeater]

Looks like you need at least NHD4 according to the user guide (page 3-16).

http://h18002.www1.hp.com/alphaserver/download/ek-ds20l-ug-b01.pdf

Cheers,
Rob

[Rob Leadbeater]

The readme for NHD 4.0 is also quite clear !

ftp://ftp.hp.com.au/pub/patches/unix/v5.1a/nhd/4.0/nhd4.README

Tru64 UNIX New Hardware Delivery-4 for V5.1A CD-ROM contains support for the following hardware:
* DA-81AAA-EA/-FA/-GA and DA-81BAA-EA/-FA/-GA: DS20L Compaq AlphaServer(tm) systems

[Steven L Guberman]

The suggestions to install an NHD helped to solve the problem. I installed NHD5 (Thanks to Vladimir and Rob)after making an iso file and writing a cd on a pc. The kn600 error messages are now gone. However, the boot (see below) reveals two errors:
< fatal="" error="">
fd internal driver error: FDI PROBE FAIL (A,11).
fdi0 not probed
and
Error:
:
This system appears to have no disks.
These errors appear even though sh dev (see above)shows the presence of a scsi disk:
dka0.0.0.3.0 DKA0 RZ1CC-BA 883F
Any suggestions?

Alpha boot: available memory from 0x1ffc000 to 0x3fb5a000
Compaq Tru64 UNIX V5.1A (Rev. 1885); Wed Aug 1 15:13:05 EDT 2001
physical memory = 1024.00 megabytes.
available memory = 987.36 megabytes.
using 1286 buffers containing 10.04 megabytes of memory
forcing interrupt in tl_do_command
Firmware revision: 6.6-10
PALcode: UNIX version 1.92-71
hp AlphaServer DS20L 833 MHz
pci1 (primary bus:1) at nexus
ee0 at pci1 slot 3
ee0: Intel 82559 (10/100 Mbps) Ethernet Interface
ee0: Driver Rev = V1.0.12, Chip Rev = 8, hardware address: 00-02-56-00-17-79
PCI device at bus 0, slot 3, function 0 could not be configured:
Vendor ID 0x1000, Device ID 0x21, Base class 0x1, Sub class 0x0 Sub-VID 0x14d9 2
has no matching entry in the PCI option table
PCI device at bus 0, slot 17, function 0 could not be configured:
Vendor ID 0x10b9, Device ID 0x7101, Base class 0x0, Sub class 0x0 Sub-VID 0x14d2
has no matching entry in the PCI option table
pci0 (primary bus:0) at nexus
ee1 at pci0 slot 4
ee1: Intel 82559 (10/100 Mbps) Ethernet Interface
ee1: Driver Rev = V1.0.12, Chip Rev = 12, hardware address: 00-02-56-00-17-78
isa0 at pci0
gpc0 at isa0
gpc1 not probed
ace0 at isa0
ace1 at isa0
lp0 at isa0
< fatal="" error="">
fd internal driver error: FDI PROBE FAIL (A,11).

fdi0 not probed
ata0 at pci0 slot 16
ata0: ACER M1543C
scsi0 at ata0 slot 0 rad 0
scsi1 at ata0 slot 1 rad 0
Created FRU table binary error log packet
kernel console: ace0
NetRAIN configured.


Warning: No time set in file system, using the system clock.
This date may not be correct, please check it after booting

ee0: Parallel Detection, 10 Mbps half duplex
vm_swap_init: warning UNSPECIFIED swap device not found
vm_swap_init: swap is re-set to lazy (over commitment) mode

INIT: SINGLE-USER MODE


Initializing system for Tru64 UNIX installation. Please wait...

Assigning a cluster device number to root


Unable to save existing hardware configuration. New configuration will be
used.

*** Performing CDROM Installation

Loading installation process and scanning system hardware.

Welcome to the Tru64 UNIX Installation Procedure

This procedure installs Tru64 UNIX onto your system. You will be asked a
series of system configuration questions. Until you answer all questions,
your system is not changed in any way.

During the question and answer session, you can go back to any
previous question and change your answer by entering: "history"
You can get more information about a question by entering: "help"

Refer to the "Installation Guide" and "Installation Guide -- Advanced
Topics" for more detailed information about installing the operating
system.



** This system is currently running firmware revision: 6.6-10
See the "Installation Guide" for more information about
updating firmware.


Error:
:
This system appears to have no disks. The installation procedure
requires at least one disk. If there is a disk in the system, you
should confirm that it is properly connected, and then start the
installation procedure again from the ">>>" prompt. If you have
already done this, contact a customer service representative.





The installation procedure failed or was intentionally exited. To restart
the installation, halt and reboot the system or enter: restart

[Steven L Guberman]

Please note that Fatal Error #174 in the prior message can be ignored according to NHD_Notes.pdf. So this leaves the problem of the lack of recognition of the scsi drive.

[Pieter 't Hart]

check the interfaces in this locations:
PCI device at bus 0, slot 3, function 0 could not be configured:
PCI device at bus 0, slot 17, function 0 could not be configured:
if it's the video card this can be ignored at this moment. some (like powerstorm) needs an extra package in the OS .
if it's the scsi interface you may need another NHD for support of this interface.
does "show config" give any info for these interfaces?

Also check if the scsi-bus is properly terminated. this may be the cause of disk drive being detected at boottime but faulting when used from an "OS" (other scsi commands and other timing).

[Vladimir Fabecic]

Try the following from SRM prompt :
>>>boot -fl fa -fi "GENERIC" dqb0

Then you switch NHD and OS disks several times.