The problem was:
Physically installed network card was invisible for network
configuration tool in CGE.
Card name: Fast EtherWORKS PCI 10/100 (Digital)
Machine: Digital AlphaServer 400
OS: Digital Unix V4.0B
---------------------------------
Thanks to Dr. Tom Blinn <tpb_at_zk3.dec.com> I solved this problem.
First I would like to cite his description of installing new device:
"Basically, you have to shut down the system, power it off, open up
the cabinet, select an available option slot, and install the new
card physically into the system. Once it's installed physically, you
can power the system up, but if it starts to boot, type one or more
control-C characters to abort the boot and get to the console firmware
prompt. Issue a "show dev" command; the new network card should show
up as "ewa0" if there is no other network interface in the system.
Issue the command "show ewa0*" and you should see all the console's
environment variables associated with the card. You may need to set
the interface type to match your network wire, and you may need to set
the speed as well.
(...)
Once the card is clearly being seen by the console, and you've set the
console's variables to configure the card, then you are ready to add
support in your kernel.
Boot the generic kernel: >>>b -fl s -fi genvmunix
When you get the single user prompt, run the bcheckrc and update
commands:
# bcheckrc
# update
This will mount your local file systems. Now run sizer to build a new
skeleton configuration file:
# sizer -n NETWORK
Now, you can diff the file /tmp/NETWORK with your existing config file
in the /sys/conf directory (the file in /sys/conf will have the same
name you chose for your system's name, all upper case). Usually, the
existing config file would have the name that you'd use as a node
name, but it doesn't have to match.
You'll find differences in the hardware device section; there will be
a new "tu0" device definition. There will be other changes if you
have optional kernel components selected, or if you've made any
changes to the configuration file manually. What you need to do is
ADD the new hardware information to your existing file, so once you
see what's new, you can use a tool like grep to select the line from
/tmp/NETWORK and append it to your existing file.
If you want to use "vi" at the console, do this:
# EDITOR=vi
# TERM=vt100
# export EDITOR TERM
and you could use vi to edit your existing configuration file.
Once you've got your existing file updated to reflect the new
network adapter, you can build a new kernel:
# doconfig -c SYSTEMNAME
where SYSTEMNAME is the name of your config file in /sys/conf.
Then, once the build completes, copy the new kernel to / and do
a reboot:
# cp /sys/SYSTEMNAME/vmunix /
# sync
# reboot
Now, when the system comes up, it should see the network adapter,
report its address, and when you use the network configuration tool
you will see a Network interface option."
-----------------------------------------------------end of citation
What I had not done was the card setup from firmware.
After ">>>show dev" I identified my card as:
ewa0.0.0.12.0 EWA0 00-00-F8-31-0C-DF
I displayed the card configuiration:
>>>show ewa0_mode
and saw that I have "AUI" instead of "Twsted-Pair" so I changed it
by:
>>>set ewa0_mode Twsted-Pair
After that the rest of installation procedure went accordingly to the
description above.
Thanks also H. Blakely Williford <blakew_at_fullerbrush.com> and Kristin
(Kris)Larsen (klarsen_at_enterprise.afit.af.mil) for their advices.
Tomasz Gornicki
----------------------
Ossolineum
Wroclaw, Poland
http://www.oss.wroc.pl
----------------------
Received on Sat Sep 20 1997 - 12:54:04 NZST