ES40 with true 64 unix 4.0

[Lalit Sahu]

I installed true 64 unix 4.0 on ES40.
It have two PCI network adaptor connected to it. but the problem is no interface is shown at ifconfig -a output.
How can I know whether it is detecting the network card or not. I am doubting that there is some driver problem. Am I right here.
and if it is detecting then how would I know the unix name(like ee0,tu0) of that interface.

[Steven Schweda]

> two PCI network adaptor

> how would I know the unix name(like ee0,tu0) of that interface.

You might start by giving the model(s) of
these adapters. Otherwise, it's not so easy
to guess the possible device names.

"ifconfig -a" shows the interfaces which have
been configured for TCP/IP, not all the
physical devices.

I don't know about Tru64 V4, but in
V5.1B-3, these would probably tell you
something:

/sbin/hwmgr show name
/sbin/hwmgr -view hierarchy

"tu" is a DEC "tulip" chip, like a 21143.
"ee" is an Intel chip like an 82558.

You might also look at "/var/adm/messages"
(or watch the messages at the console when
you boot the system).

For example (on an XP1000):

urtx# /sbin/hwmgr -view hierarchy | grep network
13: network tu0
23: network ee0

From "/var/adm/messages":

Feb 10 23:45:32 urtx vmunix: tu0: DECchip 21143: Revision: 4.1
Feb 10 23:45:33 urtx vmunix: tu0: auto negotiation capable device
Feb 10 23:45:33 urtx vmunix: tu0 at pci1 slot 3
Feb 10 23:45:33 urtx vmunix: tu0: DEC TULIP (10/100) Ethernet Interface, hardware address: 00-00-F8-71-D4-CD
Feb 10 23:45:33 urtx vmunix: tu0: auto negotiation on: will advertise 100BaseTX (UTP) port: full duplex

Feb 10 23:45:33 urtx vmunix: ee0: COMPAQ Intel 82558 (10/100 Mbps) Ethernet Interface
Feb 10 23:45:33 urtx vmunix: ee0: Driver Rev = V1.0.28, Chip Rev = 5, hardware address: 00-50-8B-11-3A-D5

[hiroomi]

How about booting with genvmunix ? Both interfaces are listed at CCL mode ?
If you can see interfaces at CCL mode, boot with generic kernel (genvmunix) and doconfig to recreate kernel config file and make new kernel with network driver. Unfortunately you cannot see interfaces at CCL, check & update your firmware to the latest one.

[Ivan Ferreira]

I think that ifconfig -a should show all interfaces even those that are not configured or running.

You first should ensure that the adapter is supported for the operating system version and patch kit level that you are using.

You should start with the suggestion to boot with genvmunix and generate a new kernel. If the interface is not detected, you may need to install "new hardware delivery (NHD)".

http://ftp.service.digital.com/public/unix

[Steven Schweda]

> I think that ifconfig -a should show all
> interfaces even those that are not
> configured or running.

Oops. You win. My unconfigured "ee0" had
scrolled up so far that I didn't see it.

[Al Licause]

The kernel in V4.0 Digital Unix is static vs V5.X. Where V5.x will automatically detect new devices and bring up the appropriate driver, v4 and earlier require that the appropriate device be built into the kernel.

This is done, as was suggested by booting to genvmunix then running sizer -n "filename".

This will create a new kernel configuration file usually in the /tmp directory. You can then cut and paste the discovered network devices from this file to the actual kernel configuration file in /sys/conf, usually found with the hostname of the system in upper case.

Then rebuild the kernel with doconfig -c kernel_config_file_name. When complete move that new kernel to / and reboot.