Moloko, I could be wrong, but try using a different logical adapter number. IIRC, you will use the same device numbers for all adapters but the logical adapter number will change. OSAs always use adapter number 0, so this value is not used, but I'm guessing you'll need to use it for your setup.
>From your earlier example: > echo lcs0,0x510,0x511,0,9 >> /proc/chandev (first tr0) > echo lcs1,0x510,0x511,0,9 >> /proc/chandev (second tr1) either the 0 or the 9 will change in the second echo (I don't have to doco nearby, sorry). As Alan said, EMIF is transparent to Linux and would not be a factor in this configuration anyway. Cheers, Vic Cross ----- Original Message ----- From: "Moloko Monyepao" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 18, 2002 11:32 PM Subject: Insmod command RH7.2 > It is working. If I may ask, does linux390 understand EMIF, reason being > I have only one escon channel from my S390 box to the 2216 which is > shared by about 6 lpars including my linux lpar. I can get my TR0 , TR1 > up using ifconfig but as soon as I try to ping my 2216 (gw > 172.20.15.85), my linux system doesn't see it. Our network guys thinks > maybe is because linux doesn't understand EMIF. When I do ifconfig it > shows both TR0,TR1 and even on the 2216 site it shows that the devices > are up > > Thanx a lot for the last reply > > moloko > > > -----Original Message----- > > From: Rob van der Heij [SMTP:[EMAIL PROTECTED]] > > Sent: 18 February 2002 14:19 > > To: [EMAIL PROTECTED] > > Subject: Re: Insmod command (RH7.2) > > > > At 10:43 18-02-02 +0200, you wrote: > > >I've been there, done that. how do I add the second lcs , do I call > > it > > >lcs1 or lcs0 for instance: > > > echo lcs0,0x510,0x511,0,9 >> /proc/chandev (first tr0) > > > echo lcs1,0x510,0x511,0,9 >> /proc/chandev (second tr1) > > > > Yes, lcs1 will produce your eth1 network device. You'd > > need other address than 510-511 ofcourse... >
