Missing lan card error message

[jerry1]

I took a spare lan card out of the server and
I keep getting this error message logged.
I have tried doing an insf -e, ioscan -fn.

gelan_verifyfw: Text segment not correct...
gelan2: Unable to verify firmware
gelan2: Init error at 1/0/0/1/0
wsio_claim init failed isc=0xc6d40400 name=gelan

[Dan Deck]

Hi,
If you don't have any other gelan cards in the system - then go into SAM and remove the driver for this card and reboot. Move it to the out.
Just make sure you don't have any other cards using this driver otherwise they will not work any more.

DD

[jerry1]

It does not show up. When I check sam, I
see lan0(used) lan3 not used, lan4 not used.
There is no lan2.

In lanscan there is no lan2:

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/1/0 0x00306E2848F5 0 UP lan0 snap0 1 ETHER Yes 119
1/0/2/0/0/6/0 0x00306E2DB83C 3 UP lan3 snap3 3 ETHER Yes 119
1/0/2/0/0/7/0 0x00306E2DB83D 4 UP lan4 snap4 4 ETHER Yes 119


In ioscan -funClan. It does not show up
either. There is no lan2 1/0/0/1/0.

# ioscan -funClan
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
lan 0 0/0/0/1/0 gelan CLAIMED INTERFACE HP A6096-69001 PCI 1000Base-T Built-in I/O
lan 3 1/0/2/0/0/6/0 btlan CLAIMED INTERFACE HP A5838A PCI 100Base-TX/SCSI COMBO
/dev/diag/lan3 /dev/ether3 /dev/lan3
lan 4 1/0/2/0/0/7/0 btlan CLAIMED INTERFACE HP A5838A PCI 100Base-TX/SCSI COMBO
/dev/diag/lan4 /dev/ether4 /dev/lan4

Nothing in /dev for lan2 either. If it was lan2 ever. ???

[Duncan Edmonstone]

where does this message get logged? On the console? in sysylog.log? when you run certain commands? only at boot?

I guess there's a possibility that lan2 is still mentioned in one of the config files in /etc/rc.config.d

would be interesting to see if:

grep lan2 /etc/rc.config.d/*

turned up anything

HTH

Duncan

[jerry1]

There is nothing in /etc/rc.config.d/*.
Here is grep of gelan_verifyfw from
syslog.log:

# grep gelan_verifyfw syslog.log
Jul 4 00:11:29 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 5 00:00:29 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 5 23:50:07 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 5 23:50:15 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 7 00:00:30 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 11 00:11:32 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 12 00:00:30 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 12 23:50:08 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 12 23:50:16 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 14 00:00:31 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 18 00:11:28 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 19 00:00:29 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 19 23:50:08 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 19 23:50:15 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 21 00:00:29 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 24 11:13:18 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...
Jul 24 11:13:23 dbsvr1 vmunix: gelan_verifyfw: Text segment not correct...

[TTr]

As Duncan hinted, specifically check the /etc/rc.config.d/hpigelanconf file. If any of the parameters in this file have been initialized the /sbin/init.d/hpigelan is probably trying to initialize the nonexistent card. There should be nothing to the right of the equal sign in all the variables of the /etc/rc.config.d/hpigelanconf file.

[jerry1]

And as I specifically stated.

"There is nothing in /etc/rc.config.d/*"

Hint: /etc/rc.config.d/hpigelanconf