Dave Ashley <[EMAIL PROTECTED]> writes: > I'm trying to use my bastardized epia-m tree with etherboot-5.2.2 using > the bin/via-rhine.elf image in place of my 5.0.10 bin32/via6105m.ebi image > that has been working fine. > > I get this with linuxbios + 5.0.10: > Found ELF candiate at offset 0 > > New segment addr 0x94000 size 0x6f68 offset 0x60 filesize 0x3460 > (cleaned up) New segment addr 0x94000 size 0x6f68 offset 0x60 filesize 0x3460 > Loading Segment: addr: 0x0000000000094000 memsz: 0x0000000000006f68 filesz: 0x00 > Clearing Segment: addr: 0x0000000000097460 memsz: 0x0000000000003b08 > Jumping to boot code at 0x94000 > ROM segment 0x0001 length 0x0000 reloc 0x9400 > Etherboot 5.0.10 (GPL) ELF for [VIA 86C100]
> ... everything proceeds normally > > I get this with linuxbios + 5.2.2: > Found ELF candiate at offset 0 > Loading Etherboot version: 5.2.2 > Dropping non PT_LOAD segment > New segment addr 0x20000 size 0xefc0 offset 0xb0 filesize 0x5abc > (cleaned up) New segment addr 0x20000 size 0xefc0 offset 0xb0 filesize 0x5abc > Loading Segment: addr: 0x0000000005f81028 memsz: 0x000000000000efc0 filesz: 0x0c > Clearing Segment: addr: 0x0000000005f86ae4 memsz: 0x0000000000009504 > Jumping to boot code at 0x20000 > ROM segment 0x0001 length 0x0000 reloc 0x00020000 > > > These addr: values for Loading + Clearing Segment seem way off. Agreed. What does readelf -e say they are in the file? > I also tried taking out -DRELOCATE > but that made no difference. Right you need to get etherboot loaded properly before that matters. Eric _______________________________________________ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
