Tru64 5.1B on AlphaServer 4100 installation

[Rustam Aliyev_1]

Hi all,

I'm trying to install Tru64 5.1B on AlphaServer 4100.

From SRM console I started CD boot (boot dka500). System founds bootstrap, loads vmunix, founds all devices and starts X server.

When X server stars up keyboard and mouse was locked and I was unable to choose language.

I'v SRM 6.0-4 firmware.
The console is set to graphic.
Also I done "set bus_probe_algorithm new" as shown in manual.

Is there any restrictions regarding Tru64 5.1B installation on Alpha 4100?

Thank you in advance...

[Michael Schulte zur Sur]

Hi,

have you compared your hardware with the list of supported hardware for 5.1B?

greetings,

Michael

[Rustam Aliyev_1]

Yes, Tru64 5.1B supports AS4100.

AlphaServer 4100 has been listed in "hp Tru64 UNIX Operating System V5.1B QuickSpecs" document can be found on installation CD.

Only requirement I met was to have 6.0-3 firmware.

Maybe the reason is other devices? I've this controllers:
- KZPBA-CX, QLogic 1040B/V2 (fw 5.57) SCSI Controller
- Mylex DAC960 PCI RAID Controller SWXCR (fw 2.70)

[Ralf Puchner]

have you completed the firmware update by running the eisa configuration utility - which is mandatory after a firmwareupdate of eisa machines?

Btw there are 3 swxcr controller, which one do you have? (KZESC, KZPSC, KZPAC)

[Sreenivasa Prasad V.]

Downgrad the system firmware from release 6.0 to release 5.5.

- Sreenivasa Prasad V.

[Ralf Puchner]

Sorry, but downgrading is tottaly nonsense.

Have a look into the release notes of the firmware:

Tru64 > 5.x requires firmware 6.0 or higher

there is a table within the release notes showing the compatibility list between os and firmware.

[Michael Schulte zur Sur]

Hi Ralf,

I was looking for the list of supported hardware for 5.1B. I just couldn't find it. Where is it?

greetings,

Michael

[Rustam Aliyev_1]

I had run ECU and selected "Save and Exit".

Not working, same keyboard and mouse lock when loading X server. Actualy keyboard locks little bit earlier than X server starts, I had checked with NumLock :) Also console not responding too.

I don't have ECU floppy so I got ECU V1.10 (or V1.11) from DriverGuide.com, is it ok?

My SWXCR is KZPAC.

Any ideas?

[Ralf Puchner]

does the machine work in single user mode or is lookup only seen with X11? If so boot into single user mode, try sizer -gt and check if graphic card was detected properly.

btw. check if the onboard graphic card is disabled in the ecu if an additional graphic card is plugged into the machine.

[Ralf Puchner]

Michael,

look into the release notes of 5.1b for retired hardware. The Software Product Description (document area within website) contains all supported hardware components. But you must also check if the hardware options are still supported within the machine and what config restrictions exists (e.g. gigabit in slot xyz, only one per bus etc. during installation)

[Rustam Aliyev_1]

I had 4.0G at the moment installed on this machine. I had booted in single-user mode, "sizer -gt" shows correct card - S3TRIO.

Here are whole boot process from scratch:

--------------------- BEGIN ---------------------
SROM V3.0 on cpu0
SROM V3.0 on cpu1
XSROM V6.0 on cpu0
XSROM V6.0 on cpu1
BCache testing complete on cpu0
BCache testing complete on cpu1
mem_pair0 - 1024 MB
20..20..21..21..23..
please wait 24 seconds for T24 to complete
24..24..
Memory testing complete on cpu0
Memory testing complete on cpu1
starting console on CPU 0
sizing memory
. 0 1024 MB EDO
starting console on CPU 1
probing IOD1 hose 1
. bus 0 slot 1 - NCR 53C810
. bus 0 slot 2 - QLogic ISP10X0
. bus 0 slot 4 - DECchip 21140-AA
probing IOD0 hose 0
. bus 0 slot 1 - PCEB
. probing EISA Bridge, bus 1
. bus 0 slot 2 - S3 Trio64/Trio32
. bus 0 slot 3 - DECchip 21140-AA
. bus 0 slot 5 - Mylex DAC960
configuring I/O adapters...
. ncr0, hose 1, bus 0, slot 1
. isp0, hose 1, bus 0, slot 2
. tulip0, hose 1, bus 0, slot 4
. floppy0, hose 0, bus 1, slot 0
. tulip1, hose 0, bus 0, slot 3
. dac0, hose 0, bus 0, slot 5
System temperature is 22 degrees C
AlphaServer 4100 Console V6.0-4, 10-MAY-2001 10:11:42

P00>>>boot dka500
(boot dka500.5.0.1.1 -flags A)
block 0 of dka500.5.0.1.1 is a valid boot block
reading 15 blocks from dka500.5.0.1.1
bootstrap code read in
Building FRU table
base = 200000, image_start = 0, image_bytes = 1e00
initializing HWRPB at 2000
initializing page table at 1f2000
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 0x290e000 to 0x3fffa000
Compaq Tru64 UNIX V5.1B (Rev. 2650); Wed Oct 16 17:45:54 EDT 2002
physical memory = 1024.00 megabytes.
available memory = 982.92 megabytes.
using 1290 buffers containing 10.07 megabytes of memory
Master cpu at slot 0
Firmware revision: 6.0
PALcode: UNIX version 1.23
AlphaServer 4100 5/466 4MB
pci1 (primary bus:1) at mcbus0 slot 5
Loading SIOP: script c0000000, reg 7faee00, data c000a000
scsi0 at psiop0 slot 0 rad 0
isp0 at pci1 slot 2
isp0: QLOGIC ISP1040B/V2
isp0: Firmware revision 5.57 (loaded by console)
isp0: Fast RAM timing enabled.
scsi1 at isp0 slot 0 rad 0
tu0: DECchip 21140: Revision: 2.0
tu0: auto negotiation capable device
tu0 at pci1 slot 4
tu0: DEC TULIP (10/100) Ethernet Interface, hardware address: 00-00-F8-06-B1-D1
tu0: auto negotiation off: selecting 100BaseTX (UTP) port: full duplex
pci0 (primary bus:0) at mcbus0 slot 4
eisa0 at pci0
s3trio0: S3 Trio64V+ (SVGA) Plug-N-Play, 1.0 Mb
s3trio0 at pci0 slot 2
tu1: DECchip 21140: Revision: 2.0
tu1: auto negotiation capable device
tu1 at pci0 slot 3
tu1: DEC TULIP (10/100) Ethernet Interface, hardware address: 00-00-F8-06-C6-CF
tu1: auto negotiation off: selecting 100BaseTX (UTP) port: full duplex
Initializing xcr0. Please wait....
xcr0 at pci0 slot 5
RAID-ctlr-0-unit-0 at xcr0 unit 0 (unit status = ONLINE, raid level = JBOD)
RAID-ctlr-0-unit-1 at xcr0 unit 1 (unit status = ONLINE, raid level = JBOD)
RAID-ctlr-0-unit-2 at xcr0 unit 2 (unit status = ONLINE, raid level = 1)
Created FRU table binary error log packet
configure_console: No serial driver from get_info
No kernel console driver installed
NetRAIN configured.
Random number generator configured.
i2c: Server Management Hardware Present


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

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

Attempting to mount previous root file system disk to save hardware configuration information...
done


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

*** Performing CDROM Installation

Starting X Server. Please wait...

-------------------------- END --------------------------

After this graphical screen comes up and I can see Language Menu, but I cannot choose any language due to my mouse and keyboard are forzen.

Keyboard became frozen some where between "Master cpu at slot 0" and "Loading SIOP:...".

Booting from CDROM in signle-user mode are the same as this, X server starts anyway.

Also I had checked for my EISA configuration, I've no onboard graphic cards.

Thank you for your help in advance.

[Johan Brusche]

Guess you have a bootdef_dev=dra0.0.0.0.0
or similar dra.... from a previous live
of the system ?

Try:
>>>set bootdef_dev " "
>>>init
and boot the V5.1B CD again.

Johan.

[Rustam Aliyev_1]

Unsetting bootdef_dev did not helped.

Also I had no "bus_probe_algorithm" variable in my SRM. And when I done "set bus_probe_algorithm new" it created a new variable. Is there possibility that I miss someting in my system?

bus_probe_algorithm - This variable is used to determine the method used to size the PCI bus. The values are old (for OpenVMS) or new (for DIGITAL UNIX). The default is new.

[Michael Schulte zur Sur]

Hi,

this doc:
http://h30097.www3.hp.com/docs/cluster_doc/cluster_15/PS_MCAPI/NSTLLTNX.HTM

suggests that not all system support it, hence the new variable and maybe is needed only for cluster.

can you post show conf as attachment?

thanks

Michael

[Rustam Aliyev_1]

Hi Michael,

show conf and show are in attached file.

AS4100 mentioned as supported hardware here:
http://h18000.www1.hp.com/products/quickspecs/10513_div/10513_div.HTML#Supported%20Hardware

and on my installation CD:
./DOCUMENTATION/HTML/DTK_Tru64_UNIX_V5.1B_QuickSpec.html

Thank you for your help.

[Ralf Puchner]

have you checked if the onboard graphic adapter is disabled within the EISA configuration utility? It will be enabled during a firmware update...

[Rustam Aliyev_1]

Hi Ralf,

I have no onboard EISA video adapter. In EISA I have only system board with following configuration:

EISA System Slot - Digital AlphaServer 4000 Family System Board
PCD8584 I2C Controller - Always Enabled
101-KEY - Always Enabled
COM1 - Always Enabled
COM2 - Always Enabled
LPT1 - Always Enabled
PS2 MOUSE - Always Enabled

You mean that something goes wrong at boot time and I loose my EISA System Board?

[Ralf Puchner]

It doesn't matter that there is no onboard graphic device. The firmware update and ECU will always toggle the menu item "enable/disable onboard graphic adapter". So please check it also in case there is no adapter built in to be sure it is disabled!

[Rustam Aliyev_1]

There is no onboard graphic adapter or someting like this in ECU menu to enable/disable it.

I sent you whole list of my EISA devices in my previous post. All of them are 'always enabled' and I can't change the status.

Also, my VGA card is in one of the PCI0 slots.

[Ralf Puchner]

Within the ECU you will find the menu "onboard parameters/devices" (doesn't remember the exact menu item). Check if the given parameters matches your configuration. This is totally independent from real existing devices.

EISA is based on a software configuration of devices and a configured device within the EISA config utility will reserve resources independant from existing devices. The system manager must know what he have configured or selected!

After an firmware update it is recommended to verify proper settings on EISA machines.

[don cruse]

I am having this exact same problem on a 4100 that has a very similar configuration. Vga card, mylax (kzpac) raid controllers. The system hangs the same way Rustam explained.

I have tried all the things mentioned here and still no luck. Firmware updated to 6.5.

Did anyone ever figure out the problem?

Thanks.