Greetings,
I received advice and suggestions from the following folks:
Alex Gorbachev <alex_at_iss-integration.com>
Dr. Tom Blinn <tpb_at_doctor.zk3.dec.com>
Jim Fitzmaurice <jpfitz_at_fnal.gov>
John Losey <JOHLOS_at_HBSI.COM>
Saulo Murguia <saulo_murguia_at_hotmail.com>
and would especially like to thank Dr. Tom Blinn. His advice led
directly to the solution for my problem.
Dr. Blinn suggested I remove the build directory for my custom kernel
configuration (HASTINGS) and build a "fresh" custom kernel. I did
this by '/bin/rm -rf /usr/sys/HASTINGS' and re-running 'doconfig -c
HASTINGS'. The resulting vmunix was slightly larger than the previous
ones I had built and correctly recognized the 2nd DE500 when I booted
onto it. Thank You! Dr. Blinn!
It appears that the build process for V 4.0D Tru64 can go wrong in
such a fashion as to build a working kernel that does not match the
configuration file used to build it. :-(
--[Lance]
NIEHS ITSS Contract, SysAdmin Task
My original message:
Date: Wed, 01 Mar 2000 12:21:18 EST
From: "Lance A. Brown" <brown9_at_niehs.nih.gov>
To: tru64-unix-managers_at_ornl.gov
Subject: Install 2nd DE500 card in AS2100
Greetings,
I'm trying to install a 2nd DE500 10/100 Ethernet card in an AS2100
running Tru64 V4.0D, PK3. The genvmunix kernel sees the new card
as tu2 and I am able to activate the interface and use it while
running the genvmunix kernel. Booting the new kernel generated by
the procedure in the SysAdmin manual for adding new hardware
results in a kernel that does not recognize the 2nd NIC.
Following the directions in the manual, I did the following:
1. Took machine down and installed 2nd DE500.
2. Boot the genvmunix kernel, ran 'sizer -n NEW' to generate a
kernel config file with the new controller line for the 2nd
card.
3. Copied the controller line from NEW into the real config file,
HASTINGS, making sure to add it in the same location in the
HASTINGS file.
4. Ran 'doconfig -c HASTINGS' to generate a new kernel.
5. Installed the new kernel in /vmunix after saving my current
kernel away.
6. Reboot onto new kernel.
'show config' and 'show dev' display the 2nd NIC properly, but the
new kernel does not recognize or initialize tu2 during the boot
sequence.
I've scoured the archives and saw some similar problems but was
unable to locate the summaries for those problems. Can anyone
offer assistance?
Thanks!
--[Lance A. Brown]
NIEHS ITSS Contract, SysAdmin task
Received on Fri Mar 03 2000 - 16:36:27 NZDT