similar to: Hanging menu.c32 with recent pxelinux

Displaying 20 results from an estimated 40000 matches similar to: "Hanging menu.c32 with recent pxelinux"

2005 Jun 23
2
hanging pxelinux.0 and menu.c32 on Dell 1850
Hello all. I've got this weird problem. If I try to boot a simple menu using syslinux's (v 3.09) pxelinux.0 and menu.c32 -files my Dell 1850 loses the keyboard / hangs straight after loading menu.c32. The machine has to be powered off completely. I did some research and got it working by using menu.c32 v3.09 and pxelinux.0 v3.07 -combo. It seems that from version 3.08 on something has
2009 May 22
2
pxelinux.bin (3.80) hanging at the beginning of menu.c32 TFTP transfer
Hi, Using syslinux 3.80, I'm seeing pxelinux.bin hanging after the (succesfull) transfer of the default file. Running a lan trace, it appears that all goes fine until the time pxelinux sends a TFTP RRQ for menu.c32 to the TFTP server, gets the first data packet back, and apparently freezes at this point. The TFTP server then times out and retries (3 times) then finally sends an error packet
2005 Aug 23
5
SYSLINUX 3.10-pre20 menu.32 hang in SIS900 bootrom
Hi, HPA: Thanks for the nice new features, appreciate that. Syslinux is always a nice program. For the new version, 3.10-pre20, I encountered a problem now, my client machine uses sis900 chip, and it still can not run simple menu with pxelinux in this version (3.10-pre20). It's same situation as I encountered when I used syslinux 3.07, 3.08 and 3.09. For 3.10-pre20, I compiled in Fedora
2008 May 14
1
[PXELINUX] menu.c32/vesamenu.c32 and MS Virtual PC 2007 --> Hang/crash
Hi, I've recently did some extensive testing with PXELinux and I must say it's great! I've tested it with several pc's and VMware vm's at home, this works flawlessly. However at my work, we only use MS Virtual PC 2007 and so on. I've started today to testimplement pxelinux into wds/ris, this seems to work but when I want to display a menu eg: default menu.c32, then
2007 May 24
1
Help!I have problem in using pxelinux about menu.c32 and vesamenu.c32
Thanks very much for syslinux and pxelinux,they bring me many conveniences.I have problem in some computers.My english is very poor,so i submit in chinese and poor english.First I say sorry! ????pxelinux???sis900??????????? ????????default???????menu.c32??vesamenu.c32????? ???default???????DEFAULT memdisk c=638 h=2 s=18 floppy append initrd=netboot.zip???????????????????????? ???3com?boot image
2005 Jul 07
0
pxelinux and DISPLAY
Hey, I just wanted to mention that the same problem still exists for me in version 3.09, altough the changelog mentions: Reduce the command line to 511 characters; 1023 caused memory overflows. Was this meant to be a solution for this problem, or does this entry of the changelog apply to another bug? thx, marco >Yesterday Curtis Doty said: > > > >>I've begun
2005 Sep 13
2
Fw: Issue with pxelinux
I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken
2007 Dec 10
2
Reloading pxelinux via menu.c32
Hi All, I have used menu.c32 to offer several booting options to our users via pxelinux... the icing on the cake would be if there was some mechanism whereby the pxelinux boot could be restarted, with the usual search for pxelinux.cfg/... files... all without a reboot and going through POST. Does anyone know if this is possible or if a comboot module exists for such a thing ? Cheers, Doug
2015 Sep 22
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Tue, Sep 22, 2015 at 1:42 PM, Alan Sparks <asparks at doublesparks.net> wrote: > On 9/22/2015 4:33 AM, Gene Cumm wrote: >> >> https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 >> https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 >> > > Tried these new binaries this morning. No
2005 Dec 02
3
PxeLinux menu.c32 chaining
Hello, many of our platforms do not have a integrated floppy, some even don''t have a floppy controller. As pxelinux still has a problem with machines without a floppy in combination with some bios versions I need to chainload a different bootstrap loader which works on the floppyless platforms. But I also need to load a BartPE and the other BS loader does not support that. So I tried to
2016 Jun 16
0
PXELINUX 6.03 / vesamenu.c32 hang
On Thu, Jun 16, 2016 at 4:53 AM, Jackson, Dan via Syslinux <syslinux at zytor.com> wrote: > Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). > > Thanks, > Dan Jackson (Lead ITServices Technician). > > -----Original Message----- > From: Syslinux
2016 Jun 16
0
PXELINUX 6.03 / vesamenu.c32 hang
I've just tried 4.07 and that has the same results. I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt to choose the Windows Deployment Services option, it hangs. Thanks, Dan Jackson (Lead ITServices Technician). -----Original
2015 Sep 23
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
> On 9/23/2015 12:14 AM, Ady via Syslinux wrote: > > > About your customers' setup... > > Are they using official binaries downloaded from kernel.org? > > Yes. Stock versions, no local modifications. > > > Which exact version of Syslinux are they using? > > I've tried versions 3.86, 4.07, 6.01, 6.03. > We can only generally use 4.07 or less
2016 Jun 15
0
PXELINUX 6.03 / vesamenu.c32 hang
> Hello, > > I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). > > This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the
2010 Mar 24
2
INCLUDE is broken in pxelinux/menu.c32 3.85
I was trying out the INCLUDE command within menu.c32 (via pxelinux, actually gpxelinux) and noticed that it's broken. The symptom is that the text is included, as expected, but the subsequent text from the including file is wrong. In some cases it actually pulls from above the INCLUDE leading to the INCLUDE being reprocessed (an infinite recursion). (The recursion seems to stop after 20-30
2005 Feb 25
1
corner cases in 308-pre5, pxelinux.cfg/default, esp w simple menus
the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs
2006 Aug 12
1
[pxelinux] load a special (non menu.c32) cfg file from menu.c32
Hi! I have a PXE Server witch uses a the simple menu system. Is all working great also with submenus. What i want is a entry in the pxelinux.cfg/default file that can load a non-menu cfg file for the pxelinux.0. The background is, that i have here a DamnSmallLinux that is booting from PXE. it has a own cfg file but without the simple menu system (with F1-F2-F3 and a logo.16). If i move
2005 Jun 01
0
no menu.c32, no problem...
Fellow syslinux fans, I'm using syslinux on a boot floppy (I'll call this syslinux A) to invoke an etherboot image (zlilo style) which invokes a tagged NBI image from my DHCP/TFTP server. The tagged NBI image is created using mknbi-dos and also uses syslinux (I'll call this syslinux B), a linux kernel and an initrd file. It works perfectly if syslinux A has a basic .CFG, e.g.:
2015 Sep 23
3
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/23/2015 12:14 AM, Ady via Syslinux wrote: > About your customers' setup... > Are they using official binaries downloaded from kernel.org? Yes. Stock versions, no local modifications. > Which exact version of Syslinux are they using? I've tried versions 3.86, 4.07, 6.01, 6.03. We can only generally use 4.07 or less because of the described ipxe compatibility issues, 6.0x
2015 Sep 22
7
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/22/2015 4:33 AM, Gene Cumm wrote: > > https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 > https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 > Tried these new binaries this morning. No change, still will not attempt to load ldlinux.c32. As a context, what I'm really trying to do is get a newer