Try the portname in caps... Carlos :-)
Carlos A. Ordonez
IBM Corporation
Server Consolidation
|---------+--------------------------->
| | "Liang, |
| | Ih-Cheng" |
| | <[EMAIL PROTECTED]|
| | > |
| | Sent by: Linux |
| | on 390 Port |
| | <[EMAIL PROTECTED]|
| | RIST.EDU> |
| | |
| | |
| | 04/24/2002 03:13|
| | PM |
| | Please respond |
| | to Linux on 390 |
| | Port |
| | |
|---------+--------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| From:
|
| Subject: Re: try to load Gigabit OSA Ethernet driver qeth
|
|
|
>-------------------------------------------------------------------------------------------------------------------------------|
Hi,
Here are the messages during the boot process:
Mar 28 10:48:30 mmsalnxt kernel: SenseID : device 0F08 reports: CU
Type/Mod
= 1731/01, Dev Type/Mod = 1732/01
Mar 28 10:48:30 mmsalnxt kernel: SenseID : device 0F09 reports: CU
Type/Mod
= 1731/01, Dev Type/Mod = 1732/01
Mar 28 10:48:30 mmsalnxt kernel: SenseID : device 0F0A reports: CU
Type/Mod
= 1731/01, Dev Type/Mod = 1732/01
Mar 28 10:48:30 mmsalnxt kernel: SenseID : device 0F0B reports: CU
Type/Mod
= 1731/01, Dev Type/Mod = 1732/01
I added portname:osagbfda to
insmod qeth
qeth_options=noauto,0x0f08,0x0f09,0x0f0a,portname:osagbfd8
But still getting the same error.
Additional messages in the system's log:
Apr 24 12:08:27 mmsalnxt kernel: loading qeth S/390 Gigabit Ethernet driver
Apr 24 12:08:27 mmsalnxt kernel: Trying to use card with devnos
0xF08/0xF09/0xF0A
Apr 24 12:08:27 mmsalnxt kernel: qeth: received an IDX TERMINATE on irq
0x5AD with cause code 0x22 -- use another portname
Apr 24 12:08:28 mmsalnxt kernel: qeth: There were problems in hard-setting
up the card.
IC Liang.
-----Original Message-----
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 9:45 AM
To: [EMAIL PROTECTED]
Subject: Re: try to load Gigabit OSA Ethernet driver qeth
Was the device reported as being detected during the boot process? E.g.,
Detected device 010F on subchannel 0016 - PIM = F0, PAM = F0, POM = FF
Detected device 0D0C on subchannel 0017 - PIM = F0, PAM = F0, POM = FF
Mark Post
-----Original Message-----
From: Liang, Ih-Cheng [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 11:57 AM
To: [EMAIL PROTECTED]
Subject: Re: try to load Gigabit OSA Ethernet driver qeth
Yes, I loaded qdio first with insmod qdio.
IC Liang.
-----Original Message-----
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 23, 2002 8:49 PM
To: [EMAIL PROTECTED]
Subject: Re: try to load Gigabit OSA Ethernet driver qeth
Did you load the qdio module first?
Mark Post
-----Original Message-----
From: Liang, Ih-Cheng [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 23, 2002 6:12 PM
To: [EMAIL PROTECTED]
Subject: try to load Gigabit OSA Ethernet driver qeth
I have SuSE v7 running on an S390 LPAR.
I tried to load Gigabit OSA Ethernet driver with the following command:
insmod qeth qeth_options=noauto,0x0f0a,0x0f0b,0x0f0c
This command failed with the following messages:
Using /lib/modules/2.2.16/net/qeth.o
/lib/modules/2.2.16/net/qeth.o: init_module: Device or resource
busy
Hint: this error can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
Any suggestions what I did wrong? Thanks.
IC Liang.
