Mark In my case, putting in the chanids (space separated) makes things work. Leaving it blank, or using commas to separate them makes things fail. The YAST netwrok screen GUI lists them in line item order. There are no space or commas. IBM OSA Express Network card (0.0.7000)│20.15.36.52 IBM Hipersocket (0.0.f506) │192.0.1.52 IBM Hipersocket (0.0.f507) │ IBM Hipersocket (0.0.f508) │ IBM OSA Express Network card (0.0.1000)│Not configured IBM OSA Express Network card (0.0.1001)│Not configured IBM OSA Express Network card (0.0.1002)│Not configured IBM IUCV │Not configured
Prior to the mitigation performed this list looked the same except for the IP address for Hipersocket. It was stated as Not Configured prior to the action we took. So again I see two SuSE problems. 1 - 3 IO addresses listed after configuration. 2 - I see no space or commas and the action we needed to perform. 'Where ever you go - There you are!! ' Richard (Gaz) Gasiorowski Global Solutions & Technology Principal Lead Infrastructure Architect CSC 3170 Fairview Park Dr., Falls Church, VA 22042 845-773-9243 Work|845-392-7889 Cell|[EMAIL PROTECTED]|www.csc.com This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. Mark Post <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 09/24/2008 04:34 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: hsi0 and SuSE >>> On 9/24/2008 at 3:44 PM, in message <[EMAIL PROTECTED]>, Richard Gasiorowski <[EMAIL PROTECTED]> wrote: > No the Chandids were there correctly - in fact that appears to be an > issue. Why should the behavior of hsi be any different then OSA? You do > not see 3 addresses for OSA. Do you agree this a SUSE bug? I'm not sure, since I don't experience the same problem you do. In my case, putting in the chanids (space separated) makes things work. Leaving it blank, or using commas to separate them makes things fail. So, from my perspective, the bug is in the field not being pre-populated by YaST. Comparing the contents of the resulting file in /etc/sysconfig/hardware/hwcfg-qeth-ccw-??? against a working one would be useful. In any case, there is a bug in there somewhere. Mark Post ---------------------------------------------------------------------- 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
