According to the Changelog for 5.01, pxelinux.0 can load boot files via http. But I can't get it to work. Specifying http as my boot path, just gives me an invalid file or directory error. ie: KERNEL http://10.48.128.56/rhel-server/rhel-server-6.4-x86_64/vmlinuz If I do a wget on the http path, I can get vmlinuz just fine. What am I doing wrong? I also tried copying lpxelinux.0 over pxelinux.0, and all I get is the boot: prompt. ie, my menu doesn't work. Is lpxelunix.0 not supposed to be a drop in replacement for pxelinux.0? I am using syslinux 6.03pre-6, but get the same errors with 6.02. Thanks..
On Tue, Mar 4, 2014 at 10:53 PM, Virtual Xmas <luvs.christmas at gmail.com> wrote:> > According to the Changelog for 5.01, pxelinux.0 can load boot files via > http. But I can't get it to work.5.10 introduced lpxelinux.0, a variant that uses UNDI+lwIP instead of PXE calls.> I also tried copying lpxelinux.0 over pxelinux.0, and all I get is the boot: > prompt. ie, my menu doesn't work. Is lpxelunix.0 not supposed to be a drop > in replacement for pxelinux.0?lpxelinux.0 is supposed to be a drop-in replacement just like gpxelinux.0> I am using syslinux 6.03pre-6, but get the same errors with 6.02.Thanks for testing the latest pre-release. If there's a bug here, this is the best to test with. For starters, you should see more. If you haven't used any 5.xx+ version before, please ensure you have lib*.c32 copied to the same location as [l]pxelinux.0 ldlinux.c32 and (vesa)menu.c32. This will likely resolve your issue. If this does not, we should start with your config, a listing of files and perhaps perform a packet capture. By the way, I've been able to get lpxelinux.0 running such that lpxelinux.0 is the only file loaded by TFTP and the remaining are all HTTP. -- -Gene
On 3/5/2014 4:21 AM, Gene Cumm wrote:> tp. But I can't get it to work. > 5.10 introduced lpxelinux.0, a variant that uses UNDI+lwIP instead of PXE calls.Ah, ok, the wording in 5.10 change log is a little ambiguous then...It seems to imply (to me at least) that http support was added to pxelinux.0 with an old TCP stack, but lpxelinux.0 has http with a new TCP stack.> >> I am using syslinux 6.03pre-6, but get the same errors with 6.02. > Thanks for testing the latest pre-release. If there's a bug here, > this is the best to test with. > > For starters, you should see more. If you haven't used any 5.xx+ > version before, please ensure you have lib*.c32 copied to the same > location as [l]pxelinux.0 ldlinux.c32 and (vesa)menu.c32. This will > likely resolve your issue.This is the script I use to update the pxelinux files in /tftpboot....Am I missing anything? #!/bin/bash T=/tftpboot cp bios/core/pxelinux.0 ${T} cp bios/core/lpxelinux.0 ${T} cp bios/com32/modules/linux.c32 ${T} cp bios/com32/lib/libcom32.c32 ${T} cp bios/com32/libutil/libutil.c32 ${T} cp bios/com32/cmenu/libmenu/libmenu.c32 ${T} cp bios/com32/gpllib/libgpl.c32 ${T} cp bios/com32/elflink/ldlinux/ldlinux.c32 ${T} cp bios/com32/hdt/hdt.c32 ${T} cp bios/memdisk/memdisk ${T} cp bios/com32/mboot/mboot.c32 ${T} cp bios/com32/menu/vesamenu.c32 ${T}/pxelinux.cfg If I boot to pxelinux.0 I get my menu. If I change my boot-file to lpxelinux.0, I just get the boot: prompt after lpxelinux.0 loads. Network tracings shows lpxelinux.0 attempting to search for the menu files(via tftp), but something seems to be broken in that it's not picking one up. I have both a default and a 01-mac-address file for this client, and it's loading neither one (pxelinux.0 is loading the 01-mac-address one). If I specify my menu file over HTTP with DHCP options 209 and 210, I get the menu. And network tracing shows all the .c32 files and everything else coming over http at that point....