Re: SLES9 installation problem - again
On Saturday, 10/23/2004 at 08:48ZE10, Vic Cross <[EMAIL PROTECTED]> wrote: > Back to the IOCDS then: since we are really trying to work in LCS mode, > is OSE the correct CHPID type? Should it be OSA? >From Gadi's original post: CHPID PATH=(CSS(0),02),SHARED,* PARTITION=((LINTST,PROD,TEST),(=)),TYPE=OSE,* PCHID=141 CNTLUNIT CUNUMBR=1200,PATH=((CSS(0),02)),UNIT=OSA IODEVICE ADDRESS=(1200,253),CUNUMBR=(1200),UNIT=OSA IODEVICE ADDRESS=(12FE,1),CUNUMBR=(1200),UNIT=OSAD CHPID type is correctly set to OSE, indicating non-QDIO mode. TYPE=OSA was used only on the original OSA and OSA-2. The UNIT=OSA and UNIT=OSAD are also correct. From the IOCP book: UNIT=device specifies the device type. You specify a maximum of 8 alphanumeric or special (#, @, or $) characters to define the device type (such as, 3390 or 3590). IOCP only checks the syntax for alphanumeric or special characters. IOCP does not validate the device value except for devices assigned to OSA, OSD, or OSE channel paths. For OSA, OSD, and OSE channel paths, IOCP expects devices with unit addresses in the range 00-FD to have a value of OSA and the device with unit address FE to have a value of OSAD. The non-OSAs, the value of UNIT is meaningless to Linux and VM. After all these years, MVS still uses the field to carry I/O config information. And since IOCP already knows what the correct values are, it could generate them. But, again, it really isn't for IOCP's benefit. To recall Gadi's problem: The LCS driver was hanging during load. Now that all the distractions are past, hopefully someone will have some helpful advice! Alan Altmark -- 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
Re: SLES9 installation problem - again
On 22/10/2004, at 11:48 pm, Alan Altmark wrote: David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The Gigabit Ethernet feature operates only in QDIO mode. Okay then... (we're all learning on this one :) Back to the IOCDS then: since we are really trying to work in LCS mode, is OSE the correct CHPID type? Should it be OSA? Cheers, Vic Cross PS: On Gigabit/1000BaseT -- it's disappointing that the industry chooses to use the generic term "Gigabit Ethernet" to refer to a specific implementation of Ethernet that operates at gigabit speed. Sigh... No wonder everyone believes networking to be so confusing ;) -- 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
Re: SLES9 installation problem - again
On Friday, 10/22/2004 at 10:05 AST, David Boyes <[EMAIL PROTECTED]> wrote: > > David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The > > Gigabit Ethernet feature operates only in QDIO mode. > > OK, you're the boss. Previous messages indicated we were talking about > the old OSA Express cards (which have the above restriction) not a 890/990. IIRC, the OP said "OSA Express 1000Base-T" and the shown IOCP included CSS specifications. That's a z890/z990. Alan Altmark Sr. Software Engineer IBM z/VM Development -- 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
Re: SLES9 installation problem - again
On Fri, Oct 22, 2004 at 09:48:52AM -0400, Alan Altmark wrote: > > David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The > Gigabit Ethernet feature operates only in QDIO mode. OK, you're the boss. Previous messages indicated we were talking about the old OSA Express cards (which have the above restriction) not a 890/990. -- 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
Re: SLES9 installation problem - again
On Friday, 10/22/2004 at 09:42 AST, David Boyes <[EMAIL PROTECTED]> wrote: > 1000baseT *is* gigabit Ethernet -- look it up. If you mean *100*baseT, > then you might be right, but if it can be configured as LCS, then it > is NOT a 1000baseT card. > > Again, if it is a 1000baseT card, then it MUST be QDIO. If you want to > use LCS, then you cannot use that card. David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The Gigabit Ethernet feature operates only in QDIO mode. Alan Altmark Sr. Software Engineer IBM z/VM Development -- 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
Re: SLES9 installation problem - again
On Fri, Oct 22, 2004 at 09:47:25AM +0200, ?? ?? wrote: > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. > Any other thaughts? > Gadi 1000baseT *is* gigabit Ethernet -- look it up. If you mean *100*baseT, then you might be right, but if it can be configured as LCS, then it is NOT a 1000baseT card. Again, if it is a 1000baseT card, then it MUST be QDIO. If you want to use LCS, then you cannot use that card. -- db -- 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
Re: SLES9 installation problem - again
On Friday, 10/22/2004 at 08:17 EST, Don Sievert <[EMAIL PROTECTED]> wrote: > Ethernet is IEEE standard 802.3, regardless of copper or fiber media. Everyone is missing the point: In addition to the fibre Gigabit Ethernet we all know and love, the z890 and z990 have a copper 1000Base-T feature. While "1000Base-T Ethernet" and "Gigabit Ethernet" might appear on the surface to be the same, they are not. This is consistent with the industry terminology. Alan Altmark Sr. Software Engineer IBM z/VM Development -- 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
Re: SLES9 installation problem - again
Ethernet is IEEE standard 802.3, regardless of copper or fiber media. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ronald Van Der Laan Sent: Friday, October 22, 2004 6:24 AM To: [EMAIL PROTECTED] Subject: Re: SLES9 installation problem - again Linux on 390 Port <[EMAIL PROTECTED]> wrote on 22-10-2004 13:12:33: > Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.22 09:47:25 > idopontban: > > > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. > > 1000 Base-T is not Gigabit Ethernet??? > > 10 Base-T = Ethernet (eth) > 100 Base-T = Fast Ethernet (FEth) > 1000 Base-T = Gigabit Ethernet (GEth),..,gigE,... > 1000Base-T uses electrons through copper to connect to 10Base-T, 100Base-T or 1000Base-T GbE uses photons through fiber to connect to a 1Gbs LAN. Ronald van der Laan -- 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
Re: SLES9 installation problem - again
Linux on 390 Port <[EMAIL PROTECTED]> wrote on 22-10-2004 13:12:33: > Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.22 09:47:25 > időpontban: > > > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. > > 1000 Base-T is not Gigabit Ethernet??? > > 10 Base-T = Ethernet (eth) > 100 Base-T = Fast Ethernet (FEth) > 1000 Base-T = Gigabit Ethernet (GEth),..,gigE,... > 1000Base-T uses electrons through copper to connect to 10Base-T, 100Base-T or 1000Base-T GbE uses photons through fiber to connect to a 1Gbs LAN. Ronald van der Laan -- 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
Re: SLES9 installation problem - again
Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.22 09:47:25 időpontban: > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. 1000 Base-T is not Gigabit Ethernet??? 10 Base-T = Ethernet (eth) 100 Base-T = Fast Ethernet (FEth) 1000 Base-T = Gigabit Ethernet (GEth),..,gigE,... ??? -- 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
Re: SLES9 installation problem - again
It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. Any other thaughts? Gadi -Original Message- From: David Boyes [mailto:[EMAIL PROTECTED] Sent: × 21/10/2004 22:03 To: [EMAIL PROTECTED] Cc: Subject: RE: SLES9 installation problem - again > When I chose option 3 I was asked for 3 devices. The devices > I gave (1200-1202) were not acceptable. > I don't want to use QDIO at this time. Non-qdio should be > supported according to evrything I've read. Not on the gigE cards. You don't have a choice -- if it's really a gigE card, then you must define it as a QDIO device and use QDIO. That's been the situation since the gigE cards were released. If you were using this card with the LCS driver on SLES8, it's not a gigE card. -- 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
RE: SLES9 installation problem - again
> When I chose option 3 I was asked for 3 devices. The devices > I gave (1200-1202) were not acceptable. > I don't want to use QDIO at this time. Non-qdio should be > supported according to evrything I've read. Not on the gigE cards. You don't have a choice -- if it's really a gigE card, then you must define it as a QDIO device and use QDIO. That's been the situation since the gigE cards were released. If you were using this card with the LCS driver on SLES8, it's not a gigE card. -- 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
Re: SLES9 installation problem - again
> 1. Try option 3 - this did not work. The GigE OSA cannot be used with the LCS driver, so option 2 will never work. The GigE OSA must be defined as a QDIO device, so you probably should go back to the IOCP/IODF and make sure it's defined as such. -- 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
Re: SLES9 installation problem - again
Hi, When I chose option 3 I was asked for 3 devices. The devices I gave (1200-1202) were not acceptable. I don't want to use QDIO at this time. Non-qdio should be supported according to evrything I've read. Gadi -Original Message- From: Istvan Nemeth [mailto:[EMAIL PROTECTED] Sent: Thursday, October 21, 2004 2:04 PM To: [EMAIL PROTECTED] Subject: Re: SLES9 installation problem - again Linux on 390 Port <[EMAIL PROTECTED]> Ãrta 2004.10.21 11:56:07 idÅpontban: > Hi Vic, > > Thanx for your response, but > > OSD and OSE are valid for the TYPE paramter. Only OSA and OSAD are > valid for the UNIT paramter. I'm really not a z/Hardware expert, but if you really have OSA-_EXPRESS_ then normally you need qdio driver(3) not lcs (2), and qdio driver should work. You did not gave us information what happened when you choose OSA-Express... > > As I said, this worked fine in SLES8. > > Also ^c does not work (at least from the HMC). > > Gadi > If you want to have a shell, just simply select option 0 (no network) in the main menu, so you can do a 'dmesg', etc.. Istvan -- 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
Re: SLES9 installation problem - again
Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.21 11:56:07 időpontban: > Hi Vic, > > Thanx for your response, but > > OSD and OSE are valid for the TYPE paramter. Only OSA and OSAD are > valid for the UNIT paramter. I'm really not a z/Hardware expert, but if you really have OSA-_EXPRESS_ then normally you need qdio driver(3) not lcs (2), and qdio driver should work. You did not gave us information what happened when you choose OSA-Express... > > As I said, this worked fine in SLES8. > > Also ^c does not work (at least from the HMC). > > Gadi > If you want to have a shell, just simply select option 0 (no network) in the main menu, so you can do a 'dmesg', etc.. Istvan -- 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
Re: SLES9 installation problem - again
Hi Vic, Thanx for your response, but OSD and OSE are valid for the TYPE paramter. Only OSA and OSAD are valid for the UNIT paramter. As I said, this worked fine in SLES8. Also ^c does not work (at least from the HMC). Gadi -Original Message- From: Vic Cross [mailto:[EMAIL PROTECTED] Sent: Thursday, October 21, 2004 9:44 AM To: [EMAIL PROTECTED] Subject: Re: SLES9 installation problem - again On Thu, Oct 21, 2004 at 09:10:37AM +0200, ??? ?? ??? wrote: > My system has an OSA Express 1000Base-T which is configured using these IOCP > statements: > CHPID PATH=(CSS(0),02),SHARED,* >PARTITION=((LINTST,PROD,TEST),(=)),TYPE=OSE,* >PCHID=141 > CNTLUNIT CUNUMBR=1200,PATH=((CSS(0),02)),UNIT=OSA > IODEVICE ADDRESS=(1200,253),CUNUMBR=(1200),UNIT=OSA > IODEVICE ADDRESS=(12FE,1),CUNUMBR=(1200),UNIT=OSAD Technically, your CNTLUNIT and IODEVICE are incorrect[1]. Device type OSA and OSAD are for older OSAs like OSA-2. Use OSE or OSD instead -- unless you *really* want your OSA-Express to run in LCS mode, but I doubt that works. > I went back to the main menu and chose option 2 (Ethernet OSA). (This > worked in SLES8). I entered my first device address (1200) and waited. The message > that came up said: > Lcs: loading LCS driver ($ Revision: 1.72.2.4 $/$ Revision 1.15.2.2 $) > > And it's been like that for quite a while. > > What am I doing wrong? If your card is really an OSA-Express, do not use Option 2. It's loading the LCS module (as you can see) which is not correct for OSA-Express. > Suggestions I received: > 1. Try option 3 - this did not work. It should -- this might be your incorrect hardware definition causing a problem. > 2. Issue the dmesg command to look for more information - How do I > interrupt the configuration script so I can issue commands. You can issue "^c" (without the quotes) to simulate a Ctrl-C, which should break you out of the script and give you a prompt. Hope this helps, Vic Cross [1] I say *technically* incorrect because I have a system where I have an OSA-Express defined as OSA and it's okay. However this is a z/OS system, and the device type entries are only in the MVS definition not in the actual IOCDS. Why is it defined that way? Long story. :) -- 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
Re: SLES9 installation problem - again
On Thu, Oct 21, 2004 at 09:10:37AM +0200, ??? ?? ??? wrote: > My system has an OSA Express 1000Base-T which is configured using these IOCP > statements: > CHPID PATH=(CSS(0),02),SHARED,* >PARTITION=((LINTST,PROD,TEST),(=)),TYPE=OSE,* >PCHID=141 > CNTLUNIT CUNUMBR=1200,PATH=((CSS(0),02)),UNIT=OSA > IODEVICE ADDRESS=(1200,253),CUNUMBR=(1200),UNIT=OSA > IODEVICE ADDRESS=(12FE,1),CUNUMBR=(1200),UNIT=OSAD Technically, your CNTLUNIT and IODEVICE are incorrect[1]. Device type OSA and OSAD are for older OSAs like OSA-2. Use OSE or OSD instead -- unless you *really* want your OSA-Express to run in LCS mode, but I doubt that works. > I went back to the main menu and chose option 2 (Ethernet OSA). (This worked in > SLES8). I entered my first device address (1200) and waited. The message that came > up said: > Lcs: loading LCS driver ($ Revision: 1.72.2.4 $/$ Revision 1.15.2.2 $) > > And it's been like that for quite a while. > > What am I doing wrong? If your card is really an OSA-Express, do not use Option 2. It's loading the LCS module (as you can see) which is not correct for OSA-Express. > Suggestions I received: > 1. Try option 3 - this did not work. It should -- this might be your incorrect hardware definition causing a problem. > 2. Issue the dmesg command to look for more information - How do I interrupt the > configuration script so I can issue commands. You can issue "^c" (without the quotes) to simulate a Ctrl-C, which should break you out of the script and give you a prompt. Hope this helps, Vic Cross [1] I say *technically* incorrect because I have a system where I have an OSA-Express defined as OSA and it's okay. However this is a z/OS system, and the device type entries are only in the MVS definition not in the actual IOCDS. Why is it defined that way? Long story. :) -- 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
SLES9 installation problem - again
Hi, I am now trying to install SLES9. My system has an OSA Express 1000Base-T which is configured using these IOCP statements: CHPID PATH=(CSS(0),02),SHARED,* PARTITION=((LINTST,PROD,TEST),(=)),TYPE=OSE,* PCHID=141 CNTLUNIT CUNUMBR=1200,PATH=((CSS(0),02)),UNIT=OSA IODEVICE ADDRESS=(1200,253),CUNUMBR=(1200),UNIT=OSA IODEVICE ADDRESS=(12FE,1),CUNUMBR=(1200),UNIT=OSAD When I started the installation from the CD, I chose option 10 and listed all of the devices that linux knew about. I saw all of my dasd (devices 800-9ff) and device 1200,1201 and 12fe. Devices 1200 and 1201 were defined as 3088/60 and 12fe as 3088/62. I went back to the main menu and chose option 2 (Ethernet OSA). (This worked in SLES8). I entered my first device address (1200) and waited. The message that came up said: Lcs: loading LCS driver ($ Revision: 1.72.2.4 $/$ Revision 1.15.2.2 $) And it's been like that for quite a while. What am I doing wrong? Suggestions I received: 1. Try option 3 - this did not work. 2. Issue the dmesg command to look for more information - How do I interrupt the configuration script so I can issue commands. I am trying to install SLES9 in an LPAR. I do not have VM available. Gadi -- 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
