James, Not sure. I guess the only thing left to try is a POR. If that doesn't do it, then there's something else wrong.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of James Melin Sent: Thursday, December 26, 2002 9:31 AM To: [EMAIL PROTECTED] Subject: Re: Moving ethernet. What do you suggest happen when you have 1) Configured the CHP online to the new LPAR, the HMC says it's available to that LPAR, but (Installing SuSE 7, 2.4.7 Kernal) the initial probe doesn't find any devices for that chp? The other Linux partition is using the same chp/device range. I had intended to use port 1 on the OSA/ENTR card, as port 0 was in use for Linux LPAR 1. That LPAR is using devices 830/831 for send recieve. The only device LPAR 2 sees is 83F which is the device used by OSA EXPRESS when configuring the card. The CHP is 34, for what it's worth. I had originally tried the RH 2.4.7 distro, but I couldn't figure out what to tell it for the X'0xxxx' stuff at the beginning. When I tried the Redhat stuff, I found that it can only see dev 83F on CHP34. Is there some sort of 'not playing nice' problem that I should be aware of, that a SuSE 7.0 distro would be doing that could prevent another LPAR from talking to the same device # range on the same box/chp? I'd cut/paste the stuff I see but I can only get to it via the HMC. |---------+----------------------------> | | Mark Post | | | <[EMAIL PROTECTED]| | | et> | | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | | | | | | | | 12/20/2002 02:41 | | | PM | | | Please respond to| | | Linux on 390 Port| | | | |---------+----------------------------> >--------------------------------------------------------------------------- ---------------------------------------------------| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Moving ethernet. | >--------------------------------------------------------------------------- ---------------------------------------------------| Steve, One more caveat, I guess. If this is a CHPID that has not been defined to this LPAR before, you're going to need to either do a POR, or configure it online to the LPAR from the service console. This has caused a few people problems in the past (just this month, I believe.) Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Bui Sent: Friday, December 20, 2002 3:32 PM To: [EMAIL PROTECTED] Subject: Re: Moving ethernet. Thank you very much, Mark. S.B. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Post Sent: Friday, December 20, 2002 1:25 PM To: [EMAIL PROTECTED] Subject: Re: Moving ethernet. Steve, You should only need to update the contents of /etc/modules.conf to make sure the addresses specified there are correct. There may not be any specified, if you allowed the driver to auto detect the card. As long as the only thing changing in your I/O configuration is the address of the card, you should be fine. Otherwise, or just to be sure, specify the addresses anyway. (I like to do that anyway, just to document things.) If you ever move to a 2.4 kernel, you'll need to be concerned about the contents of /etc/chandev.conf, but in your case that's not necessary now. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Bui Sent: Friday, December 20, 2002 1:38 PM To: [EMAIL PROTECTED] Subject: Moving ethernet. We have a need to move our current ethernet to a different chpid and different address (cua), and is wondering what needs to be done in Linux (SuSE 2.2.16)? Thanks for any help. ____________ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Steve Bui , IRIS - IBM Systems Support Mgr. Phone(480) 965-3070 / fax(480) 965-6317
