Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

0514-040 Error initializing a device into the kernel.

Status
Not open for further replies.

coolaix

Technical User
Sep 4, 2007
17
US
I'm having trouble configuring the ent2.
Getting this error after cfgmgr.

cfgmgr
Method error (/usr/lib/methods/cfggoent -l ent2 ):
0514-040 Error initializing a device into the kernel.

Google says may be a problem with the ODM or driver.

My question is , can some will tell me , which files in the /etc/drivers are associated wit etherner Adapters.
Any help will be much appreciated.



 
What's the output of:

lscfg -l ent2

You will find a number at the end of the line in the output. Use it along with lslpp -L to find the device driver for it

lslpp -L | grep number_found_above

Try to check the output of cfgmgr -v as well and find the errors associated with ent2

Regards,
Khalid
 
Perhaps additional drivers need to be installed for this device? Or the device driver runs in 64bit kernel mode only?


HTH,

p5wizard
 
Hmmm ...

We had a similar problem when trying to install some scsi drivers for some new devices.

I'm not sure whether this will help in your case or not.

Problem was that we had 2 devices using the same "connwhere" setting in the ODM.

Try this:

odmget CuDv | more

--> Search for ent2 (Assuming you already HAVE an ent2 entry in the odm) and write down the value vor "connwhere".
--> See if there are any other devices with the same connwhere value somewhere in the CuDv.
--> If so perform an "rmdev -dl <devicename>" for all those devices including the ent2 and run cfgmgr afterwards.

That's how we were able to solve the problem.
Also there shouldn't be any problems with this procedure be sure to run an mksysb before trying anything ...

Regards
Thomas
 
Khalidaaa--> this is how it looks.

1304>lsdev -Cc adapter | grep ent
root@aixprod60:/
1304>lscfg -l ent2
ent2 U7879.001.DQD0MHP-P1-C3-T1 10/100/1000 Base-TX PCI-X Adapter (14106902)

1305>lslpp -L | grep 14106902
devices.pci.14106902.diag
devices.pci.14106902.rte 5.3.0.50 C F 10/100/1000 Base-TX PCI-X
1306>

tsch---> your solution is good but not feasible here , as I have lot of things connected from that "connwhere".



 
Logged a call with IBM , they say I'll have to reseed the NIC, reseeding is pulling the NIC (its hot swappable in my case )and putting it back in , the run cfgmgr.

Rgds
 
IBM says so:).
Change is scheduled this weekend .
 
They mean "reseating" the adapter, but you probably just misunderstood that word.

Any reason why you would wait until the weekend? I mean it's hot-swap and all...


HTH,

p5wizard
 
Its the process out here buddy..ant thing that you want to do in the production box, has to be in the weekend.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top