Assuming you did the echo(es) into /proc/chandev, then "insmod lcs" should suffice.
Mark Post -----Original Message----- From: Hall, Jammie [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 2:48 PM To: [EMAIL PROTECTED] Subject: Re: rh 7.2 zipl.conf < One other thing that I forgot (sorry) was to do the insmod for your lcs module. > and I will accomplish this how? insmod lcs0? -----Original Message----- From: Post, Mark K Sent: Tuesday, February 19, 2002 1:39 PM To: [EMAIL PROTECTED] Subject: Re: rh 7.2 zipl.conf Jammie, The "read_conf" command was brain-fade on my part. I should not have included it. If you did not do this: echo chandev=lcs0,0x0202,0x0203,0,1 > /proc/chandev then I don't know why the "ifup eth0" command did not generate any error messages. Writing something to /proc/chandev will allow you to dynamically define your device and start using it. One other thing that I forgot (sorry) was to do the insmod for your lcs module. _Then_ do the ifup eth0, followed by an ifconfig to see if it came online. If it fails, a "dmesg | tail" might provide some information as to why it didn't. I would say that until you can dynamically get your eth0 working, that you should leave zipl.conf alone. Then, you can use vi to update it correctly. That is, unless you want to learn some ed/sed commands. :( Finally, the "HOST=s390.rh-kfbs.com:eth0:172.16.1.164:1500" stuff is _not_ something you want to put into /etc/zipl.conf (or anywhere else). That is an installation script parameter only. Mark Post -----Original Message----- From: Hall, Jammie [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 2:12 PM To: [EMAIL PROTECTED] Subject: Re: rh 7.2 zipl.conf okay, here's what I did. echo chandev=lcs0,0x0202,0x0203,0,1 >> zipl.conf echo HOST=s390.rh-kfbs.com:eth0:172.16.1.164:1500 >> zipl.conf (thinking this would get eth0) ifup eth0 (no messages ... this looks good) cd /boot zipl (everything looks good) I do an ifconfig and still only have lo. I cd /etc, more zipl.conf. [defaultboot] default=linux [linux] target=/boot/ image=/boot/vmlinuz-2.4.17tape parameters="root=/dev/dasda2 dasd=487,488,987" [linux-up] target=/boot/ image=/boot/vmlinuz-2.4.17tape parameters="root=/dev/dasda2 dasd=487,488,987" chandev=lcs0,0x0202,0x0203,0,1 HOST=s390.rh-kfbs.com:eth0:172.16.1.164:1500 when I reboot, I'll still only read [linux]. how do I change the default=linux to default=linux-up? what about the ""? when I reboot, shouldn't I see the eth0 startup? what does echo read_conf > /proc/chandev do? I'm going to go try the rest but this just didn't look right. -----Original Message----- From: Post, Mark K Sent: Tuesday, February 19, 2002 10:22 AM To: [EMAIL PROTECTED] Subject: Re: rh 7.2 zipl.conf Jammie, You should be able to logon to the console as root, cd to /etc, then do echo needed.parm1 >> zipl.conf echo needed.parm2 >> zipl.conf echo needed.parm1 > /proc/chandev echo needed.parm2 > /proc/chandev echo read_conf > /proc/chandev ifup eth0 then cd /boot and re-run zipl to make the changes permanent. Mark Post -----Original Message----- From: Hall, Jammie [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 10:12 AM To: [EMAIL PROTECTED] Subject: rh 7.2 zipl.conf okay, I made a mistake somewhere. I ran loader and install went well. however, when I ipl from dasd, I do not get my eth0. I run ifconfig and all it show is lo 127.0.0.1. I looked back and I did not put the chandev=lcs0 ... in the z/IPL boot loader. can I execute something to get my system up and then vi zipl.conf and add the needed parm or do I just have to start the loader process over. regards, j-me
