IBM Advanced System Management Drivers for Linux version 2.03 CONTENTS -------- 1.0 Overview 2.0 Change History 3.0 System Management Device Driver Installation Instructions for Red Hat 4.0 System Management Device Driver Installation Instructions for SuSE 5.0 KDE and/or GNOME Session Restrictions 6.0 Stopping the IBM Director application program 7.0 Web Sites and Support Phone Number 8.0 Trademarks and Notices 9.0 Disclaimer 1.0 Overview ------------- This README.TXT file is associated with the following 3 RPM files: - ibmasm-src-suse-WRPxxxA.rpm - ibmasm-src-redhat-WRPxxxA.rpm - ibmasm-1.11-x.i586.rpm where xxx is the version of the source rpm that you are installing. These RPM files will build and install Linux device drivers and/or support software for the following IBM hardware: - Advanced System Management PCI Adapter card and its associated Shared Serial Port (Remote Mouse / Keyboard available if the Adapter firmware supports those functions) - Advanced System Management Processor, which is part of the planar board on specific models of Netfinity and IBM eServer xSeries servers (Remote Mouse / Keyboard available if the Adapter firmware supports those functions) - Automatic Server Restart (ASR) which is built onto the planar board of the x205, x220, x225 and x305 models of xSeries servers - Remote Supervisor Adapter. (Remote Mouse / Keyboard available if the Adapter firmware supports those functions) Only the "boxed set" versions of Linux are supported. See Sections 3 and 4 for details. 2.0 Change History ------------------- 2.1 Driver version 2.03 Add support to ibmsprem2 that enables it to be able to handle ALT F1 and ALT F2 key combinations in text mode. Updated this README with restrictions when using remote control and graphics mode for SuSE 9.0. See section 4.0 and 5.0 of this README. 2.2 Driver version 2.00 Fixed a problem in the ibmser device driver that would cause the floppy device to become unavailable when ibmser was loaded. Fixed a problem in the ibmsprem2 exe file that would cause a system hang if it was terminated remotely. ibmsprem2 would terminate but the Service Processor did not get notified so it kept generating remote keyboard data. Fixed an executable load problem that occurred when switching from a text console to a X session or visa versa. The ibmsprem, ibmsprem2 and ibmhalt exe's were not getting re-loaded when a context switch occurred. 2.3 Driver version 1.20 Fixed a remote control problem where a key would be repeated instead of the correct key being displayed. Fixed a remote control problem that caused the HTML CTRL and ALT radio buttons not to work. 2.4 Driver version 1.19 Added text to this readme stating that remote arrow keys and remote mouse are not supported when in X Login and X Logout dialog screens. Using startx is the perferred method to workaround this restriction. Fixed a problem in remote control. Key pad was intermittently giving unexpected results. Fixed a problem in remote control. Multiple key strokes would occur due to network latency between a key pressed and released. Added a OS watchdog to ibmsprem2 that polls the adapter from user space. This is an attempt to catch a kernel panic in which the kernel still has interrupt capability and the PCI interface is still active. 3.0 System Management Device Driver Installation Instructions for Red Hat -------------------------------------------------------------------------- Note: The IBM Director application program must be stopped before any of these service processor device drivers can be installed. Please refer to the section 5.0 of this document for instructions on how to stop the IBM Director program. 3.1 Supported versions: 1) Red Hat, version 6.2 - Specific kernel version tested 2.2.14-5 2) Red Hat, version 7.1 - Specific kernel versions tested 2.4.2-2 2.4.2-2smp 3) Red Hat, version 7.2 - Specific kernel versions tested 2.4.7-10 2.4.7-10smp 4) Red Hat, version 7.3 - Specific kernel versions tested 2.4.18-3 2.4.18-3smp 5) Red Hat Advanced Server, version 2.1 - Specific kernel versions tested 2.4.9-e.3 2.4.9-e.3smp 2.4.9-e.8 Summit kernel. See Retain tip H176211 for important information about configuring the summit kernel sources. 3.2 Red Hat Kernel source configuration Note: Normally the kernel sources will be properly configured if you installed them during your initial Linux installation. If you installed the kernel sources later or if you see errors such as "Kernel version mismatch" or "unresolved symbol errors" then verify that you have the kernel sources installed like this: rpm -qa | grep kernel Sample result (NOTE: Results will vary with different kernel versions): kernel-headers-2.4.2-2 kernel-source-2.4.2-2 kernel-smp-2.4.2-2 kernel-2.4.2-2 Make sure that kernel-headers and kernel-source rpm packages are present and that they match your kernel version number. If the packages are missing or incorrect install the correct packages before proceeding. Once you have the appropriate kernel sources installed you will need to configure them. Execute the following commands: cd /lib/modules/`uname -r`/build make mrproper Execute one of the following commands based on your hardware configuration (again, the exact file names may vary): cp -f configs/kernel-2.4.2-i586.config arch/i386/defconfig cp -f configs/kernel-2.4.2-i586-smp.config arch/i386/defconfig cp -f configs/kernel-2.4.2-i686-enterprise.config arch/i386/defconfig Verify that the kernel Makefile EXTRAVERSION information matches the version that you are running with respect to smp support. make oldconfig make dep 3.3 Distributions without precompiled ASM kernel modules already installed or when upgrading to a newer RPM This version of ibmasm-src-redhat installs all of the necessary files in a single pass. You do not need to install the binary rpm on the machine that you used to install the source rpm. The system that the source rpm file is to be run on must have Linux development/build capability with the Linux kernel source installed and properly configured for your hardware. If you intend to use the Remote Mouse / Keyboard capabilities in an XWindow environment then you will also need the X development (XFree86-devel) headers and libraries. The source rpm file (ibmasm-src-redhat) contains the open source code for the IBM Advanced System Management device drivers for Linux. The file is designed for installation using the Red Hat RPM "build" system. Executing the RPM utility against ibmasm-src-redhat will build and install Linux drivers that are customized for the Linux kernel version of the machine running the RPM utility. This process also generates a binary rpm file that can be installed on any machine running the same Linux kernel and having the same hardware configuration. The following steps must be executed in order to build and install the Linux Advanced System Management drivers. NOTE: If this is an upgrade to an existing Advanced System Management driver or if the driver failed to build properly the first time, then the previously installed driver packages must first be removed. Depending upon your system's configuration, you may see messages about missing files when running the "rpm -e" commands. You may safely ignore those messages. Type the following two commands at a shell prompt to remove the old driver source and binaries: rpm -e ibmasm rpm -e ibmasm-src-redhat To install the source rpm on Redhat version 6.2, execute the following commands: ln -s /usr/src/linux /lib/modules/`uname -r`/build rpm -ivh ibmasm-src-redhat-WRPxxxA.rpm where xxx is the build number of the source RPM that you are installing. To install the source rpm on Redhat versions later than 6.2, execute the following command: rpm -ivh ibmasm-src-redhat-WRPxxxA.rpm where xxx is the build number of the source RPM that you are installing. This RPM will uncompress and untar the archive into the /usr/local/ibmasm directory, compile the software, copy the drivers, shared library, and all configuration files to their appropriate locations, clean up (remove files that are no longer required) and load the device drivers. The drivers will be configured to start at boot-time, and to stop at reboot or shutdown. The Remote Mouse / Keyboard functions can be built with both text-based Virtual Terminal and with X Window System support if your development system has the appropriate X development header files and libraries installed. These files are typically installed if you select the development system options during OS installation. The semi-graphic mode that RedHat uses at boot time causes trouble with Remote Mouse / Keyboard operation. Delete the line "vga = 788" from the /etc/lilo.conf file, run lilo and reboot the system. Make similar changes if you are running GRUB as your boot loader. NOTE: The semi-graphic mode mentioned above is evident when graphic elements are displayed in what appears to be a text mode screen. 3.4 Installing the ibmasm binary RPM (not normally required). The source RPM creates a binary rpm in the /usr/local/ibmasm directory that may be used to install the device driver on other machines. This would be used in situations where there a many identical servers. To install the binary RPM, execute the following commands after copying the binary RPM to the target system: ls -l ibmasm*.rpm (to see the version number) rpm -ivh ibmasm-1.0-y.y.i386.rpm where y.y is the version of the binary RPM that you are installing. This RPM will uncompress and untar the archive into the /usr/local/ibmasm directory, copy the drivers, shared library, and all configuration files to their appropriate locations, clean up (remove files that are no longer required) and load the device drivers. The drivers will be configured to start at boot-time, and to stop at reboot or shutdown. 3.5 Un-installing the ibmasm RPMS. To uninstall the binary rpm, execute the following command: rpm -e ibmasm To uninstall the source rpm, execute the following command: rpm -e ibmasm-src-redhat RPM will unload the drivers, and remove all ibmasm-related files from your system. It is recommended that you uninstall the drivers with -e before installing a new version, rather than upgrading with RPM's upgrade (-U) switch. 3.6 Utility Programs. There are two useful utility programs installed by the RPM. ibmspup is a small script that loads ibmasm.o (the service processor device driver) and ibmser.o (the shared serial port driver). The ibmspup script creates /dev/ibmasm which is the device file for the Advanced System Management hardware and /dev/ibmser which allows the Shared Serial Port featured on the ASM PCI card to be used by communication programs such as minicom. Note that these modules will not load if you do not have the supported hardware installed. ibmspdown unloads the modules. You must have root priveledges to run these utilities. 4.0 System Management Device Driver Installation Instructions for SuSE ----------------------------------------------------------------------- Note: The IBM Director application program must be stopped before any of these service processor device drivers can be installed. Please refer to the section 5.0 of this document for instructions on how to stop the IBM Director program. 4.1 Supported versions: 1) SuSE, version 7.2 - Specific kernel versions tested 2.4.4-4GB 2.4.4-64GB-SMP 2) SuSE, version 7.3 - Specific kernel versions tested 2.4.10-4GB 2.4.10-64GB-SMP 3) SuSE, version 8.0 - Specific kernel versions tested 2.4.18-4GB 2.4.18-64GB-SMP 4) SuSE Linux Enterprise Server, version 7 - Specific kernel versions tested 2.4.7-4GB 2.4.7-64GB-SMP 5) SuSE Linux Enterprise Server, version 8 - Specific kernel versions tested 2.4.19-4GB 2.4.19-64GB-SMP 6) SuSE, version 8.1 If you get the following error: "couldn't find the kernel version the module was compiled for" then the kernel-supplied drivers need to be updated. Remove the kernel-supplied drivers as follows: rm /lib/modules/`uname -r`/kernel/drivers/char/ibmasm/* Then proceed as outlined in section 4.3. - Specific kernel versions tested 2.4.19-4GB 2.4.19-64GB-SMP 7) SuSE, version 9.0 RSA remote control support for SuSE 9.0 is not supported in graphics mode. 4.2 SuSE Distributions with precompiled ASM kernel modules Use Yast or Yast2 to install the ibmasm-1.11-x.i586.rpm binary rpm. If you are using the GUI interface then use the SuSe Run Level Editor to activate support for ibmasm. If you are using the text based interface then start the drivers by typing: rcibmasm start To configure the system to automatically activate the drivers on reboot type: insserv ibmasm 4.3 Distributions without precompiled ASM kernel modules or when uprading to a newer RPM. The kernel source needs to be configured. If you see errors such as "Kernel version mismatch" or "unresolved symbol errors" then configure the kernel sources. The system that the source rpm file is to be run on must have Linux development/build capability with the Linux kernel source installed and properly configured for your hardware. If you intend to use the Remote Mouse / Keyboard capabilities in an XWindow environment then you will also need the X development (xdevel) headers and libraries. After installing the kernel-source RPM configure the kernel sources by executing the following commands: cd /lib/modules/`uname -r`/build cp -f /boot/vmlinuz.version.h \ /lib/modules/`uname -r`/build/include/linux/version.h cp -f /boot/vmlinuz.config \ /lib/modules/`uname -r`/build/.config make cloneconfig make dep make menuconfig When menuconfig completes the menuconfig Main Menu will appear. From the Main Menu select exit and then save the new kernel configuration. On SuSE version 7.2, create the modversions.h file needed by the ibmasm build process by executing the following command: make all This version of ibmasm-src-suse installs all of the necessary files in a single pass. You do not need to install the binary rpm on the machine that you used to install the source rpm. The source rpm file (ibmasm-src-suse) contains the open source code for the IBM Advanced System Management device drivers for Linux. The file is designed for installation using the Red Hat RPM "build" system. Executing the RPM utility against ibmasm-src-suse will build and install Linux drivers that are customized for the Linux kernel version of the machine running the RPM utility. This process also generates a binary rpm file that can be installed on any machine running the same Linux kernel and having the same hardware configuration. The following steps must be executed in order to build and install the Linux Advanced System Management drivers. NOTE: If this is an upgrade to an existing Advanced System Management driver, then the previously installed driver packages must first be removed. Depending upon your system's configuration, you may see messages about missing files when running the "rpm -e" commands. You may safely ignore those messages. Type the following two commands at a shell prompt to remove the old driver source and binaries: rpm -e ibmasm rpm -e ibmasm-src-suse To install the source rpm for SuSE, execute the following command: rpm -ivh ibmasm-src-suse-WRPxxxA.rpm where xxx is the version of the source RPM that you are installing. The Remote Mouse / Keyboard functions can be built with both text-based Virtual Terminal and with X Window System support if your development system has the appropriate X development header files and libraries installed. These files are typically installed if you select the development system options during OS installation. The semi-graphic mode that SuSE uses at boot time causes trouble with Remote Mouse / Keyboard operation. Delete the line "vga = 788" from the /etc/lilo.conf file, run lilo and reboot the system. Make similar changes if you are running GRUB as your boot loader. NOTE: The semi-graphic mode mentioned above is evident when graphic elements are displayed in what appears to be a text mode screen. 4.4 Installing the ibmasm binary RPM (not normally required). The source RPM creates a binary rpm in the /usr/local/ibmasm directory that may be used to install the device driver on other machines. This would be used in situations where there a many identical servers. To install the binary RPM, execute the following commands after copying the binary RPM to the target system: ls -l ibmasm*.rpm (to see the version number) rpm -ivh ibmasm-1.0-y.y.i386.rpm where y.y is the version of the binary RPM that you are installing. This RPM will uncompress and untar the archive into the /usr/local/ibmasm directory, copy the drivers, shared library, and all configuration files to their appropriate locations, clean up (remove files that are no longer required) and load the device drivers. The drivers will be configured to start at boot-time, and to stop at reboot or shutdown. 4.5 Un-installing the ibmasm RPMS. To uninstall the binary rpm, execute the following command: rpm -e ibmasm To uninstall the source rpm, execute the following command: rpm -e ibmasm-src-suse RPM will unload the drivers, and remove all ibmasm-related files from your system. It is recommended that you uninstall the drivers with -e before installing a new version, rather than upgrading with RPM's upgrade (-U) switch. 4.6 Utility Programs. There are two useful utility programs installed by the RPM. ibmspup is a small script that loads ibmasm.o (the service processor device driver) and ibmser.o (the shared serial port driver). The ibmspup script creates /dev/ibmasm which is the device file for the Advanced System Management hardware and /dev/ibmser which allows the Shared Serial Port featured on the ASM PCI card to be used by communication programs such as minicom. Note that these modules will not load if you do not have the supported hardware installed. ibmspdown unloads the modules. You must have root priveledges to run these utilities. 5.0 KDE and GNOME Session Restrictions ----------------------------------------- RSA remote control support for SuSE 9.0 is not supported in graphics mode. Remote mouse and remote arrow keys are not supported when running remote control during the X Login and X Logout dialog boxes. If you plan to use the remote control option while running KDE or Gnome X server sessions, you will need to disable the X Login dialog box as well as the X Logout verification dialog box. This is due to the fact that during Login and Logout the session manager prevents all remote mouse movements as well as some key strokes from reaching the X server (specifically the up and down arrow keys). You may prefer to start your X session using the startx command from run level 3 rather than directly booting the system to run level 5. The use of the startx method will prevent the Login and Logout dialog session manager screens from being displayed. 6.0 Stopping the IBM Director application program ------------------------------------------------------- If the IBM Director application program is already running on your server it must be stopped prior to installing, updating or removing any of these device drivers. The following command examples show how to stop, start and check Director's status. To stop: /opt/IBM/director/bin/twgstop To start: /opt/IBM/director/bin/twgstart To check status: /opt/IBM/director/twgstat. For more details on how to shutdown the IBM Director application please refer to the IBM Director documentation. 7.0 WEB Sites and Support Phone Number --------------------------------------- 7.1 IBM Support Web Site: http://www.pc.ibm.com/support 7.2 IBM Marketing eServer xSeries Web Site: http://www.pc.ibm.com/us/eserver/xseries 7.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html 8.0 Trademarks and Notices --------------------------- The following terms are trademarks of the Red Hat Corporation in the United States or other countries or both: Red Hat The following terms are trademarks of SuSE, Inc. in the United States and SuSE AG in Germany or other countries: SuSE The following terms are trademarks of Linus Torvalds in the United States or other countries or both: Linux 9.0 Disclaimer --------------- 9.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 9.2 Note to Government Users Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.