Michael, Also check the "top" of the dmesg output to make sure that your re-execution and re-IPL of Linux picked up your kernel parameters properly. (I just re-noticed your note about how to run zipl in my archive.) If the kernel isn't picking up that chandev parm correctly at IPL time, you're hosed. Mark -----Original Message----- From: Michael K Lambert [mailto:mlambe7@lsu.edu] Sent: Friday, December 21, 2001 11:52 AM To: Post, Mark K Cc: redhat-s390-list@redhat.com Subject: RE: [Redhat-s390-list] X-mas wishes Mark, An lsmod reveals that the ctc module is not being loaded at startup. I can insmod it successfully, but when I attempt to ifconfig the correct settings, I get: "SIOCSIFMTU: No such device ctc0: unknown interface: No such device" A cat of chandev and subchannels reveals that the ctcs are not being detected. My parmfile reads: "root=/dev/dasdb1 dasd=400-401 iucv=linuxsx root=/dev/dasdb1 noinitrd chandev=ct c0,0x2000,0x2001" My ifcfg-ctc0 reads: "DEVICE=ctc0 BOOTPROTO=static IPADDR=10.0.0.3 NETMASK=255.255.255.255 ONBOOT=yes REMIP=10.0.0.4" My modules.conf reads: "alias parport_lowlevel parport_pc alias iucv0 netiucv options netiucv iucv=TCPIP alias ctc0 ctc" As I said, I realize that I'm missing something, I'm just not sure what. Michael Lambert
