>I also tried an insmod -f qdio and insmod -f qeth and it
>still gave the version mismatch message but it appeared to be more a
warning
>message, but then I also received an unresolved reference message from the
>insmod -f qeth.

Can you cut and paste the error message for the unresolved reference or
copy it exactly?

You may just have to load the ipv6 module also in addition to qdio and
qeth.

Jay Brenneman





                      Alan Schilla
                      <[EMAIL PROTECTED]        To:       [EMAIL PROTECTED]
                      te.mn.us>                cc:
                      Sent by: Linux on        Subject:  Re: Upgrading QDIO, QETH on 
SuSE Linux 2.4.7 SMP
                      390 Port
                      <[EMAIL PROTECTED]
                      IST.EDU>


                      03/05/2003 01:41
                      PM
                      Please respond to
                      Linux on 390 Port






Thanks Sergey. I am not sure where the parm below would be added to
modules.conf andI tried a couple of different things but I still do not get
the QETH interface. I also tried an insmod -f qdio and insmod -f qeth and
it
still gave the version mismatch message but it appeared to be more a
warning
message, but then I also received an unresolved reference message from the
insmod -f qeth. Anyway it still did not work. Below is my /etc/chandev.conf
used to try creating this interface. I have removed comments to shorten the
mailing. Can I provide any other information that would be helpful?
cat /etc/chandev.conf
---------------------------------------------------------------------------

# The installation of SuSE Linux adds the network device that was

# used for installation here:

add_parms,0x10,0x0700,0x0702,portname:LNXDQ

qeth0,0x0700,0x0701,0x0702

ctc0,0x0d00,0x0d01,0,0

lxisdn01:~ #


Thanks For YOur Help,
Al Schilla
State of Minnesota

-----Original Message-----
From: Sergey Korzhevsky [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 8:22 AM
To: [EMAIL PROTECTED]
Subject: Re: Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP


Add to /etc/modules.conf line

insmod_opt=-f

Then try new drivers. If it won't help, get to us your /etc/chandev.conf



        WBR, Sergey




Alan Schilla <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
04.03.2003 22:53
Please respond to Linux on 390 Port


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        Upgrading QDIO, QETH on SuSE Linux 2.4.7 SMP


I am trying to activate a virtual QDIO, QETH link between zVM 4.3 TCPIP
guest and a SuSE guest version:
Linux Version 2.4.7-timer-SMP, Compiled #1 SMP Tue Nov 26 23:25:11 GMT
2002
When I try activating the QDIO, QETH modules that were on the system with
this version I received:
insmod qdio

Using /lib/modules/2.4.7-timer-SMP/misc/qdio.o

qdio: loading QDIO base support version 2 ($Revision: 1.78.2.9
$/$Revision:
1.44
.2.3 $)

debug: qdio_setup: new level 2

debug: qdio_labs: new level 2

debug: qdio_sense: new level 2
debug: qdio_trace: new level 2
lxisdn01:~ #
insmod qeth

Using /lib/modules/2.4.7-timer-SMP/net/qeth.o

qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.136.2.7
$/$Revision: 1
.53.2.3 $/$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 0x700/0x701/0x702

qeth: received an IDX TERMINATE on irq 0x8/0x9 with cause code 0x22 -- try
anot
her portname

qeth: received an IDX TERMINATE on irq 0x8/0x9 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-timer-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

I get this TRY ANOTHER PORT NAME no matter what I use for portname even
though a Q NIC DETAILS and Q V for the QDIO device numbers 700-702 show:
CP Q NIC DETAILS

Adapter 0700  Type: QDIO      Name: UNASSIGNED  Devices: 3

Port 0 MAC: 00-04-AC-00-00-02  LAN: SYSTEM LNXLAN      MFS: 8192

RX Packets: 0          Discarded: 0          Errors: 0

TX Packets: 0          Discarded: 0          Errors: 0

RX Bytes: 0                    TX Bytes: 0

Connection Name: HALLOLE   State: CM_CONNECT

Device: 0700  Unit: 000   Role: CTL-READ

Device: 0701  Unit: 001   Role: CTL-WRITE

Device: 0702  Unit: 002   Role: DATA

Q V 700-702

OSA  0700 ON NIC  0700  UNIT 000 SUBCHANNEL = 0008

0700 QDIO-ELIGIBLE
OSA  0701 ON NIC  0700  UNIT 001 SUBCHANNEL = 0009
0701 QDIO-ELIGIBLE
OSA  0702 ON NIC  0700  UNIT 002 SUBCHANNEL = 000A
0702 QDIO-ELIGIBLE

I have also tried downloading the latest 2.4.7 qdio, qeth drivers and
activating these and recieve:
lxisdn01:~ # modprobe qeth

modprobe qeth

/lib/modules/2.4.7-timer-SMP/misc/qdio.o: kernel-module version mismatch

/lib/modules/2.4.7-timer-SMP/misc/qdio.o was compiled for kernel
version
2.4.7-timer

while this kernel is version 2.4.7-timer-SMP.

/lib/modules/2.4.7-timer-SMP/misc/qdio.o: insmod
/lib/modules/2.4.7-timer-SMP/mi
sc/qdio.o failed

/lib/modules/2.4.7-timer-SMP/misc/qdio.o: insmod qeth failed

lxisdn01:~ #


Does anyone know how I can get this to work or where I may find the latest
QDIO, QETH drivers for SuSE-2.4.7-SMP kernel?
Thanks,
Al Schilla
State of Minnesota

Reply via email to