My QDIO/QETH problem has been resolved. We upgraded to the latest k_timer kernel patches and the qeth unresolved reference during modprobe disappeared. Thanks everyone and special thanks to Alan and Jay for your help with this extremely elusive problem. Al Schilla State of Minnesota.
-----Original Message----- From: Robert J Brenneman [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2003 1:22 PM To: [EMAIL PROTECTED] Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP rpm -qi k_timer will show you the info page for your installed k_timer kernel. rpm -qpi k_timer-20020708.rpm will show you the info page for the rpm you're trying to install. If the release numbers and build dates match, then you have the right kernel installed. You may want to install it anyway to make sure you got all the pieces when you installed it last time. It it's giving you trouble rpm -ivh --force k_timer<mumble>.rpm will force it on. Go ahead and get the newest kernel, it can only be better, right? :) (actually I think this one fixes some DASD recovery issues also... a good thing) Jay Brenneman Linux Test and Integration Center T/L: 295 - 7745 Extern: 845 - 435 - 7745 [EMAIL PROTECTED] Alan Schilla <[EMAIL PROTECTED] To: [EMAIL PROTECTED] te.mn.us> cc: Sent by: Linux on Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP 390 Port <[EMAIL PROTECTED] IST.EDU> 03/10/2003 01:12 PM Please respond to Linux on 390 Port Thanks Jay, I think we will go with the 0301. I have been trying to install the k_timer-20020708.rpm and I get k_timer-2.4.7-24 is already installed from rpm package manager. How can I check if this is truely the kernel image I am running, and if I am already working with this version of k_timer, how do I get qeth to load? Should I wait until zVM is upgraded? I also see that SuSE has just released a new patches to k_timer. They do not appear to effect qdio, qeth other than possibly the OSA broadcast patch but should I just get this new k_timer.rpm applied and see if that resolves my problem? Thanks, Al -----Original Message----- From: Robert J Brenneman [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2003 3:46 PM To: [EMAIL PROTECTED] Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP 0201 is the GA level, 0202 is last fall's RSU package, 0301 would be the new one, I guess. I would consider 0202 to be the base level for the newer kernel, It throws a message about having an up to date VM system when you apply it. 0301 would probably be fine too, so go with that. Guess I better go order a service tape.... Jay Brenneman Alan Schilla <[EMAIL PROTECTED] To: [EMAIL PROTECTED] te.mn.us> cc: Sent by: Linux on Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP 390 Port <[EMAIL PROTECTED] IST.EDU> 03/07/2003 08:05 AM Please respond to Linux on 390 Port This is probably a VM LISTSERV question but I think it has value with this thread. My zVM person found 0301 as more current than 0202. Would you recommend 0301 or 0202? We are currently 0201. Al Schilla -----Original Message----- From: Robert J Brenneman [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 3:07 PM To: [EMAIL PROTECTED] Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP Also be sure to have you VM system up to date. I have used this kernel and driver set successfully on z/VM 4.3 RSU 0202 Jay Brenneman Alan Schilla <[EMAIL PROTECTED] To: [EMAIL PROTECTED] te.mn.us> cc: Sent by: Linux on Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP 390 Port <[EMAIL PROTECTED] IST.EDU> 03/06/03 03:54 PM Please respond to Linux on 390 Port Thanks Jay. The qdio, qeth drivers used are the drivers you indicate. Also, I cannot say for sure but I believe the timer kernal is 20020502 so I will look at updating that to the more current 20020708. Thanks, Al -----Original Message----- From: Robert J Brenneman [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 10:59 AM To: [EMAIL PROTECTED] Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP Note to those not interested in this thread: these updates for SLES-7 31bit provide a NOTICABLE IMPROVEMENT in cpu consumption for VM Linux-en attached to real OSA devices. Alan, It does indeed look like you have a driver / kernel mismatch. I dont remember the SuSE kernel dates for the various releases, but I remember that the inital releases did not work well with Guest Lan. Is this an updated kernel? If so, where did you get it? Try using Yast Online Update (YOU) if you have another network connection available, or if you can temporarily attach your VM guest to a real OSA with internet access. You should download the latest qdio / qeth drivers from developerworks: http://www-124.ibm.com/developerworks/opensource/linux390/current2_4_x-augus t2001.shtml#SBCRocos7 (check that link for chopping or wrapping) You should probably also go to the SuSE maintenance web and pick up the newest timer kernel RPM, it will match up with the above drivers nicely, but still needs the -f flag in /etc/modules.conf http://sdb.suse.de/download/s390/update/SuSE-SLES/7/rpm/k_timer-20020708.rpm (check for chopping... grumble Notes grumble.... ) That link will require a userid & password FYI - unless you are planning to run more than 15 or so linux guests under VM, you will see better performance from using the standard kernel, not the timer patched one. The timer patch does appear to affect performance in heavily loaded systems with time sensitive workloads. The general rule of thumb I've been using is standard kernel on SAP Linuxen, DB2, WAS and the like running heavy production workloads, and timer patched kernels on server consolidation systems which may not be heavily stressed all the time. Jay Brenneman Alan Schilla <[EMAIL PROTECTED] To: [EMAIL PROTECTED] te.mn.us> cc: Sent by: Linux on Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP 390 Port <[EMAIL PROTECTED] IST.EDU> 03/06/03 11:09 AM Please respond to Linux on 390 Port I sure can. Here are all rhe messages from insmod qdio, insmod qeth: lxisdn01:~ # insmod -f qdio insmod -f qdio Using /lib/modules/2.4.7-timer-SMP/misc/qdio.o Warning: kernel-module version mismatch /lib/modules/2.4.7-timer-SMP/misc/qdio.o was compiled for kernel version 2.4.7-timer while this kernel is version 2.4.7-timer-SMP qdio: loading QDIO base support version 2 ($Revision: 1.78.2.9 $/$Revision: 1.4 .2.4 $) debug: qdio_setup: new level 2 debug: qdio_labs: new level 2 debug: qdio_sense: new level 2 debug: qdio_trace: new level 2 lxisdn01:~ # insmod -f qeth insmod -f qeth Using /lib/modules/2.4.7-timer-SMP/net/qeth.o Warning: kernel-module version mismatch /lib/modules/2.4.7-timer-SMP/net/qeth.o was compiled for kernel version 2.4.7-timer while this kernel is version 2.4.7-timer-SMP /lib/modules/2.4.7-timer-SMP/net/qeth.o: unresolved symbol __copy_from_user_asm lxisdn01:~ # Thanks, Al Schilla State of Minnesota -----Original Message----- From: Robert J Brenneman [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 4:11 PM To: [EMAIL PROTECTED] Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP >I also tried an insmod -f qdio and insmod -f qeth and it >still gave the version mismatch message but it appeared to be more a warning >message, but then I also received an unresolved reference message from the >insmod -f qeth. Can you cut and paste the error message for the unresolved reference or copy it exactly? You may just have to load the ipv6 module also in addition to qdio and qeth. Jay Brenneman Alan Schilla <[EMAIL PROTECTED] To: [EMAIL PROTECTED] te.mn.us> cc: Sent by: Linux on Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP 390 Port <[EMAIL PROTECTED] IST.EDU> 03/05/2003 01:41 PM Please respond to Linux on 390 Port Thanks Sergey. I am not sure where the parm below would be added to modules.conf andI tried a couple of different things but I still do not get the QETH interface. I also tried an insmod -f qdio and insmod -f qeth and it still gave the version mismatch message but it appeared to be more a warning message, but then I also received an unresolved reference message from the insmod -f qeth. Anyway it still did not work. Below is my /etc/chandev.conf used to try creating this interface. I have removed comments to shorten the mailing. Can I provide any other information that would be helpful? cat /etc/chandev.conf --------------------------------------------------------------------------- # The installation of SuSE Linux adds the network device that was # used for installation here: add_parms,0x10,0x0700,0x0702,portname:LNXDQ qeth0,0x0700,0x0701,0x0702 ctc0,0x0d00,0x0d01,0,0 lxisdn01:~ # Thanks For YOur Help, Al Schilla State of Minnesota -----Original Message----- From: Sergey Korzhevsky [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 8:22 AM To: [EMAIL PROTECTED] Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP Add to /etc/modules.conf line insmod_opt=-f Then try new drivers. If it won't help, get to us your /etc/chandev.conf WBR, Sergey Alan Schilla <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 04.03.2003 22:53 Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP I am trying to activate a virtual QDIO, QETH link between zVM 4.3 TCPIP guest and a SuSE guest version: Linux Version 2.4.7-timer-SMP, Compiled #1 SMP Tue Nov 26 23:25:11 GMT 2002 When I try activating the QDIO, QETH modules that were on the system with this version I received: insmod qdio Using /lib/modules/2.4.7-timer-SMP/misc/qdio.o qdio: loading QDIO base support version 2 ($Revision: 1.78.2.9 $/$Revision: 1.44 .2.3 $) debug: qdio_setup: new level 2 debug: qdio_labs: new level 2 debug: qdio_sense: new level 2 debug: qdio_trace: new level 2 lxisdn01:~ # insmod qeth Using /lib/modules/2.4.7-timer-SMP/net/qeth.o qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.136.2.7 $/$Revision: 1 .53.2.3 $/$Revision: 1.18 $) qeth: allocated 0 spare buffers debug: qeth_setup: new level 3 debug: qeth_misc: new level 2 debug: qeth_data: new level 2 debug: qeth_control: new level 2 debug: qeth_sense: new level 2 debug: qeth_qerr: new level 2 debug: qeth_trace: new level 2 qeth: Trying to use card with devnos 0x700/0x701/0x702 qeth: received an IDX TERMINATE on irq 0x8/0x9 with cause code 0x22 -- try anot her portname qeth: received an IDX TERMINATE on irq 0x8/0x9 with cause code 0x22 -- try anot her portname qeth: There were problems in hard-setting up the card. debug: unregistering qeth_setup debug: unregistering qeth_qerr debug: unregistering qeth_sense debug: unregistering qeth_misc debug: unregistering qeth_data debug: unregistering qeth_control debug: unregistering qeth_trace /lib/modules/2.4.7-timer-SMP/net/qeth.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including inva lid IO or IRQ parameters I get this TRY ANOTHER PORT NAME no matter what I use for portname even though a Q NIC DETAILS and Q V for the QDIO device numbers 700-702 show: CP Q NIC DETAILS Adapter 0700 Type: QDIO Name: UNASSIGNED Devices: 3 Port 0 MAC: 00-04-AC-00-00-02 LAN: SYSTEM LNXLAN MFS: 8192 RX Packets: 0 Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 0 TX Bytes: 0 Connection Name: HALLOLE State: CM_CONNECT Device: 0700 Unit: 000 Role: CTL-READ Device: 0701 Unit: 001 Role: CTL-WRITE Device: 0702 Unit: 002 Role: DATA Q V 700-702 OSA 0700 ON NIC 0700 UNIT 000 SUBCHANNEL = 0008 0700 QDIO-ELIGIBLE OSA 0701 ON NIC 0700 UNIT 001 SUBCHANNEL = 0009 0701 QDIO-ELIGIBLE OSA 0702 ON NIC 0700 UNIT 002 SUBCHANNEL = 000A 0702 QDIO-ELIGIBLE I have also tried downloading the latest 2.4.7 qdio, qeth drivers and activating these and recieve: lxisdn01:~ # modprobe qeth modprobe qeth /lib/modules/2.4.7-timer-SMP/misc/qdio.o: kernel-module version mismatch /lib/modules/2.4.7-timer-SMP/misc/qdio.o was compiled for kernel version 2.4.7-timer while this kernel is version 2.4.7-timer-SMP. /lib/modules/2.4.7-timer-SMP/misc/qdio.o: insmod /lib/modules/2.4.7-timer-SMP/mi sc/qdio.o failed /lib/modules/2.4.7-timer-SMP/misc/qdio.o: insmod qeth failed lxisdn01:~ # Does anyone know how I can get this to work or where I may find the latest QDIO, QETH drivers for SuSE-2.4.7-SMP kernel? Thanks, Al Schilla State of Minnesota
