Dave, I don't think so, because of this message coming out: escon0: read dev: 0600 irq: 000c - write dev: 0601 irq: 000d
I really think he has them defined as escon devices, but either not coupled, or not cross-coupled to the other end properly. Mark Post -----Original Message----- From: Dave Jones [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 6:59 PM To: [EMAIL PROTECTED] Subject: Re: CTC's Turbolinux 6.5 Hi, Mark. I think that your problem is that you've only defined 1 CTC....you need two to get Linux to connect to the VM TCPIP stack. Try this: 1) from the CMS Ready prompt in the Linux virtual machine: a) DEFINE CTC 600 b) DEFINE CTC 601 c) COUPLE 600 TCPIP xxx d) COUPLE 601 TCPIP yyy 2) boot Linux and make sure the ctc parm looks like this: ctc=0x0600,0x0601 Good luck. Dave Jones > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of > Dorney, Mark > Sent: Wednesday, April 17, 2002 1:26 PM > To: [EMAIL PROTECTED] > Subject: CTC's Turbolinux 6.5 > > > First off, serious newbie alert, mainframer thrown into this world for a > POC. > > I'm doing an install from tape, I get to the part where I specify my CTC > information and I start getting errors (logs are at the end). I believe > that the hardware is ok since I went through the archives and although I > couldn't find my specific situation I ran through some other > suggestions of > shutting down the network, rmmod ctc, insmod ctc and restarting > the network. > I tried to manually configure the network by doing an "ifconfig > ctc0......" > and at one point in the day I was able to ping successfully. All > efforts to > duplicate that success have failed. > > Here's what I'm getting: > -------------------------------------------------------------------------- > > Please review your selection: > > -------------------------------------------------------------------------- > > > > Hostname : mylinux.state.wi.us > > > > Gateway IP : 198.150.235.17 > > Gateway Device : ctc0 > > > > Nameserver IP : 198.150.235.21 > > Searchlist : state.wi.us > > CTC options : ctc=0x600 > > > > -------------------------------------------------------------------------- > > Do you want to use these settings? (y/n)y > > y > > CTC driver Version: 1.29 initialized > > channel: 0 Parallel channel found - 2 ESCON channel found > > escon0: read dev: 0600 irq: 000c - write dev: 0601 irq: 000d > > SIOCSIFADDR: No such device > > ctc0: unknown interface: No such device > > SIOCSIFDSTADDR: No such device > > ctc0: unknown interface: No such device > > SIOCSIFMTU: No such device > > SIOCADDRT: No such device > > ctc0: error fetching interface information: Device not found > > search state.wi.us > > Starting portmapper: portmap > > Mounting remote filesystems. > > Starting system logger: syslogd > > Stop network, rmmod ctc, etc reults in ***************** > > bash-2.04# rmmod ctc > rmmod ctc > bash-2.04# cd /lib/modules/2.2.19/misc > cd /lib/modules/2.2.19/misc > bash-2.04# insmod ctc > insmod ctc > Using /lib/modules/2.2.19/misc/ctc.o > bash-2.04# /etc/rc.d/init.d/network start > /etc/rc.d/init.d/network start > SIOCSIFADDR: No such device > ctc0: unknown interface: No such device > SIOCSIFDSTADDR: No such device > ctc0: unknown interface: No such device > SIOCSIFMTU: No such device > SIOCADDRT: No such device > ctc0: error fetching interface information: Device not found > search state.wi.us > bash-2.04# > > Thanks for any help anyone can provide > > Mark Dorney >
