Hi Mark, 

I issued a "modprobe qeth" again, and the output was identical to what I sent 
you previously.  "ifconfig -a" output was also identical to what I sent 
previously.  Needless to say, the "rcnetwork start" didn't accomplish much.  

As for initrd not having the logic to load dqio and qeth, I think it does.  I 
did a "shutdown -r" and watched the reboot very carefully again.  The following 
sequence comes up on the HMC Integrated Console: 

Setting up network interfaces 
lo
lo    IP address 127.0.0.1/8
[1A done. 
lo
waiting for mandatory devices lcs-bus-ccw-0.0.0510  lcs-bus-ccw-0.0.0512   
__NSC__
2
0
      lcs-bus-ccw-0.0.0510   No interface found 
      lcs-bus-ccw-0.0.0512   No interface found
Setting up service network......    ..failed.

And then the Samba startup, CUPS startup, Apache startup, etc., all fail.

0.0.0510 and 0.0.0512 are the proper device numbers for the OSA ports.  And the 
OSA card and ports are shared with 4 other LPARs, and they're working just 
fine, so I am pretty sure it's not an OSA problem.  And I don't understand how 
moving /usr could cause this, unless I deleted something somewhere that I 
wasn't supposed to.  

I am completely stumped, which is not all that hard, given what I know about 
Linux.  The only thing I can think of next would be a POR of the 9672, which I 
can't do until September sometime, or a re-install of SLES 9 SP3, or both.  

Any/all ideas appreciated.

Dave 



Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
[EMAIL PROTECTED]

>>> "Mark Post" <[EMAIL PROTECTED]> 8/30/2007 8:10 AM >>>

Dave, sorry it took me so long to get back to you about this.

The lsmod command showed that the qdio and qeth modules were not loaded.  The 
modprobe you did looked pretty successful.  If you did an "ifconfig -a" after 
that, eth0 might have shown up, in which case an "rcnetwork start" command 
should bring things up the rest of the way.

I have no idea why your initrd doesn't have the logic in it to load the qdio 
and qeth modules at boot time.  But, once your system is back up and running, 
you should re-run mkinitrd, and re-run zipl.  Then, reboot to make sure things 
come up the way you expect.


Mark Post

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to