Support Notes for Red Hat Enterprise Linux AS V.4 Update 4 for HP Integrity Servers

10. The Red Hat Enterprise Linux AS v. 4 kernel supports maximum memory of 2 TB, which is
also supported by HP.
11. No support for uncertified .rpm packages.
If you add uncertified .rpm packages to the operating system, the operating system will
not be supported by Red Hat. Red Hat supports only .rpm packages bundled in supported
Linux distributions for Integrity servers and official Red Hat Updates for those distributions.
HP supports the Linux software it distributes.
12. Red Hat Enterprise Linux AS v. 4 does not ship or install a kernel-source rpm with the binary
installation CDs or DVDs. If you want to modify or view the kernel configuration, you must
extract kernel-2.6.9-42.EL.src.rpm from the source .rpm packages. Refer to the Red
Hat Enterprise Linux AS v. 4 Release Notes for instructions.
NOTE: These instructions are in the file RELEASE-NOTES-en, but not in the file
RELEASE-NOTES.
13. 32-bit emulation is not automatically installed with Red Hat Enterprise Linux AS v. 4. To
obtain this functionality, install the ia32el package from the Intel Itanium Extras CD. Then
install any additional compatibility binaries you need from the 32-bit Compatibility Layer
Binaries CD. Refer to the Red Hat Enterprise Linux AS v. 4 Release Notes for instructions.
14. Correctable platform events such as single-bit memory errors are routinely logged into
NVRAM. To ensure errors are logged into the /var/log file, configure the salinfod file
to start at boot, executing the following commands as root:
a. Enter cd /etc/init.d .
b. To configure, enter chkconfig salinfod on.
c. To start salinfod without rebooting, enter service salinfod start .
15. If you use cdrecord to burn a CD, you may need to eject the CD and reinsert before you
can mount it.
16. This issue affects Linux running on the following systems: rx1600, rx1620, rx2600, rx2620,
rx3600, rx4640, rx6600, rx7620, rx8620, and Superdome.
The Management Processor UART on these systems does not supply the Carrier Detect
signal. This causes applications to hang when opening the UART device, waiting for Carrier
Detect, unless they use the O_NDELAY or O_NONBLOCK flag.
For example, echo foo > /dev/ttyS0 hangs.
This is usually not a problem because /dev/ttyS0 is usually used as a console, the agetty
process opens it with O_NONBLOCK, and processes spawned by agetty generally inherit
the already-opened device.
However, there are some cases where the device must be opened again, and applications
will observe the hang.
You may also need to add the -L option to the agetty line in the /etc/inittab file as show
below to resolve the problem:
co:2345:respawn:/sbin/agetty -L ttyS0 9600 vt100-nav
After editing the file, signal the init process to re-read the inittab file with the following
command:
kill -HUP 1
If you are logged in to the console, then exit and log in again to restart the agetty.
17. Before booting Red Hat Enterprise Linux AS v.3 or v.4 on an nPartition on an rx7620, rx8620,
or Integrity Superdome server, your ACPI configuration value must be set to
single-pci-domain acpi flag to eliminate any bus address conflicts and ensure all I/O
Known Issues 9