I'm having a problem with Suse Linux 2.4.7 (sles7) and the OSA Gigabit
card. I have read the Linux (and MVS) chapters in the IBM z800
Technical Introduction redbook and several chapters along with the one
on OSA in the Linux Device Drivers manual. I'm installing the Suse
installation system from cdrom into an lpar on a z800, and I selected
option 0 (no network) from the network install menu. The error message
I'm getting seems to be a little different than the one I've seen in
most of the messages on the list. I'm getting an IDX ACTIVATE timeout,
instead of an IDX TERMINATE error code 22. I've double checked the
portname parameter,and it matches.
Can anyone help me get this up and running?
I issued the following commands and the system displayed these
messages:
echo 'noauto' >/proc/chandev
echo 'qeth0,0x0e50,0x0e51,0x0e52,0,0' >/proc/chandev
echo 'add_parms,0x10,0x0e50,0x0e52,portname:OSAGD00' >/proc/chandev
insmod qdio
Using /lib/modules/2.4.7 - Suse - SMP/misc/qdio.o
qdio: Loading QDIO base support version 2 ($revision:1.79
$/$revision: 1.44 $)
debug: qdio-setup: new level 2
debug: qdio-labs: new level 2
debug: qdio-sense: new level 2
debug: qdio-trace: new level 2
insmod qeth
Using /lib/modules/2.4.7 - Suse - SMP/net/qeth.o
qeth: Loading qeth s/390 OSA-Express driver ($revision: 1.135
$/$revision: 1.53 $/$revision: 1.18 $)
qeth: allocaated 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 tu sue card with devnos 0xE%0/0xE51/0xE52
qeth: IDX_ACTIVATE (rd) on read channel irq 0x5bd: timeout
qeth: there were problems in hard setting up the card
debug unregistering qeth_setup
debug unregistering qeth_misc
debug unregistering qeth_data
debug unregistering qeth_control
debug unregistering qeth_sense
debug unregistering qeth_qerr
debug unregistering qeth_trace
/lib/modules/2.4.7-Suse_SMP/net/qeth.o: init module: no such
device
Hint insmod errors can be caused by incorrect parameters
including invalid io or irq parameters
Sue Sivets
--
Suzanne Sivets
Systems Programmer
Innovation Data Processing
973-890-7300
Fax 973-890-7147
[EMAIL PROTECTED]
