similar to: fixing debian's hd-media image

On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > Here are some comments and questions for you. > Thanks. I've have my scripts to a better state, including installing/using qemu to uefi and legacy boot the usb stick for testing. It mostly works for me, but the "wget a tarball of binaries" step isn't going to sit well with

On Sat, Nov 17, 2018 at 1:54 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > Here are some comments and questions for you. > > > > > > > Thanks. > > > > I've have my scripts to a better state, including

> On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > Here are some comments and questions for you. > > > > Thanks. > > I've have my scripts to a better state, including installing/using > qemu to uefi and legacy boot the usb stick for testing. > > It mostly works for me, but the "wget a tarball of

@Carl, I'll repeat what I said in my prior email: you don't have to keep looking, we already achieved what you want (considering that you are willing to "disregard" the screen problems and similar issues, at least for now, according to your own emails). In short: 1_ Re-read my email from 2018Dec05: www.syslinux.org/archives/2018-December/026247.html where I posted

Here are some comments and questions for you. > 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 I am going to assume that by "boot this image" you don't mean something like memdisk or equivalent, but rather that you want to transfer that image using "dd" to your

On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > First, I'm confused. In the prior "whole" setup (the one you generated > after my 15 steps, plus one workaround), was/is the basic boot menu at > least "working" when you used the workaround for the buggy PATH > directive when booting in UEFI mode? I mean: > >

> > > I think add some lines around here: > > > > > > https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/x86.cfg#L113-115 > > > > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 > > > ::vesamenu.c32; \ > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libcom32.c32 > >

On Fri, Dec 7, 2018 at 7:47 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > First, I'm confused. In the prior "whole" setup (the one you generated > > > after my 15 steps, plus one workaround), was/is the basic boot menu at

works with legacy, hangs with efi. where works is: No DEFAULT or UI configuration directive found! but enter and ^v make things happen hangs is: nothing happens, no response from keyboard, have to reboot. note: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

On Fri, Nov 30, 2018 at 9:56 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I have a proposal for you here (in the Syslinux mailing list): let's > first find out _what_ exactly is required in order to boot in UEFI > mode, and then you can take the info downstream. Whether "downstream" > means your own personal customized boot.img, or

On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > After some discussion/debugging behind the scenes, we are back on > track, with updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version

On Sun, Dec 2, 2018 at 12:32 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > When booting in UEFI x64 mode in your next test, you should see a boot > > > menu. > > > > Nope: > > > > *** Press enter to boot the default label *** > > Failed to load libcom32.c32 > > Failed to load COM32 file SYSLINUX/EFI64/vesamenu.c32 >

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

On Thu, Dec 13, 2018 at 10:57 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I'll repeat what I said in my prior email: you don't have to keep > looking, we already achieved what you want (considering that you are > willing to "disregard" the screen problems and similar issues, at least > for now, according to your own emails).

> > _ target/EFI/BOOT/SYSLINUX.CFG > > I don't think that exists? (see list below) In our "first test" (simple boot prompt), we created "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ "target/EFI/BOOT/SYSLINUX/EFI64/SYSLX64.CFG". Part of my intention was to test whether it actually reaches one cfg or the other.

On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > works with legacy, hangs with efi. > > > > where works is: > > No DEFAULT or UI configuration directive found! > > but enter and ^v make things happen > > > > hangs is: nothing happens, no response from keyboard, have to reboot. > > > > note:

On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote: >> Under EFI/BOOT are the following files: >> BOOTIA32.EFI (from efi32/efi/syslinux.efi) >> BOOTX64.EFI (from efi64/efi/syslinux.efi) >> ldlinux.sys (copied from root of partition) >> lua.c32 >>

> Hello everyone, > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > Since I have to use ZENworks tftp on the windows server I have only one TFTP-root directory not 2 different tftp-root directories like on a standard windows > deployment server. ZENworks itself uses for