>From Jeremy Warren: >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:~ #
I think the qeth module will insist on using "hsi" as the prefix, but the "eth0" on the insmod may be confusing things. The rest of the setup looks good to me (but if you move to a 2.4.* kernel, I think you will need to move these parameters to chandev.conf). (snipped) >#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 You might find additional information using: #cp q nic (it should tell you whether the READ/WRITE/DATA roles have been assigned yet by the interface... and which IP Addresses have been set by this interface). In this case, since qeth.o did not find the device it will probably just show you the initial state (all three devices unassigned). Best Regards, Dennis Musselwhite ([EMAIL PROTECTED]) z/VM CP Development
