search for: pxenv

Hi All, I have encountered a problem when reading PXELinux's source code. In syslinux/core/pxelinux.asm, function *pxenv* is as below: pxenv: pushfd pushad ; We may be removing ourselves from memory cmp bx,PXENV_RESTART_TFTP ...... push es push di push bx .jump: call 0:0 add sp,6 mov [cs:PXEStatus],ax ...... ret "Around" .jump, we store ES:DI and BX on PXE stack, which points to PXE para...

In pxelinux.asm the xchg instruction in xchg ax,ax . data_on_top: should be xchg ax,dx, I think At the end of pxe_get_cached_info routine,there is and ax,ax jnz .err It is supposed to test for AX status, but since pxenv does pushad and popad, AX doesn't contain status. In fact the other routines calling pxenv don't have this bug. pxe_unload seems to be never called; if so, also RealBaseMem is unused. According to the specification, pxe_unload_stack_pkt.reserved are 10 bytes, not 10 words

...i/blib.a(pxe_entry.o): In function `pxe_segments': (.text16.data+0x36): undefined reference to `_text16_memsz' bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxe_segments': (.text16.data+0x3e): undefined reference to `_text16_memsz' bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': (.text16.data+0x76): undefined reference to `_data16_memsz' bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': (.text16.data+0x82): undefined reference to `_data16_memsz' bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': (.text16.data+0x86): undefined reference to...

...): In function `pxe_segments': > (.text16.data+0x36): undefined reference to `_text16_memsz' > bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxe_segments': > (.text16.data+0x3e): undefined reference to `_text16_memsz' > bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': > (.text16.data+0x76): undefined reference to `_data16_memsz' > bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': > (.text16.data+0x82): undefined reference to `_data16_memsz' > bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': > (.text16.data+0x86...

...pxe_segments': >> (.text16.data+0x36): undefined reference to `_text16_memsz' >> bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxe_segments': >> (.text16.data+0x3e): undefined reference to `_text16_memsz' >> bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': >> (.text16.data+0x76): undefined reference to `_data16_memsz' >> bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': >> (.text16.data+0x82): undefined reference to `_data16_memsz' >> bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv': >&gt...

Hi, I've been hacking this week-end on a Vortex86[0] based device (ebox 3300) and had quite a few trouble with pxelinux.0 on it. Actually, I narrowed the problem to the `pxenv' routine always returning 1. This lead to an infinite loop while trying to transfer the config file. I'm not sure what the problem is, but the FreeBSD PXE bootloader does work on the same hardware, with the same settings, so pxelinux.0 must be doing something wrong. Has anyone ever had a s...

Hi, I've got pxelinux 2.00 working to boot rh 7.3, 8.0, and phoebe-beta pxe install images but I've recently tried to load the rh 9 pxe install images and I get this.. 4000 AX:0208 BX:0200 CX:0002 DX:0000. Any thoughts? Thanks aaron

...append nfsroot=10.1.1.53:/usr/local/linuxnc/2.8-t/img devfs=mount ip=dhcp label 28t-check kernel lfs28 append initrd=initrd28 root=/dev/ram0 init=/linuxrc devfs=mount ip=dhcp [+/- wraparounds ...] 2.03 messages (all typed off the screen ...): PXELINUX 2.03 2003-04-10 [..] Found PXENV+ structure Old PXE API detected, using PXENV+ structure UNDI data segment at 0000 UNDI data segment size: 0000 UNDI code segment at: 0000 UNDI code segment size: 0000 PXENV entry point found (we hope) at 9981:0BE0 My IP address seems to be 0A01A8F8 10.1.168.248 ip=10.1.168.248:10.1.1.53:10.1.1...

...going to work but then hangs. The dialog below is from a vmware session just for testing but I have the exact same problem on an old IBM box with a Intel e100 card. Here is the output: Node: 0050567891DB DHCP.. TFTP........ PXELINUX 2.02 2003-02-13 Copyright (C) 1994-2002 H. Peter Anvin Found PXENV+ structure PXE API version is 0200 Old PXE API detected. using PXENV+ structure UNDI data segment at: 9840 UNDI data segment site: 5BE8 UNDI code segment at: 9DFF UNDI code segment size: 1810 PXENV entry point found (we hope) at 9DFF:0000 My ip address seems to be <IP HEX> <IP> ip=<...

It seems that 2.03-pre1 resolves PXELINUX problem on a reasonable number of hosts. Perhaps somewhat importantly this seems to include the RBFG PXE boot floppy, which did not work with 2.02. This was somewhat of a surprise, since it didn't exhibit the failure mode that I would have thought would have been the trigger of the bug. Instead, it was one of those stacks that would transmit packets

...f the PXE services stack." (not sure exactly what that means yet) I ask this because I'm getting a General Failure Error (ax = 0x1) and I think its because I am using a different stack. I also notice that when I do get this error status nothing is copied into the buffer I supply (like a PXENV error code) which kinda sucks. This leads me to believe an issue with me setting up a different stack before the far call. >From the code: ; That is all pushed onto the PXE stack. Save the pointer to it ; and switch to an internal stack. mov [InitStack],sp mov [InitStack+2],ss Comment by m...

Hello all, I want to create a program that runs from a pxe-loaded virtual floppy (using memdisk + keeppxe) to call again PXE boot. I took a piece of code form NILO to look for PXE data structures and the call to function PXENV_START_BASE from PXE spec as follows: lower = (unsigned char *)LOWER_PXE_MEM; upper = (unsigned char *)UPPER_PXE_MEM; for (i=upper; i>lower;i--) { if (memcmp (i, sig, size) == 0) { /* We found it. Now see if it's usable. */ /* Look for the version number. As...

...When I enable the boot: prompt, the prompt is displayed but then keyboard input is not echoed promptly. By that, I mean that if you hit a few keys they wont be echoed until several minutes later. I think the problem relates to the check_for_arp function; if I comment the line in that that calls pxenv, then the keyboard input is echoed promptly. C+A+D still resets promptly. I don't know if the problem exists with real hardware, but I do know that syslinux-2.07 was ok on vmware (but that didn't have the arp code, of course). Is this most likely a bug in the vmware BIOS, or is there som...

Hello Ady, On 27.08.2014 16:46, Ady wrote: >> On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>>>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> >> wrote: >>>>>> On 24.07.2014 13:52, Gene Cumm wrote: >> ... >>>>>> Your special build gets the gateway working, but the

...mware has not a pxe capable bios, using a M$ RIS boot disk, that is a PXE stack on disk, you should be able to boot a VM. I created a boot disk with rbgf.exe.Booted and thats the output: AMD PCnet Adapter Node: [the correct mac address] DHCP... TFTP... PXELINUX 2.06 2003-08-22 Copyright.... Found PXENV+ structure PXE API version is 0063 Old PXE API detected, using PXENV+ structure UNDI data segment at 991B UNDI data segment size: 564D UNDI code segment at: 97BD UNDI code segment size: 15E0 PXENV entry point found (we hope) at 941F:0DAF then nothing happens. Given this information do you th...

> Hello, > > On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: > >>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> > wrote: > >>>> On 24.07.2014 13:52, Gene Cumm wrote: > ... > >>>> Your special build gets the gateway working, but the downloaded InitRD > >>>> still

...and the buffer field of the PXE call argument struct is setup to point into the bounce buffer as well): inputRegs.es = SEG(__com32.cs_bounce); inputRegs.edi.w[0] = OFFS(__com32.cs_bounce); inputRegs.eax.w[0] = 0x0009; /* call PXE stack */ inputRegs.ebx.w[0] = 0x0071; /* PXENV_GET_CACHED_INFO opcode */ __intcall(0x22, &inputRegs, &outputRegs); However, when setup this way, 'outputRegs.eax.w[0]' contains 'PXENV_EXIT_FAILURE' (and the status field of the PXE call argument struct indicates failure as well). The instructions from the previous thre...

From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific

...(feature_flags[__byte] >> __bit) & 1; else return 0; } diff --git a/com32/include/syslinux/pxe_api.h b/com32/include/syslinux/pxe_api.h index 27166b0..203ab38 100644 --- a/com32/include/syslinux/pxe_api.h +++ b/com32/include/syslinux/pxe_api.h @@ -568,4 +568,8 @@ typedef struct s_PXENV_UNLOAD_STACK { #define PXENV_STATUS_LOADER_UNDI_START 0xca #define PXENV_STATUS_LOADER_BC_START 0xcb +int __weak pxe_call(int, void *); +void __weak unload_pxe(uint16_t flags); +uint32_t __weak dns_resolv(const char *); + #endif /* _SYSLINUX_PXE_API_H */ diff --git a/com32/lib/Makefile b...