> We aren't running VM, You really should fix that. But, anyway. 8-)
> > > > I could repair it, but when I use ht e0.0.0E200,0.0.E201,0.0.E202 > > addr > > > > for the qeth device (blank line for the portname, but I've also > > tried > > > > CHIP00), it fails to come up with the messages: > > > > > > > > Qeth: loading qeth S/390 OSA-Express driver > > > > Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory > > > > SIOCSIFNETMASK: No such device > > > > SIOCSIFBRDADDR: No such device That version of CentOS is probably old enough that it still requires a portname for the OSA port to initialize correctly. There were later RPM packages for the OSA drivers that removed that "feature". If you're using an OSA that is shared with a z/OS system, the portnames have to match for all systems using that OSA. Is this a base Centos 4 install, or did you apply any maintenance to it? ---------------------------------------------------------------------- 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
