I downloaded WEBMIN and installed it late Friday night. It provided a nice
interface for the, lets say less-experienced guys like me, to define
network interfaces. It worked great.
Upon receiving your email, I did verify that all was in order in
/etc/rc.config.
My CLAW interface is working perfectly now and I have since removed the
CTC from the network. I left the CTC between the LPARs to provide
high-speed access between Linux and z/OS but the routes are not
broadcasted to the world, nor does the LPAR have to be available to
provide network connectivity to Linux.
I want to thank everyone for their patience and assistance. Without this
forum's assistance, this Linux evaluation would not have gone very far.
Thanks again.
Peter
"Post, Mark K"
Sent by: Notes Administration
04/29/2002 04:30 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Linux CLAW Woes
Peter,
Cool. Normally I would say this is a job you would use YaST to complete,
but YaST doesn't understand "ci0" as a networking device. So, you can do
it
partway with YaST, and then finish it up by editing /etc/rc.config.
yast
System administration->Network configuration->Network base configuration
down arrow to your first unused network device (probably "1")
F5 to select the device. Ethernet will work as a convenient lie if CLAW
is
not available. Press enter. If CLAW is available, you will _not_ have to
edit the /etc/rc.config file as described below.
F6 to set the IP address, netmask, default gateway, MTU size. Press enter
when "continue" is highlighted.
F4 to "activate" the device. This doesn't try to bring it up, only marks
it
as eligible for activation on the next system boot.
F10 to exit.
You'll see SuSEconfig kick off to update all the necessary files.
Press "continue" when it gets highlighted.
Exit Yast. (Multiple escape keys should do it.)
vi /etc/config
Find NETDEV_1 and change it from "eth0" to "ci0".
Save your changes and exit vi.
Please let me know of any corrections or clarifications to this procedure.
Mark Post
-----Original Message-----
From: Peter E. Abresch Jr. - at Pepco [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 5:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Linux CLAW Woes
Ok guys, I am getting closer. I copied my .config from my boot directory
and edited the MakeFile. It now works when I load it manually. Now I want
it to load when I boot. I added the following lines to /etc/modules.conf
alias ci0 c7000
options c7000 base0=0x5100 lhost0=PEPC uhost0=PEPCOCEC
The directions said to add some more lines to /etc/sysconfig/network, but
naturally I do not have one.
I want the claw active each time I boot my SuSE SLES7-beta. Again, am I
missing something? Appreciate any input. Thanks again.
Peter
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
04/26/2002 11:58 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Linux CLAW Woes
Peter,
It's not that you have the wrong kernel source, it's that you have a
different .config file and/or Makefile. Take a look in your /boot
directory. There should be/may be a file in there called image.config or
something like that which contains the configuration options used when
building your running kernel. Do a diff on that file against the
/usr/src/linux.config and see what if any differences pop up. Also, take
a
look at the Makefile in /usr/src/linux. You should see some lines that
start with:
VERSION =
PATCHLEVEL =
SUBLEVEL =
EXTRAVERSION =
I suspect that what you'll see is
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 7
EXTRAVERSION = SMP
If you change that last line to
EXTRAVERSION = SuSE-SMP
and get the c7000 module to recompile, you'll be home free. To get the
module to recompile, do a
find . -type f -name c7000.o -exec rm c7000.o \;
then "make modules" again, followed by "make modules_install", "depmod -a"
and the insmod command.
Mark Post
-----Original Message-----
From: Peter E. Abresch Jr. - at Pepco [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 11:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Linux CLAW Woes
I copied c7000.o into the original modules directory and ran a dep ?a. I
get the following:
ibm9672:/ # insmod -f c7000 base0=0x5100 lhost0=PEPC uhost0=PEPCOCEC
noauto=1
Using /lib/modules/2.4.7-SuSE-SMP/net/c7000.o
Warning: kernel-module version mismatch
/lib/modules/2.4.7-SuSE-SMP/net/c7000.o was compiled for kernel
version 2.4.7-SMP
while this kernel is version 2.4.7-SuSE-SMP
which is what I guess we all expected.
I issued the following:
ibm9672:/usr/src/linux # grep CONFIG_MODVERSIONS .config
# CONFIG_MODVERSIONS is not set
which I guess is good. So this problem stems from the wrong source tree. I
got the SuSE source tree from YaST option "D Development (C, C++,
LISP,ETC.)". I then selected "Kernel Source ? The source of the SuSE
Kernel".
Should I be pulling the SuSE Kernel source from somewhere else? Am I
issuing the commands from UTS README.1ST from the wrong directory? Thanks
for any more ideas?
Peter
