The Gentoo/Alpha project is responsible for keeping the Gentoo distribution updated and current for the Alpha platform. This primarily includes keywording packages, porting software, and making new releases. The Gentoo/Alpha project aims to provide a usable environment for both desktops and servers.

Kind of, yes. HP stopped taking orders for new Alpha systems on April 27, 2007. and for Alpha options and upgrades on April 25, 2008. See their planning page for more details.

No, all Alpha systems use a pure 64 bit kernel and a pure 64 bit userland. You cannot even force gcc to output 32 bit code using the -m32 compiler flag.

Alpha systems are little endian. A large Cray system using Alphas was big endian, but Linux will never support it.

No, not without a x86 emulator like qemu. In the past DEC/Compaq/HP maintained a program called em86 which allowed Linux/x86 applications to be run on Linux/Alpha systems. However, the program is closed source and no longer maintained upstream. There are no em86 binaries available that are compatible with gcc-3's ABI.

Admittedly, you can find faster 64-bit systems out there, like amd64. However, that doesn't mean that Alpha systems are useless. The following are a few good reasons why you'd want to install Linux on this sort of hardware:

• You can turn an old computer into something useful. Older Alphas make great routers and servers. Their desktop performance isn't that bad either.
• You will learn about unusual computer hardware.
• It's cool. How many people can say they've got Linux running on an Alpha?

Alpha hardware generally isn't available at your local computer store. eBay is usually a good option, assuming that the shipping doesn't cost you too much. There are several used equipment dealers that can be found via Google, however most of them charge too much.

Make sure the top panel of the case is on and properly in place. The middle of the top panel of the case has a small piece of metal oriented downwards. When the top panel is put back in place properly, the small piece of metal will press down on a switch. When the switch isn't pressed down, the system will refuse to power on.

As with all compiler optimizations, don't over do it. Use these flags with care and they will give you a stable, speedy system; use them too aggressively and you could seriously break your system. When in doubt, leave it out. If you need further clarification, check the gcc man page.

You can optimize for a specific instruction set and scheduling model with -mcpu=XXX, where XXX is your cpu type. Valid cpu types are ev4, ev45, ev5, ev56, pca56, ev6 and ev67. If you do not use the -mcpu=XXX flag, then gcc will default to the cpu type of the machine it was compiled on. -mcpu= is equivalent to the -march= flag on x86.

You can specify the scheduling model without changing the instruction set with -mtune=XXX, where XXX is your cpu type. Valid cpu types are ev4, ev45, ev5, ev56, pca56, ev6 and ev67. -mtune= is implied by -mcpu=, so you don't need to specify this with if you set -mcpu=. -mtune= is equivalent to the -mcpu= flag on x86.

You can enable software assisted floating point numbers with -mieee. This will enable software assistance to correctly support denormalized numbers and exceptional IEEE values such as not-a-number and plus/minus infinity.

This should be in your global CFLAGS unless you really know what you are doing.

You can specify the memory latency of your system with -mmemory-latency=XXX, where XXX is the number of clock cycles. This sets the latency time that the scheduler should assume for memory references. gcc has some predefined "typical" values that are also accepted by -mmemory-latency=XXX. Those values are L1 for Dcache, L2 for Scache, L3 for Bcache, and main for main memory.

This flag should probably not be use in your global CFLAGS as the value you choose is highly dependent on the memory access pattern of the application you are compiling.

You can specify that static data should be placed in the small data area with -msmall-data. This will cause gcc to take advantage of some features of the Alpha architecture by storing heavily used pieces of data in specific sections called the small memory sections. The sections are limited to 64KiB which means accessing anything stored in them will only take one instruction.

-fPIC will override -msmall-data, so you should use the -fpic flag instead if you do not want -msmall-data to be overridden.

This flag should probably not be used in your global CFLAGS as some objects require more than 64KiB to be stored, and this will cause a gp_overflow ld error.

You can specify that object code should be placed in the small text area with -msmall-text. This will cause gcc to assume that the entire program (or library) fits in 4MB, and is thus reachable with a branch instruction. This reduces the number of instructions required for a function call from 4 to 1.

This flag should probably not be used in your global CFLAGS as some programs (or libraries) are larger than 4MB, and this will cause an ld error.

As already mentioned, please use these CFLAGS cautiously. They may break your system. If you experience problems, try using less aggressive CFLAGS before filing a bug report.

SRM is based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. See the SRM Howto for more information about SRM.

ARC is based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT.

When you power your system on you will see a screen with a blue background and white text if it is using SRM. You will see a graphical boot system if it is using ARC.

If your Alpha system supports SRM, then you should use aboot. If your system supports both SRM and ARCs (ARC, AlphaBIOS, ARCSBIOS), then you should follow the SRM Firmware Howto for switching to SRM and use aboot. If your system can only use ARCs (Ruffian, xl, etc.) then you will need to choose milo.

No, aboot only supports booting kernels from ext2 and ext3 partitions. You may still use other files systems for your root partition, you just need to create a /boot partition with either ext2 or ext3 on it.

Support for ext4 is planned. In fact, there are patches floating around that add support for ReiserFS, XFS, and ext4.

Compaq/HP offered binary packages, called compaq-jre and compaq-jdk. They stopped all support, and the packages were removed from Gentoo on October 11, 2006. Since then, we haven't supported Java.

It's possible to use icedtea on Alpha, but we have no plans to support it, due to the high maintenance costs involved with testing hundreds of additional packages.

Neither of the two main open source efforts, mono nor DotGNU, support the alpha architecture.

Bringing .NET to Alpha isn't a simple task. It requires coding all of the assembly language code generation macros for the JIT (just in time) compiler and coding architecture specific functions (register allocators, etc).

We recommend using gentoo-sources but vanilla-sources is also supported by Gentoo/Alpha. You should read the Gentoo Kernel Guide to determine which one is right for your needs.

Gentoo/Alpha stopped supporting 2.4 kernel and profile in January 2008. Technically you can build a 2.4 Gentoo System (the kernel is in the tree) but you will have to mask all the 2.6 only packages by yourself and you won't have support from developers.

Gentoo/Alpha will review all bug reports about non-working 2.6 systems and will try to help as much as we can.

Short answer is no. They were supported some time ago, but we lost the hardware and the maintainer so now they are not supported. If you are interested and want to continue the initial work, please let us know.

There were some times in the past when it was broken. However, modern kernel versions are known to work well.

If you find a bug or you want to send us patches, then you need to file a bug report. It only takes you a little bit of your time, and your help is really appreciated. Please follow the Gentoo Bug Reporting Guide.

Users can help us by:

• Filing clear and concise bug reports.
• Testing software that does not yet have the ~alpha keyword.
• Answering questions on the mailing lists, forum and IRC channel.
• Sending patches
• Becoming an AT

Yes, see the Gentoo Linux Alpha Arch Testers Project page for details.

This is usually caused by a bad -mcpu setting. For example, the AlphaServer 800 needs to be compiled with the ev5 flag for xorg and glibc. Failing to do so will cause undesired results.

On the Gentoo Forums there are several arch specific categories like Gentoo on PPC and Gentoo on Sparc. There is no Gentoo on Alpha category because there simply isn't enough Gentoo/Alpha activity on the forums to warrant one. All Alpha related posts should go in the Gentoo on Alternative Architectures category.

If any of your questions weren't answered here, you can try other resources like the Alpha Handbook or our project homepage. You can also ask us at #gentoo-alpha on irc.freenode.net, Gentoo on Alternative Architectures Forum, or on the gentoo-alpha@lists.gentoo.org mailing list.

AlphaLinux.org is a central repository for all things Alpha/Linux.