Ulrich, I just checked the latest version of this document, lx24jun03dd02.pdf, and it still gives examples like this: Or for two network devices (CTC + ESCON): ctc0,0x601,0x600 escon3,0x605,0x608
Who do I need to contact to get this cleaned up? Mark Post -----Original Message----- From: Post, Mark K Sent: Tuesday, December 24, 2002 2:03 AM To: 'Ulrich Weigand' Cc: [EMAIL PROTECTED] Subject: RE: CTC Driver Problem Ulrich, That did seem to correct the problem. Is this documented in the latest Device Drivers manual? Mark Post -----Original Message----- From: Ulrich Weigand [mailto:[EMAIL PROTECTED] Sent: Monday, December 23, 2002 5:57 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: CTC Driver Problem Mark Post wrote: >The problem is that I have both a CTC and ESCON channel pair coupled to >another VM guest, but only one of the pairs is being recognized, and it is >always the _last_ pair defined in /etc/chandev.conf, and it is always >recognized as ctc0. Specifying "noauto" in /etc/chandev.conf does not seem >to help. /proc/chandev shows things are being recognized properly by the >kernel. > >/etc/chandev.conf >noauto,0x0600,0x0701 >escon0,0x0701,0x0700 >ctc0,0x0601,0x0600 I *think* the CTC driver doesn't distinguish escon and ctc (any more?) and simply treats escon0 as synonymous to ctc0. Could you try naming the interfaces ctc0 and ctc1? Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
