similar to: com32 -> localboot problem

I have a Dell 1435 system that will not respond correctly to a com32 call to Local boot Int 22h AX=14h DX = 0 This call should not return. It should unload the PXE+UNDI stacks and continue the boot process with the next boot device. This call is working fine for me on an HP DL360G2 and on a Dell PE 850. But, on this Dell 1435 the call is returning from the Int 22h. I am using syslinux 3.51

diff --git a/core/localboot.c b/core/localboot.c index 0b8769e4..30bfb272 100644 --- a/core/localboot.c +++ b/core/localboot.c @@ -63,7 +63,6 @@ __export void local_boot(int16_t ax) ireg.eax.w[0] = 0; /* Reset drive */ __intcall(0x13, &ireg, NULL); - memset(&ireg, 0, sizeof(ireg)); ireg.eax.w[0] = 0x0201; /* Read one sector */ ireg.ecx.w[0] = 0x0001; /* C/H/S = 0/0/1 (first

I'm having problems with PXELINUX passing through to a "localboot" on a HP Proliant DL385. I'm working with 3.73. If I configure PXELINUX to directly "localboot", everything works. If I configure PXELINUX to use menu.c32 or anything like that, a subsequent localboot fails. I see the expected "PXE ROM exiting" message but the next device doesn't

On Mon, Jan 21, 2019 at 3:37 AM Victor Sologoubov via Syslinux <syslinux at zytor.com> wrote: > > diff --git a/core/localboot.c b/core/localboot.c > index 0b8769e4..30bfb272 100644 > --- a/core/localboot.c > +++ b/core/localboot.c > @@ -63,7 +63,6 @@ __export void local_boot(int16_t ax) > ireg.eax.w[0] = 0; /* Reset drive */ > __intcall(0x13,

HAS_LOCALBOOT is set unconditionally in config.inc. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/core/comboot.inc b/core/comboot.inc index 59db7ec..d6f670c 100644 --- a/core/comboot.inc +++ b/core/comboot.inc @@ -723,13 +723,9 @@ comapi_idle: ; ; INT 22h AX=0014h Local boot ; -%if HAS_LOCALBOOT comapi_localboot: mov ax,P_DX jmp local_boot -%else

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

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

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

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

I created a bootable usb flash with boot menu. One of items was "Boot from hard drive" with command "localboot 0x81". This item worked when this usb flash was prepared with syslinux 6.02. And it stopped working when the flash was prepared with syslinux 6.03. The message was Booting from local disk... Boot error I extracted the source code, investigated, changed, compiled

Our site has many Dell OptiPlex 790s, all of which are unable to use the 'localboot' PXELINUX option as they either hang at 'Booting from local disk...' or immediately reboot depending on which SYSLINUX version is used. Many people have suggested using chain.c32 to chain load the local disk as a workaround, but this causes problems with Windows 7 BitLocker as it detects the chain

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

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.

I'm bringing back an old thread, but I'm still having problem with this: http://etherboot.org/pipermail/gpxe/2010-March/000571.html The summary of that thread is that with gpxelinux.0, on some computers the command LOCALBOOT 0 will hang the computer. Around the same time as the original thread, there was a patch to add localboot -1. Also in the original thread, it was proposed to use

2013/8/6 H. Peter Anvin <hpa at zytor.com> > What about "chain.c32 hd1" or "chain.c32 hd1 swap"? > That's right, but due to our pxe environment we need a static entry which handles both, booting from first and second hdd if one fails. localboot does so. > > Jonas Keidel <jonas at jonas-keidel.de> wrote: > >2013/8/5 Jonas Keidel <jonas at

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 provided don't have a localboot module. It is wrong to mix components from different

Can you detail what bug that introduce ? Behavior with the current code and with your change proposal ? That's pretty unclear for me. Thanks ! Le mer. 16 janv. 2019 ? 07:46, Victor Sologoubov via Syslinux <syslinux at zytor.com> a ?crit : > > A bug in command localboot was introduced in version 6.03. > This bug was created because of inserting memsets in core/localboot.c. >

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

2013/8/5 H. Peter Anvin <hpa at zytor.com> > On 08/05/2013 06:04 AM, Jonas Keidel wrote: > > 2013/8/5 H. Peter Anvin <hpa at zytor.com> > > > >> On 08/05/2013 05:37 AM, Jonas Keidel wrote: > >>> I have problems with the current syslinux (6.02-pre16) booting CentOS > 6.4 > >>> 64bit via LOCALBOOT 0 with the Intel DX79TO. > >>