Ok, then what happens if you do a "modprobe qeth" command?
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Matt Gourley Sent: Monday, June 27, 2005 8:39 AM To: [email protected] Subject: Re: RPMs to keep/purge after installation 'lsmod | grep qdio' comes up with information; 'lsmod | grep qeth' does not. I think this is where we're running into issues, as an interface does not get created. 'dmesg' doesn't say anything about either qdio or qeth. Thanks, -Matt Post, Mark K wrote: >If you want to avoid re-installing, we'll need diagnostic information. >Do the qeth and qdio kernel modules load successfully? (lsmod) Do they >create an interface? (ifconfig -a) If not, what shows up in the kernel >ring buffer? (dmesg) > > >Mark Post > >-----Original Message----- >From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of >Matt Gourley >Sent: Friday, June 24, 2005 9:10 AM >To: [email protected] >Subject: Re: RPMs to keep/purge after installation > >Well, I did spend some time getting rid of a bunch of RPMs on the >golden image yesterday. Unfortunately for me, one or more of the RPMs >I nuked were necessary for the network configuration (qeth). The >golden image boots, but cannot connect to the network. Luckily, we had >already setup our controller per the book, and I can copy any RPM from >the source tree >(/nfs) to the golden image (/sles9golden), reboot the golden image, and >re-install the rpm. I've already done this for the vlan RPM, but the >golden image still will not come up on the network. Short of listing >every RPM I purged, can anyone out there tell me what RPMs are necessary >for qeth to run? Or is there further configuration I need to do on my >golden image? (Oh boy, a chance to work on my ed(1) skills! :-) ) ---------------------------------------------------------------------- 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
