I have just tried syslinux-4.00-pre5-3-g25fb8eb on Bochs + etherboot and it doesn't seem to work: PXELINUX 4.00 pre5-3-g25fb8eb Copyright (C) 1994-2009 H. Peter Anvin et al !PXE entry point found (we hope) at 9F00:0680 via plan A UNDI code segment at 9F00 len 0AB0 UNDI data segment at 9E00 len 1000 Getting cached packet 01 02 03 My IP address seems to be C0A80178 192.168.1.120 ip=192.168.1.120:192.168.1.88:0.0.0.0:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/01-b0-c4-20-00-00-01 [FAILED] Trying to load: pxelinux.cfg/C0A80178 TFTP unknown opcode 1 TFTP server sent an incomprehesible reply Boot failed: press a key to retry, or wait for reset... or !PXE entry point found (we hope) at 9F00:0680 via plan A UNDI code segment at 9F00 len 0AB0 UNDI data segment at 9E00 len 1000 Getting cached packet 01 02 03 My IP address seems to be C0A80178 192.168.1.120 ip=192.168.1.120:192.168.1.88:0.0.0.0:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/01-b0-c4-20-00-00-01 112.120.101.1 08 is not in my arp table! 105.110.117.120 is not in my arp table! 46.99.102.103 is not in my arp table! 47.48.49.45 is not in my arp table! 98.48.45.99 is not in my arp table! 52.45.50.48 is not in my arp table! 45.48.48.45 is not in my arp table! 48.48.45.48 is not in my arp table! 49.0.0.0 is not in my arp table! [FAILED] Trying to load: pxelinux.cfg/C0A80178 [FAILED] Trying to load: pxelinux.cfg/C0A8017 TFTP unknown opcode 1 TFTP server sent an incomprehesible reply Boot failed: press a key to retry, or wait for reset... It seems to work fine on VMware Server. Any clues? - Sebastian
On 09/02/2009 02:15 PM, Sebastian Herbszt wrote:> I have just tried syslinux-4.00-pre5-3-g25fb8eb on Bochs + etherboot and it doesn't seem to work: > > It seems to work fine on VMware Server. Any clues? >I haven't run it on Bochs myself. I know the Etherboot that is included with Bochs is pretty buggy. It's probably worthwhile to figure out what it is having problems with and work around it. -hpa
On 09/02/2009 02:15 PM, Sebastian Herbszt wrote:> Trying to load: pxelinux.cfg/C0A80178 TFTP unknown > opcode 1This means that we got an RRQ back from the TFTP server, which is nonsensical; it may be that Etherboot echoes back our own packets somehow. -hpa
H. Peter Anvin wrote:> On 09/02/2009 02:15 PM, Sebastian Herbszt wrote: >> Trying to load: pxelinux.cfg/C0A80178 TFTP unknown >> opcode 1 > > This means that we got an RRQ back from the TFTP server, which is > nonsensical; it may be that Etherboot echoes back our own packets somehow.I used wireshark to grab a network dump: 192.168.1.120 192.168.1.88 TFTP Read Request, File: pxelinux.cfg/01-b0-c4-20-00-00-01\000, Transfer type: octet\000, tsize\000=0\000, blksize\000=1408\000 192.168.1.88 192.168.1.120 TFTP Error Code, Code: File not found, Message: File not found\000 192.168.1.120 192.168.1.88 TFTP Read Request, File: pxelinux.cfg/C0A80178\000, Transfer type: octet\000, tsize\000=0\000, blksize\000=1408\000 192.168.1.88 192.168.1.120 TFTP Error Code, Code: File not found, Message: File not found\000 192.168.1.120 192.168.1.88 TFTP Error Code, Code: Option negotiation failed, Message: TFTP_protocol error\000 Looks pretty sane to me. - Sebastian