I've downloaded qeth-2.4.19-s390-1-may2002.tar.gz, then:
# tar xvfz qeth-2.4.19-s390-1-may2002.tar.gz
qeth-2.4.19-s390-1-may2002.o
LICENSE
README
and finally:
# insmod qeth-2.4.19-s390-1-may2002.o
qeth-2.4.19-s390-1-may2002.o: unresolved symbol qdio_activate
qeth-2.4.19-s390-1-may2002.o: unresolved symbol qdio_synchronize
qeth-2.4.19-s390-1-may2002.o: unresolved symbol addrconf_lock
qeth-2.4.19-s390-1-may2002.o: unresolved symbol qdio_initialize
qeth-2.4.19-s390-1-may2002.o: unresolved symbol in6_dev_finish_destroy
qeth-2.4.19-s390-1-may2002.o: unresolved symbol do_QDIO
qeth-2.4.19-s390-1-may2002.o: unresolved symbol tr_type_trans
qeth-2.4.19-s390-1-may2002.o: unresolved symbol ndisc_mc_map
qeth-2.4.19-s390-1-may2002.o: unresolved symbol qdio_cleanup
qeth-2.4.19-s390-1-may2002.o: unresolved symbol
unregister_inet6addr_notifier
qeth-2.4.19-s390-1-may2002.o: unresolved symbol tr_setup
qeth-2.4.19-s390-1-may2002.o: unresolved symbol
register_inet6addr_notifier
qeth-2.4.19-s390-1-may2002.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. Contact the module supplier for
assistance, only they can help you.
i have this config:
# cat /etc/chandev.conf
noauto;qeth0,0x500,0x501,0x502;add_parms,0x10,0x500,0x502,portname:NIC500
the virtual nic exists:
# cat /proc/subchannels
Device sch. Dev Type/Model CU in use PIM PAM POM CHPIDs
---------------------------------------------------------------------
0009 0000 3215/00 yes 80 80 FF 01000000 00000000
0191 0001 3390/0A 3990/E9 C0 C0 FF 24260000 00000000
0200 0002 3390/0A 3990/E9 yes C0 C0 FF 24260000 00000000
0201 0003 3390/0A 3990/E9 yes C0 C0 FF 24260000 00000000
0202 0004 3390/0A 3990/E9 yes C0 C0 FF 24260000 00000000
0203 0005 3390/0A 3990/E9 yes C0 C0 FF 24260000 00000000
0204 0006 3390/0A 3990/E9 yes C0 C0 FF 24260000 00000000
0205 0007 3390/0A 3990/E9 yes C0 C0 FF 24260000 00000000
0500 0008 1732/01 1731/01 80 80 80 08000000 00000000
0501 0009 1732/01 1731/01 80 80 80 08000000 00000000
0502 000A 1732/01 1731/01 80 80 80 08000000 00000000
# cat /proc/chandev
chan_type key bitfield
ctc=0x1,escon=0x2,lcs=0x4,osad=0x8,qeth=0x10,claw=0x20
*'s for cu/dev type/models indicate don't cares
cautious_auto_detect: on
persist = 0x00
use_devno_names: off
Channels enabled for detection
chan cu cu dev dev max checksum use hw auto
recovery
type type model type model port_no. received stats type
==============================================================================
0x02 0x3088 0x1e * * 0 no no
not_operational,no_path,revalidate,device_gone
0x20 0x3088 0x61 * * 0 no no
not_operational,no_path,revalidate,device_gone
0x08 0x3088 0x62 * * 0 no no
not_operational,no_path,revalidate,device_gone
0x10 0x1731 0x05 0x1732 0x05 0 no no
not_operational,no_path,revalidate,device_gone
0x10 0x1731 0x01 0x1732 0x01 0 no no
not_operational,no_path,revalidate,device_gone
0x04 0x3088 0x60 * * 1 no no
not_operational,no_path,revalidate,device_gone
0x06 0x3088 0x1f * * 15 no no
not_operational,no_path,revalidate,device_gone
0x05 0x3088 0x08 * * 15 no no
not_operational,no_path,revalidate,device_gone
0x04 0x3088 0x01 * * 15 no no
not_operational,no_path,revalidate,device_gone
No auto devno ranges
From To
====================
0x0000 0xffff
Forced devices
chan defif read write data memory port ip hw host
adapter api
type num devno devno devno usage(k) protocol no. chksum stats name
name name
===============================================================================================
0x10 0 0x0500 0x0501 0x0502 default 0 0 0
channels detected
chan cu cu dev dev in
chandev
irq devno type type model type model pim chpids use
reg.
===============================================================================
0x0008 0x0500 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0800000000000000 no
no
0x0009 0x0501 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0800000000000000 no
no
0x000a 0x0502 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0800000000000000 no
no
driver specific parameters
chan lo hi driver
type devno devno parameters
=============================================================================
0x10 0x0500 0x0502 portname:NIC500
any idea?
On Tue, 11 Mar 2003, Post, Mark K wrote:
> As Adam pointed out, you can try the "vanilla" OCO module at
> http://www10.software.ibm.com/developerworks/opensource/linux390/current2_4_
> 19-may2002.shtml#qeth20021219
>
> You may need to turn on some other options in your kernel if you still get
> unresolved reference errors. Post those errors, and someone should be able
> to help you figure out what to turn on or off in your kernel config.
>
> Mark Post
>
> -----Original Message-----
> From: Alex Leyva [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 11, 2003 6:00 PM
> To: [EMAIL PROTECTED]
> Subject: Re: QDIO for virtual NIC
>
>
> i've tried with almost all the differents oco modules, but i only get
> "unresolved symbols", its because i have a redhat installed, but with
> another kernel, so my system doesnt get into any category:
>
> Red Hat Linux 7.2 kernel version (31-bit):
> kernel version 2.4.9-38 (OCOs dated 2002-12-19)
> kernel version 2.4.9-37 (OCOs dated 2002-08-16)
> kernel version 2.4.9-17 (OCOs dated 2002-01-15)
>
> so what can i do?
>
> On Tue, 11 Mar 2003, Adam Thornton wrote:
>
> > On Tue, Mar 11, 2003 at 04:32:02PM -0600, Alex Leyva wrote:
> > > Hi all, im configuring some guest lans, but im having problems with the
> > > linux side, im using RedHat 7.2, with kernel 2.4.19, i've compiled the
> > > kernel to have QDIO as a module, but i have only the qdio.o module, i
> dont
> > > have qeth.o, i have the definitions in modules.conf and chandev.conf
> > > correct, but i just cant locate the qeth.o module, its strange to me
> > > because the kernel config includes the QDIO support as a module, so i
> dont
> > > understand why it dosnt have it.
> >
> > The QDIO infrastructure support is Open Source.
> >
> > The qeth OSA/Hipersockets driver, which plugs into the QDIO support, is
> > OCO. Get it from IBM; it's available for free download from their
> > Linux/390 DeveloperWorks site.
> >
> > Adam
> >
>
> --
> Alejandro Leyva Rabinovich.
> Jefe de la Unidad Departamental de Soporte Ticnico
> (Administracisn de Mainframe).
> Direccisn General de Informatica.
> Secretarma de Finanzas.
> Gobierno del Distrito Federal.
>
--
Alejandro Leyva Rabinovich.
Jefe de la Unidad Departamental de Soporte Ticnico
(Administracisn de Mainframe).
Direccisn General de Informatica.
Secretarma de Finanzas.
Gobierno del Distrito Federal.
