Summary: | MILO for Alpha XLT from taviso's home hangs after swapping to PALcode | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sander stokman <sander.stokman> |
Component: | [OLD] Unspecified | Assignee: | Alpha Porters <alpha> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | Low | ||
Version: | unspecified | ||
Hardware: | Alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
sander stokman
2005-09-25 14:33:00 UTC
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. |