similar to: lpxelinux.0 with device that doesn't support Interrupts

I am experiencing an issue where I ran ipxe (as an option rom) and downloaded the lpxelinux.0 as the bootloader. Next it should download the ldlinux.c32 file using UNDI API. but before that it will close and open the underlying device (which is ipxe), and hooking the device interrupt so it can start getting some packets. What I'm experiencing is that if the underlying device doesn't

On Mon, Sep 29, 2014 at 11:07 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > Is there a way to compile pxelinux.0 to work with interrupts ? > > I need to check my driver (based on iPXE) which works in interrupt mode (and > not polling) > > > > Thanks for your help. > > Wissam What version? pxelinux.0 or lpxelinux.0? I've never

Hi Gene, Thanks for the quick response. Im using pxelinux4.07. pxelinux.0 I didn?t find any lpxelinux.0 in this version I will try lpxelinux.0 from Syslinux6.03-pre20. Is there lpxelinux.0 in versions earlier than Syslinux5.10? -----Original Message----- From: Gene Cumm [mailto:gene.cumm at gmail.com] Sent: Monday, 29 September, 2014 18:40 To: Wissam Shoukair; For discussion of Syslinux and

On Thu, Jun 5, 2014 at 8:50 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > More information about this? > > I have found in the syslinux git that this commit id is the last good > commit: > > commit 41c29c26d70fde563d7c255872bbadad87a39dfa (tag: > refs/tags/syslinux-5.02-pre3) > Author: Matt Fleming <matt.fleming at intel.com> >

On 02/26/16 15:10, Wissam Shoukair via Syslinux wrote: > > I am experiencing an issue where I ran ipxe (as an option rom) and > downloaded the lpxelinux.0 as the bootloader. > Next it should download the ldlinux.c32 file using UNDI API. > > but before that it will close and open the underlying device (which > is ipxe), and hooking the device interrupt so it can start getting

On May 29, 2014 5:25 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Gene, > > I was wondering how I can set the ?printf? output to be visible on the screen? (I?m using syslinux-6.03-pre02) printf () or dprintf ()? You need to watch what functions are available at the time you want to print. For example, printf isn't available until ldlinux.c32 is

On Fri, Feb 26, 2016 at 01:00:21PM +0000, Wissam Shoukair via Syslinux wrote: > hi > does anyone know if there are some known issues with running lpxelinux.0 > with device that doesn't support Interrupts? > i.e. irq function is null... Take some time to elaborate the question. Cheers Geert Stappers Who thinks that Original Poster doesn't want to hear/read issues.

On 15 Nov 2014 05:06:52 +0200, Ady wrote: > > I would start by updating the BIOS. Prudent advice. As it turns out, I'm already at the latest version. On 15 Nov 2014 07:31:27 +0100, Geert Stappers wrote: > > And would reduce 'iPXE => pxe.0 => lpxelinux.0 => "vmlinux"' > into 'iPXE => "vmlinux"' That makes sense generally, but at

I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some advice on how to isolate and troubleshoot this. (I can't try pre18 at the moment, but did try 4.07 and 5.10 and saw similar behavior, also with pxelinux.0, so although I'll give pre18 a try soon, some isolation/troubleshooting advice will be a good education no matter what.) To get to our PXE-launched tools from

Op 2014-07-01 om 22:55 schreef Gene Cumm: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" wrote: > > > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some > > advice on how to isolate and troubleshoot this. (I can't try pre18 > > at the moment, but did try 4.07 and 5.10 and saw similar behavior, > > also with pxelinux.0, so

Hello Geert Thanks for replying.. But i think i can?t use it, as i don?t reach the point where the debug module will be available.. it just pulls the lpxelinux.0 and tries to get the next download-- the ldlinux.c32 and it fails...and freezes. And the next step would be other modules i think.. if i?m wrong.. excuse me 8-).. yesterday i managed to get ipxelinux working from ipxe.org.. so the nic

Hi All, I've been trying to understand how to use pxechn.c32 to chain a local pxelinux menu item to a remote server which has it's own pxelinux hierarchy served via TFTP and HTTP. We have no control over DHCP next-server and filename fields so I wanted to exploit the "prefix" -p option that pxechn.c32 accepts. I spent a long time hitting my head against a brick wall until I

On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux <syslinux at zytor.com> wrote: > Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 A fork is a fork, regardless the reasons behind it (yes, I have some understanding in this case). iPXE is based off of forking further development as of a certain gPXE commit with some backporting of gPXE development to iPXE. --

On this list in early July 2014 I reported that on certain hardware one cannot chain from ipxe to lpxelinux.0 . My report at the time was about 6.03-pre17. I've repeated the tests with the release version of 6.03 and here is an updated report with more details. I boot to a USB stick with iPXE, which then is told to "dhcp" and then "chain http://xxx.xxx.xxx.xxx/pxe.0".

> Now my question: where more specifically is the bug? What can I do to > help a developer isolate this? I would start by updating the BIOS.

On 07/01/2014 09:55 PM, Gene Cumm wrote: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 ... > > Odd. 4.07 should be good but the 4.10/5.1*/6.0* revisions make sense. My bad. I tried again, and in 4.07 we do get further. We couldn't boot all the way because, it seems, using

Hello everybody, I been using lpxelinux.0 with legacy boot to load KERNEL over http instead of tftp and I want to switch to efi boot. Thank you for the great tech! However it seems the syslinux.efi does not support HTTP / IP? How can I get efi boot load syslinux with an IP stack? # dpkg -S /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi syslinux-efi: /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi # dpkg

On 07/03/2014 08:44 PM, Gene Cumm wrote: > On Thu, Jul 3, 2014 at 9:13 PM, Alexander Perlis wrote: > >> I suppose we could try making an ISOLINUX CD for the local boot, which then >> uses pxechn.c32 to connect to our PXE server? > > pxechn.c32 requires a functional PXELINUX. If I understand the issue correctly, is it that pxelinux.0 does not have a network stack and

On 07/05/2013 01:02 PM, Gerardo Exequiel Pozzi wrote: > > 5.00 [pxelinux.0] OK 5.01 [pxelinux.0] OK 5.02-pre1 > [pxelinux.0] OK 5.02-pre2 [pxelinux.0] OK 5.02-pre3 [pxelinux.0] > BAD (freeze, no error messages, 100% CPU used) > > 5.10-pre1 [pxelinux.0] BAD (freeze, no error messages, 100% CPU > used) 5.10-pre2 [pxelinux.0] BAD (Failed to load: ldlinux.c32,

On 07/03/2014 06:31 AM, Gene Cumm wrote: > On Jul 2, 2014 11:13 AM, Alexander Perlis wrote: > > > Or is there a different (non-ipxe?) way we can locally boot a machine > and get it to chain to our 6.0x pxelinux server? > > Unless this is a completely isolated network, talk with your IT department. > > If there's no DHCP, make a simple server. If there's DHCP and