I am trying to boot from an NFS root-fs. I was able to figure out my errors, which involved copying the udevtrigger command to the initrd and running it just before udevsettle in my init script:
/sbin/udevd --daemon
/sbin/udevtrigger
/sbin/udevsettle
...
and adding all of the network related setup scripts (etc/sysconfig/network
and network-scripts) to the initrd:
echo "NETWORKING=yes" > /etc/sysconfig/network
echo "ONBOOT=yes" > /etc/sysconfig/network-scripts/ifcfg-eth1
echo "BOOTPROTO=dhcp" >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo "DEVICE=eth1" >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo 'OPTIONS="layer2=1"' >> /etc/sysconfig/network-scripts/ifcfg-eth1
echo "SUBCHANNELS=0.0.0800,0.0.0801,0.0.0802"
>> /etc/sysconfig/network-scripts/ifcfg-eth1
# Turn on network
echo 0.0.0800,0.0.0801,0.0.0802 > /sys/bus/ccwgroup/drivers/qeth/group
echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0800/layer2
echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0800/online
echo "alias eth1 qeth" >> /etc/modprobe.conf
echo `ifup eth1`
...
After those changes, I was able to boot from the network with my initrd.
Thank you to all who replied.
Thang 2455 South Road (Embedded
Pham image moved to
file:
pic04585.gif)
Phone: (845) 433-7567 Poughkeepsie, NY
12601
e-mail: thang.p...@us.ibm.com
From: Steffen Maier <ma...@linux.vnet.ibm.com>
To: LINUX-390@vm.marist.edu
Date: 06/24/2010 02:05 PM
Subject: Re: Red Hat network modules
Sent by: Linux on 390 Port <LINUX-390@vm.marist.edu>
On 06/23/2010 07:29 PM, Thang Pham wrote:
> I am building my initrd using cpio -H newc -o| gzip -9 -c - > initrd.gz
What do you base the content of your custom initrd on?
Is it an existing initrd generated with mkinitrd? Since you use nash,
that could be the case.
What is the use case for activating a qeth device early in initrd?
Is it root-fs on a network file system?
If we know what you try to achieve we can point in the right direction.
> I do not activate the a ccwgroup device because I thought it was done for
> you automatically by udev. I turned udevd into a daemon in my init
script,
> but I do not see the network devices online.
RHEL5: I don't know of any mkinitrd code that activates s390 network
devices. Udev is used for s390 netdev preparation in an installed system
by means of /etc/udev/rules.d/55-ccw.rules triggering /lib/udev/ccw_init
which in turn configures all SUBCHANNELS it can find in
/etc/sysconfig/network-scripts/ifcfg-* (minus backup files) in order to
provide Linux network devices.
You could copy all this and its dependencies into your custom initrd or
simply generate explicit static nash script commands setting up the
ccwgroup you'd like to have available before the root-fs has been mounted.
/sbin/mkinitrd does the latter for e.g. zfcp luns based on
/etc/zfcp.conf, while dasds are activated by means of the driver module
parameter in /etc/modprobe.conf. However, mkinitrd is missing the
necessary s390 specific preparation of network devices that ccw_init
does in an installed system (that's different with dracut the upstream
successor to mkinitrd, BTW).
> The output of lsqeth and lscss are:
>
> sh-3.2# lsqeth
You can use the following in such stripped-down environment such as
busybox to see which ccwgroups are configured with qeth:
ls -lF /sys/bus/ccwgroup/drivers/qeth
But I suspect there won't be any since you said you don't configure them
explicitly and in a previous mail we could not see any network devices
either.
> sh-3.2# lscss
> Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs
> ----------------------------------------------------------------------
> 0.0.0009 0.0.0000 0000/00 3215/00 yes 80 80 ff 00000000 00000000
> 0.0.0800 0.0.0001 1732/01 1731/01 yes 80 80 ff 00000000 00000000
> 0.0.0801 0.0.0002 1732/01 1731/01 yes 80 80 ff 00000000 00000000
> 0.0.0802 0.0.0003 1732/01 1731/01 yes 80 80 ff 00000000 00000000
Now, I'm suprised that there seems to be one qeth device active.
Is that output from within the initrd where the bringup of the network
device fails or from later on after the root-fs has been mounted and
sysV init scripts have run udev triggering ccw_init and bringing up
0.0.0800,0.0.0801,0.0.0802?
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
<<attachment: pic04585.gif>>
