I noticed that, if the OSA card is OSA Gigabit Express (OSA-GBX), the last
row of the following table. Does that mean, the linux module to be used
should be QETH, not LCS. Our card is (Hardware model -> OSA-Direct
Express,subtype -- Gigabit Ethernet)
But Marist uses LCS. If I try INSMOD QETH ... command, it says module not
found. Is this the right way to initiate Qeth module?
Or does that mean, Marist does not have the driver (qeth) for our osa
card. ( Mark Post had in the first place advised me to leave Marist).
Thanks.
inci
S/390 Open Systems Adapters (OSA) cards
for Linux Card Mbps Connection CPU Cable HCD
CHP #
CHP Ports
/CHP Multiple
IP
MAX
Addresses
Entries
/Card Access IP's
other LPARS Linux
Module
OSA2-ENTR 10 T/R or
ETH copper OSA 1 2 OSA/SF 32 yes LCS
OSA2-FE 100 ETH copper OSA 1 1 OSA/SF 16 no LCS
OSA-FEX 100 ETH G5+ copper OSE 1 1 auto 240 yes LCS
" 100 ETH G5+ copper OSD 1 1 auto 240 yes QETH
OSA-GBX 1000 ETH G5+ fiber OSD 1 1 auto 240 yes QETH
OSA-FEX 100 ETH Z copper OSE 2 1 auto 480 yes LCS
" 100 ETH Z copper OSD 2 1 auto 480 yes QETH
OSA-GBX 1000 ETH Z fiber OSD 2 1 auto 480 yes QETH
----- Original Message -----
From: "Rob van der Heij" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, September 06, 2006 12:41 PM
Subject: Re: can LINUX/390 and z/OS LPARS share devices?
> On 9/6/06, inci yeker selkan <[EMAIL PROTECTED]> wrote:
>
> > What I suspect is, linux/390 does not like to have the same device
number
> > with others. Am I right in this??? (question 1)
>
> If you talk about Linux in LPAR, I am not aware of any difference in
> this. I think later drivers even nicely work around the even/odd
> restrictions when you specify the wrong devices.
>
> > By the way, is there an equivalent of mvscp OS config ,/EDT(eligible
device
> > numbers) for linux/390???? (question 2)
>
> Linux in LPAR will "see" all the OSA devices that are in the IOCDS for
> the LPAR. You select the tripod you need by having hwconfig scripts
> that activate the right set and map it onto a qeth* number. There's
> entries in the /sys file system that represent the real devices of the
> LPAR, and by writing into these entries you communicate with the
> device drivers. For disks you can tell the driver only to use a set of
> addresses, but with root access you can get to the others as well if
> you want (or make a mistake).
>
> > Where do I define them? I mean, where do I say the Osa device number ?
I
> > say it in answering the network related questions during ipl, is it
enough?
> > Should I mention it in the parmline file. (question 3)
>
> Previously this was through parameters in the /etc/chandev.conf and
> way before then it was with kernel parameters in the parmfile.
>
> Rob
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
