Red Hat Linux 7.2: The Official Red Hat Linux Alpha Installation Guide
Prev | Chapter 1. Getting Started | Next

# The SRM Firmware Console

Before you start to install Red Hat Linux on an Alpha, you will need a basic understanding of the SRM console, what it does, and the information it can provide.

SRM is a UNIX-like firmware console used by many Alpha systems to boot into an operating system. When the system is booted, the SRM console is displayed as a blue screen with a prompt. The prompt looks like `P00>>>` (the 00 indicates the primary processor). On multi-processor machines, the prompt could be `P01>>>`, `P02>>>`, etc.

We recommend that you upgrade your SRM firmware to the most recent version available. Use the `show version` command at the SRM console prompt to see what version of SRM you are running. For more information about SRM firmware upgrades, see the following URL:

    http://ftp.digital.com/pub/DEC/Alpha/firmware/

Additional information on the SRM console can be found at the SRM Firmware HOWTO at the following URL:

    http://www.linuxalpha.org/faq/srm.html

The SRM console provides important system information which you will need to use when installing Red Hat Linux and when administering your Alpha.

## SRM Device Names

To see information about system devices that SRM recognizes, use the following command:

    show device

The `show device` command will display a list of devices. You can alternatively use the shorthand `show dev` or a command such as `show dev dk`, which will only display SRM-recognized devices that begin with `dk` (in other words, all SCSI disk drives).

SRM does not identify devices the same way as Red Hat Linux. As an example of SRM's device-naming syntax, the output provided after a `show device` on a Compaq AlphaServer ES40 will look similar to the following:

    P00>>> show device
    resetting all I/O buses
    dka0.0.0.4.1              DKA0              RZZDD-LS 0306
    dqa0.0.0.15.0             DQA0              TOSHIBA CD-ROM XM-6302B 1017
    dva0.0.0.1000.0           DVA0
    ewa0.0.0.6.1              EWA0              00-00-F8-1B-42-D5
    pka0.7.0.4.1              PKA0              SCSI Bus ID 7

The following list provides explanations for the most common SRM device names:

dka0

  The `dk` is SRM's designation for a SCSI device. The `a` after the `dk` signifies that it is the first SCSI controller; the `0`indicates the SCSI ID number. So, `dka0`, `dka100`, `dka200` and `dka300` are all SCSI devices on the first SCSI controller. Their SCSI ID numbers are, respectively, 0, 1, 2 and 3. (Note that the `a` and numeric portions of the device identifier work the same way for the other devices; they identify the ordering of the same type of device and provide an ID number.)

  If these four devices are all SCSI hard drives, Red Hat Linux would refer to the same four devices as `/dev/sda`, `/dev/sdb`, `/dev/sdc` and `/dev/sdd`.

  If your Alpha has a SCSI CD-ROM (instead of an IDE CD-ROM), usually the CD-ROM drive device will be on the second SCSI controller. The SRM device name will then be something like `dkb0` or `dkb500` (`b` for the second SCSI controller, followed by the SCSI ID number). If your machine is set up like this, then Red Hat Linux would refer to the CD-ROM drive as `/dev/scd0`.

  | Identification of CD-ROM Drives
  | If the device is a CD-ROM drive, the entry in the third column will identify it as a CD-ROM or be something like `CD-224E` (older Alphas may identify a CD-ROM drive as `RRD46 1337` or something similar).

dqa0

  The `dq` is SRM's designation for an IDE device (for example, an IDE hard drive or an IDE CD-ROM drive). As in the previous example, the `a` indicates that it is the first IDE device, and the `0` is the device's ID number.

  Red Hat Linux would refer to the same IDE device as `/dev/hda`.

  If your Alpha has an IDE hard drive and an IDE CD-ROM, then SRM will refer to the hard drive as something like `dqa0` and to the CD-ROM drive as something like `dqb0` or `dqb500`. Red Hat Linux would refer to the same devices as `/dev/hda` and `/dev/hdb`.

dva0

  The dva0 device name is the floppy disk drive; Red Hat Linux would refer to the floppy disk drive as `/dev/fd0`.

ewa0

  The ewa0 device name is the network card; if it is an Ethernet network card, Red Hat Linux would refer to it as `eth0`.

Examples of other SRM device names include `mka0`, the first SCSI tape device, and `pka0`, a SCSI host adapter for the first SCSI bus.

Before you begin the installation process, look at the list provided in response to `show device` on your Alpha's SRM console. Write down how SRM refers to the devices in Table 1-1.

Table 1-1. SRM Device Names for your System

Device | SRM Device Name
--- | ---
3.5-inch diskette drive (usually dva0) |
Hard drive |
CD-ROM drive |

In this document, we have used the SRM device name dka0 to refer to the hard drive and dqa0 to refer to the CD-ROM drive.

You must choose one of these devices from which to boot Red Hat Linux, during the installation process and every time you wish to boot your machine, unless you set up your SRM boot parameters to boot automatically.

| Devices that SRM Can Not Detect
| You may have a SCSI adapter, IDE drives, or networking hardware that is compatible with Red Hat Linux but is neither OEM Digital or Compaq hardware or otherwise detectable by the SRM console. These types of hardware will not be displayed after the `show device` command on the SRM console. Using unrecognized hardware may not stop you from running Red Hat Linux on your Alpha machine, but you must boot from a device recognized by the SRM console.

## SRM Boot Parameters

Certain SRM system parameters designate information needed to boot an operating system. These parameters include the device from which SRM will boot, which kernel to use, and what filesystem it will use as the root filesystem.

To see the boot parameters recognized by SRM, use the following command:

    show boot*

For example, the output provided for a `show boot*` on the SRM console might look like the following:

    P00>>> show boot*
    boot_dev                       dka0.0.0.4.1
    boot_file                      3/boot/vmlinuz
    boot_osflags                   root=/dev/sda3
    boot_reset                     ON
    bootdef_dev                    dka0.0.0.4.1
    booted_dev                     dka0.0.0.4.1
    booted_file                    3/boot/vmlinuz
    booted_osflags                 0

The `bootdef_dev` parameter specifies the device from which SRM will try to boot. In this example, SRM will boot from `dka0`, which is the first SCSI hard drive.

The `boot_file` parameter sets the partition, location, and name of the kernel file from which SRM will boot. In this example, `boot_file` is set to boot from the `vmlinuz` kernel, which is located in the `/boot` directory on the third partition of the hard drive. The `boot_file` variable is equivalent to the `-file` value for `boot` on the SRM command line.

The `boot_osflags` parameter can specify which filesystem will be used as the root filesystem. Note that if this parameter is used, it requires Red Hat Linux (instead of SRM) device naming conventions. The `boot_osflags` variable is equivalent to the `-flags` value for `boot` on the SRM command line.

You can use the `set` command to change the boot parameters. After you have finished the installation, you will need to set these variables to the right values, if you want your Alpha to automatically boot Red Hat Linux. Setting the boot parameters to automatically boot Red Hat Linux is covered in the section called Setting SRM Boot Variables in Chapter 3.

To set a boot parameter, use the following command:

    set variable "value"

When you are setting a value for an SRM console parameter, integer values and single word string values do not have to be in quotes; however, since multiple word string values need to be quoted, it is recommended that you enclose all string values in quotes.

To clear an SRM console variable, use the following command:

    set variable ""

In the above command, `variable` is the name of the SRM console parameter, and the empty quotes ("") denote a blank value. Some integer values cannot be cleared, but can be set to 0. Also note that some SRM console variables are integer in value, but Boolean in nature.

## Displaying System Information Using SRM

The SRM console can provide more information about your Alpha. Use the following command:

    show config | more

Note the video card on your system. The video card information will be helpful to you if the Red Hat Linux installation program has any trouble probing your video card.

## Booting the Installation Program

Your Alpha system will probably be able to boot the Red Hat Linux installation program directly from the Red Hat Linux CD 1. If your Alpha can not boot the installation program from the CD-ROM (or if you want to perform a hard drive, NFS image, FTP, or HTTP installation) you will need to boot from a diskette. See the section called Booting the Installation Program from a Diskette for more information on booting from a diskette.

### Booting the Installation Program from the CD-ROM

Red Hat Linux CD 1 has a valid `aboot` block, so many modern Alphas which use SRM and `aboot` can boot directly from the Red Hat Linux CD 1 shipped in the boxed set. The command to boot from an IDE CD-ROM drive looks like the following:

    boot dqa0 -flags 0

If the previous command is problematic for your system, the format for the full command is as follows:

    boot dqa0 -file /kernels/vmlinux.gz -flags "root=/dev/hda initrd=images/cd-rom.img"

Please note that in the above command, we have used `dqa0` (SRM) and `/dev/hda` (Linux) to refer to an IDE CD-ROM device. Your system may be set up differently, so the command may need to be changed. For example, if your Alpha uses a SCSI CD-ROM device, you might use a command like the following:

    boot dkb0 -file /kernels/vmlinux.gz -flags "root=/dev/scd0 initrd=images/cd-rom.img"

If you would like to perform a text mode installation instead of a GUI installation, you will need to add the `text` flag to the flags at the end of the full boot command. For example, if you wanted to use the previous boot command to boot a text mode installation, you would use the following command:

    boot dkb0 -file /kernels/vmlinux.gz -flags "root=/dev/scd0 initrd=images/cd-rom.img text"

If you want to run the installation program at 640x480 resolution instead of the default 800x600 resolution, you can boot in `lowres` mode with the following command:

    boot dkb0 -file /kernels/vmlinux.gz -flags "root=/dev/scd0 initrd=images/cd-rom.img lowres"

If you want to run the installation program without using frame buffer, you can boot in `nofb` mode with the following command:

    boot dkb0 -file /kernels/vmlinux.gz -flags "root=/dev/scd0 initrd=images/cd-rom.img nofb"

If you are having problems detecting your hardware in the installation program, try using the noprobe mode. Instead of trying to autodetect your hardware, it will ask you a series of questions about your hardware. You can boot in noprobe mode with the following command:

    boot dkb0 -file /kernels/vmlinux.gz -flags "root=/dev/scd0 initrd=images/cd-rom.img noprobe"

See the section called SRM Device Names for more information on how SRM refers to system devices.

| Returning to SRM from the `aboot` Prompt
| If your boot command does not work for some reason, you will end up at the `aboot` prompt. To return to the SRM console, use the `q` command.

Once the installation program has booted, follow the instructions contained in Chapter 3 to install Red Hat Linux in graphical mode. Refer to Chapter 4 to install Red Hat Linux in text mode.

### Booting the Installation Program from a Diskette

If your Alpha will not boot the Red Hat Linux installation program directly from Red Hat Linux CD 1, you will need to boot from a diskette. If you want to perform a hard drive, NFS image, FTP, or HTTP installation, you will need to boot from a diskette.

You must create a boot image file diskette from the boot image file on CD 1: `images/generic.img`. You will also need a RAM disk image made from `images/ramdisk.img`, also on CD 1. Instructions for creating disk images are located in Appendix D. Remember to label the diskettes appropriately.

Put the boot image diskette into your floppy drive. If you are going to load the installation program from the CD-ROM drive, you will need to put CD 1 into the CD-ROM drive. Use the following command to boot the Red Hat Linux installation program:

    boot dva0 -flags 0

This command assumes that the `aboot` bootloader file is on the diskette and that the boot parameters on the diskette are all correct. If you are booting from the diskette provided with Red Hat Linux, this boot command will work.

If for some reason you need the long version of the command to boot from a diskette, it looks like the following:

    boot dva0 -file vmlinux.gz -flags "root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1"

In the previous command, you will need to modify the parameters to match the location of the kernel file on your diskette and the location of the root filesystem.

After you have booted from the floppy, you will be prompted to take out the boot image diskette and insert the RAM disk diskette with the following message:

    VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER

Insert the RAM disk diskette and press [Enter].

If you are not using the Red Hat Linux CD, the installation program will start in text mode. You will need to choose a few basic options for your system and then you will need to select which installation method you would like to use. See the section called Selecting an Installation Method in Chapter 3 for more information on different installation methods.

If you are using the CD-ROM to load the installation program, follow the instructions contained in Chapter 3 to install Red Hat Linux.

The `text`, `lowres`, `nofb`, and `noprobe` modes described in the section called Booting the Installation Program from the CD-ROM also work when booting from a diskette.

Prev | Home | Next
Do You Have Enough Disk Space? | Up | Which Installation Class is Best for You?