similar to: Fixing the localboot 0x80 feature

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

That is perfectly true. I had a beautiful bug in the code .... Switching from python to C have some weird side-effect. Indenting is not enough, brackets are required.... So I pushed https://github.com/ErwanAliasr1/syslinux/commit/5a122d218553a6d4019273653ba9fad66d6ae79e with the fix. I tested it on my multi-disk system with success. I also changed the name of the function. 2016-07-17 8:21

The idea is to boot a disk in an mbr fashion while using the GPT (not filesystem) label to detect the disk. That is useful when you use grub2 & gpt. I was in case where my nodes (100s) have 8 disks each and no guarantee of which disk is "bootable" in the disk. This way I can tell "please boot the disk that have one partition labelled "xyz"". So nothing related

Hi folks, As per Ady request (thanks for the reminder), I forgot to send the patches I run in Mageia. There is two of them : One is making errors in parsing modules.alias not fatal. The other one is adding an option to chain to avoid reading garbage on the command line. I had some issues with gfxboot and had to implement that. I know it's a workaround, I don't really get if that's

> On 30.06.2016 19:41, Erwan Velu via Syslinux wrote: > > The exisiting label= option offer to boot on a gpt partition that have > > a particular label. > > The existing guuid= option offer to boot on a disk or partition with a > > particular label. > > > > This new option offer to boot the disk that have a partition which > > have a given label. >

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.

The exisiting label= option offer to boot on a gpt partition that have a particular label. The existing guuid= option offer to boot on a disk or partition with a particular label. This new option offer to boot the disk that have a partition which have a given label. The label is so just a way to detect a disk to boot. A typical use is for making an intelligent localboot like : label

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,

Gene Cumm wrote: > On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > <syslinux at zytor.com> wrote: > > Hi folks, > > > > As per Ady request (thanks for the reminder), I forgot to send the patches > > I run in Mageia. > > > > There is two of them : > > > > One is making errors in parsing modules.alias not fatal. > > >

https://github.com/ErwanAliasr1/syslinux/commit/6993cc151a67f68673bf58372870b301a3d1022a sorry. 2016-07-28 15:52 GMT+02:00 Erwan Velu <erwanaliasr1 at gmail.com>: > That is perfectly true. I had a beautiful bug in the code .... Switching > from python to C have some weird side-effect. Indenting is not enough, > brackets are required.... > > So I pushed >

The following is the current change-log for Syslinux 6.03. The final stable version might include additional items. Before the final release, it would be helpful to receive feedback about: _ Any item that should be added or eliminated. _ Any item that should be edited in any way (rewording, technical details...). _ Any item that should not be included. _ Any credit that should be added /

> > As opposed to "label", > "dlabel" ... > https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf > > SeaBIOS / GRUB2 > > ... > ... > <target dev='vdc' bus='virtio'/> > <boot order='3'/> > ... > ... > <target dev='vdd' bus='virtio'/>

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

Gene Cumm wrote: > On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gene Cumm wrote: > >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > >> <syslinux at zytor.com> wrote: > >> > Hi folks, > >> > > >> > As per Ady request (thanks for the reminder), I forgot to send the patches >

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

> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gene Cumm wrote: > >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > >> <syslinux at zytor.com> wrote: > >> > Hi folks, > >> > > >> > As per Ady request (thanks for the reminder), I forgot to send the patches > >> > I

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.

On Fri, Sep 04, 2015 at 09:15:07AM -0700, syslinux-bot for Erwan Velu wrote: > Commit-ID: 66105926f3d748de827eb863913171efb9624165 > Gitweb: http://www.syslinux.org/commit/66105926f3d748de827eb863913171efb9624165 > Author: Erwan Velu <erwanaliasr1 at gmail.com> > AuthorDate: Wed, 2 Sep 2015 18:26:37 +0200 > Committer: Erwan Velu <erwanaliasr1 at gmail.com> >