search for: pathprefix

>>> So.. my conclusion for now: 8702009 crashed because of some http pathprefix bug 8702009 contains the multinic bug so wouldn't work anyway e466d24 solves the mutlinic bug AND the http pathprefix bug e466d24 kept crashing on me because I mixed up libraries from 8702009 e466d24 still has an issue with png's in vesalinux causing crashes <<< This is a...

On Wed, Aug 5, 2015 at 3:03 PM, Oscar Roozen via Syslinux <syslinux at zytor.com> wrote: > Unfortunately I can't test anymore until Friday. Maybe gnu-efi got > updated? I seem to remember seeing a shell script pulling in the > newest version during compilation... It's version locked to a certain commit ID. -- -Gene

...r false; # Don't respond to ICMP Mask req > > server-name "dhcp209l"; > > next-server 192.168.0.100; > > option space pxelinux; > > option pxelinux.magic code 208 = string; > > option pxelinux.configfile code 209 = text; > > option pxelinux.pathprefix code 210 = text; > > option pxelinux.reboottime code 211 = unsigned integer 32; > > > > subnet 192.168.0.0 netmask 255.255.255.0 { > > range 192.168.0.1 192.168.0.88; > > option routers 192.168.0.100; > > } > > > > host rhelclient { > > ne...

I am trying to set a uniform PXE environment to load multiple distros. RHEL 5.1 and 4.7 SUSE 10.2 and 11 Solaris 10 X86 Window Multiple server versions.... - Why? Because I am in hell. What I want is to have an upper level pxelinux.0 call the default menu directories that come with the releases. Is there a way to call pxelinux.0 and point it at a different pxelinux.cfg directory?

On 07-08-15 18:29, Patrick Masotta wrote: >>>> > So.. my conclusion for now: > > 8702009 crashed because of some http pathprefix bug > 8702009 contains the multinic bug so wouldn't work anyway > e466d24 solves the mutlinic bug AND the http pathprefix bug > e466d24 kept crashing on me because I mixed up libraries from 8702009 > e466d24 still has an issue with png's in vesalinux causing crashes...

...2015-June/023629.html > OK I got lost. > are you saying you finally were able to chainload syslinux.efi on the HP?? > by doing what? Some magic in dhcpd.conf: if option architecture-type = 00:09 { filename "efi64/syslinux-87020-or.efi"; option pxelinux.pathprefix "http://bla/efi64/"; } elsif option architecture-type = 00:07 { filename "efi64/ipxe-git87981.efi"; } else { filename "pxelinux.0"; }

...(The firmware then immediately clears the screen, so a human being without a capturing tool can't read it, but that's another story) So.. something else must be the problem. Did I change something else in between? Absolutely! I commented out this line in dhcpd.conf: option pxelinux.pathprefix "http://10.X.255.254:8080/tftpboot/efi64/"; Put it back in => *crash* Making the path very short ("http://x/") => *crash* But when I leave out the http part => graceful exit. Attached is a patch that works against both commits so you can see where the extra debuggi...

...forwarding false; # No IP forwarding option mask-supplier false; # Don't respond to ICMP Mask req server-name "dhcp209l"; next-server 192.168.0.100; option space pxelinux; option pxelinux.magic code 208 = string; option pxelinux.configfile code 209 = text; option pxelinux.pathprefix code 210 = text; option pxelinux.reboottime code 211 = unsigned integer 32; subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.1 192.168.0.88; option routers 192.168.0.100; } host rhelclient { next-server 192.168.0.100; option pxelinux.configfile "linux-install/pxelinux.cfg/d...

...hich version of pxelinux.0 is it possible to boot on UEFI? Those questions elaborated: What I want is fast netboot UEFI servers. What I'm looking for is an advice which version of PXELINUX between version 4.something and 6.03pre18. If http transport only works with DHCP Option 210 (pxelinux.pathprefix), please tell so. If pxelinux can't do UEFI booting, please tell so. Groeten Geert Stappers -- Leven en laten leven

...f exists dhcp-parameter-request-list { # Always send the PXELINUX options (specified in hexadecimal) option dhcp-parameter-request-list = concat(option dhcp-parameter-request-list,d0,d1,d2,d3); } option pxelinux.magic f1:00:74:7e; option pxelinux.configfile "menu.cfg"; option pxelinux.pathprefix "/"; filename "pxe_bin/pxelinux.0"; next-server <tftp_server_ip>; In my menu.cfg, I tried the following to to chainload the ubuntu installer: UI pxe_bin/menu.c32 PROMPT 0 MENU TITLE PXE Boot Menu LABEL ubuntu_10_10_amd64 MENU LABEL Ubuntu 10.10 (Meerkat) AMD64 KERNEL pxe...

...c syslinux-3.82/core/comboot.inc --- syslinux-3.82-orig/core/comboot.inc 2009-06-09 10:19:25.000000000 -0700 +++ syslinux-3.82/core/comboot.inc 2009-07-27 11:23:23.000000000 -0700 @@ -963,6 +963,24 @@ mov ecx,P_ECX jmp shuffle_and_boot_raw + +; +; INT 22h AX=0025h Change PathPrefix +; +comapi_changedir: + push di + push ds + mov ds,P_ES + mov si,P_SI + mov di,CurrentDirName + call strcpy + pop ds + pop di + clc + ret + + + section .data %macro int21 2 @@ -1022,6 +1040,7 @@ dw coma...

...respond to ICMP Mask req >> > server-name "dhcp209l"; >> > next-server 192.168.0.100; >> > option space pxelinux; >> > option pxelinux.magic code 208 = string; >> > option pxelinux.configfile code 209 = text; >> > option pxelinux.pathprefix code 210 = text; >> > option pxelinux.reboottime code 211 = unsigned integer 32; >> > >> > subnet 192.168.0.0 netmask 255.255.255.0 { >> > range 192.168.0.1 192.168.0.88; >> > option routers 192.168.0.100; >> > } >> > >> >...

...issue. To start debugging here are some of my settings: Configured DHCP options in isc-dhcp-server 4.3.5-3: option architecture-type code 93 = unsigned integer 16; option space pxelinux; option pxelinux.magic code 208 = string; option pxelinux.configfile code 209 = text; option pxelinux.pathprefix code 210 = text; option pxelinux.reboottime code 211 = unsigned integer 32; class "pxeclients" { # 1. Dont know exactly what this if-statement does # 2. Aparently the pxelinux.pathprefix is ignored (perhaps a Debian DHCP issue) # So the ln -s workarround is nee...

...rding > option mask-supplier false; # Don't respond to ICMP Mask req > server-name "dhcp209l"; > next-server 192.168.0.100; > option space pxelinux; > option pxelinux.magic code 208 = string; > option pxelinux.configfile code 209 = text; > option pxelinux.pathprefix code 210 = text; > option pxelinux.reboottime code 211 = unsigned integer 32; > > subnet 192.168.0.0 netmask 255.255.255.0 { > range 192.168.0.1 192.168.0.88; > option routers 192.168.0.100; > } > > host rhelclient { > next-server 192.168.0.100; > filename &q...

...very unlikely.... > A complete wireshark traffic capture would be handy. I will send you one directly. I can reveal now that it will not contain any packets after it has downloaded syslinux.efi. > Are you trying to retrieve anything using http? Yes, so in this case syslinux has parsed the pathprefix and is about to setup a http-connection to the server. If I leave out the pathprefix, the errormessage changed to 'core_udp_connect: stalling on configure with no mapping'. Looking at udp.c, the cause is also EFI_NO_MAPPING. Unfortunately I can't test this any more, because since up...

...to gPXE. Note that currently chainloading other NBPs from gpxelinux.0 is broken. This will be fixed. In order to invoke the new functionality, you need a filename or filename prefix which is a URL, identified by the character sequence. In my test setup, I simply use DHCP option 209 (pxelinux.pathprefix) to redirect loading to my http server. Please test it out and holler when (not if) it breaks. A huge amount of effort has gotten into this, and I would like to thank specially Michael Brown of the Etherboot/gPXE project, without whom this never would have been possible. -hpa

...doing my testing using a vCetner 4.10 Vmware virtual machine. This works some of the time, but not always. I just copied the prebuilt modules from the syslinux 4.04 distribution for gpxelinx.0, menu.c32, reboot.c32, and pxelinux.0 When I boot a machine dhcpd says to boot gpxelinux.0 with pxelinux.pathprefix "http://10.250.50.72/tftpboot/gpxe/" and pxelinux.configfile "menu.pl" so that menu.pl generates the real configuration information for the chain loaded pxelinux.0. I see the startup messages from gpxelinux.0 and pxelinux 4.04, a message saying that menu.pl was loaded OK, and t...

...ate transfer speeds given a large enough file. > What I'm looking for is an advice which version of PXELINUX > between version 4.something and 6.03pre18. I'd suggest 6.02 or the latest 6.03-pre release (currently 18). > If http transport only works with DHCP Option 210 (pxelinux.pathprefix), > please tell so. No need. > If pxelinux can't do UEFI booting, please tell so. See second statement. -- -Gene

...he filename for ldlinux.EXT. The code appears to do that, but what the TFTP server sees is a second request for /efi/syslinux.efi and then ldlinux.e64 searched for in the hard coded search_directories list which doesn't match my network configuration. If I change the DHCP configuration to use pathprefix set to /efi/ then it finds ldlinux.e64 and can find my configfile, but I want to follow the layout recommended in the wiki documentation where I could have all three of bios, e32 and e64 versions of com32 modules in subdirectories of the same parent expecting a PATH directive to find he right versi...

...the latest 6.03-pre release (currently 18). With syslinux-6.03-pre18/bios/core/lpxelinux.0 I have the wanted HTTP transfers. (With syslinux-6.03-pre18/bios/core/pxelinux.0 no succes yet on my (old) virtualbox test environment ) > > If http transport only works with DHCP Option 210 (pxelinux.pathprefix), > > please tell so. > > No need. Nope, no extra DHCP server configuration needed (in my test environment with VirtualBox O.S.E.). > > If pxelinux can't do UEFI booting, please tell so. > > See second statement. What I read / understand is that for UEFI netboot r...