search for: localbooting

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

I just picked up 3.10-pre15 and the "PXELINUX corrupts graphic filename referenced from DISPLAY file" bug is zapped. Yipee! Thanks hpa. And Arwin too, if that 'xor esi,esi' was the crux. However, LOCALBOOT -1 and LOCALBOOT 0 don't work the same as they did for me in 3.07. :-( 3.07: LOCALBOOT -1 apears to work as I have a hard disk listed in bios boot order after the

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 UEFI. Firmware as up to date as it comes. The UEFI boot order has the hard drives and OS ESPs before the PXE interfaces

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

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

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

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

git://git.zytor.com/users/genec/syslinux.git Branch doc-syslinux-for-hpa Expand upon the explanation of the usage of CONFIG (including a new directory). Edit LOCALBOOT to include the fact that all variants understand LOCALBOOT type -1. Compact the PXELINUX section to one paragraph. -- -Gene

How to boot from syslinux 6.01 over PXE (syslinux.efi) into an EFI installed GPT system on a hdd? Via localboot 0 it doesn't work. (no output) Also via chain.c32 hd0 1 it doesn't work. Errormessage: Can not find MBR magic, treat hdd as raw disk. Stop booting.

Hi, all I can't boot from local drive on some machines(thinkpad x200 and thinkpad x1 carbon) using syslinux 3.05 or syslinux 4.05. And i change localboot 0xffff to localboot 0x80, boot from local drive is available. I find "0x80 is the primary hard drive. The special value -1(0xffff) causes ISOLINUX to report failure to the BIOS, which, on recent BIOSes, should mean that the next

Hi, I am having some problem with LOCALBOOT and menu.c32 This is my isolinux.cfg: ------------------------------------------- default menu.c32 timeout 50 prompt 0 ontimeout local menu title "TITLE" label livecd menu default manu label "LiveCD" kernel gentoo append initrd=initrd.igz root=/dev/ram0 init=/linuxrc looptype=squashfs loop=/ livecd.squashfs

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.

Hi! A friend of mine has tried a PXE floppy (build from the new etherboot 5.3.12) to load PXELINUX.0; a menu voice of the pxelinux.cfg use the LOCALBOOT statement. Selecting this statement, the PC retry to boot from the floppy... is this normal? The user expected that LOCALBOOT would have tried the NEXT boot device (ie CDROM or HD), not the FIRST boot device (the floppy)... (note: this has

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

On 2019-4-10 1:20, Ady Ady via Syslinux wrote: >>> Test #2: if you unplug the USB and reboot the system, can you >>> successfully boot directly to the HDD's OS? >>> >> Yes. The only HDD, NTFS, WindowsXP native boot loader ntldr. > > > Let me rephrase my question. It was/is clear that you used to be able > to boot Windows when the first boot

On 10/26/2015 7:47 PM, Gene Cumm wrote: > On Mon, Oct 26, 2015 at 2:09 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: >> For reference this is on different models of HP Proliant Gen-9 systems >> with UEFI. Firmware as up to date as it comes. The UEFI boot order >> has the hard drives and OS ESPs before the PXE interfaces (the default). >> A

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 hard disk. If I have multiple labels in my pxelinux.cfg/default file then I can successfully localboot after my com32 program returns ... as in: DEFAULT foo LABEL foo KERNEL foo.c32 A...

I have been using PXELINUX, with "LOCALBOOT 0" when wanting to boot from disk, for many years. Now on new Dell Optiplex 990 machines, PXE boot with "LOCALBOOT 0" hangs after message Booting from local disk... without the expected "Exiting PXE" message. I tried "LOCALBOOT -1" and some other values also, none seemed to work. I tested SYSLINUX 4.04.

2013/8/5 H. Peter Anvin <hpa at zytor.com> > On 08/05/2013 07:04 AM, Jonas Keidel wrote: > > > > So i've also tried to use chain.c32, but there are also some problems. > > For example FreeBSD doesn't boot with chain.c32, so we've decided to use > > localboot, because it works in 90%, except with that board. > > Maybe you have an idea how to fix