The Q NIC shows E04/E05/E06 and the original CHANDEV.CONF reads E03/E04/E05 because I changed from 3/4/5 to 4/5/6 to see if that would fix it and then I did the Q NIC to respond to Mark.
Last night I took out the chandev= string and rebooted. The LCS driver failed to come up but the QETH driver worked fine. There does seem to be some incompatibility between LCS and QETH. I doubt IBM ever tried both in the same linux server. The NICs will be defined in the directory entry for production mode. This is still testing. But with this apparent incompatibility, I might be able to force the network/security people to let me test the more recent RedHat system. The linux system is rebooted to run each test since I am unsure of all the commands necessary to unload/load/initialize these different drivers. A 'shutdown -r now' works just fine. This is an older TurboLinux, so there is no manual entry for chandev. I am attaching the output of 'cat /proc/chandev' to this email. /Thomas Kern /301-903-2211 > -----Original Message----- > From: Dennis Musselwhite [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 31, 2004 20:55 > To: [EMAIL PROTECTED] > Subject: Re: Adding QDIO guest lan to server > > I think Mark already pointed out a significant problem (the chandev > parameter line inside /etc/chandev.conf). You can find out > how much the > channel device layer actually understood from your > configuration file by > showing the /proc/chandev output (cat /proc/chandev). You > should see a > table near the end of the output that lists the options (like > portname) > associated with different device ranges. > > Also... your Q NIC shows 0E04, 0E05, 0E06 but your > /etc/chandev.conf shows > eth2 with 0xe03,0xe04,0xe05 (which must have led to some of > the confusion > during initialization. Please continue to define your NIC > starting on an > even device number and adjust your /etc/chandev.conf to > match. The OSA > Express now allows odd/even pairs for the read and write > control devices, > but Guest LAN does not allow that yet. > > You have portname defined for both interfaces in > /etc/chandev.conf, and the > portname does NOT have to match anybody else because you do > not share these > virtual NICs. I don't understand why the portname would be > rejected unless > the earlier problem (the extra line in your chandev.conf) > prevented the > channel device layer from processing the rest of the > configuration file. > > Suggestion: Add the 'define nic' and 'couple' commands to > your profile exec > for this guest so they are done each time you start this guest. The > devices exist (and are coupled) before you IPL Linux. > > If you modify your /etc/chandev.conf and don't restart Linux, > remember to > tell the channel device layer to read your configuration file > and reprobe > for devices (see 'man chandev' for specific commands that you > can echo to > /proc/chandev). ---------------------------------------------------------------------- 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
proc.chandev
Description: Binary data
