When I create a MILO boot floppy for an Alpha XL 300 (machine type XLT) per the instructions from http://dev.gentoo.org/~taviso/milo/readme.htm the machine hangs when it jumps to MILO. The last message is "Swapping to PALcode at 0x80000 ..." Reproducible: Always Steps to Reproduce: 1. Obtain freshly formatted DOS floppy. 2. Download "linload.exe" and "milo-2.2-18-gentoo-alpha-xlt" from http://dev.gentoo.org/~taviso/milo/ 3. Rename "milo-2.2-18-gentoo-alpha-xlt" to "milo" and copy to the floppy. 4. Copy "linload.exe" to the floppy. 5. Run md5sum on floppy and verify results with CHECKSUMS.md5 from web site to ensure files were transfered correctly. 6. Insert floppy in Alpha XL 300. 7. Reboot Alpha, press F2 to enter AlphaBIOS. 8. Go to "Utilities" -> "OS Selection Setup..." 9. Create entry with on the "Boot File:" line device "A:" and command "linload.exe." 10. Exit AlphaBIOS setup, this will take you to the Select Operating System screen. 11. On the Select Operating System screen select the entry you just created. Actual Results: linload loads MILO, but it hangs when it jumps to MILO. The last message is "Swapping to PALcode at 0x80000 ..." Expected Results: The "MILO>" prompt should be displayed. The machine is an Alpha XL 300 with 144 MByte of RAM. To my knowledge this is an XLT type machine, not an XL type machine. As far as I know SRM is not an option for the XL 300. I was able to find an older XLT MILO that does load, but it refuses to boot the installation CD from a Promise PDC20267 IDE controller. The XL 300 does not have an IDE controller on board and I do not have access to a SCSI cdrom drive to boot the installation CD. Note: "emerge info" is not available it this point as we are just getting started with the boot process.
Almost forgot. The version string of the working MILO is "Linux/Alpha Miniloader (MILO) v/aux/KERNELS/MILO/xlt-2.2-18 (Sat Apr 13 17:25:21 EDT 2002)"
Have you tried the milo-2.2-18-gentoo-alcor boot file instead? Apparently the XL300 system comes in two slightly different models, one being the alcor and another being bret.
Tried milo-2.2-18-gentoo-alcor, but same result. System hangs after "Swapping to PALcode at 0x80000 ..." I was able to boot the 2.6 kernel from the install CD by copying it onto a SCSI disk and then using the working MILO to boot from that. When the kernel boots there is a message "alcor_init_pci: Detected AS500 or XLT motherboard." In /proc/cpuinfo it says "system type: Alcor", "system variation: Bret". Googling around I found a message from Jay Estabrook (http://alphalinux.org/archives/debian-alpha/January1999/0084.html) that XLT and Alcor are not the same. XLT has served me well so far, so I am going to presume I have an XLT on my hands.
Taviso is no longer a dev and the homepage was removed some time ago and we don't have a box with MILO to check problems so I think we can close this.