API Technical Support — Alpha Motherboards, Firmware and Linux

This support hub collects the practical knowledge needed to install, configure and troubleshoot API Alpha motherboards, from choosing the right firmware console to populating memory and getting Linux to boot. It also explains, in general terms, how warranty returns were handled.

Firmware concepts: SRM, AlphaBIOS and Linux loaders

Alpha systems do not use a PC-style BIOS. Instead they boot into a firmware console, and which console you run determines which operating systems you can load and how you load them. Understanding this is the single most important step in setting up an Alpha board.

SRM console

The SRM (System Reference Manual) console is the traditional Alpha firmware, used by Tru64 UNIX and OpenVMS and preferred by many Linux users. It offers a text-mode command prompt with commands such as show config, show dev, set and boot. Linux boots from SRM through the aboot loader installed on the boot disk.

AlphaBIOS

AlphaBIOS is a menu-driven firmware originally introduced for Windows NT on Alpha. It looks more like a PC setup utility and loads operating systems through ARC-style boot entries. Linux can be started from AlphaBIOS using the MILO loader.

MILO

The Linux Miniloader is a small program that initialises hardware and loads a Linux kernel on systems where SRM is not available or not desired. It is typically launched from AlphaBIOS or from a floppy.

aboot

The standard Linux boot loader for SRM systems. It reads a kernel and configuration from a disk partition and hands control to Linux.

As a rule of thumb, choose SRM if you plan to run Linux long term or want the most mature Alpha tools, and AlphaBIOS only if you have a specific legacy need. Firmware updates were distributed as images that could be written from floppy or CD, and it was always worth updating before installing a new operating system.

Installation guidance by board

UP1000

The UP1000 is a single-processor ATX board with a Slot B processor module. Seat the module fully and secure its retention mechanism before applying power, and use a power supply rated comfortably above the combined load of the processor module, drives and PCI cards; the 21264 draws considerably more power than most desktop processors of its day. Connect a serial console during first setup so that firmware messages are visible even if the graphics card is not yet initialised.

UP2000

The UP2000 is a dual-processor board. For a single-processor build, install the module in the primary slot. For two processors, use matched modules of the same speed grade and cache size, and check that both are recognised in the firmware configuration display before booting an operating system. Cooling matters: plan airflow across both modules and the memory banks.

Chassis

The 320 chassis was designed around API boards and their power and cooling requirements. If you use a third-party case, check that it provides adequate front-to-back airflow and room for full-length processor modules.

Memory configuration tips

Most memory problems on Alpha boards come from mixing modules or ignoring bank rules. Alpha systems use wide memory buses and error-correcting code, so modules are installed in groups rather than one at a time.

• Use registered ECC SDRAM of the type and speed listed for your board, and buy modules in matched sets.
• Fill banks completely and in order, starting with the lowest-numbered bank.
• Keep modules within a bank identical in capacity, rank organisation and, ideally, manufacturer.
• After adding memory, confirm the total in the firmware configuration display before booting.
• If ECC errors are logged repeatedly on one bank, swap modules between banks to see whether the fault follows the module.

Troubleshooting checklist

When a board fails to start or behaves unpredictably, work through these steps in order. They catch the large majority of problems.

1. Strip the system to the essentials: board, processor module, one bank of memory, power supply and a serial console.
2. Confirm the power supply meets the board's requirements and that all power connectors, including auxiliary connectors, are attached.
3. Reseat the processor module and memory, checking for bent contacts or debris.
4. Watch the serial console and any diagnostic indicators during power-on and note where the self-test stops.
5. Reset firmware settings to defaults, or reload firmware from a known-good image if the console is corrupted.
6. Add components back one at a time: graphics, storage controller, network card, remaining memory.
7. For Linux boot problems, verify the boot loader configuration, kernel image and root device before suspecting hardware.
8. Record everything you observe before requesting further help; it shortens any return process considerably.

Frequently asked questions

Can I run standard x86 Linux binaries?

No. Alpha Linux needs software compiled for Alpha. Most open-source packages were available natively from the major distributions of the time, and some binary translation tools existed for specific commercial applications.

Does the board accept ordinary PC graphics and network cards?

Many PCI cards work, but the card must be supported by the operating system driver and, for graphics, by the firmware if you want console output on screen. A serial console avoids this dependency during setup.

Can I switch between SRM and AlphaBIOS?

On boards that ship both, yes. The switch is made from within the firmware, and the change takes effect after a reset.

Why is my memory total lower than expected?

Usually a bank is only partially populated or contains mismatched modules. Recheck the bank rules above.

Which processor does my board use?

API boards use the 21264 family. See the microprocessors overview for the differences between generations.

Warranty and RMA process

API products were covered by a limited hardware warranty, and returns were managed through a return merchandise authorisation (RMA) process. In general terms, the steps were as follows: confirm the fault with the troubleshooting checklist, gather the product serial number and proof of purchase, request an RMA number through the original reseller or partner, package the item in anti-static protection with the RMA number clearly marked, and ship it to the designated service location. Units returned without an authorisation number, or damaged through improper handling, could be delayed or refused. Customers who bought through a systems integrator normally went through that integrator first, since the integrator was responsible for the complete system.