Jxrgen Birkhaug writes: > Ok - I've ditched the uneven device and reverted back to an even boundary. > > z/VM now sees the following *after* trying to initialize the qeth module: > > ------------ > Q NIC DETAILS > Adapter 0960 Type: HIPER Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-0E LAN: SYSTEM LNXLAN02 MFS: 16384 > Connection Name: HALLOLE State: Startup > Device: 0960 Unit: 000 Role: CTL-READ > Unassigned Devices: > Device: 0961 Unit: 001 Role: Unassigned > Device: 0962 Unit: 002 Role: Unassigned > ------------ > > The dev numbers do match with the contents of /proc/subchannels. I'm > slightly perplexed as to why the nic is in "State: Startup" and why 0961 > and 0962 are "Unassigned". > > Linux, on the other hand, reports: > > ------------ > qeth: Trying to use card with devnos 0x960/0x961/0x962 > qeth: received an IDX TERMINATE on irq 0x11/0x12 with cause code 0x17 > qeth: IDX_ACTIVATE on read channel irq 0x11: negative reply > qeth: There were problems in hard-setting up the card. > ------------ > > Back to scratch.
OK, let's keep going at it. What's the output of # cat /proc/chandev on the Linux side (1) when you've freshly rebooted it, (2) after you've caused the chandev settings to take effect (whether you use SuSE's rcchandev, echo a read_conf to /proc/chandev or whatever) and also (3) after you do the "modprobe qeth"? --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself