We have several alphaserver 4100s running DU4.0d or du4.0e that only catch
the tail end of the boot information. Observe:
********************************* ENTRY 1. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 300. SYSTEM STARTUP
SEQUENCE NUMBER 1.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Apr 15 05:43:14 1999
OCCURRED ON SYSTEM devora0
SYSTEM ID x00070016
SYSTYPE x00000000
MESSAGE aulting to 10BaseT (UTP) port: half
_duplex
tu6: DECchip 21143: Revision: 3.0
tu6: auto negotiation capable device
tu6 at pci2000 slot 2
tu6: DEC TULIP (10/100) Ethernet
_Interface, hardware address:
_00-06-2B-00-2A-52
tu6: no console mode: defaulting to
_10BaseT (UTP) port: half duplex
tu7: DECchip 21143: Revision: 3.0
tu7: auto negotiation capable device
tu7 at pci2000 slot 3
tu7: DEC TULIP (10/100) Ethernet
_Interface, hardware address:
_00-06-2B-00-2A-53
tu7: no console mode: defaulting to
_10BaseT (UTP) port: half duplex
Created FRU table binary error log
_packet
kernel console: trio0
dli: configured
I have two questions:
What can I do to fix this so the entire boot is logged?
Till the next boot, what command can I run to get info on what hardware
is on the system??
TIA!
Judith Reed
jreed_at_appliedtheory.com
Received on Mon Jun 28 1999 - 15:06:27 NZST