Hello Unix admins,
See end of this message for original post.
I wish to thank Dr. Tom Blinn for his two replies to my query, which I
both reprint further down this message.
Unfortunately, none of his wisdom could help me make our installation of
Tru64 UNIX v4.0F able to recognize and use the DE-600 network adapter
installed in the ES40.
We fought for over one week with "New Hardware Delivery" (NHD) CDs
version 1, 2 and 3 for 4.0F, with the help of our local Compaq Services,
which were about as much puzzled as we were on this issue. Having
double- and tripled-checked that we were following the exact
instructions to installl the NHDs (which vary slightly for version to
version) and having exhausted our imagination as for which tests we
could have performed, we ended up giving up on 4.0F and we installed
4.0G, which natively knows about the DE-600. We made this decision when
Compaq staff confirmed us that some ES40 (and also some 4100's) **could
not** ever be upgraded using NHD kits during in-factory tests :-)
So, if one sees error messages during a NHD installation like:
"kio_read: xx undefined symbols"
"Internal error in OSF_BOOT: bad sc in merged external symbol in
layout()"
"Internal limit reached in OSF_BOOT: out of space for compressed
relocations"
you may as well have one of these servers which will not be upgradeable
with an NHD kit.
Here are Tom's replies:
#1:
TPB>I have not seen the problem you describe, but I know enough about
how the NHD
TPB>installation procedure and the bootlinking process work to know that
you've
TPB>got something wrong with your system installation.
TPB>
TPB>In your root directory, there should be a GENERIC file which is a
text file.
TPB>It lists all of the kernel modules that need to be loaded to
boot-link the
TPB>kernel. When you do the NHD supplement, you add modules from the
NHD media
TPB>during the boot process. On your system, after all the listed
modules have
TPB>been loaded into memory, either from the /sys/BINARY directory in
your root
TPB>disk or from the NHD media, there are still undefined symbols.
TPB>
TPB>As I recall, the NHD media is adding the "alt" driver, so you would
add the
TPB>"config_driver alt" line in the /usr/sys/conf/GENERIC configuration
file to
TPB>build a static generic kernel with the driver included. What
happens if you
TPB>add this line by hand and try to rebuild the GENERIC kernel with
doconfig?
TPB>What happens if you try to build the GENERIC kernel without
modifying the
TPB>existing config file? (There are other things in the NHD kit, but
the way
TPB>the kit is installed, you should be able to link a GENERIC kernel by
using
TPB>the doconfig -c GENERIC command.)
TPB>
TPB>I suspect you'll find you can't build a new GENERIC kernel, but
that's just
TPB>a guess.
TPB>
TPB>Do you have ANY patches on the system in question? Are you CERTAIN
that it
TPB>has correct kernel modules? Because the failure you are seeing
looks like
TPB>you've got some bad kernel modules in /sys/BINARY or a bad GENERIC
file in
TPB>the root directory.
TPB>
TPB>I can tell you that the NHD3 kit was tested on a mix of V4.0F
systems and
TPB>what you are reporting simply was not seen during testing, so I am
pretty
TPB>sure it's something unique to your system, not a general problem.
But it
TPB>is very hard to tell you exactly what is wrong.
TPB>
TPB>Tom
#2:
TPB>The "unresolved symbols" is definitely indicative of a mismatch
among some
TPB>of the kernel modules on your system.
TPB>
TPB>There is a module in /sys/BINARY called "kio.mod". I don't believe
that
TPB>the message means there are six or five unresolved symbols in
"kio_read"
TPB>but rather that something is trying to call "kio_read" (it is a
routine
TPB>in the kernel interfaces for reading files from the file system,
used to
TPB>read /etc/sysconfigtab for example and also in reading the DDR
database),
TPB>and that the symbol "kio_read" is missing. The definition should be
in
TPB>the "kio.mod" file.
TPB>
TPB>The bootlink is just linking the modules on your system (from
/sys/BINARY)
TPB>along with what's on the NHD CD. Be sure that your osf_boot got
replaced
TPB>with the one from the NHD CD, or that you are booting off the NHD
CDROM
TPB>as described in the NHD3 release notes (the old osf_boot delivered
on the
TPB>original V4.0F media is buggy, and it just might be the root cause
of the
TPB>problems you are seeing. You have to do the boot JUST RIGHT).
TPB>
TPB>If the /GENERIC text file doesn't list "kio.mod" in the list of
modules,
TPB>then that would lead to the error you report, but there would be
others
TPB>as well, I believe (the module has several entry points it defines).
TPB>
TPB>Having a bad osf_boot that doesn't boot link correctly is a more
likely
TPB>root cause. Or not getting all the console variables set EXACTLY
RIGHT
TPB>(that is, failing to follow the NHD3 instructions EXACTLY) would
lead to
TPB>problems.
TPB>
TPB>If all you're after is the DE600 driver, I'm pretty sure that's the
alt
TPB>driver, I would have to double check. If that was already in V4.0F
(I
TPB>don't have a V4.0F system handy to double check), then you don't
need
TPB>to use the NHD CDROM media to add it, right?
TPB>
TPB>Tom
##### ORIGINAL POST #####
>Hello admins,
>
>We just received a new Alpha box, an ES40, equipped with a DE-600-AA
>network interface card. This card is not directly supported by Tru64
>Unix v4.0f, so I have to install the "New Hardware Delivery" CD (NHD
for
>short) which will enable the NIC. I downloaded nhd3.tar.gz from
>http://ftp1.support.compaq.com/public/unix/v4.0f/, followed the
>instructions to burn a CD and also a good old RZ26 disk with the same
>ISO image.
>
>Booting from either the CD or this RZ26 is OK. Then follows a procedure
>to grasp new modules, which poses no problem. My problem is that
shortly
>after reading the GENERIC kernel modules and NHD-provided modules (206
>of them in my installation), the bootlinking phase fails with a message
>like:
>
>error: undefined:
>
>kio_read
>6 undefined symbols, aborting load
>
>and the system returns to the SRM prompt.
>
>I have tried to install NHD3 first on an unpatched installation of
>TU4.0F, and then an installation patched with PK4. The result is the
>same in both, expect for the number of undefined symbols, which is down
>to 5 when PK4 is installed.
>
>Has anyone seen such problems with NHD3? Any suggestions/hints/comments
>appreciated. TIA
===============================================
Charles Vachon tel: (418) 627-6355 x2760
email: cvachon2_at_mrn.gouv.qc.ca
Administrateur de système
FRCQ/Ministère des Ressources
Naturelles du Québec
===============================================
Received on Thu Nov 09 2000 - 21:12:15 NZDT