See the information posted on this WSC FLASH:
http://www-1.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/Flash10119
Kurt Acker
[EMAIL PROTECTED]
Ken Vance
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
et> cc:
Sent by: Linux on Subject: OSA connection no longer
connects
390 Port
<[EMAIL PROTECTED]
IST.EDU>
12/10/01 10:11 AM
Please respond to
Linux on 390 Port
Hi,
Several months ago, I configured our Suse 7.0 system to use a OSAD
connection. It all worked fine at that time. The system has been
inactive for awhile, and now when I bring it up it will not connect to the
OSA card. I tried several other addresses, as well as trying it on two
other cards, but I still get the same message. I believe the only change
is that we switched our z/VM system to a different OSA card. I have also
used the card(s) for other z/VM testing. Would this error be related to a
change in the port name? Is there a way of changing the setup via the
console? I have included the error message at the bottom of this note.
Any help would be appreciated.
Thanks,
Ken Vance
Amadeus
------------------------------------------------------------------------------------------
Setting up network device eth0
loading QDIO base support
loading qeth S/390 Gigabit Ethernet driver
Trying to use card with devnos 0xBC14/0xBC15/0xBC16
qeth: received an IDX TERMINATE on irq 0x1 with cause code 0x22 -- use
another p
ortname
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,
including
invalid IO or IRQ parameters
insmod: /lib/modules/2.2.16/net/qeth.o: insmod eth0 failed
SIOCSIFADDR: No such device
