On Wed, Jan 16, 2002 at 08:39:01AM -0600, Tyler Koyl wrote:
> We have a test system running SuSE7.0 (2.2.16 kernel), I have gone through
> and compiled a 2.2.19 kernel from the SuSE 2.2.19 source tree, however the
> lcs module is failing to insert properly at boot. Neither the IBM nor the
> provided SuSE lcs module is working. I have the obvious kernel parameters
> set ie. Networking, TR and Ethernet support. The modules are not created
> during the compile, which leads me to believe that I might have missed
> setting a kernel parameter during the make menuconfig that the lcs modules
> require to insert properly, and that the parameter I am missing might not
> be completely obvious.
>
> Any help would be appreciated.

Welcome to the wonderful world of OCO.

The short answer is, you're screwed.

If you use the LCS driver, you're stuck using IBM-blessed kernel
releases; you cannot get source code to the LCS modules, and although I
and other people have been asking for a minimal-functionality (no
accelerated anything, just put bits on the network and take them off)
source-available module for, oh, two years now, no progress has
happened.

Failing this, an architecture that contains the binary object that does
the work and a compilable wrapper that you could build for any kernel
level (like, for instance, NVidia does with its video drivers) would be
nice.  This also has not happened.

Possible workarounds:
a) use some other device.  If you're running under VM, this is easy.
You can give the OSA to VM and use IUCV or vCTC to get to the VM stack
and out from there.  If you're not, well, an actual CTC works, or if you
have a CIP router, you can get CLAW drivers which work fine.
b) If you're running VM, you can run a 2.2.16 router machine and
communicate from it to your test machine via IUCV/VCTC/whatever.

If you're running standalone or in an LPAR, of course, and you do not
have access to an actual CTC or a CIP router, this doesn't help you.  In
which case, you can add your voice to the chorus of protest against
IBM's OCO policy with respect to its LCS drivers, but don't expect it to
do much good.

Adam

Reply via email to