HP Workstations User Manual for Linux

A collection of installation, configuration and setup papers

Part Number 364387-001

November 2005 Edition

Contents

Chapter 1: Overview of the HP Installer Kit for Linux

Chapter 2: Obtaining the HP Installer Kit for Linux from the HP Support Website

Chapter 3: Installing with the HP Installer Kit for Linux

Chapter 4: HP Release Notes for Red Hat® Enterprise Linux

Chapter 5: Setting Up Large Memory Configurations

Chapter 6: Enabling Hyper-Threading Technology

Chapter 7: Setting Up Multi-Monitor Configurations

Chapter 8: Using your HP 16X DVD Burner

Chapter 9: Enabling IEEE-1394 on HP Linux Workstations

Chapter 10: Introducing HP 64-bit Linux Workstations

Chapter 11: FAQ for HP 64-bit Linux Workstations

Chapter 12: Install Guide for Novell Linux Desktop-9 (Service Pack 2) and SLES-9(SP2)

Overview of the HP Installer Kit for Linux

Summary ...... 2 Supported Operating Systems ...... 2 HP Installer CDs ...... 2 HP Driver CDs ...... 2 Links...... 3

Summary

This document provides an overview of the HP Installer Kit. For specific information on how to install Linux, refer to Installing with the HP Installer Kit for Linux. Use this document with the Hardware Support Matrix for HP Linux Workstations and HP Installer CDs/HP Driver CDs, which can be found at www.hp.com/support/linux_hardware_matrix. Supported Operating Systems HP supports multiple versions of Red Hat® Linux on HP Pentium® 4 and Xeon® Workstations. The supported versions include Red Hat Linux 7.2, Red Hat Linux 7.3, Red Hat Linux 8.0, Red Hat Linux 9, and Red Hat Enterprise Linux WS 3. To provide flexibility in installing the Red Hat OS version of your choice, HP has created Installer CDs and Driver CDs. These CDs are included in the HP Linux Installer Kit, and the CD images (ISOs) for these CDs can be downloaded from the HP support website at www.hp.com/go/workstationsupport. The Installer Kit does not include the OS, so the customer also needs to download from the web or purchase a Red Hat box-set with the desired Red Hat version to be used with the Installer CD or the Driver CD. To view the current Installation Support Matrix for HP Linux Workstations and the supported configurations and operating systems, go to www.hp.com/support/linux_hardware_matrix. HP Installer CDs The HP Installer Kit includes an Installer CD or a Driver CD, which are based on the needs of a particular installation, for each supported Red Hat release. An Installer CD is provided for a Red Hat version when the amount of HP-added content to support HP Workstations is substantial or critical to Linux boot/operation. Older versions of Red Hat Linux typically do not work without altering the most current version of HP Workstation hardware because new components, such as network cards, sound cards and SCSI adapters, require newer device drivers than what was released when the box-set was created. Often, the box-set kernel does not boot because of this issue. To get around this situation, the Installer CD provides additional and updated critical drivers and Errata for the HP Workstation hardware used during installation and installed in the final image on the hard drive. The Installer CD is used as the first CD for installing Red Hat Linux box-sets. To install the box-set, insert this CD first and reboot the HP Workstation. This starts the Anaconda, the familiar Red Hat Installer. All the HP-added content is in the /NEW_DRIVERS directory on the CD and can be used by customers to build their own image or to browse the HP-added content. HP Driver CDs HP provides a Driver CD for a Red Hat version when the amount of HP-added content for drivers and other software packages (called RPMS) is small and not as critical as when HP provides an Installer CD. The more recent versions of Red Hat Linux include the most current device drivers and typically only require driver updates with minor fixes to support HP Workstations. These recent releases can usually be supported using the Driver CD. This Driver CD can be used as a post-install utility for the standard Red Hat install. After the standard Red Hat install is complete and the system is rebooted, a Red Hat utility called “first-boot” is invoked that allows the user to set up the security level, time and date, root password, user accounts, and other settings. The last thing that first-boot allows the user to do is to load additional CDs. The Driver CD is designed to use during this additional CD phase. (Refer to Installing with the HP Installer Kit for Linux. ) All the HP-added content is in the /HP directory on the CD and can be used by customers to build their own image or to browse the HP content.

2 Links

HP Workstations Linux Home Page: http://www.hp.com/linux HP Workstations Home Page http://www.hp.com/workstations Hardware support matrix for HP xw Linux Workstations http://www.hp.com/support/linux_hardware_matrix HP User Manual for HP xw Linux Workstations http://www.hp.com/support/linux_user_manual For additional information on HP products and services, visit us at: http://www.hp.com/ For the location of the nearest sales office, call: United States: +1 800 637 7740 Canada: +1 905 206 4725 Japan: +81 3 3331 6111 Latin America: +1 305 267 4220 Australia/New Zealand: +61 3 9272 2895 Asia Pacific: +8522 599 7777 Europe/Africa/Middle East: +41 22 780 81 11 For more information, contact any of our worldwide sales offices or HP Channel Partners (in the U.S. call 1 800 637 7740).

© 2004-2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds. Intel, Xeon, Intel Inside and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

3 Obtaining the HP Installer Kit for Linux from the HP Support Website

Summary ...... 2 Obtaining the appropriate ISOs in the HP Installer Kit for Linux ...... 4 Links...... 5

Summary

The HP Installer Kit for Linux assists customers installing Red Hat® Linux on HP Workstations. The kit provides updated drivers, tools, and operating system errata to enable HP hardware with various Linux Operating System Versions. This document details the CDs (ISOs) contained in the HP Installer Kit for Linux, the supported platforms, and how to download the CDs (ISO0s) from the HP support website.

2 Table 1-1. Red Hat Enterprise Linux Supported Hardware Platforms

Red Hat Enterprise Linux 4 (x86) Red hat Enterprise Linux 4 (AMD64/EM64T)

Rev Supported HW Platforms CDs (ISOs) in the HP Installer Kit for Linux

Update 1 Xw4200, xw4300, xw6200, HP Installer Kit for Linux—HP Driver CD for Red Hat Enterprise Rev. A xw8200, and xw9300 Linux 4 HP Installer Kit for Linux—Red Hat Drivers Disk for Red Hat Enterprise Linux 4

Red Hat Enterprise Linux 3 (x86) Red Hat Enterprise Linux 3 (AMD64/ EM64T)

Rev Supported HW Platforms CDs (ISOs) in the HP Installer Kit for Linux

Update 1 xw4100, xw6000, and xw8000 HP Installer Kit for Linux—HP Driver CD for Red Hat Enterprise Rev. B Linux 3

Update 2 xw4200, xw6200, and xw8200 HP Installer Kit for Linux—HP Driver CD for Red Hat Enterprise Rev. A Linux 3 HP Installer Kit for Linux—Red Hat Drivers Disk for Red Hat Enterprise Linux 3

Update 4 xw4200, xw6200, xw8200, and HP Installer Kit for Linux—HP Driver CD for Red Hat Enterprise Rev. A xw9300 Linux 3

Update 5 xw4200, xw4300, xw6200, HP Installer Kit for Linux—HP Driver CD for Red Hat Enterprise Rev. B xw8200, and xw9300 Linux 3 Update 5 HP Installer Kit for Linux—Red Hat Drivers Disk for Red Hat Rev. A Enterprise Linux 3

Red Hat Linux 9

Rev Supported HW Platform CDs (ISOs) in the HP Installer Kit for Linux

B Rev. 0 xw4100, xw6000, and xw8000 HP Installer Kit for Linux—Installer CD for Red Hat 9

Red Hat Linux 8.0

Rev Supported HW Platform CDs (ISOs) in the HP Installer Kit for Linux

B Rev. 0 xw4100, xw6000, and xw8000 HP Installer Kit for Linux—Installer CD for Red Hat 8.0

Red Hat Linux 7.3

Rev Supported HW Platform CDs (ISOs) in the HP Installer Kit for Linux

B Rev. 0 xw4100, xw6000, and xw8000 HP Installer Kit for Linux—Installer CD for Red Hat 7.3

E Rev. 0 xw4200, xw6200, and xw8200 HP Installer Kit for Linux—Installer CD for Red Hat 7.3

Red Hat Linux 7.2

Rev Supported HW Platform CDs (ISOs) in the HP Installer Kit for Linux

B Rev. 0 xw4100, xw6000, and xw8000 HP Installer Kit for Linux—Installer CD for Red Hat 7.2

E Rev. 0 xw4200, xw6200, and xw8200 HP Installer Kit for Linux—Installer CD for Red Hat 7.2

3 Obtaining the appropriate ISOs in the HP Installer Kit for Linux

1. Open a browser and go to http://www.hp.com/go/workstationsupport. 2. Select your workstation model from Table 1-1. 3. In the “I would like to” section, click download drivers and software. 4. Select your Operating System from the table. 5. In the “quick jump to download by category” section, click Software. 6. Download the ISO title (from column 3 in Table 1-1) for the desired revision (column 1 in Table 1- 1) 7. Optional: Create Source DVD. NOTE: The Source DVD provides source for the drivers and internal Linux tools used on the Installation CDs, and most customers never need to use it.

a. Download Source DVD ISOs from any Linux OS page. – HP Installer Kit for Linux—Source DVD; Part 1 – HP Installer Kit for Linux—Source DVD; Part 2 – HP Installer Kit for Linux—Source DVD; Part 3 – HP Installer Kit for Linux—Source DVD; Part 4 – HP Installer Kit for Linux—Source DVD; Part 5 b. Untar the ISOs (e.g. untar –zxf “filename”). c. Cat the output of untar (e.g. cat srcDVD_3.2.part1.iso srcDVD_3.2.part2.iso srcDVD_3.2.part3.iso srcDVD_3.2.part4.iso srcDVD_3.2.part5.iso > srcDVD_3.2.iso).

4 Links

Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds.

5 Installing with the HP Installer Kit for Linux

Installing with HP Installer CDs ...... 2 Installing with HP Driver CDs...... 3 Warranty...... 3 Platform Support...... 3 Localization ...... 3 Graphics ...... 4 System RAM...... 4 Network Cards...... 4 Links...... 5

Installing with HP Installer CDs

To install with the Installer CD:

1. Insert the HP Installer CD into the CD-ROM tray. 2. Reboot your workstation from the Installer CD. 3. Select the option for loading Linux that best suits your needs: – “gui” for a custom install leveraging all software packages (called RPMS) needed to enable your HP hardware. WARNING: This erases your hard disk and rewrites new disk partitions. – “install” for an HP identified install leveraging all RPMS needed to enable your hardware as well as specific RPMS identified to optimize your HP Workstation experience. – “recover” for a fully automated, HP identified install that leverages the maximum amount of HP engineering. WARNING: This erases your hard disk and rewrites new disk partitions.

4. Insert the Linux operating system CDs from the Red Hat® box-set as prompted. 5. Continue following prompts until the operating system is successfully installed. 6. The parameters entered during the X configuration step of the install are replaced by HP defaults when the accelerated graphics drivers are installed. After the installation is complete, the installed system can be rebooted for the first time. The installed image contains the Red Hat box-set image plus HP-added RPMS to ensure proper operation on HP Workstations.

2 Installing with HP Driver CDs

To install with the HP Driver CD:

1. Install the operation system using the CDs included in your Red Hat Linux box-set. 2. If there is a Red Hat Driver Disk that corresponds to the Red Hat OS version that is being installed, installing with this Red Hat Driver Disk requires “linux dd “ be typed into the initial install splash screen. (Do not just type .) 3. When asked if you have a driver CD, answer “Yes”. Place the Red Hat Driver Disk in the drive and select the appropriate drive – hd[abcd]. Continue the normal installation. 4. After successfully installing the Red Hat Linux operating system, reboot your system. 5. The Red Hat Setup Agent (also known as “first-boot”) will setup system parameters such as networking, time/date, and adding new users. Complete this process. A screen titled “Additional CDs” displays, and you will have an opportunity to initialize the system with HP Driver CD components. 6. Insert the HP Driver CD. 7. When prompted, click Install for the “Additional CD” option. 8. When the driver installation task is completed, finish the first-boot setup. 9. Continue following the prompts until the operating system is successfully installed. 10. Reboot your system to allow for the proper post-install configuration of the drivers. Warranty

As part of your hardware warranty, HP provides software configuration and installation support for Red Hat Linux for up to 90 days from date of purchase of the Linux-enabled workstation configuration. To download the latest Linux drivers, visit www.hp.com/go/workstationsupport. For full warranty information, refer to the warranty that shipped with your HP Workstation or visit www.hp.com/go/workstationsupport and select the Warranty Information link. Platform Support

For supported platforms, see Table 1.1 in Obtaining the HP Installer Kit for Linux from the HP Support Website. Localization

Red Hat delivers localization support throughout the installation process and with the base OS on both Red Hat 9 and Red Hat Enterprise Linux WS 3. Some README files and menus in the HP installer CDs only have English support, but the installer CDs generally support localization. The supported hardware localization kits are listed in the Installation Support Matrix.

3 Graphics

HP Workstations may be ordered without a graphics card, or with a selection of graphics cards that have gone through extensive verification with HP and the graphics vendors. See the Installation Support Matrix for a complete list of drivers and the platforms that support them. Due to power requirements of the graphics cards and market focus of the different workstation boxes, not all graphics cards are available on each box. Accelerated drivers that are supported by HP and the graphics vendors are available on the Installer CD and from the HP support website. These accelerated drivers are not found on the Red Hat CDs because they are not open source. More recent drivers that have not been qualified by HP are sometimes available from the graphics vendor’s website. These drivers are not supported by HP, but the graphics vendor can provide some level of support with these versions of their drivers. When installing your Red Hat OS with the HP Installer CD, the X configuration step is replaced with default values that work well for the accelerated graphics drivers. A default resolution of 1280x1024 is set up. System RAM

Red Hat only supports 3 GB of memory per process, but supports a total system memory of up to 16 GB on Red Hat Enterprise Linux WS 3 and Red Hat Linux 9. HP supports different amounts of total RAM in the different boxes based on the number of hardware DIMM slots and market requirements. The total memory supported for each hardware/OS configuration is listed in the Installation Support Matrix. To use more than 3.5 GB of RAM, HP workstations must be booted with the bigmem kernel on Red Hat Linux 7.3 and 8.0 and have the BIOS updated to a recent version. BIOS updates can be downloaded from the HP support website. Network Cards

The integrated network cards are all supported for the different workstation platforms and are set up as the first network device (eth0) after the installation. In addition, network cards that can be ordered separately (called AMO kits) are supported. Specifically, the Intel network cards and Broadcom network cards are both supported. Given that all the HP workstations come with an integrated LAN card, the additional cards can be used for a second LAN card or to replace the existing integrated LAN.

Links

Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds.

5 HP Release Notes for Red Hat® Enterprise Linux

Summary ...... 6 RHEL 3 Update 6 WS ...... 7 X86 or AMD64/EM64T on xw4300 Does not Contain the Intel HD Audio Driver...... 7 DESCRIPTION...... 7 SCOPE...... 7 RESOLUTION...... 7 x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices ...... 7 DESCRIPTION...... 7 RHEL 3 Update 5 WS ...... 8 x86 or AMD64/EM64T on Dual Core HP xw4300 Workstation Only Reports 2 CPU's When Running the SMP Kernel...... 8 DESCRIPTION...... 8 SCOPE...... 8 RESOLUTION...... 8 x86 or AMD64/EM64T on xw4300 LAN-on-Motherboard tg3 Driver is Not Fully Integrated...... 8 DESCRIPTION...... 8 SCOPE...... 8 RESOLUTION...... 8 x86 or AMD64/EM64T on xw4300 Does Not Contain the Updated LAN Driver Necessary to Enable Network/PXE Boot Installations...... 10 DESCRIPTION...... 10 SCOPE...... 10 RESOLUTION...... 10 x86 or AMD64/EM64T on xw4300 Does Not Contain the Intel HD Audio Driver...... 11 DESCRIPTION...... 11 SCOPE...... 11 RESOLUTION...... 11 x86 or AMD64/EM64T with FX3400, FX3450, or FX4500 Graphics Card May Fail to Start X ...... 11 DESCRIPTION...... 11 SCOPE...... 11 RESOLUTION...... 11

x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices ...... 11 DESCRIPTION...... 11 x86 or AMD64/EM64T with ATI3100 Fails to Save and Restore libGL.so.1 ...... 12 DESCRIPTION...... 12 SCOPE...... 12 RESOLUTION...... 12 x86 or AMD64/EM64T with ATI3100 Can Only be Configured Using ATI Tool 'fglrxconfig' ...... 12 DESCRIPTION...... 12 SCOPE...... 12 RESOLUTION...... 12 RHEL 3 Update 4 WS ...... 13 AMD64/EM64T Installation Fails on HP xw6200 Workstation or HP xw8200 Workstation with a SATA Drive and 4GB or More of Memory...... 13 DESCRIPTION...... 13 SCOPE...... 13 RESOLUTION...... 13 AMD/EM64T on HP xw8200 Workstation and HP xw6200 Workstation Might Panic with 4GB of Memory and SATA and FX1400 or FX540...... 13 DESCRIPTION...... 13 SCOPE...... 14 RESOLUTION...... 14 AMD64/EM64T Preinstalled HP xw6200 Workstation and HP xw8200 Workstation Systems Need to Have Accelerated Graphics Configured ...... 14 DESCRIPTION...... 14 SCOPE...... 14 RESOLUTION...... 15 x86 on HP xw9300 Workstation Does Not Install Accelerated Graphics ...... 16 DESCRIPTION...... 16 SCOPE...... 16 RESOLUTION...... 16 x86 on HP xw9300 Workstation Does Not Have A Functional Network Driver For LOM...... 16 DESCRIPTION...... 16 SCOPE...... 16 RESOLUTION...... 17 AMD64/EM64T on HP xw9300 Workstation Will Not Ask to Set up Networking...... 17 DESCRIPTION...... 17 SCOPE...... 17 RESOLUTION...... 17 x86 or AMD64/EM64T on HP xw9300 Workstation Does Not Install Audio Driver ...... 18 DESCRIPTION...... 18 SCOPE...... 18 RESOLUTION...... 18 x86 or AMD64/EM64T on HP xw9300 Workstation Does Not Fully Enable the Use of HP USB 2.0 Disk-On- Key Devices ...... 19 DESCRIPTION...... 19 SCOPE...... 19 RESOLUTION...... 19 AMD64/EM64T on HP xw9300 Workstation Does Not Contain the Necessary LAN Drivers to Enable Network Install or PXE Booting...... 19 DESCRIPTION...... 19 SCOPE...... 19 RESOLUTION...... 19 AMD64/EM64T on HP xw9300 Workstation Will Panic if 8GB Installed on CPU#1 ...... 20 DESCRIPTION...... 20 SCOPE...... 20 RESOLUTION...... 20

AMD64/EM64T on HP xw9300 Workstation with 4GB or More of Memory Will Panic When Booting the Install Kernel...... 20 DESCRIPTION...... 20 SCOPE...... 20 RESOLUTION...... 20 AMD64/EM64T on xw9300 Total Memory May Be Less Than Expected with x86_64 Kernel...... 20 DESCRIPTION...... 20 SCOPE...... 21 RESOLUTION...... 21 x86 on xw9300 Total Memory May Be Less Than Expected with the athlon Kernel ...... 21 DESCRIPTION...... 21 SCOPE...... 21 HP xw9300 Workstation with RHEL3 32-bit OS...... 21 RESOLUTION...... 22 x86 or AMD64/EM64T on the HP xw4200 Workstation Only Reports Approximately 3GB when 4GB Of Memory Is Present...... 22 DESCRIPTION...... 22 SCOPE...... 22 RESOLUTION...... 22 RHEL 4 Update 2 WS ...... 23 AMD64/EM64T May Panic on xw9300 when the X Server Starts with the NVidia Accelerated Driver .... 23 DESCRIPTION...... 23 SCOPE...... 23 RESOLUTION...... 23 x86 SMP Kernel May Panic on xw9300 or xw4300 After the X Server Starts with the Accelerated NVidia Driver...... 24 DESCRIPTION...... 24 SCOPE...... 24 RESOLUTION...... 24 x86 or AMD64/EM64T Audio on xw4300 is Muted by Default...... 24 DESCRIPTION...... 24 SCOPE...... 24 RESOLUTION...... 24 x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices ...... 25 DESCRIPTION...... 25 RHEL 4 Update 1 WS ...... 25 x86 on xw9300 Will Panic when Booting the SMP Kernel...... 25 DESCRIPTION...... 25 SCOPE...... 25 RESOLUTION...... 25 AMD64/EM64T on xw9300 Will Panic if Dual Core Processors Are Used Along with the Kernel Option 'numa=on' ...... 25 DESCRIPTION...... 25 SCOPE...... 25 RESOLUTION...... 25 x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices ...... 25 DESCRIPTION...... 25 SCOPE...... 25 RESOLUTION...... 25 x86 or AMD64/EM64T on xw4300 LAN-on-Motherboard Driver is Not Fully Integrated...... 26 DESCRIPTION...... 26 SCOPE...... 26 RESOLUTION...... 26 x86 or AMD64/EM64T on xw4300 Does Not Contain the Intel HD Audio Driver...... 27 DESCRIPTION...... 27 SCOPE...... 27 RESOLUTION...... 27

x86 for AMD64/EM64T on xw4300 Does Not Contain the Updated LAN Driver Necessary to Enable Network/PXE Boot Installations...... 28 DESCRIPTION...... 28 SCOPE...... 28 RESOLUTION...... 28 x86 or AMD64/EM64T on xw4300 With Dual Core Only Reports 2 CPU's When Running the SMP Kernel28 DESCRIPTION...... 28 SCOPE...... 28 RESOLUTION...... 28 x86 or AMD64/EM64T ATI3100 Can Only be Configured Using the ATI Tool 'fglrxconfig' ...... 29 DESCRIPTION...... 29 SCOPE...... 29 RESOLUTION...... 29 x86 or AMD64/EM64T on xw4200, xw6200, xw8200, xw9300 Audio Defaults to Zero Volume ...... 29 DESCRIPTION...... 29 RESOLUTION...... 29 AMD64/EM64T on xw9300 Workstation May Panic During Install...... 29 DESCRIPTION...... 29 RESOLUTION...... 29 X86 on xw9300 Workstation May Hang or Fail to Find SCSI Drives During the Install ...... 29 DESCRIPTION...... 29 RESOLUTION...... 29 AMD64/EM64T May Panic When Booting the SMP Kernel ...... 30 DESCRIPTION...... 30 SCOPE...... 30 RESOLUTION...... 30 RHEL 4 WS...... 30 AMD64/EM64T on HP xw4200 Workstation, HP xw6200 Workstation or HP xw8200 Workstation Fails to Start X When Using an FX540 or FX1400 Accelerated Graphics Card ...... 30 DESCRIPTION...... 30 SCOPE...... 30 RESOLUTION...... 31 x86 or AMD64/EM64T on HP xw4200 Workstation, HP xw6200 Workstation, HP xw8200 Workstation Audio Defaults to Zero Volume ...... 31 DESCRIPTION...... 31 SCOPE...... 31 RESOLUTION...... 31 AMD64/EM64T on HP xw9300 Workstation with 4GB or More of Memory Will Panic When Booting the Install Kernel...... 32 DESCRIPTION...... 32 SCOPE...... 32 RESOLUTION...... 32 x86 or AMD64/EM64T on HP xw4200 Workstation, HP xw6200 Workstation, and HP xw8200 Workstation Fails to Install with USB Mouse and PS/2 Keyboard...... 32 DESCRIPTION...... 32 SCOPE...... 32 RESOLUTION...... 32 AMD64/EM64T on HP xw9300 Workstation May Report Total Memory Less than Expected with the x86_64 Kernel...... 33 DESCRIPTION...... 33 SCOPE...... 33 RESOLUTION...... 33 AMD64/EM64T on xw9300 Workstation May Panic During Install...... 33 DESCRIPTION...... 33 SCOPE...... 33 RESOLUTION...... 33

x86 or AMD64/EM64T on xw9300 Workstation is Currently Unable to Perform Network Installs or PXE Booting...... 34 DESCRIPTION...... 34 SCOPE...... 34 RESOLUTION...... 34 x86 on xw9300 Workstation May Hang or Fail to Find SCSI Drives During the Install ...... 34 DESCRIPTION...... 34 SCOPE...... 34 RESOLUTION...... 34 Links...... 35

Summary

This document contains a list of known issues on HP Linux Workstations when using Red Hat Enterprise Linux (RHEL) 3 Update 6 WS and Red Hat Enterprise Linux 4 Update 2 WS as of November 1, 2005. If additional issues are uncovered or updates are provided after this date, go to http://www.hp.com/go/workstationsupport. Select your HP Workstation. From the “I would like to” section, click troubleshoot a problem. From the “useful documents” section, click operating system. Locate the Linux section. If you are interested in other distributions that are certified on HP Workstations, the preceding Web site provides that information as well.

6 RHEL 3 Update 6 WS

X86 or AMD64/EM64T on xw4300 Does not Contain the Intel HD Audio Driver DESCRIPTION The HP xw4300 Workstation Intel HD audio driver is not integrated in the Red Hat Enterprise Linux (RHEL 3 WS Update 6 kernel. SCOPE HP xw4300 Workstation with RHEL3U6 WS. RESOLUTION 1. Go to http://www.hp.com/go/workstationsupport and select the product name "HP xw4300 Workstation", then click on the "download drivers and software" link. 2. Select the "Red Hat Enterprise Linux 3" - either x86 or AMD64/EM64T. 3. Under the Software table, download the "ALSA Sound Support for Red Hat Enterprise Linux 3" "Update 5 Rev B" and download the .tgz Softpaq. DO NOT follow the installation instructions as the included RPMS are for Update 5 and not Update 6. 4. Unpack the .tgz Softpaq and follow these instructions: a. ‘tar –xvzf ’. b. ‘cd’ into the directory created and go to the ‘build’ directory c. ‘tar –xvzf realtek-audiopack-3.3-9.tgz’ d. ‘cd Realtek-audiopack-3.3’

5. Modify the ‘install’ script by opening it with an editor and searching for “Library”. 6. Read the comments in that block of the script and comment/uncomment as appropriate for your 32-bit or 64-bit build. 7. Save the file and exit. 8. Run the install script as root ‘./install’ and follow the prompts. 9. At a command line run ‘alsamixer’ and using the ‘m’ key on your keyboard, unmute the ‘Headphone’, ‘CD’, ‘Aux-In’, and ‘iSpeaker’. 10. Raise those volumes with the up/down arrows to adjust system volumes. x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices DESCRIPTION Refer to same issue under RHEL3 Update 4 WS.

7 RHEL 3 Update 5 WS x86 or AMD64/EM64T on Dual Core HP xw4300 Workstation Only Reports 2 CPU's When Running the SMP Kernel DESCRIPTION These particular Dual Core processors from Intel® do not support Hyperthreading. Therefore, when running the SMP kernel with Dual Core processors, you will only see 2 CPUs. SCOPE HP xw4300 Workstation with a Dual Core Processor RESOLUTION None; see HP xw4300 Workstation Specification at http://www.hp.com/workstations/pws/xw4300/specs.html x86 or AMD64/EM64T on xw4300 LAN-on-Motherboard tg3 Driver is Not Fully Integrated DESCRIPTION The updated driver needed to support the BCM5752 LAN-on-Motherboard is not integrated in the Red Hat Enterprise Linux (RHEL) 3 WS Update 5 kernel, therefore it is recommended that tg3 v3.27RH or greater be used. If you see errors such as tg3: tg3_reset_hw timed out for eth0 or SIOCSIFLLAGS: No such device and any attempt to ping will result in "connect: Network is unreachable", then follow the steps under the Resolution section. Also, if you update your kernel via Red Hat Network prior to the availability of RHEL 3 WS Update 6, your LAN-on-Motherboard will no longer work. SCOPE HP xw4300 Workstation with RHEL3U5 WS RESOLUTION NOTE: This issue is resolved in RHEL3U6. If you are using RHEL3U5, then the following resolution still applies. If /var/log/messages already indicate that you are running tg3 v3.27RH, then you already have the correct driver installed, but if you are seeing either of the errors described previously, then you'll need to reconfigure the LAN and do a one-time power cycle to return the LAN to the correct state.

1. Configure your network with 'setup'. 2. Execute: 'shutdown -h 0'. 3. Remove the power cord for at least 15 seconds. 4. Replace the power cord and restart the machine. 5. As the system restarts, you should see "Bringing up eth0 [OK]".

8 The tg3 driver that is provided with the standard RHEL 3 WS Update 5 does not support the BCM5752 LAN-on-Motherboard for the HP xw4300 Workstation. There are 4 ways to enable the xw4300 BCM5752 LAN-on-Motherboard with RHEL 3 WS U5 with kernel 2.4.21-32. Select one of the following:

1. If the workstation was ordered with RHEL 3 WS Update5 preloaded, then support for this BCM5752 LAN-on-Motherboard has already been enabled. Verify that the RPM is installed using the command 'rpm -qa | grep tg3'. 2. As part of the HPIKL for RHEL 3 WS Update5, HP has provided a Red Hat Driver Disk that can be used at the time of install to load a tg3 driver that will enable network installs as well as enable networking after the install has completed. For instructions on how to install the tg3 driver from this CD, please refer to the documentation at http://www.hp.com/support/linux_user_manual. Select the chapter “Installing with the HP Installer Kit for Linux” and search for “Red Hat Driver Disk”. 3. As part of the HP Driver CD, which is also part of the HPIKL for RHEL 3 WS Update5, HP has provided tg3-2.4.21-32-1-0.i386.rpm, tg3-2.4.21-132-1-0.x86_64.rpm, and tg3-2.4.21-32-1- 0.src.rpm. Therefore, if you did not use the Red Hat Driver Disk during the install process, you can add support in your 2.4.21-32 kernel for the BCM5752 LAN-on-Motherboard by installing this RPM. To install it: Mount the HP Driver Cd under /mnt/cdrom cd /mnt/cdrom/HP/RPMS/{arch} rpm -ivh tg3-2.4.21-32-1-0.{arch}.rpm

Where {arch} is i386 if you are installing on RHEL 3 WS Update5 x86, and x86_64 if you are installing on RHEL 3 WS Update5 AMD64/EM64T. Once the rpm is installed, an additional step is required to reset the LAN. a. Configure your network with 'setup'. Execute: 'shutdown -h 0'. Remove the power cord for at least 15 seconds. Replace the power cord and restart the machine. As the system restarts, you should see “Bringing up eth0 [OK]”.

Go to http://www.hp.com/go/workstationsupport and select the product name “HP Workstation xw4300”, then click on the “download drivers and software” link. Download the “HP Installer Kit for Linux - Red Hat Driver Disk for Red Hat Enterprise” rev “Update5” and follow the instructions to install the RPM. NOTE: If you update/re-build your kernel such that you are no longer running the 2.4.21-32 kernel, you will find that your BCM5752 LAN-on-Motherboard is no longer functional. To resolve this, you will need to either go to Red Hat Network to get the RHEL 3 WS Update 6 kernel SRPM or get the source tar from the tg3-2.4.21-32-1-0.src.rpm and include these files in any kernel build that you plan to do.

9 The following is an example of the steps required to include the tg3-2.4.21-32-1-0 files for a kernel rebuild:

1. cp tg3-2.4.21-32-1-0.src.rpm /usr/src/redhat/SRPMS 2. cd /usr/src/redhat/SRPMS 3. rpm -ivh tg3-2.4.21-32-1-0.src.rpm 4. cd ../SOURCES 5. tar xvfz tg3-rhel3u5.tgz 6. Change directory to your kernel build directory that contains tg3- generally this is /usr/src/linux- {version}/kernel/drivers/net/ 7. cp /usr/src/redhat/SOURCES/tg3.c. 8. cp /usr/src/redhat/SOURCES/tg3.h. 9. cp /usr/src/redhat/SOURCES/tg3_compat.h . 10. Add the following to your pci_ids.h that exists in your kernel build tree 0x14e4 0x1600 "tg3" "BROADCOM Corporation|NetXtreme BMC5752 Gigabit Ethernet" 11. re-build the kernel x86 or AMD64/EM64T on xw4300 Does Not Contain the Updated LAN Driver Necessary to Enable Network/PXE Boot Installations DESCRIPTION The HP xw4300 Workstation LAN-on-Motherboard driver is not integrated in Red Hat Enterprise Linux (RHEL) 3 WS Update 5 kernel. Therefore, to enable PXE boot installation, a new initrd image has been provided which includes the updated tg3 driver (v3.27RH). SCOPE HP xw4300 Workstation with RHEL3U5 WS which attempt to do PXEboot installs RESOLUTION NOTE: This issue is resolved in RHEL3U6. If you are using RHEL3U5, then the following resolution still applies. From an alternate Internet connected computer, download the new PXE boot image from http://www.hp.com/go/workstationsupport and select the product name “hp xw4300 Workstation”.

1. Select “download drivers and software”. 2. Select “Red Hat Enterprise Linux 3 (AMD64/EM64T)” or “Red Hat Enterprise Linux 3 (x86)” 3. Under the Utility Tools section of the table, you will find: Network/PXE Boot Support for Broadcom 5752 4. Select “obtain software” to download xw4300_network_install.tgz 5. Unpack the files on the desired system with: tar xvfz xw4300_network_install.tgz The tar file contains: i386/isolinux/initrd.img i386/images/boot.iso i386/images/pxeboot/initrd.img x86_64/isolinux/initrd.img x86_64/images/boot.iso x86_64/images/pxeboot/initrd.img SRPMS/kernel-2.4.21-32.EL.src.rpm SRPMS/tg3-2.4.21-32-1-0.src.rpm

10 The initrd.img and the initrd.img within the boot.iso contain the needed LAN drivers to support the xw4300's Broadcom 5752/A1 LAN On Motherboard (LOM). On your PXEboot server, use the i386 versions of these files if you are PXEbooting RHEL3U5 x86 and use the x86_64 versions of these files if you are PXEbooting RHEL3U5 AMD64/EM64T. x86 or AMD64/EM64T on xw4300 Does Not Contain the Intel HD Audio Driver. DESCRIPTION The HP xw4300 Workstation Intel HD audio driver is not integrated in Red Hat Enterprise Linux (RHEL) 3 WS Update 5 kernel. SCOPE HP xw4300 Workstation with RHEL3U5 WS RESOLUTION Go to http://www.hp.com/go/workstationsupport and select the product name "HP xw4300 Workstation", then click on the "download drivers and software" link. Select the "Red Hat Enterprise Linux 3" - either x86 or AMD64/EM64T. Under the Software table, download the "ALSA Sound Support for Red Hat Enterprise Linux 3" rev "Update5 Rev B" and follow the instructions to install the RPM. Once you have followed the instructions and loaded the 3 RPMS, at a command line run ‘alsamixer’ and using the ‘m’ key on your keyboard, unmute the ‘Headphone’, ‘Aux-In’, and ‘iSpeaker’. Raise those volumes with the up/down arrows to adjust system volumes. x86 or AMD64/EM64T with FX3400, FX3450, or FX4500 Graphics Card May Fail to Start X DESCRIPTION The FX3400, FX3450, or FX4500 may fail to start the X Server and the /var/log/XFree86.0.log reports NoPowerConnectorCheck. SCOPE Any Workstation with a FX3400, FX3450, or FX4500 Graphics Card RESOLUTION Power down the system, attach the 6pin 12V power cable to end of the graphics card, and power the system back up. x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices DESCRIPTION Refer to same issue under RHEL3 Update 4 WS.

11 x86 or AMD64/EM64T with ATI3100 Fails to Save and Restore libGL.so.1 DESCRIPTION The /opt/hp/graphics/ati/configure and unconfigure scripts included in the fireglrx 8.12 drivers do not properly save and restore the libGL.so.1 file. SCOPE Affects RHEL3U5 systems installed with HP Installed Kit for Linux (HPIKL) where user is trying to remove ATI accelerated driver and go back to Vesa driver. RESOLUTION If the unconfigure script has not been run yet, there is still a copy of the original file that can be set aside and manually copied back into place.

1. cp /opt/hp/graphics/ati/libGL.so.1.2.prev /tmp 2. ./unconfigure 3. cp /tmp/libGL.so.1.2.prev /usr/X11R6/lib/libGL.so.1.2 Another alternative is to copy this file over from a system that is running the same version of the original vesa driver. NOTE: Verify that the /etc/X11/XF86Config-4 file refers to Driver “vesa” instead of “fglrx”. The unconfigure script deletes the XF86Config-4 file, so you might want to save a copy of it first. x86 or AMD64/EM64T with ATI3100 Can Only be Configured Using ATI Tool 'fglrxconfig' DESCRIPTION Using the X open source method of running “/usr/X11R6/bin/XFree86 –configure” fails during creation of the XF86Config-4 file SCOPE ATI3100 cards used with RHEL3 U5 [x86 or AMD64/EM64T] RESOLUTION Instead, use the ATI “fglrxconfig” tool to create an XF86Config-4 file or copy one of the HP template files from /opt/hp/graphics/ati/example_configs to /etc/X11. NOTE: Systems installed with the HP Installed Kit for Linux (HPIKL) will be automatically installed with a functional XF86Config-4 file, so only users who do their own advanced customization to the graphics settings will ever run into this problem.

12 RHEL 3 Update 4 WS

AMD64/EM64T Installation Fails on HP xw6200 Workstation or HP xw8200 Workstation with a SATA Drive and 4GB or More of Memory DESCRIPTION When attempting to install Red Hat Enterprise Linux (RHEL) 3 Update 3 or Update 4 WS Update 3 Gold (EM64T) on workstations listed in the SCOPE section of this document, the message “No drives found” is displayed. SCOPE This issue only applies to workstations when ALL of the following conditions are true: • HP xw6200 Workstation or HP xw8200 Workstation • RHEL 3 Update 3 or Update 4 WS EM64T • SATA drive • 4GB to 16GB of memory RESOLUTION NOTE: This issue has been resolved in RHEL3U5. If you are using RHEL3U3 or RHEL3U4, then the following resolution still applies. HP recommends performing one of the following workarounds to avoid the issue. Maintain the system’s current configuration with more than 4GB of memory.

1. Boot to Red Hat CD 1. 2. When you see the blue highlighted "F1: Boot," press the F1 key. The following prompt is displayed: boot: _. 3. At the boot prompt, enter linux mem=508M. 4. Proceed with the installation as usual. OR Reduce the amount of memory to 3GB or less prior to the install and replace it after the install is complete. AMD/EM64T on HP xw8200 Workstation and HP xw6200 Workstation Might Panic with 4GB of Memory and SATA and FX1400 or FX540 DESCRIPTION On HP xw6200 Workstation or HP xw8200 Workstation systems that have Red Hat Enterprise Linux 3 Update 3 or Update 4 WS AMD64/EM64T with 4–4.5GB of memory and a SATA drive, the system will panic when booting if the kernel is booted with the boot option swiotlb=16384.

13 SCOPE This issue applies to HP xw6200 Workstation systems when ALL of the following conditions are true. • Red Hat Enterprise Linux 3 Update 3 or Update 4 WS AMD64/EM64T • 4–4.5GB of memory • SATA hard drive • FX1400 or FX540 graphics card • kernel boot option swiotlb=16384 is used This affects HP xw8200 Workstation systems that meet all of the following conditions: • Red Hat Enterprise Linux 3 Update 3 or Update 4 WS AMD64/EM64T • 4–4.5GB of memory • SATA hard drive • FX1400 graphics card • kernel boot option swiotlb=16384 is used RESOLUTION NOTE: This issue has been resolved in RHEL3U5. If you are using RHEL3U3 or RHEL3U4, then the following resolution still applies. HP recommends increasing or reducing your memory so that you are above or below the 4-4.5GB boundary. This can be accomplished in a number of ways. • Modify your /etc/grub.conf and replace "swiotlb=16384" with "mem=4000m." This will force your kernel to behave as if it has only ~3.3G of memory. • If possible, remove memory to get to 3GB or lower. (The memory sticks need to be removed in pairs.) • If possible, add memory to get to 5GB or higher. (The memory sticks need to be added in pairs.)

AMD64/EM64T Preinstalled HP xw6200 Workstation and HP xw8200 Workstation Systems Need to Have Accelerated Graphics Configured DESCRIPTION On HP xw6200 Workstation and HP xw8200 Workstation systems that have been pre-installed in the factory with Red Hat Enterprise Linux 3 Update 4 WS AMD64/EM64T, the accelerated graphics driver fails to configure during the factory preload process. You can determine if your system needs to have the accelerated graphics driver configured by first determining if the unaccelerated driver is currently being used: # glxinfo | grep "direct rendering" If this returns direct rendering: No, you are running with an unaccelerated graphics driver and you will want to configure the accelerated driver. If this returns direct rendering: Yes, you are running with an accelerated graphics driver and no further actions are needed. SCOPE This affects all HP xw6200 Workstation and HP xw8200 Workstation systems that have been preinstalled in the factory with Red Hat Enterprise Linux 3 Update 4 WS AMD64/EM64T.

14 RESOLUTION NOTE: This issue has been resolved in the RHEL3U5 preload. If you are using RHEL3U3 or RHEL3U4 preload, then the following resolution still applies. HP recommends you configure the accelerated driver as follows as root:

1. Change to the needed directory: # cd /opt/hp/graphics/nvidia 2. Run the configure script: # ./configure 3. If you are running with 4GB of memory or greater, run the script to add the needed entry to your grub.conf: # perl nv_swiotlb.pl 4. At "Attempt to add /boot/grub/grub.conf entry (y/n):,” answer Y. 5. If you are running with 4-4.5GB of memory, you will need to make one additional change to work around a possible panic: 6. Increase or reduce your memory so that you are above or below the 4-4.5GB boundary. This can be accomplished by any one of the following: a. Modify your /etc/grub.conf and replace swiotlb=16384 with mem=4000m. This will force your kernel to behave as if it has only ~3.3G of memory. b. If possible, remove memory to get to 3GB or lower. (The memory sticks need to be removed in pairs). c. If possible, add memory to get to 5GB or higher. (The memory sticks need to be added in pairs). 7. Reboot you system: # reboot

15 x86 on HP xw9300 Workstation Does Not Install Accelerated Graphics DESCRIPTION Revision 6633 of NVIDIA’s proprietary accelerated graphics driver has problems initializing the X server properly. The problem is very apparent as the Graphical Desktop Manager (Gnome or KDE) cannot start properly, and the system appears to be hung with a black screen. SCOPE This problem affects all NVIDIA graphics cards (FX540, FX1400, FX3400, NVS280) on HP xw9300 Workstation systems with the x86 version of Red Hat Enterprise Linux 3, Update 4 installed. Furthermore, this problem is present with version 6633 of the NVIDIA proprietary driver. RESOLUTION NOTE: This issue has been resolved in RHEL3U5 when using a revision 7167 or greater of the NVIDIA proprietary accelerated graphics driver. If you are using RHEL3U4, then the following resolution still applies. 1. Change directory to /opt/hp/graphics/nvidia/driver 2. Execute ./NVIDIA-Linux-x86-1.0-6633-pkg1.run --no-network 3. Change directory to../example_configs 4. cp XF86Config-4.nvidiaStandard /etc/X11 5. Change directory to /etc/X11 6. mv XF86Config XF86Config.orig 7. ln -s XF86Config-4.nvidiaStandard XF86Config 8. After the preceding steps are completed, then you will need to reboot your system with the boot option "noapic". To do this, either: 9. Reboot the system. 10. When you see the blue highlighted "F1: Boot," press the F1 key. The boot prompt "boot: _" will be displayed. 11. At the boot prompt, enter: linux noapic

Modify your /etc/grub.conf file to add "noapic" to the end of the line, which starts with "kernel", such as: kernel /vmlinuz-2.4.21-27.EL root=LABEL=/ noacpi x86 on HP xw9300 Workstation Does Not Have A Functional Network Driver For LOM DESCRIPTION The binary kernel image installed from RHEL 3 Update 4 distributions for x86 does not contain the open source driver (forcedeth) needed for the NVIDIA nForce Professional 2200 chipset's built-in gigabit Ethernet controller. SCOPE This affects only the x86/i386/i686 version of RHEL 3 U4 running on any HP xw9300 Workstation configuration.

16 RESOLUTION NOTE: This issue is resolved in RHEL3U5. If you are using RHEL3U4, then the following resolution still applies. There are two reasonable alternatives to provide a functional network interface on the HP xw9300 Workstation if one is using the x86 version of RHEL 3. The first available solution is to use one of the HP supported NICs in a PCI slot. Both of the supported NICs (Broadcom 5751 PCIe & Broadcom 5782) work fine with the available open source drivers built into Update 4. The second solution is to install NVIDIA’s proprietary LAN driver for the nForce Professional 2200 chipset. This driver is created specifically for the 2200's LAN implementation and can be downloaded from the NVIDIA Web site at http://www.nvidia.com. To find the x86 Linux driver:

1. From the top of the page, click Download Drivers. 2. From the Start Here panel, click Platform/nForce Drivers. 3. Select the Unified Driver option in the middle panel. 4. Select the Linux option in the far right panel and select the GO! button. 5. Select the link associated with the Download Drivers option and download the driver package. 6. Once this driver package is loaded onto your HP xw9300 Workstation, execute the driver package directly. It is a shar-like executable, which contains both the audio and LAN drivers, and a wrapper application that will direct you to install the driver properly. 7. When the driver has completed installing, edit /etc/modules.conf and add the line alias eth0 nvnet to the bottom of the file. 8. Execute: insmod nvnet. 9. Set up your networking configuration through whatever means you choose.

AMD64/EM64T on HP xw9300 Workstation Will Not Ask to Set up Networking DESCRIPTION RHEL 3 Update 4 does not properly recognize the network device provided by the nForce Professional 2200 chipset, which is in the HP xw9300 Workstation. Because neither the install kernel/process nor Red Hat's "FirstBoot" program recognizes that a network device is present, they do not provide the interface to the user to allow for input of the machine's network parameters. SCOPE This affects all versions of RHEL 3 U4 [AMD64/EM64T] running on any HP xw9300 Workstation. RESOLUTION NOTE: This issue is resolved in RHEL3U5. If you are using RHEL3U4, then the following resolution still applies. RHEL 3 Update 4 [AMD64/EM64T] does contain a functional open source network driver for the nForce Professional 2200. Once the system is booted, the user can easily configure networking with one of the following methods:

• The Red Hat ‘setup’ script from a command line: i. From the shell command line, execute the command: modprobe forcedeth ii. Edit the file /etc/modules.conf and add the following line at the end of the file: alias eth0 forcedeth • The Red Hat graphical network configuration tool: i. Select the Red Hat symbol in the desktop control panel. ii. Select “System Settings” and then “Network.” iii. Select “New” and set the Device Type to “Ethernet connection.” iv. Set the Ethernet Card to “CK891 Ethernet Controller(eth0).” v. Edit the network setup as needed. vi. Select “DNS” tab and set the proper value for your network. vii. Select “Host” tab and set proper values for you network. viii. Select “Devices” tab and then “activate” button. • Manually edit each of the necessary network file in the /etc/hierarchy. x86 or AMD64/EM64T on HP xw9300 Workstation Does Not Install Audio Driver DESCRIPTION RHEL 3 Update 4 does not properly recognize the audio solution provided by the NVIDIA nForce Professional 2200 chipset in the HP xw9300 Workstation and will not load the proper driver. Audio, therefore, is not functional. SCOPE Audio will not function on any HP xw9300 Workstation configuration using Red Hat Enterprise Linux 3 Update 4 WS. RESOLUTION This issue has been resolved in RHEL3U5. If you are using RHEL3U4, then the following resolution still applies. The NVIDIA proprietary closed source audio driver which is available from NVIDIA’s website will enable audio on the xw9300. To obtain the NVIDIA proprietary closed source driver: 1. Go to NVIDIA’s Web site at http://www.nvidia.com. 2. Click the Download Drivers link on the banner at the top of that page. 3. Click the Linux and FreeBSD Drivers link. 4. Select the appropriate version of the nForce driver for the version of RHEL you are running. 5. Follow the steps provided by NVIDIA to download, install, and configure the driver package. NOTE: Version 0292 of the NVIDIA nForce Linux audio driver has a bug whereby audio will play, but you cannot control the volume setting for playback of .wav files. NVIDIA is aware of this defect. Hopefully the next version of this driver posted at the NVIDIA Web site will fix this issue.

18 x86 or AMD64/EM64T on HP xw9300 Workstation Does Not Fully Enable the Use of HP USB 2.0 Disk-On-Key Devices DESCRIPTION There is an infrequent situation where a 2.0 USB disk-on-key/jump drive will not be properly recognized by the operating system when plugged into an HP xw9300 Workstation. The error message indicates that the USB device is not a valid block device. SCOPE This problem has only been observed with HP-branded 2.0 USB Disk-on-Keys. All other USB devices tested with (1.1 and 2.0 devices) do not show this problem. RESOLUTION You can work around this problem by inserting the problem device in one of the other USB ports available on the HP xw9300 Workstation.

AMD64/EM64T on HP xw9300 Workstation Does Not Contain the Necessary LAN Drivers to Enable Network Install or PXE Booting DESCRIPTION RHEL 3 Update 4 does not properly recognize the network device provided by the nForce Professional 2200 chipset, which is in the HP xw9300 Workstation. Because the install kernel/process does not include this LAN driver, network installs and PXE booting will not work. SCOPE This affects all versions of RHEL 3 U4 running on any HP xw9300 Workstation. RESOLUTION NOTE: This issue has been resolved in RHEL3U5. If you are using RHEL3U4, then the following resolution still applies. 1. Go to http://www.hp.com/support/xw9300. 2. Click download drivers and software. 3. Click Red Hat Enterprise Linux 3 (AMD64/EM64T) 4. Under the Utility Tools section of the table, you will find Network/PXEboot install for nForce Professional 2200. Select obtain software to download xw9300_network_install.tgz. 5. Unpack the file: tar xvfz xw9300_network_install.tgz The file contains: isolinux/initrd.img images/boot.iso images/pxeboot/initrd.img SRPMS/kernel-2.4.21-27.EL.src.rpm

The initrd.img and the initrd.img within the boot.iso contain the needed LAN drivers to support the nForce Professional 2200 built-in-LAN.

19 AMD64/EM64T on HP xw9300 Workstation Will Panic if 8GB Installed on CPU#1 DESCRIPTION On the HP xw9300 Workstation, there are memory slots associated with each CPU. Because of the way AMD designs its Opteron processors, you can choose to install memory in both memory banks or only in one of the memory banks. With RHEL 3 Update 4, if you install 8GB of memory (using 2GB memory DIMMs) in CPU 1’s memory bank and no memory in CPU 0’s memory bank, the Red Hat set installation kernel will panic. Furthermore, if a system has RHEL 3 U4 installed with a functional memory configuration and then the user changes the configuration to have 8GB only on CPU 1, the installed kernel will panic when booting. SCOPE This problem is only seen on an HP xw9300 Workstation using RHEL 3 Update 4 for x86-64 under the specified conditions. RESOLUTION Divide the memory in an HP xw9300 Workstation between the CPUs equally. This is easily done in the HP xw9300 Workstation because memory must be loaded in pairs.

AMD64/EM64T on HP xw9300 Workstation with 4GB or More of Memory Will Panic When Booting the Install Kernel DESCRIPTION When installing RHEL 3 Update 4 [AMD64/EM64T] on an HP xw9300 Workstation with 4GB or more of memory, the install kernel will panic. SCOPE This affects an HP xw9300 Workstation with 4GB or more of memory. RESOLUTION NOTE: This issue is resolved in RHEL3U5. If you are using RHEL3U4, then the following resolution still applies. HP recommends that you boot the install kernel with the additional boot option “acpi=off” by following these steps:

1. Start the install as you normally would. The Red Hat Enterprise Linux install boot prompt “boot: “ is displayed. 2. At the prompt, type linux acpi=off 3. Continue with the install as usual.

AMD64/EM64T on xw9300 Total Memory May Be Less Than Expected with x86_64 Kernel DESCRIPTION The RHEL3 64-bit kernel that is installed on xw9300 Workstations is the x86_64 kernel. If the kernel reports less memory than expected (due to the kernel's need to allocate space for memory mapped I/O), you can enable Memory remapping to access the remapped memory. Your system will then report the full amount of memory installed.

20 With Memory Remapping disabled you may see nearly 1GB less of memory than expected due to the fact that the kernel reserves the ~3GB to 4GB region of memory for memory mapped IO. With a 64-bit OS, HP recommends that Memory remapping be enabled. SCOPE HP xw9300 Workstation with RHEL3 64-bit OS RESOLUTION To enable Memory Remapping in the BIOS:

1. Reboot the workstation. 2. When you see the blue highlighted “F1: Boot” press F10 for Computer Setup Utility. 3. Select your language. 4. Use the Arrow keys to move across to Advanced. 5. Use the Arrow keys to move down to Chipset/Memory. 6. Use the Arrow keys to move down to Memory Remapping. 7. Use the Right Arrow key to set the entry to “Enable”. 8. Press F10 to Accept, Press F10 again followed by the Enter key and press F10 one last time to save the changes. 9. Boot as usual. x86 on xw9300 Total Memory May Be Less Than Expected with the athlon Kernel DESCRIPTION The RHEL3 32-bit kernel that is installed on HP xw9300 Workstations is the UP and SMP athlon kernels. These kernels are intended for systems that have up to 4GB of memory installed. To determine if you are running the athlon kernel, you first need to determine what kernel RPMs you have installed: 'rpm -q --qf "%{N}.%{V}-%{R}.%{ARCH}\n" kernel' 'rpm -q --qf "%{N}.%{V}-%{R}.%{ARCH}\n" kernel-smp' 'rpm -q --qf "%{N}.%{V}-%{R}.%{ARCH}\n" kernel-hugemem'

This will list all the kernel packages that may be installed on your system. From that list you can see which RPM packages are for i686 and athlon. You will then need to do 'uname -r' and match the currently running kernel version with the RPM package to determine if you are running the kernel*.athlon.rpm kernel.

If you have more than 4GB of memory installed, you may want to install the i686 hugemem kernel to access memory above 4GB. If you have 4GB or more of memory installed and are seeing less memory than expected (due to the kernel's need to allocate space for memory mapped I/O), you can enable Memory remapping and also use the hugemem kernel to access the remapped memory. Your system will then report the full amount of memory installed. SCOPE HP xw9300 Workstation with RHEL3 32-bit OS

21 RESOLUTION To install the hugemem kernel:

1. Mount CD2 from the RHEL3U5 i386 install media under /mnt/cdrom. 2. cd /mnt/cdrom/RedHat/RPMS 3. rpm -ivh kernel-hugemem-2.4.21-32.EL.i686.rpm 4. umount /mnt/cdrom 5. Reboot. 6. Select the hugemen kernel when the system restarts.

To enable Memory Remapping in the BIOS:

1. Reboot the workstation. 2. When you see the blue highlighted "F1: Boot" press F10 for Computer Setup Utility. 3. Select your language. 4. Use the Arrow keys to move across to Advanced. 5. Use the Arrow keys to move down to Chipset/Memory. 6. Use the Arrow keys to move down to Memory Remapping. 7. Use the -> Arrow key to set the entry to Enable. 8. Press F10 to Accept, Press F10 again followed by the Enter key and press F10 one last time to save the changes. 9. Boot as usual. With the RHEL3 32-bit OS, if you are running a kernel which does not have PAE enabled (such as the athlon kernel) you will always want to Disable Memory Remapping otherwise your system will only report up to 2GB of memory. x86 or AMD64/EM64T on the HP xw4200 Workstation Only Reports Approximately 3GB when 4GB Of Memory Is Present DESCRIPTION The HP xw4200 Workstation which contains the Intel 925x chipset does not support greater than 4GB of DRAM and thus does not support memory remapping above 4GB. Therefore, if you have 4GB of physical memory installed on an xw4200, you will see approximately 3GB due to the fact that the kernel reserves the approximate 3GB to 4GB region for memory mapped for IO. SCOPE HP xw4200 Workstation RESOLUTION None; see xw4200 Specification at http://www.hp.com/workstations/pws/xw4200/specs.html.

22 RHEL 4 Update 2 WS

AMD64/EM64T May Panic on xw9300 when the X Server Starts with the NVidia Accelerated Driver DESCRIPTION If your system meets all of the criteria listed in the "scope" section below, your system will crash the kernel when you start the Xserver. SCOPE HP xw9300 Workstation with: • RHEL 4/Update 2, AMD/EM64T version • 4 GB of memory, or greater • Nvidia accelerated graphics driver installed & configured • BIOS option "memory remapping" enabled RESOLUTION HP recommends performing one the following workaround to avoid the issue. Modify the BIOS to disable Memory Remapping: 1. Reboot the system. 2. When you see the blue highlighted "F1: Boot" press the F10 key for Setup. 3. Select your language. 4. Use your Arrow keys to move across to "Advanced." 5. Use your Arrow keys to move down to "Chipset/Memory." 6. Use your Arrow keys to move down to "Memory Remapping." 7. Use your -> Arrow key to set the entry to "Disable." 8. Press F10 to Accept. Press F10 again followed by the Enter key and press F10 one last time to save the changes. 9. Proceed with the install as usual.

See Red Hat's Knowledge Base for additional information: http://kbase.redhat.com/faq/FAQ_85_6436.shtm

Red Hat expect to have this issue resolved in an errata kernel by October 26, 2005. Please refer to the above Red Hat Knowledge base as well as this advisory for updated information.

23 x86 SMP Kernel May Panic on xw9300 or xw4300 After the X Server Starts with the Accelerated NVidia Driver. DESCRIPTION If your system meets all the criteria listed in the "scope" section below, your system may hang and the kernel may panic in __change_page_attr when you start the X server or shortly thereafter. SCOPE HP xw4300 or xw9300 Workstation system with: • RHEL4U2 WS x86 SMP kernel (2.6.9-22.ELsmp) • NVidia accelerated graphics driver installed & configured

RESOLUTION HP recommends that one of the following be selected: • RHEL4 U2 not be used until Red Hat has provided a new errata kernel which resolves this issue, or • Run the accelerated Nvidia driver only with the UP kernel, or • Unconfigured the accelerated Nvidia driver and thus use the vesa driver : 1. Boot the UP kernel. 2. As root, run the following to unconfigure the accelerated Nvidia driver.

# /opt/hp/graphics/nvidia/unconfigure

3. Reboot to the SMP kernel.

See Red Hat's Knowledge Base for additional information: http://kbase.redhat.com/faq/FAQ_85_6976.shtm Red Hat expect to have this issue resolved in an errata kernel by October 26, 2005. Please refer to the above Red Hat Knowledge base as well as this advisory for updated information. x86 or AMD64/EM64T Audio on xw4300 is Muted by Default DESCRIPTION Red Hat Enterprise Linux 4 Update 2 [x86 and AMD64/EM64T] audio on xw4300 cannot be heard at firstboot because the internal speakers are muted by default. This is true even after the system is up and running. Note that the headphones via the front jack or back jack are unmuted, so no changes are needed to hear audio from your headphones. SCOPE HP xw4300 Workstation system running RHEL4U2. RESOLUTION In order to hear audio from the internal speakers on the xw4300, you must 1. From the command line, start 'alsamixer' and unmute the Mono slider. 2. From the panel, select Red Hat -> Sound & Video -> Volume Control and adjust the Mono slide upwards.

24 x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices DESCRIPTION Refer to same issue under RHEL4 Update1 WS.

RHEL 4 Update 1 WS x86 on xw9300 Will Panic when Booting the SMP Kernel DESCRIPTION The HP xw9300 Workstation will panic when booting the i686 SMP kernel in Red Hat Enterprise Linux (RHEL) 4 WS Update 1. SCOPE HP xw9300 Workstation system with RHEL4U1 WS RESOLUTION This issue is resolved in RHEL4U2.

AMD64/EM64T on xw9300 Will Panic if Dual Core Processors Are Used Along with the Kernel Option 'numa=on' DESCRIPTION The HP xw9300 Workstation with Dual Core processors will panic in Red Hat Enterprise Linux (RHEL) 4 WS Update 1 if 'numa=on'. By default, when the user sets the kernel option 'acpi=off', the system will also turn off numa. HP recommends that the xw9300 use the 'acpi=off' kernel option in RHEL4U1. SCOPE HP xw9300 Workstation with RHEL4U1 WS RESOLUTION This issue is resolved in RHEL4U2. x86 or AMD64/EM64T on the xw9300 Does Not Fully Enable the Use of All HP USB 2.0 Disk-on-Key Devices DESCRIPTION There is frequent situation where a 2.0 USB disk-on-key/jump drive will not properly be recognized by the operating system when connected into an HP xw9300 Workstation. The messages in /var/log/messages indicate that a timeout occurred. SCOPE This issue has only been observed with HP-branded 256K and 128K 2.0 USB disk-on-keys. All other USB devices tested (with 1.1 and 2.0 devices) did not experience this issue. RESOLUTION A resolution may exist in a future release of RHEL4.

25 x86 or AMD64/EM64T on xw4300 LAN-on-Motherboard Driver is Not Fully Integrated DESCRIPTION The HP xw4300 Workstation LAN-on-Motherboard driver is not integrated in Red Hat Enterprise Linux (RHEL) 4 WS Update 1 kernel, therefore a Driver Disk is required during installation. If you see any of the following: • Network install panics • Network install is unable to mount the directory from the server • Install hangs during "Performing post install configuration" • Installed version of tg3 is not 3.27-rh (or greater) Then follow the steps under the resolution section. NOTE: If you update your kernel via Red Hat Network prior to the availability of RHEL 4 WS Update 2, your LAN-on-Motherboard will no longer work. SCOPE HP xw4300 Workstation with RHEL4U1 WS RESOLUTION NOTE: This issue is resolved in RHEL4U2. If you are using RHEL4U1, then the following resolutions still applies. The tg3 driver that is provided with the standard RHEL 4 WS Update 1 does not support the BCM5752 LAN-on-Motherboard for the xw4300. There are 4 ways to enable the xw4300 BCM5752 LAN-on-Motherboard with RHEL 4 WS U1 with kernel 2.6.9-11. Select one of the following:

1. If the workstation was ordered with RHEL 4 WS Update1 preloaded, then support for this BCM5752 LAN-on-Motherboard has already been enabled. Verify that the tg3 RPM has been installed by running 'rpm -qa | grep tg3' 2. If you have the HP Installer Kit for Linux for RHEL 4 WS Update1then HP has provided a Red Hat Driver Disk that can be used at the time of install to load a tg3 driver that will enable network installs as well as enable networking after the install has completed. Please use this Driver Disk when doing your installs as it will resolve the first three errors listed in the Description. For instructions on how to install the tg3 driver from the Driver Disk, refer to the documentation at http://www.hp.com/support/linux_user_manual. Select “Installing with the HP Installer Kit for Linux” and search for “Red Hat Driver Disk”. 3. If you have the HP Installer Kit for Linux for RHEL 4 WS Update1 then HP has provided a HP Driver CD which contains tg3 RPMS (tg3-2.6.9-11-1-0.i386.rpm, tg3-2.6.9-11-1-0.x86_64.rpm, tg3- 2.6.9-11-1-0.src.rpm) which can be loaded onto an already installed system. Therefore, if you did not use the Red Hat Driver Disk during the install process, you can add support in your 2.6.9- 11 kernel for the BCM5752 LAN-on-Motherboard by installing the tg3 RPM. To do this: a. Mount the HP Driver CD under /mnt/cdrom b. cd /mnt/cdrom/HP/RPMS/{arch} c. rpm -ivh tg3-2.6.9-11-1-0.{arch}.rpm

where {arch} is i386 if you are installing on RHEL 4 WS Update1 x86, and x86_64 if you are installing on RHEL 4 WS Update1 EM64T.

26 d. After the rpm is installed, configure your LAN and reboot your system.

4. If you do not have the HP Installer Kit for Linux: Go to http://www.hp.com/go/workstationsupport. a. Select the product name HP Workstation xw4300. b. Click on the download drivers and software link. c. Select the operating system. d. Download the “HP Installer Kit for Linux - Red Hat Driver Disk for Red Hat Enterprise” rev “Update1” and follow the instructions to install the RPM onto a running system or to use the Red Hat Driver Disk during the install process.

NOTE: If you update/re-build your kernel such that you are no longer running the 2.6.9-11 kernel, you will find that your BCM5752 LAN-on-Motherboard is no longer functional. To resolve this, you will need to either go to Red Hat Network to get the RHEL 4 WS Update 2 kernel SRPM or get the source tar from the tg3-2.6.9-11-1-0.src.rpm and include these files in any kernel build that you plan to do. The following is an example of the steps required to include the tg3-2.6.9-11-1-0 files for a kernel rebuild:

1. cp tg3-2.6.9-11-1-0.src.rpm /usr/src/redhat/SRPMS 2. cd /usr/src/redhat/SRPMS 3. rpm -ivh tg3-2.6.9-11-1-0.src.rpm 4. cd ../SOURCES 5. tar xvfz tg3-rhel4u1.tgz 6. Change directory to your kernel build directory that contains tg3- generally this is /usr/src/linux- {version}/kernel/drivers/net/ 7. cp /usr/src/redhat/SOURCES/tg3.c . 8. cp /usr/src/redhat/SOURCES/tg3.h . 9. cp /usr/src/redhat/SOURCES/tg3_compat.h . 10. Add the following to your pci_ids.h that exists in your kernel build tree: 0x14e4 0x1600 “tg3” “BROADCOM Corporation|NetXtreme BCM5752 Gigabit Ethernet” 11. Re-build the kernel. x86 or AMD64/EM64T on xw4300 Does Not Contain the Intel HD Audio Driver DESCRIPTION The HP xw4300 Workstation Intel HD audio driver is not fully integrated in Red Hat Enterprise Linux (RHEL) 4 WS Update 1 kernel. SCOPE HP xw4300 Workstation with RHEL4U1 WS RESOLUTION This issue is resolved in RHEL4U2.

27 x86 for AMD64/EM64T on xw4300 Does Not Contain the Updated LAN Driver Necessary to Enable Network/PXE Boot Installations DESCRIPTION The HP xw4300 Workstation LAN-on-Motherboard driver is not integrated in Red Hat Enterprise Linux (RHEL) 4 WS Update 1 kernel. Therefore, to enable PXE boot installation, a new initrd image has been provided which includes the updated tg3 driver (v3.27-rh). SCOPE HP xw4300 Workstation with RHEL4U1 WS which attempt to do PXEboot installs RESOLUTION NOTE: This issue is resolved in RHEL4U2. If you are using RHEL4U1, then the following resolution still applies. From an alternate Internet connected computer:

1. Download the new PXE boot image from http://www.hp.com/go/workstationsupport and select the product name HP xw4300 Workstation. 2. Select download drivers and software. 3. Select “Red Hat Enterprise Linux 4 (AMD64/EM64T)” or “Red Hat Enterprise Linux 4 (x86)”. 4. Under the Utility Tools section of the table, you will find Network/PXE Boot Support for Broadcom 5752. Select obtain software to download xw4300_network_install.tgz 5. Unpack the files on the desired system with: tar xvfz xw4300_network_install.tgz The tar file contains: • i386/isolinux/initrd.img • i386/images/boot.iso • i386/images/pxeboot/initrd.img • x86_64/isolinux/initrd.img • x86_64/images/boot.iso • x86_64/images/pxeboot/initrd.img • SRPMS/kernel-2.6.9-11.EL.src.rpm • SRPMS/tg3-2.6.9-11-1-0.src.rpm The initrd.img and the initrd.img within the boot.iso contain the needed LAN drivers to support the xw4300's Broadcom 5752/A1 LAN On Motherboard. On your PXEboot server, use the i386 versions of these files if you are PXEbooting RHEL4U1 x86 and use the x86_64 versions of these files if you are PXEbooting RHEL4U1 AMD64/EM64T.

x86 or AMD64/EM64T on xw4300 With Dual Core Only Reports 2 CPU's When Running the SMP Kernel DESCRIPTION These particular Dual Core processors from Intel do not support Hyperthreading. Therefore, when running the SMP kernel with Dual Core processors, you will only see 2 CPUs. SCOPE HP xw4300 Workstation with a Dual Core Processor RESOLUTION None

28 x86 or AMD64/EM64T ATI3100 Can Only be Configured Using the ATI Tool 'fglrxconfig' DESCRIPTION Using the X open source method of running '/usr/X11R6/bin/Xorg -configure' fails during creation of the XF86Config-4 file. SCOPE ATI3100 cards used with RHEL4 U1 [x86 or AMD64/EM64T] RESOLUTION Instead, use the ATI 'fglrxconfig' tool to create an XF86Config-4 file or copy one of the HP template files from /opt/hp/graphics/ati/example_configs to /etc/X11. Note that systems installed with the HP Installed Kit for Linux (HPIKL) will be automatically installed with a functional XF86Config-4 file, so only users who do their own advanced customization to the graphics settings will experience this issue. x86 or AMD64/EM64T on xw4200, xw6200, xw8200, xw9300 Audio Defaults to Zero Volume DESCRIPTION Refer to same issue under RHEL4 WS. RESOLUTION This issue is resolved in RHEL4U2. AMD64/EM64T on xw9300 Workstation May Panic During Install DESCRIPTION Refer to same issue under RHEL4 WS. RESOLUTION This issue is resolved in RHEL4U2.

X86 on xw9300 Workstation May Hang or Fail to Find SCSI Drives During the Install DESCRIPTION Refer to same issue under RHEL4 WS. RESOLUTION This issue is resolved in RHEL4U2.

29 AMD64/EM64T May Panic When Booting the SMP Kernel DESCRIPTION The HP workstation xw9300 may panic when booting the x86_64 SMP kernel in Red Hat Enterprise Linux (RHEL) 4 WS Update 1. SCOPE HP xw9300 Workstation with RHEL WS 4 Update 1. • Two processors (single or dual core) • 2GB of memory per processor for a total of 4 GB of memory RESOLUTION NOTE: This issue is resolved in RHEL4U2. If you are using RHEL4U1, then the following resolution still applies. To avoid the issue, HP recommends disabling Memory Remapping by performing the following steps: 1. Reboot the workstation. 2. When you see the blue highlighted “F1: Boot” message, press F10 for Computer Setup Utility. 3. Select your language. 4. Use the Arrow keys to move across to Advanced. 5. Use the Arrow keys to move down to Chipset/Memory. 6. Use the Arrow keys to move down to Memory Remapping. 7. Use the Right Arrow key to set the entry to “Disable”. 8. Press F10 to Accept, Press F10 again followed by the Enter key and press F10 one last time to save the changes. 9. Proceed with the install as usual. A resolution to allow for Memory Remapping to be enabled is expected in RHEL4U2.

RHEL 4 WS

AMD64/EM64T on HP xw4200 Workstation, HP xw6200 Workstation or HP xw8200 Workstation Fails to Start X When Using an FX540 or FX1400 Accelerated Graphics Card DESCRIPTION RHEL 4 fails to start the X server when an FX1400 or FX540 is installed on an HP xw4200 Workstation, HP xw6200 Workstation, or HP xw8200 Workstation. You will see a blue/grey screen without a cursor, and the system will be in a hung state. This occurs with the RHEL4 vesa driver as well as with the currently available NVIDIA accelerated driver. SCOPE All HP xw4200 Workstation, HP xw6200 Workstation, HP xw8200 Workstation with FX1400 or FX540, and RHEL 4 [AMD64/EM64T] installed.

30 RESOLUTION NOTE: This issue is resolved in RHEL4U1. If you are using RHEL4, then the following resolution still applies. Use the latest NVIDIA proprietary closed source graphics driver available from NVIDIA’s Web site at http://www.nvidia.com. To obtain the NVIDIA proprietary closed source driver:

1. Go to NVIDIA’s Web site at http://www.nvidia.com. 2. Click the Download Drivers link on the banner at the top of that page. 3. Click the Linux and FreeBSD Drivers link. 4. Select the appropriate version of the graphics driver for the version of RHEL you are running. 5. Follow the steps provided by NVIDIA to download, install, and configure the driver package. NOTE: Version 6629 of the Nvidia Linux graphics driver does not resolve this issue. Hopefully the next version of this driver posted at the NVIDIA Web site will fix this issue. x86 or AMD64/EM64T on HP xw4200 Workstation, HP xw6200 Workstation, HP xw8200 Workstation Audio Defaults to Zero Volume DESCRIPTION The default volume setting on audio for RHEL 4 is zero. After installing a system, the 'firstboot' GUI will come up (part of firstboot setup includes the sound card). When you "Play test sound,” no sound is heard. This is due to the fact that in RHEL4, ICH5 and ICH6 volume is set to zero for headset and mono; both are also set to muted. SCOPE Default audio volume will be zero on all HP xw4200 Workstation, HP xw6200 Workstation, and HP x8200 Workstation systems using Red Hat Enterprise Linux 4 WS. RESOLUTION NOTE: This issue is resolved in RHEL4U2. If you are using RHEL4 or RHEL4U1, then the following resolution still applies. After the system has booted up, you can easily adjust the volume as follows:

1. From your desktop, click Red Hat and highlight Sound & Video, and click Volume Control.

2. Unmute the Master control and adjust the corresponding slider bars. Then unmute PCM control and again adjust the slider bars. Now you should be able to successfully play .wav and hear it through your headset. If you wish to hear it through your internal speaker, unmute Master Mono control.

31 AMD64/EM64T on HP xw9300 Workstation with 4GB or More of Memory Will Panic When Booting the Install Kernel DESCRIPTION When installing RHEL 4 [AMD64/EM64T] on an HP xw9300 Workstation with 4GB or more of memory, the install kernel will panic. SCOPE This affects an HP xw9300 Workstation with 4GB or more of memory. RESOLUTION NOTE: This issue is resolved in RHEL4U2. If you are using RHEL4 or RHEL4U1, then the following resolution still applies. HP recommends performing the following workaround to avoid the issue. Modify the BIOS to disable memory remapping:

1. Reboot the system. 2. When you see "F1: Boot," press the F10 key for Setup. 3. Select your language. 4. Use your arrow keys to select Advanced. 5. Use your arrow keys to select Chipset/Memory. 6. Use your arrow keys to select Memory Remapping. 7. Use your arrow key to set the entry to Disable. 8. Press F10 to accept. Press F10 again followed by the Enter key and press F10 one last time to save the changes 9. Proceed with the install as usual. x86 or AMD64/EM64T on HP xw4200 Workstation, HP xw6200 Workstation, and HP xw8200 Workstation Fails to Install with USB Mouse and PS/2 Keyboard. DESCRIPTION When installing RHEL 4 with a USB Mouse and PS/2 Keyboard, the mouse will not work during the install. After the install, it will work as expected. SCOPE All HP xw4200 Workstation, HP xw6200 Workstation, HP xw8200 Workstation systems that have a USB mouse and PS/2 keyboard and are attempting to install Red Hat Enterprise Linux 4 WS. RESOLUTION HP recommends performing one of the following workarounds to avoid the issue. Maintain the system's current configuration

1. Boot to Red Hat CD 1. 2. When you see the blue highlighted "F1: Boot," press the F1 key. The following prompt is displayed: boot: _. 3. At the boot prompt, enter linux acpi=off. 4. Proceed with the installation as usual. OR

32 Modify your configuration so that you are using both USB Mouse and Keyboard or PS/2 Mouse and Keyboard. AMD64/EM64T on HP xw9300 Workstation May Report Total Memory Less than Expected with the x86_64 Kernel

DESCRIPTION The RHEL4 64-bit kernel that is installed on xw9300 Workstations is the x86_64 kernel. If the kernel reports less memory than expected, then you may want to enable Memory Remapping in the BIOS. With Memory Remapping disabled you will see ~0.3-0.8G less than expected due to the kernels need to allocate space for Memory Mapped IO. With Memory Remapping disabled you may see nearly 1GB less of memory than expected due to the fact that the kernel reserves the ~3GB to 4GB region of memory for memory mapped IO. With a 64-bit OS, HP recommends that Memory remapping be enabled. SCOPE HP workstation xw9300 system with RHEL4 64-bit OS RESOLUTION To enable Memory Remapping in the BIOS:

AMD64/EM64T on xw9300 Workstation May Panic During Install DESCRIPTION When installing RHEL 4 [AMD64/EM64T] on the xw9300 Workstation, you may see a panic indicating "PCI-DMA: high address but no IOMMU" or a panic on the console which includes acpi_ functions. SCOPE Installing RHEL 4 AMD64/EM64T on HP xw9300 Workstation RESOLUTION NOTE: This issue is resolved in RHEL4U2. If you are using RHEL4 or RHEL4U1, then the following resolution still applies. HP Recommends that you boot your install kernel with the additional boot option "acpi=off" using the following steps:

1. Start the install as you usually would. 2. The RHEL install boot prompt "boot:_" is displayed.

33 3. At the prompt, type linux acpi=off. 4. Continue with the install as usual. x86 or AMD64/EM64T on xw9300 Workstation is Currently Unable to Perform Network Installs or PXE Booting DESCRIPTION RHEL 4 does not properly recognize the network device provided by the nForce Professional 2200 chipset which is in the HP xw9300 Workstation. SCOPE Network Installing or PXE Booting RHEL 4 x86 or AMD64/EM64T on HP xw9300 Workstation RESOLUTION NOTE: This issue is resolved in RHEL4U1. If you are using RHEL4, then the following resolution still applies. Because the install kernel/process in all current versions of RHEL 4 cannot recognize this LAN device, network installs and Preboot Execution Environment (PXE) booting will not work. Attempting to create an initrd.img with the nForce Professional 2200 LAN driver will not resolve this issue as the problem is within the install process. x86 on xw9300 Workstation May Hang or Fail to Find SCSI Drives During the Install DESCRIPTION RHEL 4 x86 on xw9300 Workstation, during the install you may see a hang or a message indicating that no hard drives can be found. SCOPE Installing RHEL 4 x86 on HP xw9300 Workstation with one or more SCSI drives. RESOLUTION NOTE: This issue is resolved inRHEL4U2. If you are using RHEL4 or RHEL4U1, then the following resolution still applies. HP recommends that you boot the install kernel with the additional boot option "acpi=off":

1. Start the install as you usually would. 2. The Red Hat Enterprise Linux install boot prompt "boot:_" is displayed. 3. At the prompt, type linux acpi=off. 4. Continue with the install as usual.

34 Links

35 Setting Up Large Memory Configurations

Summary ...... 2 Maximum Memory Allowed ...... 2 HPIKL/Factory Preinstalled Systems ...... 2 x86 (32-bit) Red Hat Legacy Information ...... 2 Bigmem Kernel ...... 2 Bigmem and UP systems ...... 3 Performance Implications ...... 3 Large Memory and MTRRs ...... 4 Conclusion...... 4 Links...... 5

Summary

Various HP Linux Workstations can support large memory configurations (greater than or equal to 4GB). To use large memory configurations, an SMP, hugemem, or bigmem kernel must be installed and configured. Even though a system may have more than 4GB of memory, 3GB is the maximum amount of memory that can be used by a single process for HP Workstations running the uni- processor kernel. Maximum Memory Allowed

The maximum amount of memory that can be physically supported on HP xw Workstations: 1 CPU* 2 CPU xw4100 4GB 4GB xw4200 4GB 4GB xw4300 4GB 8GB xw6000 4GB 8GB xw6200 4GB 8GB xw8000 4GB 12GB xw8200 4GB 16GB xw9300 4GB 16GB *If there is only one CPU but Hyper-Threading Technology is enabled, the maximum amount of memory supported equals the value in the 2 CPU column. Although you can physically install 4GB memory, only 3 to 3.5GB will show up as addressable with a uni-processor kernel. The maximum amount of memory for each workstation is limited by the number of memory slots on the system board and the maximum size of the supported memory sticks. The maximum amount of memory recommended for each Linux version varies depending on the kernel that it includes. See the current Linux Hardware Support Matrix (http://hp.com/support/linux_hardware_matrix) to find out the maximum memory currently verified for your configuration. HPIKL/Factory Preinstalled Systems

If your Linux system has 4GB or more of memory and the Red® Hat Linux OS was either preinstalled at the factory or installed using the HP Installer Kit for Linux, the correct kernel for supporting the large amount of memory should be automatically installed and configured. x86 (32-bit) Red Hat Legacy Information

Bigmem Kernel Starting with Red Hat Enterprise Linux WS 3, the SMP kernel is sufficient for the maximum amount of memory supported in HP Workstations. The kernel for larger memory configurations (now called kernel-hugemem instead of kernel-bigmem) is only needed for systems that support >16GB. For 4GB configurations, using the hugemem kernel allows you to access all 4GB as long as the BIOS “Enable Memory Remapping” option is enabled.

2 In order for earlier Linux operating systems to use more than 3.5GB of physical memory, a special kernel called the bigmem kernel must be used. For example, for kernel 2.4.18-26, the rpm package that provides that kernel for Red Hat 8.0 is kernel-bigmem-2.4.18-26.8.x.i686.rpm. If more than 3.5GB of memory is installed and a bigmem kernel is not used, the system can only use 3.5GB of the memory. The bigmem kernel rpm installs like most Red Hat Linux rpms: rpm –i kernel-bigmem-2.4.18-26.8.x.i686.rpm You need to reinstall accelerated HP graphics drivers from the HP Linux Installer Kit CDs, or the latest driver from http://www.hp.com/go/workstationsupport. In order for the accelerated graphics driver to work correctly, you must install the source for the particular version of the kernel you installed. Install the kernel source before you attempt to reinstall the graphics driver. The kernel source should be available from wherever you got the bigmem kernel rpm. To reinstall the graphics driver:

1. Identify the accelerated driver that was installed on the UP kernel. rpm –qa |grep nv rpm –qa |grep firegl 2. Remove the driver that was identified. rpm –e 3. Install the new driver. rpm –i .rpm 4. Run the configure script. cd /usr/hp/graphics/ for Legacy Red Hat versions or, cd /opt/hp/graphics/ for Red Hat Enterprise Linux ./configure You might also need to rebuild and/or reinstall any other loadable kernel modules on your system because a different module is needed for each different Linux kernel. Bigmem and UP systems The bigmem kernel as released by Red Hat is an SMP (Symetric Multi-Processing) kernel, which means that it can support multiple CPUs. The bigmem kernel has only been tested by HP on dual CPU systems and on single CPU systems with Hyper-Threading Technology enabled, plus 4GB or more of memory. Thus, using the bigmem kernel on systems with one virtual CPU or less than 4GB of memory is not supported. Performance Implications When using the bigmem kernel, memory references inside the kernel require one more level of indirection, so general system performance might suffer slightly compared to using the SMP or UP kernels. For user processes using large amounts of memory, the additional installed memory can prevent swapping to the hard drive, which should more than offset any memory reference penalty incurred by the bigmem kernel. On x86 (32-bit) systems, the Linux kernel makes available only 3GB of address space available for each user process. Even though a single process can only use 3GB of memory, installing 4GB or more of memory and running the bigmem kernel can still provide a performance advantage when running multiple processes requiring large amounts of memory. It should be noted that the maximum amount of memory that you can malloc in one chunk is 2GB, due to fragmentation of the malloc pool across a process address space.

3 Large Memory and MTRRs In some situations, adding additional memory to a system can cause AGP graphics drivers to fail to operate. In this case, increasing the AGP aperture size may allow the configuration to operate. On Intel Pentium family processors memory access is controlled using special dedicated registers in the processor called Memory Type Range Registers (MTRR). For system RAM to be available for processor use, it must be configured using these registers. A configuration requirement of these registers is the defined memory size must be a power of two. Maximizing configured memory results in some system memory sizes using almost all of the MTRRs available in the processor. Some Linux graphics drivers require exclusive use of two MTRRs, which might not be available in these circumstances. If an error occurs when the graphics driver loads, the system memory configuration might not have enough free MTRRs. This can be checked from the console by viewing the /proc/mtrr file. Registers six and seven are normally unlisted, or list as OMB if X has not started since the last system boot. If viewing /proc/mtrr shows register six or seven is in use, changing the memory configuration might free a MTRR. One method is to increase the AGP graphics aperture by rebooting the system, selecting Setup at the initial screen, and selecting Advanced. However, a larger AGP aperture can reduce the amount of configured memory and can cause a slight decrease in performance for some graphics- intensive applications. Conclusion

Support for large memory configurations on HP Linux Workstations requires the use of an SMP kernel on Red Hat Enterprise Linux WS 3 and later or a bigmem kernel on earlier Red Hat versions

4 Links

Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds.

5 Enabling Hyper-Threading Technology

Summary ...... 2 What is Hyper-Threading Technology?...... 2 Notes, Limitations, and Requirements ...... 2 Hardware ...... 2 Software ...... 2 Enabling HT Technology...... 3 Adding an x86 SMP Kernel ...... 3 Verifying HT Technology...... 4 Conclusion...... 4 Links...... 5

Summary

HP Workstations support Hyper-Threading Technology on systems installed with Red Hat Linux® versions 8.0, 9, Enterprise Linux WS 3, or a later release. HT Technology is disabled in the BIOS by default. It must be enabled and run with an SMP (symmetric multiprocessing) kernel. HT Technology is not supported on AMD processors. What is Hyper-Threading Technology?

HT Technology is a high performance technology, developed by Intel®, that allows a single processor to execute multiple threads of instructions simultaneously. HT Technology enables the processor to utilize its execution resources more efficiently, delivering performance increases and improving user productivity. Not all systems or applications benefit from the HT Technology. For more information about the HT Technology, visit the Intel website at http://www.intel.com/. Notes, Limitations, and Requirements

Hardware • HT Technology is not supported on earlier platforms, such as the xw4000 and xw5000. • HT Technology is not supported on dual core or AMD® platforms such as the xw4300 and xw9300. • Systems must be using one or two Intel Pentium®4/Xeon processors. • Red Hat process schedulers support 4 logical CPUs (or 2 CPU pairs with HT Technology) on the HP Workstation xw8000/xw8200 and xw6000/xw6200 and 2 logical CPUs on the xw4100/xw4200. • Systems with above normal disk I/O activity might experience better performance using SCSI drives instead of IDE or SATA drives. SCSI drives take better advantage of the increased simultaneous reads/writes provided with HT Technology. Software • An SMP kernel is required. • Some kernels prior to 2.4.20 produce boot hangs or system hangs while running hyper-threaded applications. If this occurs, download the latest SMP kernel from http://www.redhat.com/. • HP Linux Installer Kit CDs and preinstalled versions of Red Hat + HP Additions have been tested using HT Technology. Some versions contain kernels that work and others do not.

2 The following table identifies the tested Red Hat version and kernel version combinations that support HT Technology.

Red Hat Version Kernel Version (box HT Technology works? set/HP media) Red Hat Enterprise Linux WS 4 Update 1 2.6.9-11 Yes Red Hat Enterprise Linux WS 3 Update 5 2.4.21-32 Yes Red Hat Enterprise Linux WS 3 Update 4 2.4.21-27 Yes (32-bit and EM64T) Red Hat Enterprise Linux WS 3 Update 2 2.4.21-15 Yes (32-bit and EM64T) Red Hat Enterprise Linux WS 3 (32-bit and 2.4.21-4 Yes EM64T) Red Hat 9 2.4.20-8 Yes Red Hat 8.0 2.4.18-14 Yes (some applications may hang) Red Hat 7.3 2.4.18-26 No (intermittent boot hangs) Red Hat 7.2 2.4.18-3 No

Enabling HT Technology

To enable HT Technology:

1. Download and install the latest BIOS version from www.hp.com/go/workstationsupport. NOTE: BIOS update is critical for the following platforms. Some earlier BIOS versions do not fully support HT Technology. – xw8000 requires 1.10 or later – xw6000 requires 1.16 or later – xw4100 requires 1.14 or later 2. Reboot and go into the BIOS setup menu. 3. Select the Advanced menu. 4. Change the “Hyperthreading” option to “enabled” under the either the Processors or Devices menu. 5. Save the changes and Exit. 6. Verify that the SMP kernel is installed and that the boot loader is configured to load it. For information about the boot loader configuration, visit http://www.redhat.com/. Adding an x86 SMP Kernel

For systems that were installed with a single processor, the SMP kernel and source .rpm files must be installed from either CD 1 of your Red Hat box-set (look under the RedHat/RPMS directory for kernel-smp*.rpm, kernel-hugemem*.rpm, or kernel-source*.rpm ) or download from http://www.redhat.com.

1. To find out if you need to install a new SMP kernel, run the uname-r command. 2. Verify that the output has “smp”, “bigmem”, or “hugemem” in the name. You only need to install a new kernel if:· – only a UP (non-SMP) kernel is installed – the SMP kernel is likely to be too old to support the Hyper-Threading Technology (see the preceding table)

3 3. Reinstall an accelerated HP graphics driver from the HP Linux Installer Kit CDs, or install the latest driver from www.hp.com/go/workstationsupport. This step is required so that an accelerated kernel module for the new SMP kernel gets built. NOTE: The matching kernel source (kernel-source*.rpm) must be installed for this step to be successful. On Red Hat EL 4 and later, matching kernel source is not required. 4. Identify the accelerated driver that was installed on the UP kernel. rpm –qa |grep nv rpm –qa |grep firegl 5. Remove the driver that was identified. rpm –e 6. Install the new driver. rpm –i .rpm 7. Run one of the following configure scripts. cd /opt/hp/graphics/ ./configure Verifying HT Technology

To verify that HT Technology is active and working correctly:

1. Check /proc/cpuinfo to see how many CPUs are identified. 2. Run top to verify that processes are active on all virtual processors. 3. Measure application performance with HT Technology disabled and enabled. Conclusion

This newly integrated functionality requires relatively new BIOS and kernel versions. Not all applications run faster with HT Technology enabled.

4 Links

Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds. Intel, Pentium, Intel Inside and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

5 Setting Up Multi-Monitor Configurations

Summary ...... 2 Basics...... 2 Independent and Continuous Displays...... 4 Multi-Monitor Configuration Strategies ...... 5 Configuring X with Multiple Graphics Cards Using Vizconfig Tool...... 6 Configuring XFree86/X.org by Editing Config Files ...... 7 Example Configurations...... 11 Troubleshooting...... 16 Known Limitations...... 16 Links...... 17

Summary

This document provides a working overview of multiple-monitor solutions for HP Workstations running the Linux® operating system and the XFree86® X windowing system. It covers system concepts, configuration examples, support information, and configuration tradeoffs for system designers. This paper assumes familiarity with Linux configuration, basic X server usage, window managers, and essential video graphics card fundamentals, e.g., AGP versus PCI, and now PCI Express interfaces, VGA versus DVI versus dual-link DVI connectors, 3D versus 2D accelerated graphics. Many advanced graphics cards have the speed and capacity to simultaneously drive multiple display monitors. While conventional systems provide single-monitor setups, markets now demand multiple monitors to fully support their data-intensive visualization needs, such markets include: • Digital Content Creation • Medical Imaging • Oil and Gas • Automotive • Electronic Design Automation • Financial Services The emerging standard for efficient production workstations considers 2, 3, and 4 monitors the norm and 6 to 8 displays an interesting future goal.

Basics

HP supports a wide spectrum of graphics device solutions from Professional 2D to Extreme 3D. Professional 2D devices offer affordable multiple screen real estate for business professionals. For users requiring 3D solutions, HP offers a range of devices from Entry-level 3D with price performance advantages to Extreme 3D devices offering the latest features in programmability, stereo, antialiasing and lots of memory. Almost all HP Workstation graphics cards provide two video output connectors and can drive dual video monitors. The most common graphics interface in systems today is AGP supporting various transfer rates [8x,4x,2x], with 8x mode offering up to 2GB/s in bandwidth. However, in HP’s latest workstations, the primary graphics interface is now PCI Express (PCIe) supporting up to 16x transfer rates with approximately 4GB/s bandwidth. PCIe is seen as the new standard for a scalable interface as graphics and other devices become more powerful and require more bandwidth. A few card models also support the PCI interface such as the NVIDIA® 280NVS-PCI graphics card. A complete list of HP supported Linux graphics devices is located at www.hp.com/workstations/programs/leadership_graphics/product_features.html. • Graphics Drivers: Software drivers dictate the available functionality and performance of graphics cards under XFree86 on Linux. Users should be aware of two distinctions:

2 – XFree86/X.org-native drivers — Graphics software provided by open-source developers included as part of the XFree86 and X.org distributions. Functionality and performance depend upon code maturity and low-level access. Often these drivers have more basic functionality as device manufacturers choose to keep their acceleration techniques and full functionality limited to proprietary drivers. – OEM-proprietary drivers — Graphics software that is developed and maintained by the respective manufacturer. They generally provide the highest degree of card acceleration and functionality but may not always be compatible with the version of XFree86 provided to the user.

NOTE: HP recommends OEM drivers when configuring multiple video ports on its supplied graphics cards. HP works with both XFree86/X.org providers and OEM graphics partners to provide robust graphics driver solutions on its workstations. Version-matched drivers for ATI and NVIDIA graphics cards are available through HP Linux Installer Kit CDs or HP Driver CDs for Red Hat Linux releases or the HP support website: www.hp.com/support. • Multiple Graphics Cards: HP supports multiple, same-vendor graphics cards in a variety of combinations. The xw9300 delivers 2 full speed x16 PCIe graphics slots which enable high end graphics configurations with 2 full performance graphics cards. Multiple graphics cards can also be supported in other workstations by combining one PCIe-based (previously AGP) graphics card with one or more PCI-based graphics cards. Same-vendor card requirements come from the tested reliability of a single universal graphics driver for all installed cards. Mixed-vendor combinations might require conflicting drivers that are not guaranteed to work together and thus cannot be fully supported by HP.

Many workstation customers typically reserve the high-performance PCIe channels for accelerated 3D graphics work. Additional PCI-based graphics cards provide complementary access to user interfaces (menus, navigation, help screens) or other workspaces. For example, financial or EDA segments fill multiple slots with economical Professional 2D cards (PCIe, AGP, and PCI versions of the same card) to increase visibility of their data. However, PCI cards are not limited to 2D. There are also PCI-based 3D cards that are supported on HP workstations as Distinctive solutions. • Multiple Display Monitors: XFree86 and X.org manage each display monitor as part of one or more screens that are used by the user’s window manager (e.g., GNOME, KDE, etc.). Regardless of the number of graphics cards driving individual display monitors, a primary goal is more real estate―expanding viewable workspace across all monitors. Two and three monitor configurations typically define a horizontal setup (side by side). Four or more monitor configurations may define square or rectangular presentations (2-high x 2-wide, 2-high x 3-wide, etc.). Users can control how the mouse pointer moves from monitor to monitor. They can also control how desktop workspaces appear in each display and how independently each display behaves relative to its neighbor. A detailed discussion of these configuration issues follows in the next section.

• SLI Graphics Acceleration: Dual PCIe graphics cards can also be ganged to drive a single graphics display and achieve up to 2 times the performance of a single graphics card. This is performed through a new technology provided by Nvidia called SLI. Only some of the graphics cards support the SLI technology, and SLI requires that the graphics cards be of the same type (homogeneous configuration).

Independent and Continuous Displays

The X server tracks every graphics card video port as a unique entity. Assuming one display monitor connected to each port, here are some important definitions: • Independent Display — the type of monitor screen that defines the conventional behavior of most computers. The edges define a specific boundary from which user windows cannot escape. All content remains fixed within the surrounding borders. Window managers provide a desktop only within the specified display. See Figure 1.

Figure 1. Two independent displays • Continuous Display — a type of monitor screen that shares an adjacency relationship with another display. One or more of its edge borders can share content with its configured neighbors. Windows are allowed to penetrate and span borders such that multiple monitors share their content. Window managers provide a continuous desktop across all participating displays. See Figure 2.

Figure 2. Two continuous displays

• Xinerama — the XFree86 extension that supports continuous display technology on the X server. When enabled, it changes independent displays to continuous displays. Xinerama is configured with a ServerFlags option or enabled with a command-line option. Note: Xinerama only supports accelerated 3D between screens controlled by independent cards with the more recent NVIDIA drivers (not ATI drivers). The vizconfig tool (run /opt/hp/viztools/bin/run_vizconfig) is a multi-card graphics configuration tool that provides a simple way to configure the multiple graphics cards (see description below).

• NVIDIA TwinView — an NVIDIA-specific driver extension that supports Xinerama-like functionality across the two video ports of an NVIDIA graphics card. When configured, it allows the X server to manage dual video ports as one independent display. User windows can traverse the entire graphics card framebuffer. Note: Xinerama can integrate each NVIDIA TwinView device as one logical display in a series of continuous displays. • ATI Big Desktop — an ATI-specific driver configuration mode that supports Xinerama-like functionality across the two video ports of an ATI graphics card. When configured, it allows the X server to manage dual video ports as one independent display. User windows can traverse the entire graphics card framebuffer. Note: This mode is only configurable with the provided configuration tool, fglrxconfig, from ATI. When installed from the HP Linux Installer Kit CDs, this utility resides in the directory: /opt/hp/graphics/ati This utility configures a new XF86Config file with the necessary driver bit-flags properly set. See included documentation for more information. Note: HP does not currently support any PCI-based ATI cards for Personal Workstations.

Multi-Monitor Configuration Strategies

Multi-monitor workstations must balance a number of configuration details to deliver optimal functionality and performance. Users should consider the following when designing an ideal multi- monitor system: • Performance — continuous display configurations should consider: – Faster PCIe-slots — graphics cards driving 3D/2D accelerated content for highest performance. – Slower PCI-slots — graphics cards typically driving 2D content (user-interface, windows) for increased real-estate. – Number of cards — more cards require greater system bandwidth that can reduce refresh performance and interactivity. – X server addressable screen units — 32000 units high/wide maximum for any continuous display. • Supportability — continuous display configurations should consider: – Matched monitor model type and functionality – Matched monitor resolution and refresh frequencies • Ergonomics — physical monitor placement should follow best practices for ergonomic design — display configurations that are excessively wide can result in user fatigue and eye strain

5 Configuring X with Multiple Graphics Cards Using Vizconfig Tool

With the advent of dual high performance graphics slots on the xw9300 and the increased importance of advanced multi-head configurations, HP now provides a multi-head graphics configuration tool called vizconfig. This tool is designed to make it much easier to setup multi-head and multi-card graphics configurations. On the xw9300, this tool has a launcher preinstalled on the Desktop. It can also be easily run from the command line by executing /opt/hp/viztools/bin/run_vizconfig. Today, this vizconfig tool works only on NVIDIA devices since that is the current HP-supported multi-card solution for HP workstations. ATI has a configuration tool called fglrxconfig with a GUI that configures a single graphics card.

Once the vizconfig GUI is invoked, pointing and clicking is all you need to do for most configs. If you need to do anything that vizconfig does not support, you can edit the config file that vizconfig generates to add the missing functionality.

The steps to using vizconfig are outlined below: (1) Login as root. (2) Launch vizconfig using the desktop icon or by executing /opt/hp/viztools/bin/run_vizconfig. (3) Select the display arrangement from the pull-down labeled “Selected Display Arrangement.” The options are: - 1 Card, 1 Display - 1 Card, 2 Displays, (2x1) - 2 Cards, 2 Displays (2x1) - 2 Cards, 3 Displays (3x1) - 2 Cards, 4 Displays (4x1) - 2 Cards, 4 Displays (2x2) - 2 Cards, 4 Displays (1 over 3) (4) Once a display arrangement is selected, you can also set different options in the “Options” tab. Your options are: - SLI Multiview (Xinerama) – enables/disables 2d/3d Xinerama - Use TwinView where possible – enables/disables TwinView - HardwareOverlays – enables/disables using the hardware overlays (See detailed discussions on these topics in this whitepaper) (5) Setup the different displays/monitors. The different displays are shown in the picture of the current selected display arrangement along with how the graphics cards are connected to those displays. (6) Select the display via the “Selected Display” pull-down. The picture of the display arrangement will be updated to highlight the selected display. (7) Set the resolution for this display with the Display Resolution slider. (8) If you want the display to be connected to the other connector on the graphics card, click the “Swap Left_Right Monitors” button. The picture of the display arrangement will be modified to reflect this change. (9) Repeat steps 6 thru 8 as needed for each display. (10) Press “SaveConfig” to save the changes to the /etc/X11/XF86Config file.

If the tool was run as root, the system config file wil be updated (/etc/X11/XF86Config). The old XF86Config file is saved as /etc/X11/XF86Config.vizconfig.sav. If the tool was not run as root, the generated file can be found in /usr/tmp/vizconfig-xf86config. To try the saved changes, restart the Xserver by pressing .

6 If the Xserver does not start, the old XF86Config file should be put back in place (e.g., cp /etc/X11/XF86Config.vizconfig.sav /etc/X11/XF86Config). Diagnose the problem by looking at /var/log/Xfree86.0.log.

Once a vizconfig-generated config file is in place, vizconfig will use the settings from that config file as the starting point the next time vizconfig is run. This is based on several comment fields at the beginning of the XF86Config file. That is, it will remember the display arrangement and the display resolutions, etc.

The vizconfig tool does not setup every possible multi-card configuration possible. Instead, it attempts to meet the most common needs of workstation customers. If a configuration is desired that is slightly different than the supported vizconfig configurations, you can use vizconfig to setup the closest configuration and then make minor edits to the /etc/X11/XF86Config file to get the desired configuration. Note that when re-running vizconfig, manual edits of the config file will not be remembered and must be re-applied.

When using the highest resolution (2560x1600) on a high-res monitor such as the Apple 30 inch Cinema display, more advanced graphics cards are needed. These include the NVIDIA Quadro FX 3450 or the FX 4500 which have 1-2 dual-link DVI connectors. Your display may also need to have a modified Modeline in the XF86Config file if it is not a supported HP monitor. See the documentation in /usr/share/doc/NVIDIA_GLX-1.0 directory for more configuration info.

Configuring XFree86/X.org by Editing Config Files

On Red Hat Enterprise Linux 4 and beyond, the X.org version of the X server replaces the older Xfree86 version. To ease the transition, the X.org X server will look for configuration files in all the old Xfree86 locations. The X.org versions of the files are referenced below for completeness.

Graphics vendors provide detailed information of how to edit and configure the Xserver when using their hardware. Examples include the documentation found in the /usr/share/doc/NVIDIA_GLX-1.0 directory for NVIDIA info. On a Linux workstation, the default XFree86/X.org X server configuration file resides at: /etc/X11/XF86Config or /etc/X11/xorg.conf Users can configure multiple files and start X with an alternative file through the command: /usr/X11R6/bin/XFree86 -xf86config /etc/X11/XF86Config.xinerama Each file contains a complete description of X server’s execution environment including monitor descriptions and timings, graphics drivers, and continuous display settings (e.g., Xinerama). This section covers basic concepts for configuration. The XF86Config file is a hierarchical definition file. In cascading order of significance: • ServerLayout section — highest level section that binds all input and output devices together for a given session including output device “hints” that describe Screen position relationships (e.g., RightOf, LeftOf, Above, Below,…). • Screen section — definition that binds together a Monitor and graphics card Device description with color depth and display resolution preferences.

7 • Monitor — monitor description and timing refresh information. • Device — graphics card description, device driver name and driver control options.

The following discussions build from lowest-level components to high-level server layout in the file. • Monitor section — the configuration file must contain one or more monitor descriptions.

Section “Monitor” Identifier “name” entries … HorizSync H-range # example: 63.6 VertRefresh V-range # example: 60 … EndSection Each monitor is referenced in the Screen section by its unique Identifier. For multi-monitor configurations, one definition is sufficient if the monitors match in type and function. For simplicity, it is recommended that a single monitor configuration be attempted first to properly define compatible Horizontal and Vertical timings for the display. Digital Flat Panel (DFP) monitors, for example, have a narrow synchronization range to properly function. XFree86 will either fail to start or a monitor will remain blank if reasonable refresh timings cannot be synchronized with the graphics card. Attempts to run monitors at higher frequencies than their ratings can result in damage, so care should be taken to specify reasonable operational ranges. Reasonable starting defaults (one frequency, no ranges) for this section can be: CRT displays: HorizSync 80, VertRefresh 75 (75Hz refresh for 1280x1024) DFP displays: HorizSync 63.6, VertRefresh 60 (60Hz refresh for 1280x1024) Red Hat distributions 9 and later include access to the XFree86 utility gtf for computing monitor modelines for this section if more specific timing ranges are required. Device section — The configuration file must contain one device description for each graphics card installed. Section “Device” Identifier “name” Driver “drivername” # example “nvidia” entries …

BusID “PCI:bus:device:function” # example “PCI:64:0:0” … Screen number # optional, number = 0,1 EndSection Each graphics card is referenced in the Screen section by its unique Identifier. Each device section must specify the loadable device Driver provided to drive the graphics card. These drivers reside at: /usr/X11R6/lib/modules/drivers

Driver modules names do not include the drv.o extension found on the files at this location, e.g., nvidia_drv.o is simply “nvidia” in the configuration file. Each graphics card resides at a specific PCI bus location in the workstation. Multi-monitor configurations require each of these cards to be identified in the XF86Config file. The address locations are specified in decimal form. To identify each card, use the lscpi utility (convert HEX to decimal here) or: more /proc/pci

8 Each device will appear by its VGA controller address. Specify the XF86Config BusID address as “PCI:128:0:0” or “PCI:64:1:0” as seen below in Figure 3.

Bus 64, device 1, function 0: VGA compatible controller: nVidia Corporation NV34GL [Quadro4 280/400 NVS] (rev a2). … Bus 128, device 0, function 0: VGA compatible controller: nVidia Corporation NV25GL [Quadro4 980 XGL] (rev 163). … Figure 3. /proc/pci output

For graphics cards with multiple video output ports, each port usually defines a unique device. In order for the X server to properly address a single card with two ports, two device descriptions with the same BusID are defined but with different Device section Screen numbers. The use of the term Screen is private and unique to this section. It identifies the video output port within a range of zero to N-1 ports [usually 0 or 1 for a two-headed card]. The first port always starts at zero. For example, an NVIDIA 980XGL or 280NVS might be described as:

Section “Device” Identifier “PCIe_card_port0” Driver “nvidia” … BusID “PCI:64:0:0” # PCIe slot Screen 0 # port zero EndSection

Section “Device” Identifier “PCIe_card_port1” Driver “nvidia” … BusID “PCI:64:0:0” # PCIe slot Screen 1 # port one EndSection

This effectively describes two available graphics devices to the X server located at the same bus address. Note: When using the NVIDIA TwinView option to unite screens, the Device section Screen numbers are optional and may not always be necessary to uniquely identify the output port. Screen section — The configuration file contains one Screen section for each combination of Monitor and Device defined elsewhere in the file. Each Screen effectively defines one video display of a user’s workstation. Note: the usage of Screen here differs from that used in the Device section as a port number ID.

Section “Screen” Identifier “name” Device “device_identifier” Monitor “monitor_identifier” entries … DefaultDepth 24 … SubSection “Display” Depth 24 Modes “1280x1024” “1024x768” “800x600” entries … EndSubSection … EndSection

9 In the example below, three Screen sections are required for the situation shown in Figure 4.

Figure 4. Three screen configuration

NVIDIA TwinView — the NVIDIA graphics driver specifies its TwinView configuration as Screen options within each Screen section that is used. After installing drivers from the HP Linux Installer Kit CD, configured examples are installed at: /opt/hp/graphics/nvidia/example_configs

As previously mentioned, recall that NVIDIA TwinView can privately specify the adjacency of two video outputs as a single Screen definition. Both monitors are treated as one unit by the X server. • ServerLayout section — The configuration file must contain one or more ServerLayout descriptions.

Section “ServerLayout” Identifier “name” Screen screen-num “screen_identifier” position-info … InputDevice “input_device_identifier” … options … EndSection

Each Screen definition must be specified by its identifier for it to be activated in the final layout. The number screen-num is an integer from 0 to N-1 (sequentially) that specifies the associated X screen number for that display. Note: This is not the same screen number as given internally within a Device description for multi-ported cards. The Position-information field describes the way multiple Screens are positioned (RightOf, LeftOf, Above, Below are the most commonly used options). For example, three displays are placed on a desktop side-by-side. They are defined as screenA, screenB, and screenC, respectively and have screen-num numbers as 0, 1, and 2. The ServerLayout relationships for Figure 5 are:

Section “ServerLayout” Identifier “three_wide” Screen 0 “screenA” # display A Screen 1 “screenB” RightOf “screenA” # display B Screen 2 “screenC” RightOf “screenB” # display C …

EndSection

Section “ServerFlags Option “Xinerama” “true” # option enables a continuous # display EndSection

Figure 5. ScreenLayout positions (Xinerama)

Figure 6. ScreenLayout positions (non-Xinerama)

When the Xinerama server option is specified (Figure 5), all Screens are joined into one Continuous Display. If Xinerama is not specified (or enabled on the command line), all Screens behave as Independent Displays (Figure 6). Vendor-specific Documentation — When OEM-proprietary accelerated drivers are loaded from the HP Linux Installer Kit CD, documentation and configuration examples are installed at: /opt/hp/graphics/vendor-name/

/opt/hp/graphics/ati/ /opt/hp/graphics/nvidia/ Please consult these directories for valuable graphics card customization information, including specifics about NVIDIA’s TwinView and ATI’s Big Desktop functionality. Example Configurations

Example A: Three Monitor Workstation [2 x 3D graphics, 1 x 2D graphics]

Figure 7. Three Monitor NVIDIA TwinView setup

On an HP Workstation running Linux, two graphics cards are installed: • PCIe x16 slot = NVIDIA FX1400 with two DVI connectors [A,B] • PCI slot = NVIDIA 280NVS with two VGA connectors [C] The user desires to configure two independent desktops: • 3D desktop across two continuous displays [A,B] using two matched monitors on one graphics card • 2D desktop across one independent display [C] for menus on second graphics card Note: Xinerama is not used in this solution. If Xinerama is enabled, then one continuous desktop/display for [A,B,C] will be formed. Note: This solution demonstrates NVIDIA TwinView to create the continuous displays [A,B]. Assuming three matched monitors of the exact same type, the following configuration highlights apply [Note: “…” means omitted details]: … Section “Monitor” Identifier “HP Monitor” HorizSync H-range # example: 63.6 VertRefresh V-range # example: 60 EndSection … Section “Device” Identifier “FX1300” Driver “nvidia” … BusID “PCI:64:0:0” # PCIe x16 slot EndSection … Section “Device” Identifier “NV280_NVS”

11 Driver “nvidia” … BusID “PCI:6:4:0” # PCI slot EndSection … Section “Screen” Identifier “PCIe Screen” Device “FX1300” Monitor “HP Monitor” DefaultColorDepth 24 … Option “TwinView” Option “MetaModes” “1280x1024, 1280x1024” … Option “SecondMonitorHorizSync” H-range Option “SecondMonitorVertRefresh” V-range … Option “TwinViewOrientation” “LeftOf” … SubSection “Display” Depth 24 Modes “1280x1024” EndSubSection EndSection Section “Screen” Identifier “PCI Screen” Device “NV280_NVS” Monitor “HP Monitor” DefaultColorDepth 24 … SubSection “Display” Depth 24 Modes “1280x1024” EndSubSection EndSection Section “ServerLayout” Identifier “Dual Desktop” … Screen 0 “PCIe Screen” # Screen A,B Screen 1 “PCI Screen” RightOf “PCIe Screen” # Screen C … EndSection Section “ServerFlags” # empty — no Xinerama used in this example to link desktops EndSection

Example B: Four Monitor Workstation [4 x 2D graphics]

Figure 8. Four Monitor Xinerama setup

On an HP Workstation running Linux, two graphics cards are installed: • PCIe slot = NVIDIA 280NVS with two VGA connectors [A,B] • PCI slot = NVIDIA 280NVS with two VGA connectors [C,D] The user desires to configure one continuous desktop. All screens merge to form a single continuous display. Note: Two NVIDIA TwinView Screens could be used as per Example A. This example demonstrates the generalized Xinerama configuration solution.

12 Assuming four matched monitors of the exact same type, the following configuration highlights apply [Note: “…” means omitted details]: … Section “Monitor” Identifier “HP Monitor” HorizSync H-range # example: 63.6 VertRefresh V-range # example: 60 EndSection

… Section “Device” Identifier “card_0” # 280NVS - PCIe Driver “nvidia” … BusID “PCI:64:0:0” # PCIe slot Screen 0 # note - connector 1 EndSection … Section “Device” Identifier “card_1” # 280NVS - PCIe Driver “nvidia” … BusID “PCI:64:0:0” # PCIe slot Screen 1 # note - connector 2 EndSection Section “Device” Identifier “card_2” # 280NVS - PCI Driver “nvidia” … BusID “PCI:6:4:0” # PCI slot Screen 0 # note - connector 1

EndSection Section “Device” Identifier “card_3” # 280NVS - PCI Driver “nvidia” … BusID “PCI:6:4:0” # PCI slot Screen 1 # note - connector 2 EndSection … Section “Screen” Identifier “screen_A” # display A Device “card_0” Monitor “HP Monitor” … EndSection Section “Screen” Identifier “screen_B” # display B Device “card_1” Monitor “HP Monitor” … EndSection

Section “Screen” Identifier “screen_C” # display C Device “card_2” Monitor “HP Monitor” … EndSection

Section “Screen” Identifier “screen_D” # display D Device “card_3” Monitor “HP Monitor” … EndSection … Section “ServerLayout” Identifier “Xinerama Desktop”

13 … Screen 0 “screen_A” # Screen A Screen 1 “screen_B” RightOf “screen_A” # Screen B Screen 2 “screen_C” RightOf “screen_B” # Screen C Screen 3 “screen_D” RightOf “screen_C” # Screen D … EndSection

Section “ServerFlags” Option “Xinerama” “true” # enable Xinerama

EndSection

Example C: Four Monitor Workstation [4 x 3D graphics – xw9300 only]

Figure 9. Four Monitor Xinerama setup

On an HP xw9300 Workstation running Linux, two graphics cards are installed: • PCIe slot 0 = NVIDIA FX1400 with two DVI-I connectors [A,B] • PCId slot 1 = NVIDIA FX1400 with two DVI-I connectors [C,D] The user desires to configure one continuous desktop. All screens merge to form a single continuous display. Note: Two NVIDIA TwinView Screens with 2 3D-capable graphics cards can only be done on the xw9300 because it alone offers dual PCIe x16-capable slots. Assuming four matched monitors of the exact same type, the following configuration highlights apply [Note: “…” means omitted details]: … Section "Device" Identifier "NV PCIe-1" VendorName "nvidia" Driver "nvidia" BusID "PCI:10:0:0" Option "IgnoreEDID" Option "UseInt10Module"

# sample TwinView setup Option "TwinView" # be sure to replace the HorizSync and VertRefresh with correct values # for your monitor! Option "SecondMonitorHorizSync" "31-94" Option "SecondMonitorVertRefresh" "55-85" Option "TwinViewOrientation" "RightOf" Option "MetaModes" "1280x1024,1280x1024" Option "ConnectedMonitor" "crt,crt" EndSection

Section "Device" Identifier "NV PCIe-2" VendorName "nvidia" Driver "nvidia" BusID "PCI:129:0:0"

14 Option "IgnoreEDID" ## Option "UseInt10Module"

Section "Screen" Identifier "Screen TwinView-1" Device "NV PCIe-1" Monitor "MyMonitor" DefaultColorDepth 24 Subsection "Display" Depth 24 Modes "1280x1024" EndSubsection EndSection

Section "Screen" Identifier "Screen TwinView-2" Device "NV PCIe-2" Monitor "MyMonitor" DefaultColorDepth 24 Subsection "Display" Depth 24 Modes "1280x1024" EndSubsection EndSection

########################################################################## # ServerLayout sections # (invoke using the '-layout' option of 'startx'. ##########################################################################

Section "ServerLayout" Identifier "TwinView" Screen "Screen TwinView-1" Screen "Screen TwinView-2" RightOf "Screen TwinView-1" InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" EndSection

15 Troubleshooting

When editing an XF86Config X server configuration file, know that each time the X server is started it writes out the log file: /var/log/XFree86.0.log. If the results are not as expected, or the X server fails to start, this is the first place to look for clues. Both the X server, and OEM accelerated drivers will write configuration confirmations, warnings, and errors to this file. Nine times out of ten, you can resolve configuration issues based on output in this log file. Known Limitations

There are a few notable limitations in Linux when configuring multiple monitors, especially with multiple graphics cards. For one, on earlier consumer Red Hat releases (prior to Red Hat’s Enterprise Linux), the GNOME window manager did not handle independent displays correctly. In such cases the KDE window manager should be used as it handles independent displays quite well. But, even with KDE, a few anomalies may be noticed. One such anomaly is the toolbars might differ in style on the primary display from the other independent displays. With the release of Red Hat Enterprise Linux, the GNOME window manager has been improved greatly in that it now supports independent displays. Further it has new functionality in being able to customize tool bars per display.

16 Links

NVIDIA is a registered trademark of the NVIDIA Corporation. xFree86 is a trademark of The XFree86 Project, Inc.

17 Using your HP 16X DVD Burner

Summary ...... 2 Supported Recording Modes, Media Type, and DVD Recoding Software ...... 2 CD and DVD Burning Software ...... 2 Cdrecord ...... 2 Growisofs ...... 3 Links...... 4

Summary

HP currently delivers and supports the HP 16x DVD±R/RW Dual Layer Drive for HP Linux Workstations. This device is available as an integrated option or as an after market option for HP Workstations. Supported Recording Modes, Media Type, and DVD Recoding Software

The HP 16x DVD±R/RW Dual Layer Drive supports the following recording modes: • Disk-at-once — records one or more tracks to a blank disk, leaving no gaps between the tracks and allowing for no further sessions. • Track-at-once — records one or more tracks, separating each track with a gap and allowing for further sessions. • Packet writing — records data in small increments, eliminating the need to open or close a session each time data is written. • Session-at-once — records similar to Disk-at-once except that new sessions can be written later.

NOTE: The recoding software must also support the recording modes. Growisofs (dvd+tools package) supports the above modes The HP 16x DVD±R/RW Dual Layer Drive supports the following media types: • Reading — CD-ROM, CD-RW, CD-R, DVD-ROM, DVD-R (usually), DVD-RW (usually), DVD+RW, and DVD+R. • Writing — CD-RW, CD-R, Dual-layer DVD+R, DVD+RW, DVD+R, DVD-RW, and DVD-R

NOTE: Some media are more reliable than others, so verify that the data transfers to the media as expected. The following DVD recording software is included with your Linux operating system: • Red Hat Linux® 7.3, 8.0, 9 supports ‘cdrecord’ for burning CDs. • Red Hat Enterprise Linux WS 3 and 4 supports ‘growisofs’ for burning DVDs and ‘cdrecord’ for burning CDs

Growisofs is part of the dvd_rw-tools rpm provided with Red Hat Enterprise Linux WS 3 and 4 NOTE: Red Hat Enterprise Linux does not support the Lightscribe labeling technology. Therefore, the 16x DVD+/-RW, DL, Lightscribe device will behave as a 16x DVD+/-RW, DL device. CD and DVD Burning Software

Cdrecord

1. Determine if cdrecord is installed (part of cdrecord package): rpm –qa | grep cdrecord If it is not installed: rpm –i cdrecord.rpm 2. After the cdrecord rpm is installed, you can access the basic man page with the command ‘man cdrecord’ and/or read the documentation provided in /usr/share/doc/cdrecord/.

2 To format or clear the content of a CD-RW (where the N,N,N dev values can be determined by first running the command ‘cdrecord –scanbus’) cdrecord dev=N,N,N blank=fast To burn an existing file.iso to a CD-R/RW: cdrecord dev=N,N,N –dao -pad padsize=150s –immed –data file.iso [Under Red Hat Enterprise Linux 4, use the following: cdrecord dev=/dev/cdwriter driveropts=burnfree –dao –data file.iso] Growisofs

1. Determine if growisofs is installed (part of the dvd+rw-tools package): rpm –qa | grep dvd+rw-tools If it is not installed: rpm –i dvd+rw-tools.rpm You may also want to check that the cdrecord and dvdrecord packages are installed. 2. After the dvd+rw-tools rpm is installed, a tutorial is available if you point you browser at the file /usr/share/doc/dvd+rw-tools/index.html.

NOTE: There is no manual for growisofs because all arguments are passed to mkisofs(8); the few expections are covered in the tutorial mentioned above To format new DVD media (assuming your DVD device is /dev/scd0): dvd+rw-format –blank=full /dev/scd0 To burn a DVD±RW, DVD±R, or DL DVD+R with, for example, the files in /tmp on the initial session and add the files in /bin in a later session: growisofs –Z –R /dev/scd0 /tmp growisofs –M –R /dev/scd0 /bin To burn an existing iso file, file.iso: growisofs –Z /dev/scd0=file.iso

3 Links

HP Workstations Linux Home Page: http://www.hp.com/linux HP Workstations Home Page http://www.hp.com/workstations Hardware support matrix for HP xw Linux Workstations http://www.hp.com/support/linux_hardware_matrix HP User Manual for HP xw Linux Workstations http://www.hp.com/support/linux_user_manual General Web Information on DVDs http://www.dvdhelp.us/ For additional information on HP products and services, visit us at: http://www.hp.com/ For the location of the nearest sales office, call: United States: +1 800 637 7740 Canada: +1 905 206 4725 Japan: +81 3 3331 6111 Latin America: +1 305 267 4220 Australia/New Zealand: +61 3 9272 2895 Asia Pacific: +8522 599 7777 Europe/Africa/Middle East: +41 22 780 81 11 For more information, contact any of our worldwide sales offices or HP Channel Partners (in the U.S. call 1 800 637 7740).

4 Enabling IEEE-1394 on HP Linux Workstations

Summary ...... 2 Tested Operating Systems and Devices ...... 2 Manually Installing IEEE-1394 Modules...... 2 Install Unsupported Kernel Modules...... 2 Script...... 3 rescan-scsi-bus.sh ...... 3 Links...... 7

Summary

None of the supported HP Linux Workstations operating systems support IEEE-1394 at this time. This document contains tips for how to manually enable IEEE-1394 (also known as FireWire) devices on systems installed with the 32-bit version of Red Hat® Enterprise Linux WS 3 or later. These unsupported drivers and protocols are not yet robust. Use at your own risk. Tested Operating Systems and Devices

Although IEEE-1394 is not officially supported, there are some hardware devices that have been detected and mounted successfully. Disclaimer: There are sometimes issues with file transfer performance, devices losing connection, problems having an IEEE-1394 and a USB drive key mounted at the same time, and advanced devices not being able to connect due to lack of Linux drivers and software. Use at your own risk.

A 20GB HP ipod and a Western Digital WD800B02-RNN IEEE-1394 external hard drive were tested both with the front ports and a 1394 PCI card ports of xw8200, xw6200, and xw4200 HP Linux Workstations.

OS Pass Fail 32-bit Red Hat EL WS 3 Update 2 X 64-bit Red Hat EL WS 3 Update 2 X 32-bit Red Hat EL WS 3 Update 4 X 64-bit Red Hat EL WS 3 Update 4 X Red Hat 7.x X

Manually Installing IEEE-1394 Modules

Install Unsupported Kernel Modules Prerequisites: • HP Workstation xw8200, xw6200, xw4200, or later • System already installed with a supported 32-bit version of Red Hat. See http://hp.com/support/linux_hardware_matrix to verify. • Red Hat Installation CDs To install:

1. Mount Red Hat EL WS 3 (Update 5) OS Installation CD 4. This package may be on a different CD depending on the OS version. 2. Install kernel-smp-unsupported-2.4.21-32.EL.i686.rpm (or its equivalent for your configuration). NOTE: For x86-64, always use the smp-unsupported package. Although your kernel will be labeled .EL like x86 UP kernels are, it is actually an SMP kernel.

1. Change to the directory where they were installed (/lib/modules/2.4.21…/unsupported/drivers/ieee1394/) 2. Using /sbin/insmod, load the following modules:

ieee1394 ohci1394 sbp2

2 3. Plug in the IEEE-1394 hardware (i.e. external hard drive). Follow manufacturer’s instructions for setup. Mount device

1. Look for the new device in the output from fdisk –l (i.e. /dev/sdb1) 2. If a new device is not automatically detected, force a scan of the SCSI bus. The best way to do this is to download a script that will do a complete scan. (i.e., http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh. Download it directly or cut and paste text below.) 3. Make a temporary directory (i.e., /mnt/fw) 4. Mount the device to a local directory (i.e. mount /dev/sdb1 /mnt/fw). Try /dev/sda1 or /dev/sdb2 if you get an error about needing to specify a file system type. Script rescan-scsi-bus.sh #!/bin/bash # Skript to rescan SCSI bus, using the # scsi add-single-device mechanism # (w) 1998-03-19 Kurt Garloff (c) GNU GPL # (w) 2003-07-16 Kurt Garloff (c) GNU GPL # $Id: rescan-scsi-bus.sh,v 1.15 2004/05/08 14:47:13 garloff Exp $ setcolor () { red="\e[0;31m" green="\e[0;32m" yellow="\e[0;33m" norm="\e[0;0m" } unsetcolor () { red=""; green="" yellow=""; norm="" }

# Return hosts. sysfs must be mounted findhosts_26 () { hosts= if ! ls /sys/class/scsi_host/host* >/dev/null 2>&1; then echo "No SCSI host adapters found in sysfs" exit 1; #hosts=" 0" #return fi for hostdir in /sys/class/scsi_host/host*; do hostno=${hostdir#/sys/class/scsi_host/host} hostname=`cat $hostdir/proc_name` hosts="$hosts $hostno" echo "Host adapter $hostno ($hostname) found." done }

# Return hosts. /proc/scsi/HOSTADAPTER/? must exist findhosts () { hosts= for driverdir in /proc/scsi/*; do driver=${driverdir#/proc/scsi/} if test $driver = scsi -o $driver = sg -o $driver = dummy -o $driver = device_info; then continue; fi for hostdir in $driverdir/*; do name=${hostdir#/proc/scsi/*/} if test $name = add_map -o $name = map -o $name = mod_parm; then continue; fi num=$name driverinfo=$driver if test -r $hostdir/status; then num=$(printf '%d\n' `sed -n 's/SCSI host number://p' $hostdir/status`)

3 driverinfo="$driver:$name" fi hosts="$hosts $num" echo "Host adapter $num ($driverinfo) found." done done }

# Test if SCSI device $host $channen $id $lun exists # Outputs description from /proc/scsi/scsi, returns new testexist () { grepstr="scsi$host Channel: 0*$channel Id: 0*$id Lun: 0*$lun" new=`cat /proc/scsi/scsi | grep -e"$grepstr"` if test ! -z "$new"; then cat /proc/scsi/scsi | grep -e"$grepstr" cat /proc/scsi/scsi | grep -A2 -e"$grepstr" | tail -n2 | pr -o4 -l1 fi }

# Perform search (scan $host) dosearch () { for channel in $channelsearch; do for id in $idsearch; do for lun in $lunsearch; do new= devnr="$host $channel $id $lun" echo "Scanning for device $devnr ..." printf "${yellow}OLD: $norm" testexist if test ! -z "$remove" -a ! -z "$new"; then # Device exists and we're in remove mode, so remove and readd echo "scsi remove-single-device $devnr" >/proc/scsi/scsi echo "scsi add-single-device $devnr" >/proc/scsi/scsi printf "\r\x1b[A\x1b[A\x1b[A${yellow}OLD: $norm" testexist if test -z "$new"; then printf "\r${red}DEL: $norm\r\n\n\n\n"; let rmvd+=1; fi fi if test -z "$new"; then # Device does not exist, try to add printf "\r${green}NEW: $norm" echo "scsi add-single-device $devnr" >/proc/scsi/scsi testexist if test -z "$new"; then # Device not present printf "\r\x1b[A"; # Optimization: if lun==0, stop here (only if in non-remove mode) if test $lun = 0 -a -z "$remove" -a $optscan = 1; then break; fi else let found+=1; fi fi done done done }

# main if test @$1 = @--help -o @$1 = @-h -o @$1 = @-?; then echo "Usage: rescan-scsi-bus.sh [options] [host [host ...]]" echo "Options:" echo " -l activates scanning for LUNs 0-7 [default: 0]" echo " -w scan for target device IDs 0 .. 15 [default: 0-7]" echo " -c enables scanning of channels 0 1 [default: 0]" echo " -r enables removing of devices [default: disabled]" echo "--remove: same as -r" echo "--nooptscan: don't stop looking for LUNs is 0 is not found" echo "--color: use coloured prefixes OLD/NEW/DEL" echo "--hosts=LIST: Scan only host(s) in LIST" echo "--channels=LIST: Scan only channel(s) in LIST" echo "--ids=LIST: Scan only target ID(s) in LIST" echo "--luns=LIST: Scan only lun(s) in LIST"

4 echo " Host numbers may thus be specified either directly on cmd line (deprecated) or" echo " or with the --hosts=LIST parameter (recommended)." echo "LIST: A[-B][,C[-D]]... is a comma separated list of single values and ranges" echo " (No spaces allowed.)" exit 0 fi expandlist () { list=$1 result="" first=${list%%,*} rest=${list#*,} while test ! -z "$first"; do beg=${first%%-*}; if test "$beg" = "$first"; then result="$result $beg"; else end=${first#*-} result="$result `seq $beg $end`" fi test "$rest" = "$first" && rest="" first=${rest%%,*} rest=${rest#*,} done echo $result } if test ! -d /proc/scsi/; then echo "Error: SCSI subsystem not active" exit 1 fi

# defaults unsetcolor lunsearch="0" idsearch=`seq 0 7` channelsearch="0" remove="" optscan=1 if test -d /sys/class/scsi_host; then findhosts_26 else findhosts fi

# Scan options opt="$1" while test ! -z "$opt" -a -z "${opt##-*}"; do opt=${opt#-} case "$opt" in l) lunsearch=`seq 0 7` ;; w) idsearch=`seq 0 15` ;; c) channelsearch="0 1" ;; r) remove=1 ;; -remove) remove=1 ;; -hosts=*) arg=${opt#-hosts=}; hosts=èxpandlist $arg` ;; -channels=*) arg=${opt#-channels=};channelsearch=èxpandlist $arg` ;; -ids=*) arg=${opt#-ids=}; idsearch=èxpandlist $arg` ;; -luns=*) arg=${opt#-luns=}; lunsearch=èxpandlist $arg` ;; -color) setcolor ;; -nooptscan) optscan=0 ;; *) echo "Unknown option -$opt !" ;; esac shift opt="$1" done

# Hosts given ? if test "@$1" != "@"; then hosts=$*; fi echo "Scanning hosts $hosts channels $channelsearch for " echo " SCSI target IDs " $idsearch ", LUNs " $lunsearch test -z "$remove" || echo " and remove devices that have disappeared" declare -i found=0

5 declare -i rmvd=0 for host in $hosts; do dosearch; done echo "$found new device(s) found. " echo "$rmvd device(s) removed. "

6 Links

Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds.

7 Introducing HP 64-bit Linux Workstations

HP 64-bit Linux Workstation Family...... 2 AMD-64 Technology ...... 2 Intel’s Extended Memory 64 Technology...... 2 x86_64 Technology ...... 2 Linux OS Support for 64-Bit...... 2 Running 32-bit Applications on a 64-bit Linux OS ...... 3 PCI Express Graphics on 64-bit Workstations ...... 3 Links...... 4

HP 64-bit Linux Workstation Family

On February14th at LinuxWorld 2005, HP introduced the HP xw9300 Workstation, an AMD64- based workstation to complement HP’s existing three 64-bit capable workstations based on Intel’s EM64T technology. Once again HP is delivering leading edge products on Linux by offering preinstalled 64-bit Red Hat Enterprise Linux at introduction. The new nForce Professional 22200 chipset from NVIDIA and the latest Opteron processor from AMD have enabled HP to enter the AMD workstation business with a visualization workstation that delivers two Opteron processors from AMD, two nForce chipsets, up to two full performance PCI-express x16 graphics cards, and up to four graphics displays, or soon NVIDIA’s SLI graphics acceleration capability. HP has worked closely with AMD and NVIDIA to make all this happen. Of course, 64-bit Red Hat Enterprise Linux is available across HP’s workstation product line (both Intel and AMD platforms) at the launch of the HP xw9300 Workstation. Certification on Novell Linux Desktop-64 bit across the HP Workstation products is also planned very shortly after LinuxWorld. HP’s lineup of Intel and AMD products on Red Hat and Novell Linux provides HP customers with a very broad 64-bit Linux workstation product offering.

AMD-64 Technology AMD created the 64-bit extensions to the x86 architecture, coined x86_64, and supports it across the Opteron processor family. AMD has defined these extensions to be a logical superset of the x86 architecture and thus 32-bit applications will still run on a 64-bit OS. This provides a very good compatibility story that other 64-bit architectures have not enjoyed.

Intel’s Extended Memory 64 Technology EM64T, Intel’s Extended Memory 64 Technology, is an enhancement to Intel’s IA32 architecture that allows the processor to run newly compiled 64-bit code and access larger amounts of memory. EM64T is derived from and compatible with the AMD64 extensions that AMD has already made to the x86 architecture (x86_64). This enables all user-level 64-bit programs compiled for AMD64 to also run on EM64T, and all programs compiled on EM64T will also run on AMD64 provided the code was not compiled with special Intel or AMD options. EM64T is supported across all the Intel- based HP Workstations, which includes the HP xw4200, xw6200, and xw8200 Workstations. x86_64 Technology These x86_64 extensions include extended memory addressability by way of 64-bit pointers, 64-bit general purpose registers and 128-bit XMM registers, eight additional general purpose registers, and double precision integer support. A new extended IA-32 mode will allow 32-bit and 64-bit applications to run simultaneously on the same 64-bit OS.

Linux OS Support for 64-Bit Red Hat has added OS support for 64-bit processors from Intel and AMD in the Red Hat Enterprise Linux WS 3, Update 2 (RHEL WS 3), and subsequent updates. There is both a 64-bit and 32-bit version of the OS, and only the 64-bit version is capable of running 64-bit code. None of Red Hat’s previous OS versions have 64-bit support for the Intel and AMD x86_64 processors. The 64-bit RHEL 3 box-set from Red Hat can be purchased from HP with the workstation. The HP Installer Kit for Linux should be ordered or downloaded from the HP support Web site (www.hp.com/go/workstationsupport) to complement Red Hat’s 64-bit box-set. The Installer Kit will provide the needed graphics drivers and other HP content. Red Hat Enterprise Linux-64 bit is the only preinstalled Linux OS that is available for the new HP xw9300 and xw4300 Workstations as well as the HP xw8200 and xw6200 Workstations. The 32-bit version of RHEL WS 3 is the only preinstalled Linux OS that is available today for the HP xw4200 Workstation.

The other Linux distributions are also supporting 64-bit versions. The new Novell Linux Desktop (NLD) now has 64-bit support and has been certified on the entire HP Workstation product family (xw4200, xw6200, xw8200, and xw9300) as has the 32-bit NLD 9. Other 64-bit certifications like Mandrakelinux 10.0 will be posted on HP’s Linux website. To see the certifications for Red Hat and other Linux distributions, go to www.hp.com/linux and select “Certified and supported matrices.”

Running 32-bit Applications on a 64-bit Linux OS In order to run 32-bit applications on a 64-bit Linux OS, the 32-bit runtime environment is needed in addition to the application itself. Many applications use a variety of shared libraries including core Linux support libraries such as glib and math libraries, X window libraries such as Xlib and Xext, and toolkits such as Qt. Red Hat and the other Linux distributions provide libraries and runtime support for some of the 32-bit packages that are available in their 32-bit version of the OS. This is typically not all of the 32-bit packages and thus some applications may not have all the 32-bit shared libraries and runtime support that are needed for the application to run.

Because some of the files in the 32-bit runtime support conflict with 64-bit runtime files, the 32-bit packages cannot be blindly installed on top of the 64-bit OS. To run 32-bit applications that require more runtime support than provided by Red Hat or the other Linux distribution being used, the needed files must be in place on the system running the application. The ldd command will enumerate all of the static library references in the application. Once the missing libraries are discovered, simply follow these steps to safely add the 32-bit rpms that contain these missing libraries: rpm2cpio <32-bit rpm> > <32-bitpath> rpm -i --force <64-bit rpm> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<32-bitpath> where <32-bitpath> is something like /32bitlibs and <32-bit rpm> is the name of the 32 bit rpm. Over time, the Linux 64-bit distributions have already improved and will hopefully get even better at delivering 32-bit runtime environment.

PCI Express Graphics on 64-bit Workstations The new workstations all support PCI Express x16 graphics cards instead of AGP-8x graphics cards and the HP xw9300 Workstation supports 2 of these PCI Express x16 graphics cards. Initial graphics support for 64-bit Linux consists of only NVIDIA PCI Express cards and the 280 NVS PCI card. ATI support will come in the future, once the ATI Linux 64-bit drivers for their PCI Express cards are tested and integrated into HP’s Installer Kit. The 64-bit NVIDIA driver requires a configuration change to the kernel in order to expand the size of the software TLB buffer space. The /boot/grub/grub.conf file MUST BE CHANGED to add the parameter “swiotlb=16384” to the end of the lines that begin with “kernel.” This is done automatically by HP’s graphics driver rpms, but must be done manually if the NVIDIA “_run” scripts are used to install NVIDIA drivers. This issue has been logged with Red Hat and NVIDIA and should be fixed in future releases.

Building and using graphics-intensive 64-bit applications should be similar to other 64-bit apps except for the dependency on graphics middleware and libraries. Application developers will need to make sure that all libraries that are used to build the application are available in 64-bit versions. Although HP delivers the 32-bit OpenGL libraries (from the graphics vendors) needed to run 32-bit graphics apps on the 64-bit version of the OS, the 32-bit runtime issues mentioned above may cause problems in the graphics space also. We have found that the 64-bit graphics libraries have about the same performance as the 32-bit libraries.

3 Links

© 2004-2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds. NVIDIA is a registered trademark of the NVIDIA Corporation. Intel, Pentium, Intel Inside and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. ATI is a registered trademark of ATI Technologies, Inc.

4 FAQ for HP 64-bit Linux Workstations

Summary ...... 2 Links...... 4

Summary

The following is a list of frequently asked questions and the answers concerning 64-bit support on HP Linux® workstations. Q. When will a 64-bit Red Hat Linux OS be supported on HP’s workstations with EM64T technology from Intel and AMD64 technology from AMD®? A. Today! HP’s Intel®-based Workstations (xw9300, xw4300, xw8200, xw6200, and xw4200) all support 64-bit Red Hat Linux with the Red Hat box set and the HP Installer Kit for Linux. The new Intel- based xw4300 and AMD-based xw9300 also support 64-bit Red Hat Linux pre-installed on the system. Q. What version of Red Hat Linux will support 64-bit? A. Red Hat Enterprise Linux 3, WS (RHEL 3,WS) Update 5 has both a 32-bit version and a 64-bit version. HP pre-installs the 32-bit version on Intel-based xw4200 workstations, and the 64-bit version on AMD-based xw9300 and the Intel-based xw4300, xw6200, and xw8200 workstations today and supports both 32-bit and 64-bit with the Driver CD in the HP Installer Kit for Linux. HP pre-installs and supports the 64-bit version on the new xw9300 and xw4300. There will not be any 64-bit versions of previous Red Hat releases (such as Red Hat Linux 7.3) supported on HP Workstations. Q. Do I have to have two versions of my 64-bit application—one for Intel-based workstations and one for AMD workstations? A. NO! Intel defined the EM64T extensions to the x86 architecture to be exactly compatible with the AMD64 instructions. As long as you do not use any special Intel or AMD options to the compiler when you build your application (such as 3dnow), your application should just run on either an Intel system or an AMD system. Q. Are there other 64-bit distributions of Linux that will work on the HP Workstations? A. Yes, HP has tried other distributions on the HP Workstations. To see what has been fully certified, go to www.hp.com/linux and click the OS Supported and Certified Matrices link. Q. Can I run 32-bit apps on a 64-bit Linux OS? How does this work? Will this work for all 32-bit apps? A. Yes, as long as the runtime support (mainly shared libraries) for the application exists on the system. HP has noticed that some versions of Linux are much better than others at providing a complete set of 32-bit libraries. The Linux convention for having 32-bit libraries and 64-bit libraries on the same OS is to have companion library directories. The 32-bit libraries are in the conventional locations: /lib, /usr/lib, /usr/X11R6/lib, etc., whereas 64-bit libraries just append 64 to the directory name such as /lib64, /usr/lib64, and /usr/X11R6/lib64. This also includes 32-bit versions of the graphics libraries, which HP has included from the graphics vendors. Q. What do I do if the 32-bit apps do not run due to missing shared libraries? A. Simple solution is to get the library from Red Hat’s 32-bit RHEL 3 distribution and put it on your system in the appropriate directory and report the missing library to Red Hat through your Red Hat Network subscription. This will help Red Hat to get the right set of 32-bit libraries needed for most apps in future releases. A more robust solution is to do the following: rpm2cpio <32-bit rpm> > <32-bitpath> rpm -i --force <64-bit rpm> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<32-bitpath>

2 Q. Can I run the 32-bit versions of Red Hat Linux on a 64-bit capable systems such as the xw9300, xw4300, xw8200, xw6200, and the xw4200? A. Yes, you can. If you are doing the installation yourself, the installation process will inform you that you are installing a 32-bit OS on a 64-bit machine and ask you if that is what you really want to do. Just answer “Yes” and continue. Q. How do I install the 64-bit version of Linux? A. Just purchase the Red Hat Enterprise Linux 3 bits, either from HP or from some other source, and go through the normal Red Hat Anaconda install. Once you complete the installation and are rebooting for the first time, the FirstBoot utility will run and ask if you have Additional CDs to install. Insert the HP Driver CD for RHEL 3 and answer “Yes.: This process will install RHEL 3, any HP additions, and the accelerated graphics driver from the appropriate graphics vendors. The xw9300, xw4300, xw8200, and xw6200 can be ordered with the 64-bit OS already pre-installed. Q. Once I have installed the 64-bit version of Linux, what do I have to do to build 64-bit apps? A. It is simple. Just rebuild from scratch and the compiler will build 64-bit by default. This is true for most apps. However, some apps must be made 64-bit clean, which means that the developers must review the code to get rid of any assumptions about 32-bitness, such pointer arithmetic issues. Some makefiles that explicitly declare paths such as /lib, /usr/lib and /usr/X11R6/lib might need to be changed to append “64” such as /lib64, /usr/lib64 and /usr/X11R6/lib64.

3 Links

Red Hat is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds. AMD is a registered trademark of Advanced Micro Devices, Inc. Intel, Pentium, Intel Inside and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

4 Install Guide for Novell Linux Desktop-9® (Service Pack 2) and SLES-9 (SP2) for x86_64 on HP Linux Workstations

Summary ...... 2 Certified Operating Systems...... 2 Hardware Warranty ...... 3 Graphics ...... 3 Links...... 4

Summary

To be used with the official 64 bit Novell Linux Desktop-9(base release) and the Service Pack 2 release (both CD sets are required). The base-release for Novell Linux Desktop-9 / 64-bit version was not released until Service Pack 1 timeframe and thus the 64-bit base release may be labeled as Service Pack1. Certified Operating Systems

HP Linux workstations include the HP Driver CDs with the Linux Media Kit, but if you need to download the Driver CD in order to get the most recent version, first download the ISO to local hard drive from the HP support website for the appropriate workstation platform. After the ISO is downloaded, copy it to CD-R bootable media. On a Linux Workstation, use the cdrecord utility (cdrecord -v -eject speed=16 dev=2,0,0 where dev= is the device address for the CD burner that comes from “cdrecord –scanbus”).

To install x86_64 NLD-9 or SLES-9 with the HP Driver CD:

1. Note that these instructions are specific to Novell Linux Desktop (NLD), but the SLES procedures are very similar. 2. Install the operating system by using the Novell Linux Desktop-9/Service Pack 2 CD1 first. Insert the disk in the drive before the systems boots. 3. From the Install Screen, select if installing on an xw4200, xw6200, or xw8200... OR ... Select on an xw9300. 4. When the installation requests that CD number 1 is in your drive, place CD 1 from the NLD-9 base release into the drive. (Note: for the 64bit version of NLD, the NLD base release was coincident with NLD9-SP1 and may be labeled such) 5. Proceed with the installation, answering the installation questions as needed, and inserting disks from both disk sets ...NLD (base) and NLD service pack 2... as requested. 6. After successfully installing the Novell Linux Desktop operating system, your system will be rebooted and the configuration agent will then lead you through configuring things such as root password, networking, time/date, and adding new users. Note: On the xw9300, no networking is automatically configured. The user must manually configure the NVIDIA network driver... just click on “Configure” button and then enter the module name of the open source driver (forcedeth). All other fields in this manual networking config step are OK. Next just setup the networking parameters as desired.

7. Audio on the xw9300 will not be automatically configured either... just manually setup the sound card by clicking “Add Sound Card”, and specifying the Nvidia/NForce3 as the device using “Quick Automatic Setup” 8. Install other drivers for HP hardware following these steps: A. insert HP Driver Disk B. if running X windows, start up a terminal window (Programs->Accessories- >Terminal) C. cd /media/cdrecorder [or wherever CD is mounted]... if not mounted, do D. mount /media/cdrecorder E. cd HP/scripts F. ./drivers.sh (ignoring the glut errors)

2 G. if NVIDIA hardware, then run /opt/hp/graphics/nvidia/configure from init level 3 (X windows cannot be running) 9. If you would like to configure multi-card graphics configurations using the vizconfig tool: A. get latest version of vizconfig off HP support website (includes 64 bit vizconfig which is needed for NLD/SLES) B. While X windows is running, run the vizconfig tool .... /opt/hp/viztools/bin/run_vizconfig 10. Adjust audio by running YAST (System->Administrator Settings->YAST) and selecting Hardware->Sound. Then set Master Mono to greater than 50 and the 2 sliders (master and pcm) as desired. 11. Use YAST (System->Administrator Settings->YAST) to configure the rest of your system.

Hardware Warranty

HP workstation hardware running Novell Linux Desktop OS has standard HP hardware warranty support. For full warranty information, please refer to the warranty that shipped with your workstation or visit www.hp.com/go/workstationsupport and select the Warranty Information link.

Graphics

HP workstations may be ordered with a selection of graphics cards that have gone through extensive hardware verification with HP and the graphics vendors or without any graphics card at all. Software support for the graphics vendors’ drivers on NLD is provided by the graphics vendors, not HP.

3 Links

HP Workstations Linux Home Page: http://www.hp.com/linux HP Workstations Home Page http://www.hp.com/workstations Hardware support matrix for HP xw Linux Workstations http://www.hp.com/support/linux_hardware_matrix HP User Manual for HP xw Linux Workstations http://www.hp.com/support/linux_user_manual General Web Information on DVDs http://www.dvdhelp.us/ For additional information on HP products and services, visit us at: http://www.hp.com/ For the location of the nearest sales office, call: United States: +1 800 637 7740 Canada: +1 905 206 4725 Japan: +81 3 3331 6111 Latin America: +1 305 267 4220 Australia/New Zealand: +61 3 9272 2895 Asia Pacific: +8522 599 7777 Europe/Africa/Middle East: +41 22 780 81 11 For more information, contact any of our worldwide sales offices or HP Channel Partners (in the U.S. call 1 800 637 7740).

© 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Linux is a registered trademark of Linus Torvalds. Novell Linux Desktop is a registered trademark of Novell Inc.