Hi Tom,
I did that alpha 2.4.7 :) and the reason why it has name ALPHA you can see :(
Because in IBM documentation was no any word about eth0, tr0, etc
but in real life lcs0 works only for device layer, build404 could have
some problem with lcs driver if on mainframe it has other alias then lcs0
If not lcs0 but eth0, tr0 or something else (it is defined in the IOCP ? )
then
configuration of network will not work with alha installer.
It can be fixed after configuration with lcs0 is done:
1) Set all param of network and configure lcs0 with option line:
lcs0,<options>
when ask about gateway device overwrite lcs0 with eth0 or with your
alias
2) at bash prompt do:
/etc/rc.d/init.d/inet stop
/etc/rc.d/init.d/network stop
echo 'alias eth0 lcs' >>/etc/modules.conf
mv /etc/sysconfig/network-scripts/ifcfg-lcs0
/etc/sysconfig/network-scripts/ifcfg-eth0
3) change line in file ifcfg-eth0 to DEVICE=eth0
perl -p -i -e 's/DEVICE.*/DEVICE=eth0/'
/etc/sysconfig/network-scripts/ifcfg-eth0
4) change line in file /etc/sysconfig/network to GATEWAYDEV=eth0 ( if you did
not overwrite it )
perl -p -i -e 's/GATEWAYDEV.*/GATEWAYDEV=eth0/' /etc/sysconfig/network
5) Start network and inet at bash prompt:
/etc/rc.d/init.d/network start
/etc/rc.d/init.d/inet start
After installation is completed you can fix network config files without
reboot:
mount dasd and copy files on mounted dasd:
cp /etc/modules.conf /mount/point/etc/modules.conf
cp /etc/sysconfig/network /mount/point/etc/sysconfig/network
cp /etc/sysconfig/network-scripts/ifcfg-eth0
/mount/point/etc/sysconfig/network-scripts/ifcfg-eth0
rm /mount/point/etc/sysconfig/network-scripts/ifcfg-lcs0
Or reboot (halt - IPL ) and then fix files.
Regards,
Julia
"Kern, Thomas" wrote:
> Sorry for this long posting. I am trying to install the TurboLinux ALPHA
> 2.4.7 system. I will be trying the BETA 2.4.5 system later today. I have
> moved the VM RDR kernel, parmline and initrd to the VM user and ipled. I am
> on a MP3000-H50 using a 3172 with 4 ports as my network communications
> device. A Turbolinux 2.2.16 system is already using relative adapter 3 on
> this 3172 and a SuSE 2.4.5 system is on relative adapter 1. I go through
> the network specification process and get to the LCS options area and enter
> what looks to be an acceptable response and I get the following errors. The
> lcs code can obviously talk to the 3172 because it gets the hardware
> address, but I still get the SIOCS... messages.
>
> /Thomas Kern
> /(301)903-2211
>
> lcs options :
> chandev=noauto,lcs0,0x3ad0,0x3ad1,0,2
> -----------------------------------------------------------------------
> Please review your lcs0 selection:
> -----------------------------------------------------------------------
> IP address : 205.254.145.68
> Broadcast : 205.254.145.79
> Netmask : 255.255.255.240
> Network : 205.254.145.64
> MTU : 1492
> Module options : chandev=noauto,lcs0,0x3ad0,0x3ad1,0,2
> -----------------------------------------------------------------------
> Do you want to use these settings? (y/n)
> y
> chandev_setup unknown verb chandev=noauto,lcs0,0x3ad0,0x3ad1,0,2 on
> line no 1 interpreted as chandev=noauto,lcs0,0x3ad0,0x3ad1,0,2.
> Type man chandev for more info.
> ... snipped ...
> Starting lcs module $Revision: 1.116 $ $Date: 2001/09/03 14:12:06 $
> with chandev support,with multicast support, with ethernet support,
> with token ring support.
> debug: reserved 16 areas of 2 pages for debugging lcs
> debug: lcs: new level 0
> lcs_sleepon network card taking time responding irq=0624 devno=3ad0,
> please be patient, ctrl-c will exit if shell prompt is available .
> qipassist failed, ipassists assumed unsupported for eth0
> lcs: eth0 configured as follows read subchannel=624 write subchannel=625
> read_devno=3ad0 write_devno=3ad1
> hw_address=02:60:8C:A3:A8:E5 rel_adapter_no=2
> SIOCSIFADDR: Illegal seek
> lcs0: unknown interface: No such device
> SIOCSIFNETMASK: No such device
> SIOCSIFBRDADDR: No such device
> lcs0: unknown interface: No such device
> SIOCSIFMTU: No such device
> SIOCADDRT: Illegal seek
> lcs0: error fetching interface information: Device not found
> search hqadmin.doe.gov
> Starting portmapper: portmap
> Mounting remote filesystems.
> Starting system logger: syslogd
> Starting kernel logger: klogd
> Starting INET services: inetd
> -----------------------------------------------------------------------
> ----- Congratulations! The first installation stage is finished. ------
> -----------------------------------------------------------------------
--
o || Julia Karastoianova > Turbolinux, Inc.
/\_ _|| [EMAIL PROTECTED] > Research & Development in the U.S.
\__`[_ | ph. (650)228-5156 > 8000 Marina Blvd, Suite 300,
][ \, || fax (650)228-5001 > Brisbane CA 94005 USA
