For reasons unknown we're suddenly having trouble using our OSA adapters. The problem first surfaced after VM was recently restarted after the upgrade of the processor microcode. Here's a snip from the console log:
Setting up network device eth0 loading QDIO base support loading qeth S/390 Gigabit Ethernet driver Trying to use card with devnos 0xB00/0xB01/0xB02 qeth: received an IDX TERMINATE on irq 0x1 with cause code 0x22 -- use another portname qeth: There were problems in hard-setting up the card. QDIO base support: module removed insmod: /lib/modules/2.2.16/net/qeth.o: init_module: Device or resource busy insmod: Hint: this error can be caused by incorrect module parameters, includinding invalid IO or IRQ parameters insmod: /lib/modules/2.2.16/net/qeth.o: insmod eth0 failed SIOCSIFADDR: No such device In previous weeks we've successfully used the OSA adapters. At that time /etc/modules.conf contained only: alias eth0 qeth options qeth qeth_options="auto" Because the message makes it sound like an explicit portname is required, I changed modules.conf to: alias eth0 qeth options qeth qeth_options="auto,portname:bigguy" The change did not help. I'm told that no changes were made to the OSA adapter definitions and that no other nodes are specifying a portname on their TCP/IP definitions. (There are other systems, including Linux systems, using the same OSA adapter.) The IBM 2064 processor (Freeway) was recently upgraded to support Hypersockets. We're running SuSE 7.0, kernel 2.2.16. Any ideas here? William P. Scully Systems Programmer Computer Associates International, Inc [EMAIL PROTECTED]
