Debian Planet

Welcome to Debian Planet


All your woody are (not quite, but very very very soon) belong to us.
Main Menu

  • Home

  • Topics

  • Web Links

  • Your Account

  • Submit News

  • Stats

  • Top 10

  • Debian

    These are important Debian sites one should not be without!

  • Official Debian site

  • Package search

  • Mailing list archives

  • Bug reports

  • Debian on CD

  • Unofficial woody CD ISOs

  • Unofficial APT sources

  • Developers' Corner

    Other great Debian news sources:

  • Debian Weekly News

  • Kernel Cousin Debian

    (Debian mailing lists digested)
  • Community Groups

    Need help? You're not alone on this planet.

  • debianHELP

    (User support site)

  • Debian International



  • EsDebian


  • DebianWorld


  • MaximumDebian


  • DebianUsers


  • Debian-BR


  • IRC

    The place to get help on a Debian problem (after reading docs) or to just chat and chill is #debian on

    Many of the Debian Planet staff live there so pop by and say hello.

    Wanna write?

    Got that latest or greatest scoop? Perhaps you have some important news for the Debian community? Submit a news item!

    Or perhaps you've written a rather ground breaking insight into some aspect of Debian and you feel compelled to share it with others? Knock up a longer editorial article and send it to the editors.


    DP is sponsored by Xinit Systems and

    Domains paid for and hosted by

    Buy your Debian merchandise at

    Who's Online

    There are currently, 45 guest(s) and 2 member(s) that are online.

    You are Anonymous user. You can register for free by clicking here.

    HOWTOs: Installing Debian GNU/Linux on Alphas
    Posted on Tuesday, February 19 @ 20:56:13 GMT

    This article describes how to have fun and impress your friends by obtaining old Alpha workstations and installing Debian GNU/Linux on them. I'll be installing "potato" (2.2.R3) on my AlphaStation 250. This is a 1995-vintage workstation with an Alpha CPU. It's the main application/DNS/NFS/DHCP server on my home network, and is presently my favorite machine. I had been running RedHat on it, but after seeing "apt-get dist-upgrade" run for the first time earlier this year, I've been upgrading all my boxes to Debian.

    Getting into old hardware

    It's fun to play with old hardware. I especially like old UNIX
    workstations. In addition to the AlphaStation, I own several Digital
    Multia "Universal Desktop Boxes" with Alpha CPUs, a Hewlett/Packard
    Apollo 720 (Hurray for HPPA support in "woody"!), and a NeXTstation
    N1100 - and I'm always looking for more. Why are these machines fun?
    Part of the appeal is obtaining the unobtainable: when these machines
    were new, they were the stuff of my dreams - I could never have
    afforded them. Part of the appeal is being different - anyone can own
    a PC, not everyone runs an AlphaStation. But the biggest part of the
    appeal is cost: many people don't want these machines anymore; you can
    often get them cheap, or even free!

    It's not difficult to acquire your own 90's-era UNIX workstations.
    Sellam Ismail has an excellent primer on finding old computers on the
    Vintage Computer Festival
    website. He lists many potential sources of machines. I've found
    machines on Internet auction and for-sale sites. Some turn up on
    local LUG mailing lists. I often see SPARCs, SGIs, and DECstations at
    Hamfests. (Hamfests are flea markets for Amateur Radio and computer
    users.) If you spread the word that you collect old hardware, people
    that want to get rid of old machines may actually come to you. I've
    gotten about half of my machines for free in this manner.

    Note that old computers have often been raided for spare parts;
    it's not unusual to see machines for sale without RAM and disk drives.
    So, make sure you know what's missing before you buy a machine, and
    keep in mind that you'll have to fix it before you can get the machine
    up and running.

    Alphas are a good place to start

    The early 90's had many UNIX workstation vendors. There are plenty of
    models to choose from, many of which are supported by Debian
    GNU/Linux. Alpha machines represent a good place to start exploring
    the world of old computers, for two reasons: First, there is good
    documentation available for them, and second, they are compatible with
    many kinds of common PC hardware.


    There is plenty of documentation for old Alpha workstations on the
    Net. Many operating systems support the Alpha architecture, so there
    is no shortage of support pages, mailing lists, and HOWTOs. The
    Alpha Linux page is a
    particularly good resource. Furthermore, you can still download the
    original manuals for many Alpha workstations from the old
    Digital FTP
    . This documentation can help you overcome both hardware and
    software problems.


    Alpha workstations are compatible with many kinds of inexpensive PC
    hardware. For example, my Alpha workstations use VGA, 10BaseT
    Ethernet, and PCI cards, just like the average PC. My Multia
    workstations even have two PCMCIA card slots.

    Being able to use standard PC monitors and cards on my Alphas has been
    a considerable convenience. However, there are limits to this
    compatibility: all my Alphas require full-parity 72-pin SIMMs - an
    unusual kind of RAM that seldom can be obtained as cheaply as more
    common PC-oriented flavors. Also, Multia workstations won't operate
    without a live Rayovac 840 clock battery (or a superior modern
    replacement model), requiring a trip to a store that sells batteries
    for old Macs.

    Installing Debian GNU/Linux

    I'm going to be installing Debian GNU/Linux 2.2R3 "potato" on my
    AlphaStation 250. The machine has a 3.5" floppy drive, a SCSI CD-ROM
    reader, and an 8 GB SCSI hard disk. It also has an SVGA monitor and a
    keyboard to act as a console. I've got the Binary-1 CD-ROM for
    installation media.

    The instructions provided on the Binary-1 CD-ROM for this kind of install
    are quite good. Although there's little I'll be able to add to them
    here, this account will at least demonstrate that installing on Alphas
    is not significantly harder than installing on a typical PC.

    I've already backed up all the data from the AlphaStation on which I'm
    going to install. You should make backups too, because, although it's
    intended to be accurate and helpful, this account of my install my
    contain errors, and is provided without warranty.

    FYI, there's a great deal of useful hardware support information in
    Chapter 2 "System Requirements" in the

    Debian installation manual
    , including a
    reference to the
    Linux Alpha HOWTO.
    Reading through this material is a good way to become an educated
    consumer before buying Alpha hardware.

    Section 6.6 "Alpha Console Firmware" is also a good source of
    information for those new to Alpha machines. The Alpha console
    firmware is much more powerful than the BIOS on most PCs. As a rule,
    this firmware implements two complete interactive console shells: a
    command-line-oriented one called "SRM" designed to support UNIX and
    VMS, and a menu-oriented one called "ARC" designed to support Windows
    NT. You can use either console shell to boot Linux off of a floppy or
    hard disk. However, the SRM console shell is more powerful than ARC:
    for example, SRM can boot Linux from an Ethernet device. The Debian
    installation instructions suggest SRM over ARC. Although I've had
    good luck with ARC in the past, I'm going to use SRM this time.

    1. Boot to the SRM console shell.

      The first step is to power-on the machine and boot to the SRM console
      shell. The SRM console shell prompt looks like ">>>". If, instead of
      this prompt, your Alpha boots to a blue screen with menus, that's ARC.
      If you wind up in ARC, navigate the menu tree until you find the
      option to switch to the SRM console shell. The proper series of
      choices should be something like:

      • Supplementary menu...
      • Set up the system...
      • Switch to OpenVMS or Digital UNIX console
      • Switch to Digital UNIX

      Once you select the "Switch to Digital UNIX" item, power cycle the
      machine and it should come up in the SRM console shell.

      An amusing fact: all you'd need to do to switch back to ARC from SRM
      would be to type "arc" and hit return. Who says command line
      interfaces are harder to use? The original manuals from the Digital
      FTP site cited above contain complete reference information for both
      console shells, if you want it.

    2. Boot Linux from the CD-ROM.

      Stick the Binary-1 CD-ROM in the reader. At the ">>>" SRM prompt type

      show dev

      The show command will show you all the devices. For example, my
      floppy drive shows up as dva0, my SCSI hard disk shows up as dka200,
      and my SCSI CD-ROM reader shows up as dka600. So, I'll ask the SRM
      console to boot the Linux kernel from my CD-ROM like this:

      boot dka600 -file boot/linux

      The boot command boots the Linux kernel, which should start the Debian
      install program automatically.

    3. (Re)partition the hard disk.

      The SRM console shell uses a bootloader called "aboot" to boot the
      Linux kernel. The aboot bootloader is the equivalent of lilo or grub on
      PCs. The aboot bootloader requires your hard disk partition table to
      use a BSD-style disklabel. Most PC bootloaders do not require
      BSD-style disklabels, so if you've partitioned your hard disk with a
      PC before, the disklabel is probably not there. So, you should
      execute the "partition your hard disk" installation step, even if your
      disk is already partitioned. This will allow the fdisk program to
      create the proper disklabel for you, automatically.

      Unfortunately, the default cfdisk disk partitioning program can't
      handle BSD-style disklabels. We'll be forced to use the more-powerful
      alternate fdisk program, which is harder to use. A transcript of my
      session with fdisk follows, as an example. My input and some comments
      (delimited with /* and */) are shown in bold.

      Command (m for help): b /* Give me BSD-style disklabel */
      /dev/sda contains no disklabel.
      Do you want to create a disklabel? (y/n) y

      At this point, fdisk displays an empty partition table. The
      automatically-generated entry for "c:" just shows the geometry of the
      drive; it's not a partition that takes up space, it's not a partition
      you can put data in. I'll just pretend it's not there, and I won't
      use the label "c:" for any of my partitions.

      Fdisk also shows some information about the drive geometry here,
      including the number of bytes in each sector, and the number of
      sectors in each cylinder. My disk has 512 bytes per sector, and 2048
      sectors per cylinder, so I know that each cylinder is 1MB in size.
      This is useful information, because I'll be choosing sizes for my
      partitions in units of cylinders in the next steps. Note that I start
      my first partition at cylinder 2 in order to leave room at the head of
      the drive for the "aboot" boot loader.

      BSD disklabel command (m for help): n /* 1/2GB for root */
      Partition (a-h): a
      First cylinder (1-8347, default 1): 2
      Last cylinder or +size or +sizeM of +sizeK (2-8347, default 8347): 511

      BSD disklabel command (m for help): n /* 1/2GB for swap */
      Partition (a-h): b
      First cylinder (512-8347, default 512): (enter)
      Using default value 512
      Last cylinder or +size or +sizeM of +sizeK (2-8347, default 8347): 1023

      BSD disklabel command (m for help): n /* usr */
      Partition (a-h): d
      First cylinder (1024-8347, default 1024): (enter)
      Using default value 1024
      Last cylinder or +size or +sizeM of +sizeK (2-8347, default 8347): 2047

      BSD disklabel command (m for help): n /* var */
      Partition (a-h): e
      First cylinder (1024-8347, default 1024): 2048
      Last cylinder or +size or +sizeM of +sizeK (2-8347, default 8347): 3071

      BSD disklabel command (m for help): n /* home */
      Partition (a-h): f
      First cylinder (1024-8347, default 1024): 3072
      Last cylinder or +size or +sizeM of +sizeK (2-8347, default 8347): 6143

      BSD disklabel command (m for help): n /* extra partition */
      Partition (a-h): g
      First cylinder (1024-8347, default 1024): 6144
      Last cylinder or +size or +sizeM of +sizeK (2-8347, default 8347): (enter)
      Using default value 8347

      BSD disklabel command (m for help): t /* set swap FS type */
      Partition (a-g): b
      Hex code (type L to list codes): L

      Fdisk prints a list of known codes at this point. The code for swap is 1.

      Hex code (type L to list codes): 1

      BSD disklabel command (m for help): p /* print the table */

      7 partitions:
      # start end size fstype
      a: 2 511 510 ext2 /* root, start at cyl 2 for aboot! */
      b: 512 1023 512 swap /* swap */
      c: 1 8347 8347 unused /* just ignore this */
      d: 1024 2047 1024 ext2 /* /usr */
      e: 2048 3071 1024 ext2 /* /var */
      f: 3072 6143 3072 ext2 /* /home */
      g: 6144 8347 2204 ext2 /* extra partition for future use */

      BSD disklabel command (m for help): w /* write the table to disk */
      Writing disklabel to /dev/sda
      Syncing disks.

      BSD disklabel command (m for help): q /* quit fdisk */

      There, using fdisk wasn't so bad, was it?

    4. Reboot

      When the you execute the mid-install reboot, you should return to the
      ">>>" SRM prompt. If you wish, you can use "show dev" to show the
      device names again. I used

      boot dka200 -file vmlinuz

      to boot the newly-installed Linux kernel off of my SCSI hard disk and
      complete the installation.

      The SRM console shell and fdisk may take a little getting used to, but
      installing on Alphas isn't much more complicated than installing on
      the average PC.


    Don't expect old workstations to be powerhouses of performance.
    (There's a reason why people are willing to sell these things cheap.)
    I ran some informal BYTE Magazine UNIX benchmarks (UNIXBench 4.1.0)
    on a representative sample of my Alphas and PCs just to give some
    perspective. This is a general macro-benchmark originally developed
    long ago at BYTE magazine. It's now being maintained and improved by
    David C. Niemi. It combines a variety of computational and filesystem
    exercises, and spits out a "score" at the end. The more powerful your
    machine, the bigger your score.

    I didn't put a great deal of effort into making these tests
    perfectly-controlled, so don't stake your life on their pinpoint
    accuracy. Your mileage may vary. All of the machines were running
    Linux kernels with versions between 2.2.17 and 2.2.19 using gcc
    versions between 2.91.66 and 2.95.4. I used the Intel-specific gcc
    optimization flags provided in the UNIXBench makefile when building
    the benchmark on PCs. After some experimentation with -mcpu=ev4,
    -mno-soft-float, and -mfp-regs (no improvement, perhaps these are
    defaults), I used only the makefile's default generic optimization
    flags when building the benchmark on the Alphas.

    UNIXBench 4.1 Scores for Several Alphas and PCs
    UNIXBench Score
    Alpha 21066A
    AS 250
    Alpha 21064A
    Pentium II
    Pentium III


    The benchmark shows that the Multia is slightly more powerful than a
    486 PC - powerful enough to make a good firewall, DNS, or DHCP server,
    for example. The AlphaStation 250 (shown as AS 250 in the table)
    scores ahead of the Pentium PCs that were common in 1995. Neither old
    Alpha workstation achieved anywhere near the score of the Pentium III.
    Still, it's important to put the value of performance into perspective:

    The PC market being what it is, the new PC you pull out of a shipping
    crate today will start to seem old and slow not long after you've
    gotten all the Styrofoam packing material cleaned up. Everyone has an
    old, slow PC. But an old, slow AlphaStation - that's something

    So, now that it's running Debian GNU/Linux, the old AlphaStation 250
    should be fine for my purposes... at least until someone tells me they
    want to get rid of a newer Alpha machine. Anyone have one of those
    multi-processor GS AlphaServers they want to throw out? Not yet?
    That's the upside to running old machines: sooner or later, the
    machine of your dreams will come to you. It's only a matter of time.

    Submitted by Tim Fraser

    Related Links

  • More about Linux
  • News by rob

    Most read story about Linux:
    Installing Debian GNU/Linux on Alphas

    Last news about Linux:

    Printer Friendly Page  Send this Story to a Friend
  • "HOWTOs: Installing Debian GNU/Linux on Alphas" | Login/Create Account | 21 comments

    The comments are owned by the poster. We aren't responsible for their content.

    update (Score: 3, Informative)
    by tim ( on Tuesday, February 19 @ 22:33:01 GMT
    (User Info)


    Just an update: the AlphaStation 250 described in the article has been running Debian quite smoothly for several months now.

    However, there has been one frustrating thing about using such odd hardware: it is sometimes harder to find binary packages built for Alpha CPUs than for the more common Intel 386-ish CPUs.

    For example, I've been unable to get an Ada compiler on my AlphaStation. (Some folks might think that's a *good* thing, but I want to play with Ada, just to see what it's like.) I haven't been able to find a Gnat package built for Alpha. Does someone know of one? Perhaps because I am a relatively new user of Debian, I just don't know where to look.

    For most software, this wouldn't be much of a problem - I could just build from source. Unfortunately, it seems that Gnat and the Ada support in the latest snapshots of GCC require an already-working Ada compiler to build, so in this one case I'm stuck. (I'm too cowardly to try cross-compiling.)

    Still, this Ada problem is a very unusual case. Overall, the AlphaStation's been a good machine.

    - Tim

    [ Reply ]

    Re: update (Score: 0)
    by Anonymous on Wednesday, February 20 @ 07:16:01 GMT

    You have Debian. Try adding the source .DEBs to your apt.sources file, and running the 'apt-get source' routine...

    At least you may find out why this isn't a port to the Alpha dist! 🙂

    [ Reply ]

    benchmark results for 533mhz AlphaPC164SX (Score: 2, Interesting)
    by gps on Wednesday, February 20 @ 09:09:58 GMT
    (User Info)

    I've got an AlphaPC 164SX with a 533mhz 21164sx cpu.

    Here are the benchmark results:

    BYTE UNIX Benchmarks (Version 4.1.0)

    System -- Linux soap 2.4.10 #1 Fri Sep 28 17:01:45 PDT 2001 alpha unknown

    Start Benchmark Run: Wed Feb 20 00:12:56 PST 2002

    3 interactive users.

    12:12am up 9 days, 7:37, 3 users, load average: 0.08, 0.06, 0.02

    lrwxrwxrwx 1 root root 4 Jun 10 2000 /bin/sh -> bash

    /bin/sh: symbolic link to bash

    /dev/sda8 1983728 1370112 511220 73% /home

    Dhrystone 2 using register variables 628466.2 lps (10.0 secs, 10 samples)

    Double-Precision Whetstone 131.4 MWIPS (9.9 secs, 10 samples)

    System Call Overhead 182701.2 lps (10.0 secs, 10 samples)

    Pipe Throughput 150361.3 lps (10.0 secs, 10 samples)

    Pipe-based Context Switching 59968.3 lps (10.0 secs, 10 samples)

    Process Creation 1518.6 lps (30.0 secs, 3 samples)

    Execl Throughput 286.3 lps (29.6 secs, 3 samples)

    File Read 1024 bufsize 2000 maxblocks 114969.0 KBps (30.0 secs, 3 samples)

    File Write 1024 bufsize 2000 maxblocks 86884.0 KBps (30.0 secs, 3 samples)

    File Copy 1024 bufsize 2000 maxblocks 45871.0 KBps (30.0 secs, 3 samples)

    File Read 256 bufsize 500 maxblocks 59202.0 KBps (30.0 secs, 3 samples)

    File Write 256 bufsize 500 maxblocks 39106.0 KBps (30.0 secs, 3 samples)

    File Copy 256 bufsize 500 maxblocks 21961.0 KBps (30.0 secs, 3 samples)

    File Read 4096 bufsize 8000 maxblocks 149311.0 KBps (30.0 secs, 3 samples)

    File Write 4096 bufsize 8000 maxblocks 131021.0 KBps (30.0 secs, 3 samples)

    File Copy 4096 bufsize 8000 maxblocks 66476.0 KBps (30.0 secs, 3 samples)

    Shell Scripts (1 concurrent) 555.0 lpm (60.0 secs, 3 samples)

    Shell Scripts (8 concurrent) 75.6 lpm (60.0 secs, 3 samples)

    Shell Scripts (16 concurrent) 37.3 lpm (60.0 secs, 3 samples)

    Arithmetic Test (type = short) 63601.9 lps (10.0 secs, 3 samples)

    Arithmetic Test (type = int) 68562.0 lps (10.0 secs, 3 samples)

    Arithmetic Test (type = long) 73727.2 lps (10.0 secs, 3 samples)

    Arithmetic Test (type = float) 131110.8 lps (10.0 secs, 3 samples)

    Arithmetic Test (type = double) 93626.8 lps (10.0 secs, 3 samples)

    Arithoh 2428936.0 lps (10.0 secs, 3 samples)

    C Compiler Throughput 201.9 lpm (60.0 secs, 3 samples)

    Dc: sqrt(2) to 99 decimal places no measured results

    Recursion Test--Tower of Hanoi 12367.0 lps (20.0 secs, 3 samples)



    Dhrystone 2 using register variables 116700.0 628466.2 53.9

    Double-Precision Whetstone 55.0 131.4 23.9

    Execl Throughput 43.0 286.3 66.6

    File Copy 1024 bufsize 2000 maxblocks 3960.0 45871.0 115.8

    File Copy 256 bufsize 500 maxblocks 1655.0 21961.0 132.7

    File Copy 4096 bufsize 8000 maxblocks 5800.0 66476.0 114.6

    Pipe Throughput 12440.0 150361.3 120.9

    Pipe-based Context Switching 4000.0 59968.3 149.9

    Process Creation 126.0 1518.6 120.5

    Shell Scripts (8 concurrent) 6.0 75.6 126.0

    System Call Overhead 15000.0 182701.2 121.8

    Read the rest of this comment...

    [ Reply ]

    Re: benchmark results - summary (Score: 1)
    by gps on Wednesday, February 20 @ 17:49:19 GMT
    (User Info)

    i was curious about how much improvement the new gcc makes. not a lot, but some:

    using debian potato gcc 2.95.2: 94.0

    using gcc 3.0.2: 95.9

    half of the baseline test results are 5-10% higher using gcc 3.0.2.

    [ Reply ]

    Re: update (Score: 0)
    by Anonymous on Wednesday, February 20 @ 14:06:32 GMT

    take down Contents.alpha.gz (calld something like that) run

    zcat Contents.alpha.gz |grep [gG]nat

    The most usable line in linux history (after apt-get, ls -al and a few more ;P)

    [ Reply ]

    Re: update (Score: 0)
    by Anonymous on Tuesday, March 05 @ 00:14:06 GMT

    You mean: apt-cache search gnat

    [ Reply ]

    Re: update (Score: 0)
    by Anonymous on Wednesday, February 20 @ 15:46:46 GMT

    To my knowledge the Gnat boot strap hasn't been compiled on alpha yet.. I've posted to comp.lang.ada about it. I've been trying to cross compile it over so we can build gcc 3.1 with Ada support, it's a fairly involved process though.

    [ Reply ]

    64 bit will always better 32bit (Score: 0)
    by Anonymous on Thursday, February 21 @ 06:14:04 GMT

    OK a much faster Pentium is faster, so what!

    But it will never be more accurate. If I were keeping satalites in orbit or plotting a course to the moon I would take more time to do it on an Alpha then accept the "quick and dirty" results of a pentium, all things being equil.

    [ Reply ]

    Re: 64 bit will always better 32bit (Score: 0)
    by Anonymous on Tuesday, March 05 @ 00:15:57 GMT

    Wonderful how you just ignore the fact that the Intel x87 FPU is 80-bit. Hey, an UltraSparc has 128-bit registers! Yeah!

    xx-bit is about as useful a comparison as yyy-MHz. In other words, not at all.

    [ Reply ]

    Re: Installing Debian GNU/Linux on Alphas (Score: 1, Informative)
    by Anonymous on Wednesday, February 20 @ 07:49:41 GMT

    I'm running Debian Woody on an AlphaServer 1000/266 in my company as internet gateway and quite happy with it. Only problem was (is) that there are less developers and all is a bit rocky.

    [ Reply ]

    Re: Installing Debian GNU/Linux on Alphas (Score: 1)
    by Knife on Wednesday, February 20 @ 13:43:15 GMT
    (User Info)

    Hi all,

    I have a Digital 21164 PICMG SBC station with a 500MHz 21164A Alpha CPU (EBM23). There is a AlphaBIOS Console 5.7 on it and I can only install/boot WinNT 4.0. But I would like to install Debian GNU/Linux Woody. How can I change the AlphaBIOS to a SRM console and where can I get such a SRM console?

    Thanks a lot for your help!!


    [ Reply ]

    Re: Installing Debian GNU/Linux on Alphas (Score: 0)
    by Anonymous on Wednesday, February 20 @ 14:40:12 GMT

    email me at and we'll figure it out. Ok?



    [ Reply ]

    Re: Installing Debian GNU/Linux on Alphas (Score: 1)
    by tim ( on Wednesday, February 20 @ 14:59:12 GMT
    (User Info)


    You should be able to install using your existing AlphaBIOS (also known as ARC). You'll need to use the MILO bootloader. I still use ARC and MILO on my Multia firewall - it works fine.

    There are at least three good sources of information on booting with ARC and MILO:

    1) The Debian Install instructions (linked from article), especially sections 6.6 "Alpha Console Firmware" and 6.8 "Booting from the ARC or AlphaBIOS Console".

    2) The readme.txt file under the disks-alpha/current directory on the Debian CD-ROM.

    3) The MILO HOWTO (linked from the Debian install instructions).

    Good luck, and have fun!

    - Tim

    [ Reply ]

    Re: Installing Debian GNU/Linux on Alphas (Score: 0)
    by Anonymous on Tuesday, February 26 @ 16:14:19 GMT

    ARC is not the same as AlphaBios (AlphaBIOS is graphical - a kind of win3.1 interface).

    They are two different beasts, written with the same goal in mind: boot WinNT on Alpha

    [ Reply ]

    Re: Installing Debian GNU/Linux on Alphas (Score: 0)
    by Anonymous on Wednesday, February 20 @ 16:41:29 GMT

    These boards have a half-size flash, and can only hold one console at a time. If you want to replace the AlphaBIOS console with SRM, download the Flexor A164 console at

    [ Reply ]

    Alpha systems as general machines (Score: 1)
    by gwolf (gwolf at gwolf dot cx) on Wednesday, February 20 @ 22:06:11 GMT
    (User Info)

    I have a fairly recent Alpha system - 21164 CPU (PC164), 600MHz, 128MB RAM. It runs (estimated) at about the speed of a 400MHz PC, which is quite fine for me. Now, if this can be useful to you (or you can help me out 😉 ), I have run into the following problems:

    - DB engines are SLOW and unreliable. This is my main desktop machine, and I use it for my programming. I often use PostgreSQL - It plainly SUCKS 🙁 Tons of 'unaligned trap' messages (three per query), and sometimes even the engine dies. MySQL works even worse.

    - Won't play MP3. I don't know why, but the audio comes out COMPLETELY garbled. I suppose it is a 64-bit-related quirk - I usually use my UltraSparc for MP3, and sometimes I get similar noises.

    - XFree 3.3.x freezes about once a day, also due to unaligned traps. XFree 4.x works perfectly, though.

    All in all, it is a pretty nice machine. I have learned lots with it, and am very proud to be its owner - many people envy me just for that 😉 I like working in heterogeneous environments (many old Sparcs [beautiful machines too!], one UltraSparc, this Alpha, maybe soon a HPPA machine and a couple of PCs).

    If you have the chance of using an Alpha, do yourself a favor: Don't use ARC/AlphaBIOS. SRM is much faster, and it is much closer to the True Unix Way... With AlphaBIOS, booting was a PC-derived joke.

    [ Reply ]

    Re: Alpha systems as general machines (Score: 0)
    by Anonymous on Thursday, February 21 @ 00:36:02 GMT

    Oh, well yes! I agree wholeheartly.

    Alphas are excellent desktop/server machines, my current collection includes

    -Digital Server 3305 (Alphaserver 800) 500 Mhz 21164A

    Runs great with linux and FreeBSD

    -Alphaserver 2100A 5/375 (366 Mhz 21164)

    A machine to avoid if planning to use Linux, as it is unsupported and probably never will, works OK with FreeBSD, through

    -Alphastation 255/300 (300 Mhz 21064A)

    -Alphastation 200/166 (166 Mhz 21064)

    -Alphastation 500/333 (333 Mhz 21164)

    These make great desktop machines,as the author states, especially the (faster) 21164 ones.

    One word about databases and GCC

    I've not seen problems with either PostgreSQL or MySQL for a very long time (more than a year) on very heavy database work on alphas. I would suggest gwolf to update his config. I can post known working configs if someone wants them.

    GCC is not very good optimizing for the Alpha CPU, at least for

    the in order models (21064, 21164), the Compaq C compiler is supposed to provide an important increase in performance. I'll try to do some benchmarking ....

    On the graphics side, Compaq recommends a 3dLabs Permedia 2 based Elsa card, yet i;ve had much better experiences with Matrox and Ati products (You can also have some decent hardware aceleration for 3D on them with Xfree >= 4.10)

    Good luck



    Roberto de Iriarte

    Santiago, Chile

    [ Reply ]

    Re: Alpha systems as general machines (Score: 0)
    by Anonymous on Thursday, February 21 @ 01:43:24 GMT

    To reply to both postings, I own a 275/64mb Cabrio.. It runs secksay.

    The mp3 problem you're experiencing is due to the clock speeds of the pci bus(at least i recall that is what causes that error) you should prolly port a version yerself.

    As for gcc, yeah, gcc isnt too hot for the alpha, but, if you comb the net you can find articles dealing with optimizing gcc on the alpha..

    i have yet to have a problem with installing and running X on this particular Alpha, perhaps luck?

    check if you havent already.. be weary of what compaq recommends, they are also discontinuing the alpha line as of this year.. 🙁



    [ Reply ]

    Re: Alpha systems as general machines (Score: 0)
    by Anonymous on Thursday, February 28 @ 02:02:12 GMT

    The mp3 problem you're experiencing is due to the clock speeds of the pci bus(at least i recall that is what causes that error) you should prolly port a version yerself.

    What sound card are you using? My alpha has been VERY picky about sound cards (ISA works best, I'm trying to port the cs46xx driver in my spare time). I made a patch years ago that fixed mpg123 on alpha and since then I've been listening to mp3's. My alpha has a 13GB collection (I ripped all my CD's). xmms works fine.

    As to gcc, go
    download Compaq's ccc compiler
    (the same one as is used under Tru64). That link may not work. I'm not sure why, but copy that URL and download it with ncftp.
    Here is the relevant web page
    . This compiler often generates code that runs 3x faster than gcc. Unfortunately, only gcc can compile the kernel. 🙁

    [ Reply ]

    Re: Alpha systems as general machines (Score: 0)
    by Anonymous on Thursday, February 28 @ 02:06:49 GMT

    On the graphics side, Compaq recommends a 3dLabs Permedia 2 based Elsa card, yet i;ve had much better experiences with Matrox and Ati products (You can also have some decent hardware aceleration for 3D on them with Xfree >= 4.10)

    I highly recommend Matrox products. The linux support for Matrox is better than Elsa. I have a Marvel G200, and on my LX164 (21164) alpha, I record TV to avi/mov files and play it back using the mjpeg tools, and convert to mpeg the things I want to keep. So basically I use my alpha as an expensive TiVo. 😉

    [ Reply ]

    Re: Alpha systems as general machines (Score: 0)
    by Anonymous on Thursday, February 21 @ 01:35:23 GMT

    I have a Alpha XL 266, so I don't have a choice in the matter. I'd like to have an SRM console to learn VMS, but DEC never released one.

    [ Reply ]

    Based on: PHP-Nuke

    All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2000 by Debian Planet

    You can syndicate our news using the file backend.php.