Installation and Documentation Notes

Product readme


Abstract

General installation and usage common problems and frequently asked questions

Content

Answers to frequently asked usage and installation questions, common mistakes and documentation requests.

Issue Response
A kernel fix for SUSE Linux 10 and above may not include kernel-syms. Is kernel-syms required to build NDH? A kernel-syms package is not required to build NDH at SUSE Linux Enterprise Server 10 or above as long as the NDH build.sh is run for the running kernel.
System reports device already exists when trying to load my lcs device. You should ensure your lcs device configuration, specifically devif_num coded, does not conflict with an already configured device.

Different cards used will generate different interface base names:
* Ethernet cards will generate an interface name starting with eth
* Token Ring cards will generate an interface name starting with tr

Numbers will be appended to the base names according to the following rules:
* If a device interface number, devif_num, is specified during device configuration, that number will be used.

lcs<devif_num>,read_devno,write_devno,0,0,0,0

For example, a device configuration like:
lcs7,0x2b10,0x2b11,0,0

will cause the interface name to be eth7 for an Ethernet card and tr7 for a Token Ring card.

If the devif_num is -1, the next available number will be used.
I have all of my lcs<devif_num> definitions and I do not see the corresponding eth<devif_num> device after the kernel is rebooted. Check your boot log. You can usually see it by issuing the `dmesg` command.

If you see the following messages:

      No lcs capable cards found
      Terminating lcs module.
This is an indication that the kernel attempted to initialize the lcs devices defined, but the OSA does not report any lcs capable ports defined. Check your OSA configurations.

IMPORTANT: Look at your device configuration files and ensure you have not used double quote marks in place of single tick marks. They can be interpreted very differently by some shell programs and may prevent your devices from coming active. Refer to the examples in the CCL documentation for valid samples.

Manual load of the ccz_ndh module fails. Refer to the README documentation for complete instructions for manually loading the CCL NDH kernel components.

Make sure you use the -f flag on the insmod or modprobe command.
load_ndh.sh script does not appear to work but I cannot see any relevant failure messages. The build of the cclndh.c module may be failing. The load_nsh.sh script does not echo all messages put out when it invokes the build.sh script internally.



cd to the drivers directory and issue the `./build.sh` script and address any error messages seen.

Then change back to the CCL Installation Directory and issue the load_ndh.sh script again to load all the kernel modules properly.
Does CCL run on Red Hat Refer to the Read Me document for the latest information regarding supported distributions and kernel requirements.
Where can I obtain more information about configuring Linux Devices Refer to the following Linux on zSeries Technical Support link for the most current "Linux for zSeries and S/390 Device Drivers, Features and Commands" Manual

http://www.ibm.com/servers/eserver/zseries/os/linux/support_documentation.html
Where can I obtain more Linux on zSeries Technical support including Redbook and Library References IBM Linux on zSeries Website : http://www.ibm.com/servers/eserver/zseries/os/linux/

Rate this page:

(0 users)Average rating

Document information


More support for:

Communication Controller for Linux on System z
All

Software version:

1.2, 1.2.1, 1.3

Operating system(s):

Linux Red Hat - zSeries, Linux SUSE - zSeries, Linux zSeries

Reference #:

7005770

Modified date:

2006-05-31

Translate my page

Machine Translation

Content navigation