Have someone a tip for me? pxe with orginal bios works. But with Linuxbios and etherboot not.
There the log of the client:
Welcome to elfboot, the open souro load at offset 0x0 Loading Etherboot version: 5.2.6 Dropping non PT_LOAD segment New segment addr 0Clearing SegmentROM segment 0xfetherboot 5.2.6 (GPL) http://etherboot.og Tagged ELF for [RTL139] Relocating _text fm: [00020000,000311b0to [01eeee50,01f000 Boot from (N)etw or (Q)uit? Probing pci nic... [rtl8139] - ioaddr 000, addr 90:12:02:30:00:61 100Mbps full-duplex Vendor: 0x10EC, Devie: 0x8139 Searching for serveDHCP)... ..Me: 10.5.150.46, Server: 10.5.1.15, Gateway 10.5.1.15 Loading 10.5.1.15:/pinux.0 ...error: not a valid image sleep> to load file. <abort>
The logs of the Server: Oct 17 06:34:21 X440 in.tftpd[19227]: RRQ from 10.5.150.46 filename /pxelinux.0
no other mesage in the log.
Is something with etherboot not corect?
Greeding Markus Boas
On Wed, Oct 17, 2007 at 07:21:38PM +0000, Markus wrote:
pxe with orginal bios works. But with Linuxbios and etherboot not.
You need a different Etherboot image when it's going to be used as a payload with LB, but you probably knew that already.
There the log of the client:
Welcome to elfboot, the open souro load at offset 0x0
^ ^
These messages do not match what is in the source code, so there was corruption somewhere between the source code and the mailing list.
The first step is to find where that comes from. It may be as simple as typos, but please do set up serial logging then, so that we get accurate debug messages from the code to work with.
It may also be caused by bad RAM, which is much more difficult to fix.
New segment addr 0Clearing SegmentROM segment 0xfetherboot 5.2.6 (GPL)
^^ ^^^^ This is hard (read: impossible) to work with. :\
Is something with etherboot not corect?
Maybe, maybe a problem with LB. Please send the full serial output from LB all the way through EB.
//Peter
-
Markus -
Peter Stuge