> I am trying to install Redhat 5.2 on a new DEC Alpha 500a and ran into some
> problems. Although I followed the Redhat manual instructions on how to
> build the load diskettes, set OS start, etc... My machine keeps giving the
> following at startup when I select Linux for startup (NT is the other
> "Invalid OS selection - The highlighted OS selection is not valid"
The trick here is in the OS Selection Setup. If you are trying to boot
off of a "Rescue" style floppy (One with linload.exe, milo, kernel,
1) Make sure the Boot File: line is set for A: and linload.exe
2) The OS Path line should be set to CD:
(Actually, anything for the device - it isn't used by linload)
and \ (backslash only - forward slash will not allow it to find
3) OS Options should be: (This is Debian - see the notes - most
boot fd0:linux root=/dev/fd0 rw ramdisk_size=5120 load_ramdisk=1
^ ^ ^ ^
| | | --- could differ with
ver. and distrib. . .
| | --- first floppy - use fd1 for second, etc.
| --- name of the kernel - could be vmlinuz . . .
--- first floppy - use fd1 to boot from second, etc.
AlphaBIOS will reply Warning: Operating System Selection not Valid
It will list OS Path: CD: (or whatever you used in 2 above) \ not
This is normal - Alpha BIOS just doesn't understand linload/milo
If it also lists Boot File: A: linload.exe not found.
then make sure your rescue disk is in the first floppy drive.
(It doesn't really matter at this point - just be sure it is there
when you try to boot.)
Press [Enter] to continue, [F10] to save, and [Enter] again to confirm.
[Esc],[Esc] should leave the bios utility and present you with your
boot menu -
be sure the rescue disk is in the first floppy drive and select the
option you created. linload will run - load milo, and prompt you for
Note: You may see something similar to a reboot (or at least a blanked
depending on your video card.) Don't sweat it - it is just a
reinitialization. . .
If this doesn't work, or something seems to act strange, flip-out,
smoke, etc. let me know.
OnLine Web Marketing
> anyone know what I should be doing that is not in the Redhat 5.2 startup
> BTW: I tried with Redhat 5.0 with same results. Also, tried on an Alpha
> based clone with the same results.
> Note that this is a new machine with a "clean" disk - first time used...