Re: [LinuxBIOS] Problems with Filo booting - HELP

Quoting Corey Osgood :
> [e-mail] wrote:
> > I just wanted to report etherboot is doing the same thing. What could
> > be causing this?? Someone please help me.............
> > Thanks - Joe
> >
> > rom_stream: 0xfffd0000 - 0xfffeffff
> > Found ELF candidate at offset 0
> > header_offset is 0
> > Try to load at offset 0x0
> > n_type: 00000001 n_name(8): ELFBoot  n_desc(10): Etherboot
> > n_type: 00000002 n_name(8): ELFBoot  n_desc(6): 5.4.3
> > Loading Etherboot version: 5.4.3
> > Dropping non PT_LOAD segment
> > malloc Enter, size 32, free_mem_ptr 00018000
> > malloc 0x00018000
> > New segment addr 0x10000 size 0xa880 offset 0x0 filesize 0x6560
> > (cleaned up) New segment addr 0x10000 size 0xa880 offset 0x0 filesize 0x6560
> > lb: [0x0000000000004000, 0x000000000001c000)
> > segment: [0x0000000000010000, 0x0000000000016560, 0x000000000001a880)
> >   bounce: [0x0000000007fdc000, 0x0000000007fe2560, 0x0000000007fe6880)
> > Loading Segment: addr: 0x0000000007fdc000 memsz: 0x000000000000a880
> > filesz: 0x0000000000006560
> > [ 0x0000000007fdc000, 0000000007fe2560, 0x0000000007fe6880) <-
> > 0000000000000000
> > Clearing Segment: addr: 0x0000000007fe2560 memsz: 0x0000000000004320
> > Loaded segments
> > verified segments
> > closed down stream
> > Jumping to boot code at 0x100b0
> > entry    = 0x000100b0
> > lb_start = 0x00004000
> > lb_size  = 0x00018000
> > adjust   = 0x07fe4000
> > buffer   = 0x07fd0000
> >       elf_boot_notes = 0x000139a0
> > adjusted_boot_notes = 0x07ff79a0
> > Unexpected Exception: -1 @ ffffffff:ffffffff - Halting
> > Code: -1 eflags: ffffffff
> > eax: ffffffff ebx: ffffffff ecx: ffffffff edx: 00018000
> > edi: ffffffff esi: ffffffff ebp: 0010003c esp: 00100014
>
> This looks, to me, like LinuxBIOS thinks there's more ram
> there/available then there really is. 0x100b0 is just above the 64MB
> line, so if you only have 64MB (and IIRC that's what's built onto your
> board), FILO is trying to execute in non-existent ram. I might be
> reading that wrong :/ Also, if you are trying to bring up video, setting
> certain registers will reserve ram and FILO won't be able to access it.
> Check your ram_resource() calls in northbridge.c.
>
> If that isn't the case, then yes, memtest is the thing to try.
>
> -Corey

Corey the onboard memory is 128MB. I have to set the video buffer to  
something or it won't boot past raminit.c. I have it set to 512K.  
Could this be causing the problem? I will test it with memtest.

Thanks - Joe