Michael, Try this. See if you have an /etc/chandev.conf. Either create it, or make sure you either add (or update) an entry as follows: ctc0,0x2000,0x2001 Then do this command: echo read_conf > /proc/chandev Then "cat /proc/chandev" to see if your CTCs show up in the "forced report." Mark Post -----Original Message----- From: Michael K Lambert [mailto:mlambe7@lsu.edu] Sent: Friday, December 21, 2001 2:22 PM To: Post, Mark K Cc: redhat-s390-list@redhat.com Subject: RE: [Redhat-s390-list] X-mas wishes No, it doesn't show up, which leads me to believe that I am missing some definition. When I first attempted to start iucv, it behaved in exactly the same way until I added the "REMIP=10.0.0.1" line in the ifcfg-iucv0 def. and the "options netiucv iucv=TCPIP" line in modules.conf. There mut be a similar problem here. Michael Lambert "Post, Mark K" To: "'Michael K Lambert'" <mlambe7@lsu.edu>, "Post, Mark K" <mark.post@ed <mark.post@eds.com> s.com> cc: redhat-s390-list@redhat.com Subject: RE: [Redhat-s390-list] X-mas wishes 12/21/2001 01:09 PM Ok, now what happens if you do an "ifconfig -a" command. Does ctc0 show up? Mark Post -----Original Message----- From: Michael K Lambert [mailto:mlambe7@lsu.edu] Sent: Friday, December 21, 2001 2:01 PM To: Post, Mark K Cc: redhat-s390-list@redhat.com Subject: RE: [Redhat-s390-list] X-mas wishes Mark, Dmesg reveals that my parmfile is being processed. The chandev statement is included. "After you did the insmod, what, if anything, showed up in the kernel ring buffer, as shown by the dmesg command? That's the only place you're going to see any error messages." The only dmesg entry that is generated after insmod is: "CTC driver Version: 1.51 initialized" I'm obviously missing something, I'm just not sure what. Michael Lambert _______________________________________________ Redhat-s390-list mailing list Redhat-s390-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-s390-list
