similar to: LOCALBOOT

Code doesn't just write itself... Jonas Keidel <jonas at jonas-keidel.de> wrote: >I like to reactivate this topic because i don't see any changes at the >last >time... >So what about the topic? > > >2013/8/9 Jonas Keidel <jonas at jonas-keidel.de> > >> 2013/8/7 Jonas Keidel <jonas at jonas-keidel.de> >> >>> >>>

On 08/05/2013 11:29 PM, Jonas Keidel wrote: > 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. > Actually this does

2013/8/7 Jonas Keidel <jonas at jonas-keidel.de> > > > 2013/8/6 H. Peter Anvin <hpa at zytor.com> > >> On 08/05/2013 11:29 PM, Jonas Keidel wrote: >> > 2013/8/6 H. Peter Anvin <hpa at zytor.com> >> > >> >> What about "chain.c32 hd1" or "chain.c32 hd1 swap"? >> >> >> > >> >

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. > > Did it work in previous versions? > As i have written, in every previous syslinux version it didn't work. > > Also in every previous

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

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

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.

I just tried to boot extlinux off of /dev/sdb and use the option localboot 0x80. I was hoping to see syslinux for the second time as the system loaded the master boot rec from /dev/sda. Why is this option only in pxelinux and isolinux? Nicholas A. Schembri State College PA USA

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, Ady thanks for your suggestions. >> What if you dropped the timeout to 0.8-2.0 seconds or even 0.2 seconds? I tried setting the delay to 2 seconds and 0.2 with no change in behavior. >> First, please be sure you are using all C32 modules from the exact same Syslinux version, including ldlinux.c32 and all lib*.c32 library modules, all located somewhere under the

Hi LocalBoot have unpredictable behaviour. I have tried 0, 0x80 and -1 on different machines. Some work good, some hang, some reset and some repoen the menu. I also uses chain.c32 but it had the same problem. I checked 3COM MBA menu mba.pxe and it works good on all machines. Is there any workaround? Behrad

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

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

Randy McAnally wrote: > > Thank you so much, this is the kind of news I needed! > > ---------- Original Message ----------- > From: "Arends, R.R." <r.r.arends at hro.nl> > To: "Randy McAnally" <rsm at fast-serv.com> > Cc: <gpxe at etherboot.org> > Sent: Wed, 03 Mar 2010 10:10:56 +0100 > Subject: Re: [gPXE] localboot 0 hang on some

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

Hello all, I'm booting a USB stick (DOS formatted, one 1GB partition) and I'd like to offer the choice of either continue booting from the USB stick, or booting from the installed hard disk (Linux ext3). I've asked this question here previously and Quinn replied saying I should use the 'localboot -1' option which would pass boot to the next device. And so I did. The BIOS

What about "chain.c32 hd1" or "chain.c32 hd1 swap"? Jonas Keidel <jonas at jonas-keidel.de> wrote: >2013/8/5 Jonas Keidel <jonas at jonas-keidel.de> > >> >> >> 2013/8/5 H. Peter Anvin <hpa at zytor.com> >> >>> On 08/05/2013 07:04 AM, Jonas Keidel wrote: >>> >>> > >>> > So i've also

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