OSA1 is what is defined in the VTAM TRLE and caps does not make a difference.
Glen -----Original Message----- From: Mark Kliner [mailto:MarkK@;VSP.com] Sent: Wednesday, November 06, 2002 9:37 AM To: [EMAIL PROTECTED] Subject: Re: OSA express gb adapter Is that indeed the same portname defined in the VTAM TRLE setup under OS/390? Does it need to be specified as upper-case? Mark Kliner Systems Programmer Vision Service Plan Rancho Cordova, CA -----Original Message----- From: Crowley, Glen L [mailto:GLCROWLEY@;arkbluecross.com] Sent: Wednesday, November 06, 2002 7:15 AM To: [EMAIL PROTECTED] Subject: OSA express gb adapter I have an LPAR that shares a gb ethernet osa express adapter with OS/390 LPAR's. I am using SUSE distribution as it is the only one that I found that includes the OCO modules. I get the error that follows when setting up my network definition. I have on ocasion be able to get this to work, but 99% of the time it fails. Anybody have any ideas that might help me. Enter the device addresses for the qeth module, e.g. '0xf800,0xf801,0xf802' or auto for autoprobing (auto): Starting with microcode level 0146, OSA-Express QDIO require a portname to be set in the device driver. It identifies the port for sharing with other. OS images, for example the PORTNAME dataset used by OS/390. Do you have OSA Express microcode level 0146 or higher? y Note: If you share the card, you must use same portname on all guest/lpars using the card. Please enter the portname (must be 1 to 8 characters) to use: osa1 Using /lib/modules/2.4.7-SuSE-SMP/net/qeth.o qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.136.2.3 $/$Revision: 1 .53.2.2 $/$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 0xC40/0xC41/0xC42 qeth: received an IDX TERMINATE on irq 0xAF4/0xAF5 with cause code 0x22 -- try another 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-SuSE-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 qeth module not loaded, module problem. Do you want to retry the qeth-setup (Yes/No) ? Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield [EMAIL PROTECTED]
