Hi, On 16 Sep, Jay Estabrook wrote: > On Wed, Sep 17, 2003 at 02:00:02AM +0200, Goswin von Brederlow wrote: >> >> There is a kernel option that changes the address the kernel will >> reside at. Maybe you need to toggle it to the old address. > > Correct; you need to say YES to the "Legacy Start Address" question, > for *all* MILO machine kernels.
Thanks for the hint, but I've tried that before posting on this list. No go. As a side question: Are more recent milo's ( such as 2.2.x ) still affected ? I seem to recall, that this has been fixed. Anyway, I tried and it didn't solve my problem. To me, it seems that something alpha-specific has changed in recent kernels, that might break milo's jump-to-kernel. Has anybody successfully build and run a kernel, that meets the following criteria: 1. Version >= 2.4.22 ( including -bk and -pre series and/or even 2.6.0-test... ) 2. Build using the "correct" alpha arch-type, instead on "Generic" 3. Is being loaded/started by Milo Regards, Thomas -- Thomas Weyergraf [EMAIL PROTECTED] Funny IA64 Opcode Dept: ( see arch/ia64/lib/memset.S ) "br.ret.spnt.few" - got back from getting beer, did not spend a lot.
