From: Dr. Tom Blinn, 603-884-0646 [tpb@doctor.zk3.dec.com]
Sent: Monday, July 12, 1999 6:39 PM
To: jpfitz@fnal.gov
Subject: Some hints on the DEGPA driver kit

My trusted colleague who put together the driver kit says this about how to
get it to work:


------- Forwarded Message

Tom,

No need to re-install the kit.

Basically, when you move hardware around, you need to do a kernel rebuild.
With the DEGPA driver kit installed, you have to do one additional step
(see step 3 below).

1) boot genvmunix (>>> b -fi genvmunix)
2) Login as root
3) Dynamically load the driver (# sysconfig -c alt)
4) rebuild your kernel (# doconfig)
5) install the kernel (# mv /sys/SYSTEMNAME/vmunix /vmunix)
6) reboot

On Wed, 7 Jul 1999, Dr. Tom Blinn, 603-884-0646 wrote:

> Any insights or suggestions?  I might have some other messages about this
> on file, I'd have to look.

> Tom

> ------- Forwarded Message

> Delivery-Date: Tue, 06 Jul 99 15:09:02 -0400
> Sender: tru64-unix-managers-owner@ornl.gov
> Followup-To: poster
> Date: Tue, 06 Jul 1999 13:48:44 -0500
> From: Jim Fitzmaurice <jpfitz@fnal.gov>
> Subject: UPDATE: DEGPA Gigabit Ethernet Card.
> To: Tru64 -unix -managers <tru64-unix-managers@ornl.gov>
> Message-Id: <000501bec7e0$2c8f40a0$03e7e183@d0nt36.fnal.gov>

> Hello again,
> 	This is an update. Over the weekend I swapped the DEGPA Gigabit Ethernet
> Cards in the two systems, but it made no difference. The card was good, so
> it's something in the machine. A deeper investigation revealed this message:

> Jul  1 08:55:02 d0osfa vmunix: alt.mod: Cannot configure driver

> Not exactly a clear message. Nothing as to what's wrong and why, but, most
> likely the core of my problem.
> 	First impulse was to reinstall the driver from the CD. Unfortunately, setld
> won't let you install something that is already loaded, and it won't let you
> remove kernel components, so that won't work.
> 	Does anybody have any info on "alt.mod" or has anyone seen anything
> similar? The systems are both 4100's running 4.0D-PK3, what could cause it
> to work on one but fail on the other? Can the working driver on the first
> system be copied over the failed driver on the second system? Any other
> ideas? I like to know the right way to fix this, but right now work-arounds
> would be acceptable.

> Jim Fitzmaurice
> jpfitz@fnal.gov

------- End of Forwarded Message

If that doesn't do it for you, drop a note and maybe we can figure out what is
going wrong.

Tom