Hipersockets requires Linux kernel 2.4
http://www10.software.ibm.com/developerworks/opensource/linux390/restrictions2_2_16.shtml
Gigabit Ethernet driver and QDIO base support
Multicasting has to be switched on in the kernel.
The Gigabit Ethernet Driver needs QDIO base
support.
Starting with microcode level 0146, OSA-Express
QDIO require a portname to be set in the device driver. This portname is
specified using "portname:FOOBAR" in the qeth_options module parameter (see
Device
Drivers and Installation Commands).
HiperSockets support is not available for kernel
2.2, but for kernel 2.4 only.
Broadcast functionality is only available on
OSA-2 hardware, not on OSA-Express QDIO.
Carlos A. Ordonez
IBM Corporation
Linux for S/390 Competency Center
|---------+--------------------------->
| | Jeremy Warren |
| | <jwarren@kbtoys.|
| | com> |
| | Sent by: Linux |
| | on 390 Port |
| | <[EMAIL PROTECTED]|
| | RIST.EDU> |
| | |
| | |
| | 01/17/2002 04:45|
| | PM |
| | Please respond |
| | to Linux on 390 |
| | Port |
| | |
|---------+--------------------------->
>----------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| From:
|
| Subject: Guest-Lan QDIO/QETH on 2.2.16 kernel
|
|
|
>----------------------------------------------------------------------------------------------------------------------------------------------|
We are attempting to setup guest-lan for our linux box running 2.2.16
kernel. under zvm 4.2
We have applied ptf's : UM30225 / UQ61461 / UM30140 to CP and IP on vm and
it "appears" that the VM IP stack is inserting into our guest lan. We can
ping the address etc.
Linux on the other hand is being stubborn...
We have DL'd the latest qdio.o and qeth.o from developerworks.
We have also applied all recommended maintenance to the kernel from this
site:
http://www10.software.ibm.com/developerworks/opensource/linux390/current2_2.shtml
When we do insmods for qdio and qeth this is what we get....
linux1:~ # insmod qdio
Using /lib/modules/2.2.16/net/qdio.o
linux1:~ #
linux1:~ # insmod qeth noauto,0x0500,0x0501,0x0502,portname:VLAN1,eth0
Using /lib/modules/2.2.16/net/qeth.o
linux1:~ #
On the console we see:
Jan 17 16:40:32 linux1 kernel: qdio: loading QDIO base support
Jan 17 16:40:32 linux1 kernel: debug: reserved 1 areas of 4 pages for
debugging
qdio_setup
Jan 17 16:40:32 linux1 kernel: debug: reserved 2 areas of 4 pages for
debugging
qdio_labs
Jan 17 16:40:32 linux1 kernel: debug: reserved 1 areas of 2 pages for
debugging
qdio_sense
Jan 17 16:40:32 linux1 kernel: debug: reserved 2 areas of 4 pages for
debugging
qdio_trace
,
Jan 17 16:41:07 linux1 kernel: qdio: loading QDIO base support
Jan 17 16:41:07 linux1 kernel: debug: reserved 1 areas of 4 pages for
debugging
qdio_setup
Jan 17 16:41:07 linux1 kernel: debug: reserved 2 areas of 4 pages for
debugging
qdio_labs
Jan 17 16:41:07 linux1 kernel: debug: reserved 1 areas of 2 pages for
debugging
qdio_sense
Jan 17 16:41:07 linux1 kernel: debug: reserved 2 areas of 4 pages for
debugging
qdio_trace
That's it. An ifconfig fails for either name eth0 or hsi0 any help would
be greatly appreciated.
ifconfig eth0 up
eth0: unknown interface: No such device
ifconfig hsi0 up
hsi0: unknown interface: No such device
Here are some of the key config files....
System config:
define lan vlan1 maxconn 100 ownerid system
User Directory:
PROFILE LINDFLT
SPECIAL C000 CTCA
SPECIAL C001 CTCA
SPECIAL 500 HIPER 3 SYSTEM VLAN1
SPOOL 000C 2540 READER
SPOOL 000D 2540 PUNCH A
SPOOL 000E 1403 A
CONSOLE 009 3215 T TSTTWS
LINK MAINT 0190 0190 RR
LINK MAINT 019D 019D RR
LINK TCPIP 0592 0592 RR * tcpip client code
LINK MAINT 019E 019E RR
*
USER LINUX1 ****** 128M 2046M G
INCLUDE LINDFLT
IPL CMS PARM AUTOCR
MACHINE ESA
MDISK 0191 3390 0460 0010 LNS001 MR ALL SOME FEW * LINUX1'S A DISK
MDISK 1000 3390 0470 0200 LNS001 MR ALL SOME FEW * LINUX1'S ROOT
MDISK 1010 3390 0670 0200 LNS001 MR ALL SOME FEW * LINUX1'S TMP
MDISK 1020 3390 0870 0050 LNS001 MR ALL SOME FEW * LINUX1'S VAR
MDISK 1030 3390 0001 3337 LNS006 MR ALL SOME FEW * USR
MDISK 9000 3390 0200 0199 LNS004 MR ALL SOME FEW * LINUX1'S SWAP FILE
*LINK LINUX0 1030 1030 RR * LINUX0'S USR - READ
LINK LINUX0 1040 1040 RR * LINUX0'S KBCOMMON -
modules.conf
(Only what we added/modified)
alias hsi0 qeth
alias eth0 qdio
#cp q v osa
linux1:~ #
CP Q V OSA
OSA 0500 ON NIC 0500 UNIT 000 SUBCHANNEL = 0009
0500 QDIO-ELIGIBLE
OSA 0501 ON NIC 0500 UNIT 001 SUBCHANNEL = 000A
0501 QDIO-ELIGIBLE
OSA 0502 ON NIC 0500 UNIT 002 SUBCHANNEL = 000B
0502 QDIO-ELIGIBLE
'just making sure we are coupled.....
#CP COUPLE 0500 TO SYSTEM VLAN1
CP COUPLE 0500 TO SYSTEM VLAN1
HCPCPL2788E NIC 0500 not connected; already connected to LAN SYSTEM VLAN1
