search for: nvvars

Hi, Ady wrote: > * ISO images, > * burnt to _optical media_, > * and using then the resulting _optical media_ to boot in _UEFI mode_, > * in which the _main bootloader_ for such _optical media_ booting in > such _UEFI mode_ is part of The Syslinux Project. I would be willing to try such an ISO with qemu+OVMF. Regrettably my real test iron has no EFI firmware. Do you know the

...t; ??? f2.txt > ??? f3.txt > ??? f4.txt > ??? f5.txt > ??? f6.txt > ??? f7.txt > ??? f8.txt > ??? f9.txt > ??? g2ldr > ??? g2ldr.mbr > ??? gtk.cfg > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? setup.exe > ??? spkgtk.cfg > ??? splash.png > ??? stdmenu.cfg > ??? syslinux.cfg > ??? txt.cfg > ??? win32-loader.ini > > except that PATH into the bios files is a problem for efi, or i...

> > > > You should be able to see the effects of the DISPLAY directive when > > testing the floppy image I sent you, because it starts with the boot > > prompt, not with a menu. > > I see the effects, both good and bad. I'm having trouble knowing how > bad the bad is. How about comparing it with the current behaviour in BIOS mode? > I'm not

...blua.c32 ? ??? libmenu.c32 ? ??? libutil.c32 ? ??? linux.c32 ? ??? ls.c32 ? ??? menu.c32 ? ??? pwd.c32 ? ??? rosh.c32 ? ??? vesamenu.c32 ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? NvVars ??? SYSLX64.CFG > > > Regards, > > Ady. > > > > > > _______________________________________________ > > Syslinux mailing list > > Submissions to Syslinux at zytor.com > > Unsubscribe or set options at: > > http://www.zytor.com/mailman/l...

...butil.c32 ? ??? vesamenu.c32 ??? disk.lbl ??? exithelp.cfg ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ??? initrdg.gz ??? initrd.gz ??? ldlinux.c32 ??? ldlinux.sys ??? linux ??? menu.cfg ??? NvVars ??? prompt.cfg ??? rqgtk.cfg ??? rqspkgtk.cfg ??? rqtxt.cfg ??? setup.exe ??? spkgtk.cfg ??? splash.png ??? stdmenu.cfg ??? syslinux.cfg ??? txt.cfg ??? win32-loader.ini except that PATH into the bios files is a problem for efi, so I'm trying to move syslinux.cfg into target/boot/syslinux but...

...; ??? f6.txt > > ??? f7.txt > > ??? f8.txt > > ??? f9.txt > > ??? g2ldr > > ??? g2ldr.mbr > > ??? gtk.cfg > > ??? initrdg.gz > > ??? initrd.gz > > ??? ldlinux.c32 > > ??? ldlinux.sys > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > > ??? rqgtk.cfg > > ??? rqspkgtk.cfg > > ??? rqtxt.cfg > > ??? setup.exe > > ??? spkgtk.cfg > > ??? splash.png > > ??? stdmenu.cfg > > ??? syslinux.cfg > > ??? txt.cfg > > ??? win32-loader.ini > > > >...

...??? zzjson.c32 ??? exithelp.cfg ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ??? initrdg.gz ??? initrd.gz ??? ldlinux.c32 ??? ldlinux.sys ??? libcom32.c32 ??? libutil.c32 ??? linux ??? menu.cfg ??? NvVars ??? prompt.cfg ??? rqgtk.cfg ??? rqspkgtk.cfg ??? rqtxt.cfg ??? setup.exe ??? spkgtk.cfg ??? splash.png ??? stdmenu.cfg ??? syslinux.cfg ??? txt.cfg ??? vesamenu.c32 ??? win32-loader.ini carl at twist:/media/carl/Debian Inst$ cat syslinux.cfg # simple syslinux.cfg DEFAULT linux LABEL linux KERNEL...

...xt > ??? f5.txt > ??? f6.txt > ??? f7.txt > ??? f8.txt > ??? f9.txt > ??? g2ldr > ??? g2ldr.mbr > ??? gtk.cfg > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? libcom32.c32 > ??? libutil.c32 > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? setup.exe > ??? spkgtk.cfg > ??? splash.png > ??? stdmenu.cfg > ??? syslinux.cfg > ??? txt.cfg > ??? vesamenu.c32 > ??? win32-loader.ini > > carl at twist:/media/carl/Debian Inst$ ca...

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave

I want to eufi boot this image: http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz there is a bug against it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913523 I'd like to fix the resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids

On Fri, Dec 7, 2018 at 11:16 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > If this is the best we can do, I'm ok with that. > > It's _not_ the best we can do. The question is... what exactly is this > "we"? We have both made some contributions to my little goal. you certainly share in the credit. > > After some testing (which I

...t > > ??? f9.txt > > ??? g2ldr > > ??? g2ldr.mbr > > ??? gtk.cfg > > ??? initrdg.gz > > ??? initrd.gz > > ??? ldlinux.c32 > > ??? ldlinux.sys > > ??? libcom32.c32 > > ??? libutil.c32 > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > > ??? rqgtk.cfg > > ??? rqspkgtk.cfg > > ??? rqtxt.cfg > > ??? setup.exe > > ??? spkgtk.cfg > > ??? splash.png > > ??? stdmenu.cfg > > ??? syslinux.cfg > > ??? txt.cfg > > ??? vesamenu.c32 > > ??? win32-loa...