similar to: lpxelinux.0 - 6.02 - failed to load ldlinux.c32

On Sat, Oct 26, 2013 at 4:08 AM, Petry Roman, SHS-S IT-TS <Roman.Petry at shsservices.org> wrote: > 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. You're right. Since you can't

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

Hello Gene, thanks for finding that.. i will try tomorrow again and send the output to the list.. Bye roman -----Urspr?ngliche Nachricht----- Von: Syslinux [mailto:syslinux-bounces at zytor.com] Im Auftrag von Gene Cumm Gesendet: Samstag, 26. Oktober 2013 14:26 An: For discussion of Syslinux and tftp-hpa Betreff: Re: [syslinux] lpxelinux.0 - 6.02 - failed to load ldlinux.c32

O.K Here we go: 8-) Pxelinux 4.10 4.10-pre22 Copyright ..... !PXE entry point found (we hope) at 9073:00F6 via plan A UNDI code segment at 9073 len 216A UNDI data segment at 9059 len 01A0 UNDI: baseio ec00 int 11 MTU 1500 type 1 "DIX+802.3" flags 0x81b Getting cached Packet 01 02 03 MY IP addr seems to be 172.31.126.10 UNDI : IRQ11(0x73):0a63:4f9b -> 0000:8de2 Mac: Addr: 80 ee 73

Hello Gene, >>>They're flags to indicate the behavior of the UNDI interface. >>>Unfortunately, my first suspicion appears to be wrong. A flags value of 0x81b does not indicate that the UNDI interrupts should be used. So we/you or i am on a dead end to get it running or debugged ? is there hope to get it more debugged , with a special build or so ? someone wanting to port

On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu> 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 although I'll give pre18 a try soon, some

So there seem to be some shortcomings in NTFS, still. 1. Symlinks are not supported. Proper symlinks exist in NTFS since Vista, so we should support them. 2. readdir() seems to be broken. I have been using the following test load to generate disk images: http://www.zytor.com/~hpa/syslinux/exttest-20140521.tar.xz Anyone who has been involved with the NTFS code who has a chance to take a

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".

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...

On 07/10/2014 04:07 PM, Alexander Perlis wrote: > Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel > Boot Agent 1.3.81 (2.1 build 089). It gets network and launches > lpxelinux.0, I see the PXELINUX banner line, but there it hangs. > > I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead > use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or

On Fri, Jul 11, 2014 at 5:49 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/11/2014 04:31 PM, H. Peter Anvin wrote: >> >> On 07/11/2014 10:17 AM, Alexander Perlis wrote: >>> >>> >>> Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that >>> there is only ARP traffic: a "gratuitous" ARP announcement by

On 07/11/2014 10:17 AM, Alexander Perlis wrote: > > Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that > there is only ARP traffic: a "gratuitous" ARP announcement by the > client, and then a string of ARP requests and replies in which the > client is asking for the MAC of the PXE server, about every 3 seconds, > for about 2 minutes, after which I

Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel Boot Agent 1.3.81 (2.1 build 089). It gets network and launches lpxelinux.0, I see the PXELINUX banner line, but there it hangs. I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or 5.10 or 4.07, there are no problems. The problem seems isolated to

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

Hi all, I try to switch from pxelinux.0 to lpxelinux.0 as a PXE boot loader. With pxelinux.0 I am able to boot my Linux kernel and initrd without any problems. When I change DHCP option 67 to lpxelinux.0 this file gets loaded via TFTP. On the client screen I see the welcome message (PXELINUX 6.03 lwIP ?) but nothing more. Sniffing revealed that there are no further attempts to load

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

On 07/10/2014 06:39 PM, Gene Cumm wrote: > On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: >> On 07/10/2014 04:07 PM, Alexander Perlis wrote: >>> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >>> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >>> lpxelinux.0, I see the PXELINUX banner line,

On Tue, Jul 5, 2016 at 2:16 AM, Christof B?ckler <syslinux at zytor.com> wrote: > Hi all, > > I try to switch from pxelinux.0 to lpxelinux.0 as a PXE boot loader. With > pxelinux.0 I am able to boot my Linux kernel and initrd without any > problems. > > When I change DHCP option 67 to lpxelinux.0 this file gets loaded via TFTP. > On the client screen I see the welcome

Decided to try out lpxelinux on a couple of Dell R610s. Both versions 5.10 and 6.03 hung on a server with fairly up-to-date BIOS (6.1.0), but work fine on another R610 with old BIOS (1.2.6). Watching the TFTP log and running tcpdump on the PXE server, I see it download pxelinux.0 (renamed from lpxelinux.0), but it never even tries to transfer anything after that succeeds. It eventually (seems

On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/10/2014 04:07 PM, Alexander Perlis wrote: >> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >> lpxelinux.0, I see the PXELINUX banner line, but there it hangs. >> >> I tried both 6.03-pre18