DEGPA-TA on a ES40 with UNIX TRU64 40F

[Helder Lopes]

Hello I have a running server with 40F and with the lastest firmware 6.9.1.

I installed the DEGPA-TA and removed the other NIC card which is a DECtulip ( not sure) and entered console did show dev and nothing.

What am I doing wrong shouldn't show on console when I do show dev??

Any help is apreciated

[Michael Schulte zur Sur]

Helder,

it seems, you've updated the firmware.
Does
show config
show anything?
In which slot did you install it?

greetings,

Michael

[Johan Brusche]

Helder,

The console does not know DEGPA's, it will show a device in a PCI slot, but will not show an identification.

Important is that you should have patchkit#8 installed on V4.0F, then boot from genvmunix, run a doconfig (not -c), and reboot with new kernel.

Have fun,

__ Johan.

[Ralf Puchner]

Have a look into the supported option list of ES40:

DEGPA-TA:

http://h18002.www1.hp.com/alphaserver/options/ases40/ases40_%20%20-degpa-ta.html

# For UNIX:

During installation of DEGPA driver, only one adapter per PCI bus allowed. After installing target kernel, additional adapters may be installed on same PCI bus. Rebuilding kernel not necessary.

* v4.0F:
o Patch Kit 6 (BL17): DUV40FAS0006-20010620.tar required. See most up-to-date patch information.

So please check proper installation of the patchkit (for the specific patch required by DEGPA-TA - 99,9% root cause of problem)

[Helder Lopes]

I have on the alpha patch 6.

But when I did show dev without the card I have the same devices as when I have the card in.

is there any other way of finding out if unix reconises the card.

Thanks ..

[Johan Brusche]

Once more.....

1)
Firmware update OK ?
2)
You need to boot with a /genvmunix that supports the DEGPA-TA. (As said the one from PK#8)

Within the startup messages you should see the DEGPA being recognized, then run doconfig, to make new kernel -> /vmunix.

__ Johan.

[Helder Lopes]

so I have to install patch 8 file "DUV40FB22AS0008-20030730" and then it should detect my card?

My problem is that I have oracle on the machine I have to have some precautions on the machine.

but in the bios should it be detected??

thanks ..

[Helder Lopes]

Is it possible to provide a step by step procedure on what should be done ..


Thanks..

[Johan Brusche]

There is a pdf format installation manual in each patchkit !!

__ Johan.

[Ralf Puchner]

Installing a patchkit means not to have the right part of the patch installed! So please doublecheck manually if the right module was properly installed!

Life could be soo easy!

[Helder Lopes]

HI:
´
I installed patch 8 doing ./patch and following the screen.

I installed everything on the machine I reboot the alpha and I went to netsetup the network card did not show up.

Am I doing something wrong?

And how can I solve this situation??

I'm new to UNIX and help is apreciated.

Thank

[helder Lopes_1]

What I meant was I did ./dupatch in the patch_kit 8.

What am I doing wrong..
thanks

[Ralf Puchner]

starting a program is not equal to verify its proper work. dupatch only starts the setup process it will not quarantee all the patch were properly installed! It's up to the administrator itself to be sure the output will match the input (IT-basics)

So go through the logfile and check if the patches - required for the adapter - are properly installed and within the selected range of patches!

[Helder Lopes_2]

When I installed the patch I selected all the above patch it didn't give me any erro.

What is the name of the patch?? that I should look for to verify that it was sucessfully installed.

Thanks

[helder Lopes_1]

Hi :
I'm really confused
Where is the logfile of the patch??or what is it's name I can do a find on it.

Thanks

[Michael Schulte zur Sur]

Helder,

you will find the patch logs in
/var/adm/patch/log

greetings,

Michael

[Helder Lopes_2]

IN the log what should like look for??
Is there any especific patch for the card??

Any details would be apreciated.

Thanks

[Ralf Puchner]

Maybe to read the answers carefully: As written in one of my previous answers:

DUV40FAS0006-20010620

All patches are delivered with an description, so why not going thru the description and check the kernel modules itself by using "sum" and verify proper kernel rebuild?

You have all information to solve your problem: howto setup the adapter, required software and patches, hardware setup information, firmware etc. it is all well documented and given within the answers.

[Al Licause]

If you have a degpa then the driver will be alt.mod. See if a file called alt.mod exists in /sys/BINARY.

Also check to see if there is any reference to alt: DEGPA in /etc/sysconfigtab. That section would contain information about the
device such as vendor_id, device_id, and more.

Try typing sysconfig -c alt
This will attempt to load the alt subsystem for the degpa. If this is successful, try sysconfig -q alt and it should show the
driver version that has been installed.

The base operating system contains what you need for a fiber version of the degpa, but only the latest patch kit, pk8 has the driver required for the twisted-pair version of this device.

This is the note from patch kit 8 regarding the driver:

PROBLEM: (none) (PATCH ID: OSF440-480)
********
This patch provides support for the DEGPA-TA (1000BaseT) Gigabit Ethernet device.

Often times trying to figure out just which patches were installed can be a difficult task given the fact that the patches are often referenced with several different designations.


If the driver loads, but is then lost on reboot, you may need to add the
following to the kernel configuration file which is /sys/conf/{YOUR_HOST_NAME}.

In this file, find the "Static Driver Definitions" section and if not
there, add the following line:

config_driver alt

Then save the file and rebuild the kernel (doconfig -c {YOUR_HOST_NAME}).
When complete, move the new kernel into the / partition and reboot.

Let us know if you still don't see the device.....