On 12.06.2002 at 07:19:52, Rob van der Heij <[EMAIL PROTECTED]> wrote:
> On real OSA devices the number is ignored afaik.
Yep. This is because on OSA, each port is its own LCS device which only has
port '0'. So the default (0) is fine.
When using 'real' LCS (3172, AWS3172, 2216 AFAIK), as Rob
PROTECTED]
Subject: Linux LPAR install on MP3000 - LCS definition
I am currently trying to install the latest version of Suse Linux (2.4
kernel) in an LPAR and having trouble defining the ethernet card. The
machine is a MP3000 H30 with 3 LPARs with 3 ethernet cards and 1 token ring
card.
LPAR
On 13.06.2002 at 00:45:18, Alan Altmark <[EMAIL PROTECTED]> wrote:
> On Wednesday, 06/12/2002 at 10:58ZE10, Vic Cross <[EMAIL PROTECTED]>
> wrote:
> > Yep. This is because on OSA, each port is its own LCS device which only
has
> > port '0'. So the default (0) is fine.
>
> Unless it is a dual-por
On Wednesday, 06/12/2002 at 10:58ZE10, Vic Cross <[EMAIL PROTECTED]>
wrote:
> On 12.06.2002 at 07:19:52, Rob van der Heij <[EMAIL PROTECTED]> wrote:
>
> > On real OSA devices the number is ignored afaik.
>
> Yep. This is because on OSA, each port is its own LCS device which only
has
> port '0'.
I found the MP3000 (and P/390 too) very sensitive
to proper 'relative adapter number' for the adapter.
You need the number as defined in MPTS or LAPS (?)
and letting the lcs.o driver sense them crashed my
AWS3172 device driver.
On real OSA devices the number is ignored afaik.
Rob
I am currently trying to install the latest version of Suse Linux (2.4
kernel) in an LPAR and having trouble defining the ethernet card. The
machine is a MP3000 H30 with 3 LPARs with 3 ethernet cards and 1 token ring
card.
LPAR 1: VSE had TR card dedicated to it.
LPAR 2: not in use
