This section presents HP hardware supported today by Linux. Informations are based on the latest stable version of the Linux kernel, which is currently version 2.4.16. A development kernel (version 2.5) is also available but doesn't offer any guarantee of stability.
That computer range is today the main set of HP machines supported by Linux, and that till many years.
In case you didn't already do it before, some preliminaty readings are recommended before to try to install Linux on these platforms.
The
Linux Installation HOWTO
contains a great number of information to install Linux. If you bought linux on a CD-ROM, chances are that installation instructions are provided with it (the little booklet inside the disk case, and/or files on the CD).
The
Linux Kernel HOWTO
should be read to have details on kernel construction.
I will just mention here points which are specific to HP hardware.
Outside particular indication, Linux support means during the installation of a RedHat/Mandrake type distribution. In special cases, a kernel rebuild will be necessary to support completely some hardware elements. You should note that what is true for one distribution is generally true for another, as these functions are linked to the kernel or the XFree86 server, and not to the distribution itself.
In case of problem, the first reflex should be to update the BIOS of the HP machine, and to verify whether the problem is always there. If yes, you may then contact HP support, if your configuration is supported by HP (This document focus on what is working, superset of what is supported, and has no value in that area). On the other hand, if your machine is working correctly, don't update the BIOS without reason, this is always a risked operation. BIOS updates are available from
http://www.hp.com/cposupport/software.html
HP insures the support of certified Linux hardware by the following method : all the machines have the
Diagtool
utility. If this utility indicates a problem, it's taken in account by HP maintenance. If it doesn't, it's considered as a software problem and should be reported to the distribution provider.
The following tables indicate the state of Linux support by these platforms :
Visualize systems come in two flavors: the p and x class systems are preinstalled, supported, and configured with Windows; the pl and xl class systems are preinstalled, supported, and configured with Linux. There is no hardware difference between the base systems, but the Linux image that is preinstalled on the pl and xl is customized so that all drivers for the systems are preconfigured -- there's no need to specify or tune the box and drivers.
CD-ROM, DVD and ZIP drives are supported by Linux kernel. Read the various HOWTO for their use, following the interface type.
There are 4 supported graphics cards with XFree86 on HP x2000 and x40000 systems with Linux: SynergyPlus, Synergy2, Matrox G450, and FireGL2/4. There are also 4 rpms that are associated with these cards and they must be present on your system in order to have a supported graphics environment: synergyplus, synergy2, firegl2 and mgag450. For example, to check for the existence of the firegl2 rpm, run
#rpm -q firegl2
Once you have installed the new card and rebooted, run
/usr/X11R6/bin/graphicsconfig
to configure the card. If it is a recognized card supported by your Linux system, the function will return the name of the card and it will be configured to run. At this point you may start up your X window environment.
If it returns "UNKNOWN", then your graphics card either is not one of the 4 currently supported cards, or it is a newer/older version of the card than is supported. In either case you will need to run
Xconfigurator to set it up.
To suspend to disk the current session, you need to not have deleted the hibernation partition (type a0), which size should be the size of the RAM, to have support for APM in the kernel, and to use the key combination Fn+F12.
To send the video signal, either to an external screen, or through the docking station, it is be necessary to add the following parameter to your XFree86 configuration file
/etc/X11/XF86Config:
For TopTools Remote Control Cards (TTRCC), the B.02.02 firmware release shows some strange symptoms at boot time, namely you get no data in your browser (Netscape on Linux) until way past selftest and LILO, so it's kind of hard to boot an alternate kernel. The fix is to 'downgrade' your firmware on the TTRCC to B.02.00. You can see what revision you're running on the TopTools 'Identity Screen'. You can flash the eeprom on the TTRCC anytime (unless you really want to make a DOS floppy and reboot) by tftping the right firmware (ttrc0200.bin) in the 'Configuration' tab -> 'Card Info' area, and press 'Update'. It takes a minute or so to download/verify/and reset the TTRCC.
(Information from Lee Mayes)
The
"Web hosting" SA1100 (P4533A) and SA1120 (P4534A)
machines are equiped with a RedHat based distribution of Linux.
The
"Web caching" SA2100 (P4535A), SA2150 (P4651A), SA2200 (P4536A) and SA2250 (P4537A)
machines are equiped with a RedHat based distribution of Linux and of the Inktomi software. The hardware base is a LP1000r.
Hp doesn't make UPS anymore, but has a world-wide agreement with APC. APC distributes a free software (no cost, not open-source), to manage its UPS under Linux. It's available at
http://www.apcc.com/products/management/pcp_linux.cfm.
This card can support up to two displays. These displays can be configured in two different ways.
For uniquely independent screen operation, you can configure displays for "multi-screen" work. In this mode, the X server reports two independent screens for client connections. These are numbered using the "minor" display number (e.g. <hostname>:0.0 and <hostname>:0.1). There is no support to move client windows between the screens.
The other configuration option uses the XINERAMA extension. This configuration links multiple screens to behave as one logical screen. In this mode, the X server reports one screen for all client connections. X clients can move between screens and the overall screen resolution is doubled width or height depending upon the desired setup.
The following examples demonstrate these possibilities through the configuration file
/etc/X11/XF86Config-4 :
To enable the XINERAMA extension, you may use one of two ways. The first is by adding a command-line option to the X server. This can be done as follows:
#startx -- +xinerama
The second method is by adding an option to
/etc/X11/XF86Config-4 :
The Matrox driver supports several XFree86 options through the file
/etc/X11/XF86Config-4.
The example below describes two such options that contribute to improved graphics performance:
Section "Device"
Identifier "Matrox G450"
Driver "mga"
# Use this option to enable AGP 2X mode
# In default mode AGP 1x, the host to graphics bandwidth is about 500 MB/sec
# This will increase the host to graphics bandwidth to about 1 GB/sec
# This mode is recommended by HP for X2000/X4000
Option "AGPMode4x" "on"
# Use this option to enable AGP 4X mode
# This will increase the host to graphics bandwidth to about 2 GB/sec
# This mode is recommended by HP for X2000/X4000
EndSection
To enable multi-screen with FireGL4, set the monitor resolution to a supported multi-screen resolution like 2560x1024 in the
/etc/X11/XF86Config-4 file.
The firegl driver recognizes this and sets up multi-screen when the Xserver starts. Make sure you have two monitors set up and connected to the two DVI ports on the FireGL4 card.
The firegl driver supports several XFree86 options through the file
/etc/X11/XF86Config-4.
Values indicated in the example correspond to the default values.
Section "Device"
Identifier "FIRE GL2"
Driver "firegl"
Option "Overlay" "off"
# Use this option to enable limited overlay plane support.
# NOTE: currently this is not intended to support the running of applications in the overlay planes.
# Number of 4k DMA buffers used per OpenGL context.
# number of 4k DMA buffers used per OpenGL process by texture manager.
# parameter command line passed to firegl kernel module
# Example:Option "KernelModuleParm" "maxlockedmem=64;agpgart=2"
# Option list:
# maxlockedmem: Maximum locked DMA memory
# Maximum locked display list memory
# Value 0, use firegl built-in support, value 2, disable firegl built-in AGP GART support if an agpgart module is loaded, it will be used, value 3, disable AGP GART support
# agp_try_unsupported: try unsupported chipsets
Option "OffScreenPixmaps" "no"
# enables the use of frame buffer memory to save/generate pixmaps.
Option "BIOSInfo" "no"
# enable BIOS version output to the XFree86.0.log file
Option "HW Cursor" "yes"
# Enable HW Cursor
Option "enable DVI" "no"
# enable DVI connector(s) (always enabled in dual mode (Fire GL3/4)
Option "no_accel" "no"
# Disable XAA hardware acceleration
Option "NoDDC" "no"
# disables PnP Monitor functionality such as automatic mode configuration (This important for Fire GL3/4 users who want to work with dual screen modes)
Option "AGPSpeed" "-1"
# 0 for AGP off, 1 for AGP 1x, 2 for AGP 2x, 4 for AGP 4x, -1 for "Query Chipset"
#
EndSection
To use a Cirrus Logic GD 5465 AGP card, with a version below Xfree86 3.3.3, you have to use an option in the file
XF86Config : Option "xaa_no_color_exp".
Specifications of that card should be consulted on Elsa web site.
This card is equiped with an hardware OpenGL accelerator.
Under Linux, there is an OpenGL compatible layer called Mesa.
This layer begins to support hardware accelerators, and among them the 3DLabs chipset which is on Elsa Gloria cards.
This card is only supported by the 3.3.6 version of XFree86 and upper. Nevertheless, even in that version, this is a preliminary support, which isn't as stable as the Frame Buffer mode.
On the other hand, to be able to install a RedHat 6.1 version, you should do that in text mode, because the server provided (3.3.5) doesn't support this card.
If you have a dual-boot system, booting first on Windows, and initialize the card through its driver seems to improve the operations then under Linux (warm reboot).
Versions of XFree86 above 4.0.2 also offer the support of this chipset.
These cards are only supported with a specific X server XFCom_i810/5 downloadable in both format
RPM or tar.gz
and a complementary module for the kernel agpgart, downloadable in both format
SRPM or tar.gz (old).
To summarize, once the X server installed, the module compiled and installed, it's sufficient to modify with the following parameters the file
/etc/X11/XF86Config :
You have to note that the agpgart module provided by Intel should replace the one delivered in the kernel so that it works. You then have to reinstall it, particularly when a kernel update occurs.
It's possible to use XFree86 in dual-head mode. The following example of configuration is provided by S. Eranian for a Matrox G200 AGP and a ATI Rage 128 PCI card. "The key element is that you must specify the PCI id for both cards."
# /etc/X11/XF86Config-4
# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# SubSection "extmod"
# Option "omit xfree86-dga" # don't initialise the DGA extension
# EndSubSection
Load "extmod"
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx"
# Load "dri"
EndSection
Section "DRI"
Mode 0666
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/opt/fonts"
# The module search path. The default path is shown here.
ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
# Option "Protocol" "PS/2"
Option "Protocol" "imps/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "HP4331D"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 30-82
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 48-150
++vsync
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xf86config:
Section "Device"
Identifier "G200"
Driver "mga"
BusID "PCI:4:0:0"
#VideoRam 8192
VideoRam 8192
# Option "SWCursor"
# Option "ShadowFB"
# Option "PciRetry"
# Insert Clocks lines here if appropriate
EndSection
Section "Device"
Identifier "permedia2"
Driver "glint"
BusID "PCI:1:8:0"
#VideoRam 4096
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection
Section "Device"
Identifier "rage"
Driver "r128"
BusID "PCI:01:08:00"
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "rage"
Monitor "HP4331D"
DefaultDepth 16
Subsection "Display"
Depth 8
Modes "640x480" "800x600" "1024x768" "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
# Modes "800x600" "1024x768" "1280x1024"
Modes "1024x768" "1280x1024" "640x480" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
# Modes "640x480" "800x600" "1024x768" "1280x1024"
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Identifier "Screen 2"
Device "G200"
Monitor "HP4331D"
DefaultDepth 16
Subsection "Display"
Depth 8
Modes "640x480" "800x600" "1024x768" "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
# Modes "800x600" "1024x768" "1280x1024"
Modes "1280x1024" "640x480" "800x600" "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "640x480" "800x600" "1024x768" "1280x1024"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Screen "Screen 1"
Screen "Screen 1" "" "" "" "Screen 2"
Screen "Screen 2" "" "" "Screen 1" ""
# Screen "Screen 2"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
To use the D6692A card, you need to use a 2.1.122 kernel at least.
Previous kernels didn't handled correctly the shared IRQ between the network and SCSI parts of the card. In particular, a standard RedHat 5.2 version doesn't allow to the network part to be supported. You have to update your kernel with a recent one (preferably 2.4.16) and the distribution with the complementary packages needed.
A driver is provided by Intel to support its cards based on the PRO/100 model, in its various versions. Depending on the model, you'll have a better support with this one, or with the standard eepro100 provided in the Linux kernel. It should allow a systematic support of the latest models. It's available at
ftp://download.intel.com/df-support/2896/eng/e100-1.6.22.tar.gz
If you use the e100 driver, you could also use the ANS tools (Advanced Network Services) allowing you to do AFT (Adapter Fault Tolerance), ALB (Adaptive Load Balancing, including AFT), FEC or 802.3ad (Link Aggregation). For more details on these modes, please refer to the file associated with the file to download called
readme.txt.
It's available at
ftp://download.intel.com/df-support/2895/eng/ians-1.4.27.tar.gz
To use this functionality, proceed as follow:
#ifconfig ethx down # For all adapters of the team
#ianscfg -a -tTEAM # Create the team
#ianscfg -C -tTEAM -Mmode # Determine the mode of the team
#ianscfg -a -tTEAM -methx # Add the interface ethx to the team
#ianscfg -a -tTEAM -vveth0 # Create the virtual interface veth0 associated to the team
#ianscfg -c -tTEAM # Activate the team
#ianscfg -w -f/etc/ians.conf # Save the configuration
#ifconfig veth0 xxx.yyy.zzz.ttt ... # Configure the virtual interface as usual
The Intel Pro/100 and 3Com 3C59x network cards used in majority in HP machines support the Wake on Lan function (WOL). All the details on
http://www.scyld.com/expert/wake-on-lan.html,
The chipset 2EM (Vendor id: 125d - device id: 1978)
is supported in 2.2.14 kernel and upper. Version 3 (Vendor id: 125d - device id: 1998)
on the other side is supported in 2.2.19pre5 kernel and upper. Cf : the site of the
maestro3,
driver, the
AlsaRem.
project
(version >= 0.5.10)
driver, and the commercial software
Open Sound System
. The latest version of the ESS Maestro driver is available from the
reference site.
The Alsa project has for primary goals to develop drivers to support sound cards in Linux, being fully compatible with current OSS drivers, bringing more functionalities and supporting more hardware.
All the information on this project, as well as sources under the GPL license, are available from their home page
http://www.alsa-project.org
On that machine, the Bios doesn't give the right amount of memory which is in the machine to Linux. You need to use a line such as
append="mem=xxxM" at the begining of /etc/lilo.conf
where xxx is your RAM in MB.
The support of "big size" IDE disks (for example, 27 GB disks provided for the XU 800) on these machines needs a kernel 2.2.15 at least.
If you intend to use both the sound chipset and a PCMCIA card in this laptop, in order to avoid conflicts at input/output ports level, you'll have to modify the file
/etc/pcmcia/config.opts
to change the line 6 to
It is recommended to not launch
/sbin/halt
under X11. The integrated modem card is not supported under Linux
(ESS ES56CVM-PL).
The installation of a RedHat 6.2 distribution gives a problem when rebooting the system, at the PCMCIA initialisation. You have to install the latest version of the pcmcia-cs package at
ftp://pcmcia-cs.sourceforge.net/pub/pcmcia-cs/
If you use the Adaptec APA-1480 SCSI PCMCIA card, It must be in the top slot. If you don't put it in the top slot, the card that is in the top slot will not work. Also, even though the APA-1480 was supported long before this, the first time it worked on an Omnibook was kernel 2.2.16. There was some problems with the earlier cardbus drivers and the Omnibook.
(Information from Bruce Kives)
reboot
doesn't work correctly on this machine, which remains blocked instead of rebooting. Use the poweroff button to reset it.
(Information from Yuthay Yean)
B models use Ultra 3 SCSI sym53c1010 (A models use ultra 2).
To use the native SCSI bus of this machine, it"s necessary to use the sym53c8xx driver with a version upon 1.6c. A driver disk for RedHat distributions is available for versions
6.1, 6.2 and 7.0.
For the SuSE 7.0 distribution, you have to enter the manual mode to load the driver, as autodetection doesn"t work correctly.
In order to use the native SCSI controler you need to disable in the Bios the option "Reserve PCI Bus Numbers", in the menu PCI Device Setting (Indication of Gillynn Couch). Models P3493B and P5364B are equiped with an additional NetRaid 1M card.
To use the native SCSI bus of this machine, it"s necessary to use the sym53c8xx driver with a version upon 1.6c. A driver disk for RedHat distributions is available for versions
6.1, 6.2 and 7.0.
For the SuSE 7.0 distribution, you have to enter the manual mode to load the driver, as autodetection doesn"t work correctly.
In order to use the native SCSI controler you need to desactivate in the Bios
the "reserver PCI Bus #s", in the menu PCI Device Setting.
The PS/2 system doesn't work correctly with a RedHat 6.1 or 6.2 distribution. In order to correct that you need to either put the machine in MPS 1.1, in the BIOS, or use a kernel above 2.3.47 in MPS 1.4 mode.
The network card doesn't work correctly with the kernel of the RedHat 6.2 distribution.
These machines are equiped with a Pentium IV processor, supported by kernels 2.2.18/2.4.0 and above. The RedHat 7.0, Mandrake 7.2 and TurboLinux 6.1 distributions, e.g., can be installed correctly on this kind of machines.
Attention, the XF86_SVGA server works correctly with this mother board embedded version only above XFree86 3.3.5, due to the use of different frequencies (In particular, use the updates for
RedHat 5.2/6.0).
To be able to boot with the RedHat 5.1 boot disk, and to have the support of the 3C905B-TX card, you need to do the following :
Log as root. Go in the home directory (~root)
#cd ~
Put there the 3c59x.c source module for the 3Com card
#ncftp ftp://ftp.scyld.com/pub/network/3c59x.c
Compile it
#gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -c 3c59x.c `[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS`
put the RedHat 5.1 floppy boot disk in the drive
you have to copy the initrd.img file from the floppy disk
#mcopy a:initrd.img /tmp
then uncompress it
#gzip -cd /tmp/initrd.img > /tmp/initrd.ext2
Mount the "file" filesystem thus obtained
#mount -t ext2 /tmp/initrd.ext2 /mnt/floppy -o loop
uncompress the modules provided
#gzip -cd /mnt/floppy/modules/modules.cgz > /tmp/modules.cpio
extract the modules
#cd /tmp ; mkdir modules ;
cd modules ; cat /tmp/modules.cpio | cpio -i
Copy the new updated module for the 3Com card
#cp ~/3c59x.o .
recreate the compressed cpio file
#ls | cpio -o | gzip -c9 > ../newmodules.cgz
replace the modules by their update
#cp ../newmodules.cgz /mnt/floppy/modules/modules.cgz
unmount the "file" filesystem
#umount /mnt/floppy
compress the "file" filesystem
#gzip -c9 /tmp/initrd.ext2 > /tmp/initrd.img
copy it on the floppy disk
#mcopy /tmp/initrd.img a:
This driver is provided with latest RedHat 7.1, 7.2/Mandrake 8.0, 8.1 distributions, as kernel patches, but isn't included yet in the standard 2.4 kernel.
To be able to boot with a RedHat distribution (>6.1), and to have the recognition of a peripheral non supported in standard in the distribution, you need to do the following :
Download the delopment toolkit to create driver disk for the RedHat distribution at the following address:
http://people.redhat.com/dledford
Install the sources of the driver in a directory and follow the instructions of the README file of the kit to create the modules necessary for the various kernel of the distributions.
Log as root. (~root)
put the RedHat floppy boot disk to modify in the drive
you have to copy the initrd.img file from the floppy disk
#mcopy a:initrd.img /tmp
then uncompress it
#gzip -cd /tmp/initrd.img > /tmp/initrd.ext2
Mount the "file" filesystem thus obtained
#mount -t ext2 /tmp/initrd.ext2 /mnt/floppy -o loop
create a temporary directory
#cd /tmp ; mkdir modules ; cd modules
uncompress and extract the modules provided
#gzip -cd /mnt/floppy/modules/modules.cgz | cpio -ivdum
Copy the new updated module. In case you add it, remove also other useless modules of the same size.
#cp ~/.../mod_devel_kit/rhxx/modules/x.y.z-iBOOT/module.o x.y.z-iBOOT
Also in case you add it, copy the modules needed for the installed kernel during reboot, and adapt the files pcitable, module-info and modules.dep by using the information provided in the development kit.
#cp -a ~/.../mod_devel_kit/rhxx/modules/x.y.z-i ~/.../mod_devel_kit/rhxx/modules/x.y.z-ismp .#vi /mnt/floppy/modules/pcitable /mnt/floppy/modules/module-info /mnt/floppy/modules/modules.dep
recreate the compressed cpio file
#find * -print -depth | cpio -ov -H crc | gzip -c9 > /mnt/floppy/modules/modules.cgz
unmount the "file" filesystem
#umount /mnt/floppy
compress the "file" filesystem
#gzip -c9 /tmp/initrd.ext2 > /tmp/initrd.img
copy it on the floppy disk
#mcopy /tmp/initrd.img a:
The LH4 doesn't seem to work correctly when not in Raid. Even with the latest Bios available at the time of the test (16.00), the problem remains. If you desactivate the Raid management, during the boot, the ncr53c8xx driver in Linux detects 4 controlers instead of 2 and boot doesn't end. To avoid that, you have to activate the Raid in the Bios and use each of the disk in Raid0 mode, which is quite the same as the solution without Raid at all.
This machine can not be installed correctly with RedHat 7.1 or Mandrake 8.0 distributions.
Some NetRaid cards, as well as the chipset integrated on the LH3 and LH4 mother boards are supported by recent version of the Linux kernel (2.0.36/2.2.19/2.4.16 typically - don't use 2.0.37/38).
For the RedHat 5.2 distribution, it's not possible to install the system on this type of controler, because it's not detected by the installation program. You have to use a specific
floppy disk
. This floppy disk should be used as input to the rawrite tool, for example. It works for systems with less than 1 GB of memory.
For the RedHat 6.0 distribution, you have to manually declare the existence of this card as a supplementary SCSI adapter, in order to use it directly during the installation. The megaraid driver isn't automatically detected.
To avoid strange messages during the boot printed by the megaraid driver, it's necessary to recompile it with the option -DHP (before kernel 2.4.2) or -DMEGA_HP_FIX (after) or even nothing now (> 2.4.13).
For the RedHat 6.1 distribution, the megaraid driver provided by the kernel does support only the first logical drive. In order to obtain the others, please recompile a 2.2 standard kernel.
You have to note that the integrated card of the LH3/4 realises a software parity checks and performs thus less efficiently than the NetRaid daughter cards. On the other side, LH3000/6000 are equiped with an integrated card doing hardware checks.
In the driver provided by AMI there is a Raid management tool megamgr, usable within Linux, and equivalent to the tool included in the software embedded on the controler. It's downloadable from
http://www.ami.com/support/prodsearch.cfm?InpProdID=17
Kernel patches and utility to monitor logical/physical drives on MegaRAID (NetRAID) Adapters have been made by Katsuyuki Yumoto. "This can detect physical drive failure, send E-Mail and syslog it. NetRAID-1Si/3Si, embeded NetRAID and NetRAID-1M/2M are okay to use. Don't use this for NetRAID-4M."
You'll find the code at this address
http://www.jpn.hp.com/biz/products/pcserver/linux/tech/megascan-20011113.tar.gz.
Use with care as the versions I tried have conducted to kernel panic.
The NetRaid 1Si card isn't recognized correctly by RedHat 7.2.
You'll have data corruption by using these cards with the standard kernel of the RedHat 7.1 distribution. You necessaraly need
this driver disk
to use it correctly. This has been seen with both H.01.07 and H.01.08 firmware. Sources of the patch required to make this card work correctly with kernels 2.4.x (x < 7) are available here
http://www.HyPer-Linux.org/HP-HOWTO/mirror/Software/mega115hp.tgz.
The same problème is true with the Mandrake 8.0, but the 8.1 has the right driver.
These cards are equiped with a StrongARM Chipset and correspond to the Adaptec card AAC-3642. A driver is available at
http://domsch.com/linux.
The RedHat 7.0 includes in standard the driver even if that release of the kernel doesn't handle it normaly. Information are also available on the HP Navigator L.19.00.
On these machines, when the second ide bus is probed by the kernel, there is a timeout, which doesn't hurt, but is useless. To avoid it, just add to your lilo.conf the following line :
Some of the PCs provided by HP are equiped with a multimedia keyboard. You may use the additional keys thanks to the HotKeys daemon
(Cf: http://freshmeat.net/projects/hotkeys/)
The PA-Risc range is achitectured around a processor designed and realised by HP. First versions were produced in 1987. Currently the versions are named
PA-8000 (8200, 8500, ...).
The initiative to port Linux on the PA-RISC architecture was taken during the Atlanta Linux exhibition in October 1998.
HP has announced in February 1999 its sponsorship to to this port of Linux. This port is a native one, which is different from a preceding project which used MkLinux on machines based on PA-7200.
The work is currently done with
The Puffin Group
bought by Linuxcare, and more precise information on the status may be found on the
official Web site.
In particular, interesting starting points may be found on
http://www.parisc-linux.org/faq.html and http://www.parisc-linux.org/hw.html.
Consult also ESIEE site (712 on Linux/PA) which participates actively to the port :
http://mkhppa1.esiee.fr/en/
The last version is 0.9.3. It supports the following systems
L1000, L2000, A500, A180, B, C, J, D, R, 742, 725, 735, 755, 705, 710, 720, 730, 750, 712, 715.
This version supports 32 and 64 bits modes, SMP (1-4 way), RAM up to 16 GB, HP-UX compatibility, X-Window, KDE, Gnome, 80% of Debian packages.
Debian has accepted PA-RISC as a supported architecture for the upcoming Debian GNU/Linux 3.0 (woody) stable release.
http://www.debian.org/ports/hppa/.
HP, as a founding member of the IA-64 Linux project, works on the port of the kernel, the initial version of gcc, gas, ld and emacs. Another major contribution of HP to this project is the availability of the software development kit available at
http://www.software.hp.com/ia64linux.
It allows to develop applications as well as kernel code on Linux/IA32 for IA64 platforms and moreover to test them through a simulator.
You may find some useful tools for IA-64 architecture on the ftp site of the
HP labs.
The following key features which are all unique to IA-64 are described by Stéphane Eranian:
IA-64/EPIC goes beyond pure VLIW. Code is portable from one implementation to another. The timing dependencies are protected by stop bits. This allow unmodified code to run with no recompilation. Of course better performance is achieved by recompilation.
Very large register set: 128 floating point, 128 general registers.
Predication: a very elegant way of removing the cost of branch in if-then-else statments.
Speculation: a elegant mechanism to hide memory access latency by allowing load instructions to be hoisted from the location where they are needed without risking unwanted faults (like NULL pointer).
Register Stack Engine: a mechanism similar to the register window found a SPARC but much more powerful and dynamic. The window size varies on demand. Take advantage of the large register set and is used on function calls.
Hardware support for software pipelined-loop: this is the most powerful construct which takes advantages of : predication, large registers. This is a renaming scheme for general, floating point or predication registers which allows one to unroll loops without incuring the code expansion seen on other architectures.
All the multmedia-type instructions are support in IA-64 mode.
IA-32 hardware emulation: possibility to run unmodified Linux/ia32 applications on Linux/ia64 (requires some OS support).
On the system level: full 64 bit address space. Hardware walker to TLB misses.
Banked registers (16 of them) to help speed up interrupt processing.
Stéphane Eranian and David Mosberger
will publish begining of 2002 a book called
'Design and implementation of the Linux/ia64 kernel' (Prentice Hall)
To boot Linux on this kind of machine, you need to type in the initial environment
Verify the correspondance between logical drives and peripherals
Shell>map
Go to the logical drive corresponding to the CD-ROM
Shell>fs1:
Boot the system
fs1:>eli linux
Install your distribution as usual
The only difference is that you need to create a so-called 'EFI' partition of type FAT32 (Id:b) of around 128 MB. This partition will be mounted as /boot/efi later
After the installation, reboot and redo the initial sequence, verifying again the correspondance (which may have changed because the CD-ROM isn't available anymore, the numbers indicating the order of detection of bootable devices)
Shell>mapShell>fs0:Shell>dir
Verify the name of the kernel to boot
fs1:>eli linux-up
To automize the boot, you need to remove all options from the EFI boot except the EFI Shell and create a file in the EFI partition (/boot/efi) called startup.nsh containing:
fs0:
eli linux-up
fs0:
(From information provided by S. Eranian. Only mistakes are mine :-)
David Mosberger
reports that recent versions (7.2) of Red Hat install a GPT partition and that you must enable the following two config options for the kernel to recognize them:
HP proposes now NCD X terminals to replace the Envizex/Entria range.
The HP X terminal range (Entria, Envizex) is usable with a Linux server. More over, a Linux server may be a boot server for X terminals. To do it, a certain number of operations are mandatory.
We suppose we have a HP-UX machine named hpux, on which is installed Enware, a Linux server, named linux and an X Terminal with MAC address 08:00:09:db:8d:1c. The gateway on the network is at IP address 192.168.1.254, and the DNS name server at 192.168.1.1.
Commands to do are :
Enware Home Directory
hpux #cd /opt/hpxt/enware/xthome
Creation of a tar archive of this software
hpux #tar cvf ~ftp/en.tar * .??*
Download of the tar archive
linux #ftp hpux
Connected to hpux.
220 hpux FTP server (Version wu-2.5.0(1) Wed Aug 25 12:50:08 EDT 1999) ready.
Name (ftp:Root):ftp
331 Password required for ftp.
Password:(type your mail address here)
230-
[...]
230-
230 User ftp logged in. Access restrictions apply.
ftp>lcd /tmp
Local directory now /tmp
ftp>get en.tar
200 PORT command successful.
150 Opening BINARY mode data connection for en.tar (57638340 bytes).
226 Transfer complete.
57638340 bytes received in [...]
ftp>quit
[...]
Creation of the target directory on the linux machine
linux #mkdir -p /tftpboot
Go there
linux #cd /tftpboot
untar the archive
linux #tar xvf /tmp/en.tar
Launch the X Font Server working on port 7100
linux #/usr/X11R6/bin/xfs -port 7100
Creation of the bootpd configuration file
linux #cat >> /etc/bootptab << EOF
global.prof::sm=255.255.255.0::ds=192.168.1.1::gw=192.168.1.254::ht=ethernet::bf=bin/C3253A: # Adjust to your X-terminal
tx1:hd=/tftpboot:tc=global.prof:ha=080009db8d1c:ip=192.168.1.100:
EOF
Install bootpd say from http://rpmfind.netlinux #rpm -Uvh bootp-2.4.3-7.i386.rpm
Verify the existence of such a line in /etc/inetd.conf, and restart if needed the server by killall -1 inetd
linux #grep bootps /etc/inetd.conf
bootps dgram udp wait root /usr/sbin/tcpd bootpd
Now enkoy your X terminal by booting it
For a more detailed description, as well as the software related to that operation, consult also the page
http://www.cb3rob.net/~sven/xterm.
Printers may be connected directly to a machine through either a parallel port (generally), or a serial port, or even (more recently) through a USB port.
They may also be directly wired to the network, for a global access; this is done thanks to a card put in a slot of the printer, or through the connexion of the parallel port of the printer to a sharing network box.
HP provides such boxes, called JetDirect, which allow thus to share personnal printers on the network, directly, without going through a machine.
They exist for various network topologies (10 BT, 10/100 BT, Localtalk, 10B2) and offer the ability to access to the printer directly from machine which like Linux support the LPD protocol, by using a remote printer in the
/etc/printcap
file. The name of the queue to use is then
raw.
An example of
/etc/printcap
file allowing to access to a printer, equiped with such a box or card, named lj4000 on the network is given below :
The configuration access to the box is done either through the
WebJetAdmin
tool provided also under Linux now, or by the
telnet
command. The default address of these products is 192.0.0.192. To connect to them initially, you just have to add an IP alias on your network interface, typically by :
#ifconfig eth0:0 192.0.0.1
and a route to that network (if not automatically created) typically by :
#route add -net 192.0.0.0
The access to the equipment is thus done simply by :
#telnet 192.0.0.192
Please pay attention to have only one such equipment on the network, at the same time, or you'll have duplicate IP addresses, which always causes problems. Note that HP manageable network equipments also use the same default address.
The reading of the
IP Alias mini HOWTO
may be useful if you don't understand the previous paragraph :-).
It is of course possible to access through the network to an HP printer attached and declared directly on a Linux machine, thanks to the
lpd
service for the other Unix clients, through
SaMBa
for the clients of Microsoft systems (Win9x ou WinNTx) or through
NetAtalk
for the MacIntosh clients.
At last,
SaMBa
offers a tool, smbclient,
which allows to print from a Unix/Linux machine to a printer wired directly on a Microsoft based PC, without any need to use a JetDirect system.
All the details useful to realize this operation are described in the example file of
smbprint provided with the
SaMBa
package and on the page http://www.medasys-digital-systems.fr/linux/samba-truc.html.
Communication between a Linux machine and a printer needs also, outside a network dialog, a discussion with an exchange language between the two elements.
There are a lot of languages of that sort, such as
PCL, Postscript or HPGL.
To be able to print correctly, the tool providing the datas to print has to generate code known by the printer.
Filters exist which allow to easily transform an output in one given format to another one.
Thus the
Ghostscript
software authorizes the transformation of Postscript source in a great variety of output formats, as indicated by its invocation in the 'Available devices' part :
This represents only the output formats compiled in the program.
Other are also available.
You may find a complete list of all the printers known by this software at
http://www.cs.wisc.edu/~ghost/printer.html.
The main tool available in Linux environment to manage scanners is
SANE
(Scanner Access Now Easy).
This software provides in particular a driver for HP scanner management:
hpbackend.
The following table provides all information on the support for this hardware by Linux.
To use these peripherals, you have to compile SCSI support with your kernel, and turn on mass storage device in USB support. Then mount the /dev/sdxx device as usual.
The following table provides all information on the support for this hardware by Linux.
This product is a scanner, able to send the result of the digitalisation through e-mail, by sending the digitalised document as an attachement in PDF format.
It may so well be used with a Linux (or other) mail server (sendmail, postfix, ...), as well as with clients reading their messages under Linux, providing they have a tool to display PDF file such as
Acrobat Reader or xpdf.
The Digital Sender can also send images as black and white or colour TIFF files. The black and white images work fine, however, there is a problem with the coloured TIFF files. These are sent in an obsolete format which is not supported by
libtiff,
which is the basis of support for the TIFF format for nearly all Linux software. This means that you cannot directly open colour TIFF images created by the Digital Sender using Linux software (e.g. The GIMP, ImageMagick).
Most HP SCSI tape drives (DAT 1, 2, 3, 4, DLT, LTO) work with Linux. the driver file to use is /dev/st0 for the first drive, /dev/st1, for the second...
These systems are supported in a mixed environment Windows NT/2K, HP-UX 11.0 and Linux. They are connected through Fibre Channel controlers to the SAN. Among all FC cards supported on Linux, HP supoprts those provided by
Emulex and QLogic.
HP sells a Linux version of the management software for these arrays. Supported models are
VA7100 (A6183A), VA7400.
Here are the configurations supported by HP for these Storage Systems:
Redhat 6.0/6.1
Qlogic QLA2100F or QLA2200F with driver V2.23
Private Loop or Direct Fibre Attach
No boot support
XP256 has to have firmware >= 44.14.00 Mode 00
For direct attach XP512/48 has to have firmware >= 11.22.00 Mode 00
For attachment to a switch XP512/48 has to have firmware >= 12.19.00
Redhat 6.2
Emulex LP8000 with driver V4.10g
Private Loop or Direct Fibre Attach
No boot support
For attachment to a switch use Brocade 2400/2800 with firmware >= V2.1.9f)
XP512/48 has to have firmware >= 12.19.00 Mode 00
Khalid Aziz
reports that there may be a problem with XP512 support of Linux due to a hole in LUN numbers. If the LUNs were numbered continuously, you would see all LUNs. Some folks in HP have written patches for this. Essentially all that is needed is to add an entry in device_list[] in scsi_scan.c for the XP512 and set the flag BLIST_SPARSELUN. The entry would look something like:
{ "HP", "XP512", "*", BLIST_SPARSELUN}
The first field is the vendor name as reported by XP512 and second
field is the model name as reported by XP512. These two need to match
what XP512 returns in Inquiry command, exactly.