similar to: localboot in pxelinux recurses back into pxelinux then eventually crashes

Hello, A couple of months back there was this message on the list. http://syslinux.zytor.com/archives/2010-October/015459.html I have exactly the same result on just a few types of machines. Acer Tavelmate 8372 and 5742 InsydeH2O Bios v1.05 Broadcom UNDI PXE 2.1 V 14.0.8 It started after I upgrades pxelinux.0 to version 3.86 Versions tested and got the recursing: 3.86, 3.85, 3.84 and 3.83 On

Hi H. Peter Anvin, I wanted to thank you for sharing information about PXE, I have used this a lot and I wanted to share something that may be important for you and your readers. I have many different Dell model, they all worked well with PXE booting however not for E5510. I noticed that using "LocalBoot -1 or 0" doesn't work well. What I did use for Latitude E5510 (Bios A06)

Hi, After yum update on a Cent OS 6.0 IBM x3850 server to Cent OS 6.1, the kernel crashes on boot. I have googlet a little, and find that others have the same problem and there seems not to be a solution yet. The kernel that crashes is 2.6.32-131.21.1.el6.x86_64. If i boot the prior kernel 2.6.32-71.29.1.el6.x86_64 instead it works! Is it advisable to run the server with kernel

Hi all, I have searched the net and haven''t found a good answer so I hope perhaps someone here can help. I have an IBM x3850 (8863) that I am upgrading from SLES11SP1 to SLES11SP2, and at the same time XEN is being upgraded as part of the distro. The server is used as a Xen host for up to 6 guests. Anyway, the server boots fine with the SLES11SP2 default kernel, and the trace

Hi, I am new to virtualization and I am having the obvious hassle of choosing between Xen and KVM. Can Xen experts help me with this? Regards, Arindam _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Message: 7 Date: Wed, 15 Jun 2011 19:17:36 +0800 From: Lee Eric <openlinuxsource at gmail.com> To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> Cc: Wen Wei Tang <tangww at cn.ibm.com>, Xiao Dong Zhao <zhaoxd at cn.ibm.com>, Shu Hua SH Chen <cshchen at cn.ibm.com> Subject: Re: [syslinux] error when booting Message-ID:

I notice for some reason you can no longer get pre- builds from the listed place. Can you point me to a better location? UEFI boot isn't working on my hardware so I'd like to try something newer. It is an IBM x3850 X6 if that's interesting info. ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \UTGERS |---------------------*O*--------------------- ||_//

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 I have a similar problem. Hardware configuration: - IBM x3850 server - 6GB DDR2 RAM - IBM ServeRAID 8i configured to RAID0 - 2x DualCore Xeon processors with HyperThreading. The following options available for CPU: - HyperThreading - Processor Adjacent Selector Prefetch - Processor Hardware Prefetcher - Processor Execute

Hi, we use PXELINUX in our product to show a boot menu on client computers, with options like "Boot from local hard disk", "Install Windows", etc. Unfortunately, a lot of computers seem to have broken BIOSes and won't boot with the LOCALBOOT command, and need to be booted with chain.c32 instead. We also have encountered some computers where it works only the other way -

Hi, I just found this post: http://syslinux.zytor.com/archives/2005-September/005814.html ONTIMEOUT was broken in menu.c32, and you fixed it. But the fix broke support for LABEL references in ONTIMEOUT. I changed my "ONTIMEOUT local" to "ONTIMEOUT .localboot -1" and it works! Anoying is that I tried ONTIMEOUT LOCALBOOT -1 before. This failed, but after having a look at the

Hi, I'm trying to get the LOCALBOOT option to work with syslinux. I have a bootable USB that boots using syslinux and when ever I select the localboot label it says that it could not find the kernel image. This is my syslinux set up LABEL start localboot 0x80 and when I type "start" at the boot prompt this is what I get back "Could not find kernel image: start" Is

On Mon, Oct 26, 2015 at 02:03:08PM -0600, Alan Sparks via Syslinux wrote: > On 10/26/2015 1:46 PM, Geert Stappers via Syslinux wrote: > > On Mon, Oct 26, 2015 at 12:09:40PM -0600, Alan Sparks via Syslinux wrote: > >> I'm still trying fruitlessly to get some sort of local disk boot from > >> syslinux EFI to work... using the 6.03 modules. Tried various > >>

A detailed description of our status and dilemma is given below... This week I've been on samba.org and searched the MARC mailing list archives for discussions pertinent to our situation. My search for "slow DOS client" produced over 100 hits dating back to the last millennium, some of which were really about something else. Many of the rest were descriptions of problems VERY

A bug in command localboot was introduced in version 6.03. This bug was created because of inserting memsets in core/localboot.c. The third memset before /* Read one sector */ clears the field ireg.edx, which was assigned earlier and is required for subsequent __intcall0x13. So localboot type works as localboot 0. I think, this third memset in core/localboot.c is useless and excessive.

On 10/26/2015 1:46 PM, Geert Stappers via Syslinux wrote: > On Mon, Oct 26, 2015 at 12:09:40PM -0600, Alan Sparks via Syslinux wrote: >> I'm still trying fruitlessly to get some sort of local disk boot from >> syslinux EFI to work... using the 6.03 modules. Tried various >> combinations of configurations on Gene's test binaries. > > The test binariers Gene

Hi, We have been testing the localboot functionality today and it could be useful if localboot was a com32 module rather than a configuration directive so that one can use it on the boot prompt, rather than require a menu entry/alias at all times. A more userfriendly localboot.c32 could do this and allow eg for friendly device-names. localboot next localboot floppy0 localboot hdd0 or

pxelinux, when given a localboot=... option, will try to boot next bios device itself. The problem is it takes next BIOS device by BIOS order of enumeration. That has no connection with the boot order defined in BIOS. Since a user cannot control BIOS enumeration but can control the boot order, there is no way one can force a desired next device for local boot with pxelinux. In general, you

Ive got a soekris 4801 on which Ive used pxelinux... its bios is set to go to pxeboot 1st, then localboot. Ive got: label bootlocal MENU label ^9 Boot Local localboot 0 # timeout 80 # TOTALTIMEOUT 9000 but using hangs: Booting from local disk... PXE-M0F: Exiting MacPhyter PXE ROM. then nothing. the same compact flash image works fine when boot order is 80 1st, or

On Mon, Oct 26, 2015 at 2:09 PM, Alan Sparks via Syslinux <syslinux at zytor.com> wrote: > I'm still trying fruitlessly to get some sort of local disk boot from > syslinux EFI to work... using the 6.03 modules. Tried various > combinations of configurations on Gene's test binaries. > > For reference this is on different models of HP Proliant Gen-9 systems > with

Summary ======= I am having trouble with com32 API call AX=0014h [3.10] Local boot [PXELINUX, ISOLINUX] Input: AX 0014h DX Local boot parameter Output: Does not return My observation is that is returning from the call and is not localbooting the system. Detail ====== I am using a com32 program to configure some hardware before I boot from the local