Hello Chris, The parameter string is being built with a slight error (a comma where it really needs a semicolon). I learned from Bernhard Kaindl that there is a simple work-around for this. You can enter the add_parms information when you are prompted for the list of device addresses:
Enter the device addresses for the qeth module, e.g. '0xf800,0xf801,0xf802' or auto for autoprobing (auto): 0xff00,0xff01,0xff02;add_parms,0x10,portname:TESTVLAN You should not be asked for portname. If you are... just press enter I guess. The add_parms was being taken as an extraneous parameter, so your portname was being ignored. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM z/VM Development -- CP Network Simulation Chris Little <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/27/2003 11:27:48 AM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: [LINUX-390] sles7 install issue with qdio Hello, list, when installing sles7 31-bit, i get the following error qeth: received an IDX TERMINATE on irq 0x0/0x1 with cause code 0x22 -- try another portname here is some various things that i have gone through. i have successfully installed this before, so i'm not quite sure what the issue is. i've included a lot of configuration/log files that i've gone through and can seem to find any problems. is there something that i'm missing? it's been awhile since i've done an install. --profile tcpip: 00134 DEVICE VLAN2 OSD FF00 PORTNAME TESTVLAN PRIROUTER 00135 LINK VLAN2 QDIOETHERNET VLAN2 --query virtual osa's on the guest: q v osa Ready; T=0.01/0.01 10:06:52 01: OSA FE00 ON NIC FE00 UNIT 000 SUBCHANNEL = 0009 01: FE00 QDIO-ELIGIBLE 01: OSA FE01 ON NIC FE00 UNIT 001 SUBCHANNEL = 000A 01: FE01 QDIO-ELIGIBLE 01: OSA FE02 ON NIC FE00 UNIT 002 SUBCHANNEL = 000B 01: FE02 QDIO-ELIGIBLE 01: OSA FF00 ON NIC FF00 UNIT 000 SUBCHANNEL = 0000 01: FF00 QDIO-ELIGIBLE 01: OSA FF01 ON NIC FF00 UNIT 001 SUBCHANNEL = 0001 01: FF01 QDIO-ELIGIBLE 01: OSA FF02 ON NIC FF00 UNIT 002 SUBCHANNEL = 0002 01: FF02 QDIO-ELIGIBLE Ready; T=0.01/0.01 10:06:52 --install log Do you want to retry the qeth-setup (Yes/No) ? yes Enter the device addresses for the qeth module, e.g. '0xf800,0xf801,0xf802' or auto for autoprobing (auto): 0xff00,0xff01,0xff02 Do you have OSA Express microcode level 0146 or higher? yes 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: TESTVLAN Writing 'noauto;qeth0,0xff00,0xff01,0xff02,add_parms,0x10,portname:TESTVLAN' to /proc/chandev Using /lib/modules/2.4.7-SuSE-SMP/net/qeth.o qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.135 $/$Revision: 1.53 $/$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 0xFF00/0xFF01/0xFF02 qeth: received an IDX TERMINATE on irq 0x0/0x1 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-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.
