similar to: Bugs in pxelinux.asm - syslinux 3.75

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

Tim Legge has passed the following message on to me: hpa wrote: > Quinn wrote: > > Now it seems I have found a bug in PXELINUX with regards to etherboot. > > Up until 2.07 pxelinux was responsive to the keyboard. From 2.08 and > > up the keyboard is locked at the boot prompt when pxelinux is loaded > > via etherboot 5.3.14. > > That would not be a PXELINUX bug,

Hi all, I currently use iPXE to load memdisk and, subsequently, a FreeBSD disk image to perform an OS installation to disk. This works great in BIOS, but upcoming requirements make UEFI a prerequisite. Because memdisk is not UEFI-aware, new UEFI-aware media is necessary. The current plan is to integrate the installation scripts (currently in the hard drive image) into a bootable FreeBSD ISO

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

Hi. I've ever wondered how nuch timeis left to timeout while waiting at the boot prompt, so I've writen this small patch to show it. This add a configuration command 'showtimeout'. If you like the patch I could improve it (for example to show the timeout in decimal because now it uses the writehex functions) Regards. -- ______ ________ / / \/ /___ ) I N T E G

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

Hi, We're planning to deploy PXELINUX as a primary kernel loader in cluster environment. Problem is that we plan to have IP numbers assigned dynamically while there is no guarantee that all machines has same CPU architecture. This makes IP-based config search algorithm inappropriate for our purposes because we [naturally] expect loaded kernel to match hardware. For this reason I've

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

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

> 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

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

On 1/23/2017 09:17, Rick Miller via Syslinux wrote: > Hi all, > > I currently use iPXE to load memdisk and, subsequently, a FreeBSD disk > image to perform an OS installation to disk. This works great in BIOS, but > upcoming requirements make UEFI a prerequisite. Because memdisk is not > UEFI-aware, new UEFI-aware media is necessary. The current plan is to > integrate the

Whoops, apologies. The intent was to send this email to ipxe-devel. I'll repost to that list. On Mon, Jan 23, 2017 at 10:12 AM, Shao Miller <ipxe at sha0.net> wrote: > On 1/23/2017 09:17, Rick Miller via Syslinux wrote: > >> Hi all, >> >> I currently use iPXE to load memdisk and, subsequently, a FreeBSD disk >> image to perform an OS installation to

Hi, I just tried to boot my token ring devices with 2.05 - to no avail, it hangs after loading the kernel. I then tried older versions, and found 2.03 booting like a charm, and every 2.04-pre including 2.04 hanging. Here's the config of the devices: - Networkstation 2800 with IBM PCI Token Ring card 2 - IBM Thinkpad T21 with IBM PCI Token Ring card 2 Maybe this has to do with the changes

Hi, I've checked the archives for my issue, and while there is relevant discussion, the problem the original poster was asking about didn't seem to have been resolved then either (~2 years ago). At any rate, basically what I'm trying to do is send (possibly receive) UDP packets via the PXE stack using the com32 API (using version 3.11 of syslinux). I have followed both the comboot

On Jun 29, 2014 9:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Peter, > > I approached you before on this issue that I?m having with the SYSLINUX 6.03-pre18 when booting with iPXE option ROM. > > The issue was reproduced on different OEMs, and also on 2 different cards (Mellanox and Intel), with latest and 2 years old iPXE code. > > Just

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

From: Gene Cumm <gene.cumm at gmail.com> CORE/writedec: Fix overflow and redeclaration; If EDX is greater than or equal to 10, div can cause an overflow. Comment out declaration of writechr. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Against current head. hpa: If there's a preferred way to do what this function provides, let me know. Was the writechr in there on

Hi, We have a number of HP PC's which were refusing to netboot both floppy and hard disk images with memdisk. Testing the problem under DOS for simplicity, the cause was because the INT 13 AH=0 Disk Reset function call is passed on to the BIOS by memdisk, and it appears that AMI's BIOS (V2.00) returns with the carry set flag if there are no (physical) disks present. This causes a failure