Messages in this thread | | | Date | Wed, 23 Aug 2000 10:03:37 +0200 (CEST) | From | Mike Galbraith <> | Subject | Re: INITRD/RAMDISK/SYSLINUX booting fails with new kernel (vs2.2series) |
| |
On Tue, 22 Aug 2000, Michael Peddemors wrote:
> On Tue, 22 Aug 2000, you wrote: > > Sigh, been working on this all day today.. decided to track this down once > and for all... > Stripped a bunch of printk out so I could see what was flashing by all the > time and changed the vidmode....(I thought it was just the RAM map <sheepish > grin>) > Sure enough.. There is something important there.... > initrd extends beyond end of memory (0x01ff932d > 0x01d80000)
That explains it.
> I put in a printk and get back LOADER_TYPE=49 INITRD_START=3276800 > > Hmmm.. That looks real wrong... Is it a fault with trying to prink > LOADER_TYPE as a %d or is it really seeing 49
LOADER_TYPE 49 is the identifier for syslinux. from ldlinux.asm: syslinux_id equ 031h ; SYSLINUX (3) version 1.x (1)
At a glance, it looks like INITRD_SIZE is set wrong.
Please verify INITRD_START, and add INITRD_SIZE to your printk. INITRD_START=3276800 means INITRD_SIZE=30249773.. and that doesn't jibe with floppy ;-) Here, syslinux always loads (16k aligned) the initrd at top of memory and gets INITRD_SIZE right.
> Strange why this (2.4 vs 2.2) kernel works different tho.. Something MUST > have changed.
Try mem=31M for grins (hunch-o-meter says memory detection changes)
-Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |